Skip to content
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

IPNS does not always resolve #2269

Open
chrisschaub opened this issue May 16, 2023 · 0 comments
Open

IPNS does not always resolve #2269

chrisschaub opened this issue May 16, 2023 · 0 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@chrisschaub
Copy link

chrisschaub commented May 16, 2023

I am using the javascript client, uploading ipfs / creating ipns. Sometimes, when I create ipns names, they never resolve.

https://k51qzi5uqu5djbfo0481ijxwpidu38edf3b5you07y2ukc50wx6qgh8i8sgk5i.ipns.w3s.link/
https://k51qzi5uqu5djbfo0481ijxwpidu38edf3b5you07y2ukc50wx6qgh8i8sgk5i.ipns.dweblink/

Is there anything that prevents ipns from working if I have multiple ipns keys pointing to same ipfs CID? The ipns did not error when creating and making the new revision. When I goto https://web3.storage/docs/reference/w3name-http-api/ I can see these names do not resolve, almost as if the "publish" step did not work, but it did not throw an error? Is there some way to tell if publish works?

We have a paid account. Thanks.

@chrisschaub chrisschaub added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant