-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I cannot find in IPFS gateway / online (using CID) the content I uploaded through Helia #138
Comments
I also tried to use |
2023-06-07 maintainer conversation:
|
Getting the same issue on my end, even with basic strings! Tried multiple IPFS explorers, none of them seem to index the uploaded data. |
@Eikix @maxdesalle @zveroboy @AlexCherrypi This is related to #159, ipfs-examples/helia-examples#43, ipfs-examples/helia-examples#38, and the discuss.ipfs.tech post located at https://discuss.ipfs.tech/t/how-to-retrieve-content-uploaded-via-helia-using-the-ipfs-gateway/16582. I answered at https://discuss.ipfs.tech/t/how-to-retrieve-content-uploaded-via-helia-using-the-ipfs-gateway/16582/4?u=sgtpooki, but let's continue there as this is not a Helia bug and more of a learning opportunity.
This is how IPFS works. Please go through https://proto.school/anatomy-of-a-cid/ if you haven't yet and it should explain why using a different codec changes what the final CID is. If you're running a non-browser node, the support provided by @achingbrain in ipfs-examples/helia-examples#43 may also be of assistance to you.
For an issue tracking the creation of an example where we host content on a Helia node and access that content from an IPFS gateway, please follow ipfs-examples/helia-examples#39 |
Hi all, my name's Elias,
I'm new to Helia, very cool project.
I'm currently writing a nodeJS script to add JSON files to IPFS using Helia:
The script successfully adds creates the CIDs in my
addedCIDs.json
file:But when I look them up on IPFS, I cannot seem to find them.
Is the problem linked with pinning? Or something I missed?
The text was updated successfully, but these errors were encountered: