web3.storage
web3.storage copied to clipboard
web3-storage
Pin request never goes through
When running the command: ipfs pin remote add --service=web3.storage ... it always just sits for a long time until it finally just times out and gives an error message (Error: failed to check pin status for requestid="659565b2-7314-4df0-ab66-de247e9cd8b3" due to error: empty response from remote pinning service: .....)
I've tried with CIDs that are fully accessible on IPFS and ones that are very small size wise. Doesn't seem to have to do with that.
Unsure as to why they won't pin on web3.storage.
Unfortunately, issues like this with the pinning API are difficult to debug. If the files are accessible on IPFS generally, my guess is that the pinning infra we are currently using is under heavy load, causing some issues.
We are making some changes this week / next week that will make the pinning API much more scalable. Can you try again then? Really sorry for the inconvenience.
No worries. I'll check back next week and hopefully they all go through.
Thanks!
August Rosedale Founder, Mirage Gallery https://miragegallery.ai https://linkedin.com/in/augustrosedale [image: https://twitter.com/augustfr] https://twitter.com/augustfr
On Sun, Sep 18, 2022 at 3:49 PM David Choi @.***> wrote:
Unfortunately, issues like this with the pinning API are difficult to debug. If the files are accessible on IPFS generally, my guess is that the pinning infra we are currently using is under heavy load, causing some issues.
We are making some changes this week / next week that will make the pinning API much more scalable. Can you try again then? Really sorry for the inconvenience.
— Reply to this email directly, view it on GitHub https://github.com/web3-storage/web3.storage/issues/1897#issuecomment-1250403591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJCRSPR4FIIPMNUMVD7GP3V66MAZANCNFSM6AAAAAAQNUEJYY . You are receiving this because you authored the thread.Message ID: @.***>
Ah, sorry to hear that. Do you mind sharing a few of the CIDs you're trying to pin?
cc @olizilla @mbommerez in case someone is able to help debug!
QmYZnRPPT2eYciobzPhTAymiLXgY1ZToLNJGe9vwhPCT4w and QmdszZwD9bJqCi3asNYoEWEGS7PECBs65FDvReZkaHDpuA
Thanks! I'm able to fetch them too.
Sorry for the inconvenience here. One thing you can do to work around this is get a CAR export of your data (using something like Kubo / go-ipfs https://web3.storage/docs/how-tos/work-with-car-files/#go-ipfs) and then uploading it using the web3.storage CLI. This will ensure that the data is referenced using the same CID!
But in the meantime we'll continue debugging the Pinning API - it's a tricky one to debug since there's so many moving pieces!