Pinning failed

[agmap]

CID is pinned and getting status "pinning failed" Add retry for uploaded CID with status “Pinning failed”. I can check the pinning status here: https://delegated-ipfs.dev/routing/v1/providers/bafybeifkrphyxq65xaguiiqqgow7ogcxb4ci3p7akxojqfh3qrzhai633m

[elizabeth-griffiths]

Hi there, Can you please explain this issue with more detail? I don't quite follow. Thanks!

[agmap]

I have uploaded some CIDs, and for some the message “pinning failed” appears. But when I check it, it is pinned and can be opened within the ipfs network.

[elizabeth-griffiths]

Got it. Here's an update on this: Pinning Status - The pinning status indicates a backend process where we download the CID and temporarily pin it to our local node before sending it to the Filecoin storage provider. Pinning may fail for two reasons: We couldn't download the CID from any node. This might happen if the node is offline or goes offline before the full file is downloaded. There isn't enough data cap to store new CIDs, requiring additional storage purchases. For the first issue, if we cannot download the CID, we retry every 2 hours, up to 30 retries. To resolve this issue, we will retry all Pinning Failed cases. Please ensure the following: A. If you host the data on your own node, ensure it is available. B. Pin the data to a more popular hot storage pinning provider like Lighthouse or Pinata, where the download is reliable and fast.

We are also working on making this process clearer and providing users with a way to retry pinning themselves.

[agmap]

Lighthouse having the same issues with migrating the some CIDs. But when I check with ipfs-desktop, kubo node, helia node, https://delegated-ipfs.dev/routing/v1/providers/<CID>... or https://cid.contact/cid/<CID> I can contact and load the CID.

[elizabeth-griffiths]

"Lighthouse having the same issues with migrating the some CIDs." --> What do you mean? They are not able to download the CIDs? I can put you in touch with the Lighthouse team directly, if that would help?

We are also going to retry all failed pins on our side. I'll let you know when this is done.

[agmap]

I'm so grateful for all your wonderful support. It means a lot! Lighthouse also have problems migrating my CIDs. I'm in touch with them. I don't have a local copy of the data. It must be fetched directly from native IPFS nodes or gateways. This is very hard, and I'm glad you're helping. You can check whether pinning is still available here. https://delegated-ipfs.dev/routing/v1/providers/<CID> Some CIDs are too big to preserve. (Mainly if it is a CID directory and it's above my desired limit)

Thank you so much! I'm really happy to say that most of my NFTs and many third-party NFTs are now backed up long term by nft.storage and lighthouse.storage. I really appreciate it! It's so nice to feel safe with my NFTs.

[elizabeth-griffiths]

Hi agmap - We've retried all pins. Please check your status. If there are still failed pins, the most likely cause is that you need to buy more storage. I'm going to close this, but feel free to re-open if needed.

[agmap]

I can't re-open the issue. Hope you can still read. Thank you very much. 😊 Yes, most of the CIDs should be imported. 👍 What happens to the other non-imported CIDs, which may be too large or no longer have pinning or are double uploads? Many CIDs in my account are still "in quene". Can these be cancelled automatically? It would also be nice if there was a cancel button that could be used in the "in quene" status.

[agmap]

The import still fails when the CIDs are provided by "graphsync-filecoinv1" https://specs.ipfs.tech/routing/http-routing-v1/#graphsync-schema

Example: QmbxUjT4F9UeUyMcN1ZFUQte4d8q4zjPnEBXaQSTtXuMGL https://delegated-ipfs.dev/routing/v1/providers/QmbxUjT4F9UeUyMcN1ZFUQte4d8q4zjPnEBXaQSTtXuMGL

There are providers: