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 Path Resolve error: could not resolve name at gateway #2131

Closed
jbshirk opened this issue Dec 28, 2015 · 2 comments
Closed

IPNS Path Resolve error: could not resolve name at gateway #2131

jbshirk opened this issue Dec 28, 2015 · 2 comments

Comments

@jbshirk
Copy link

jbshirk commented Dec 28, 2015

From command prompt I see that I added an object, pinned it, published it, and the name resolves:
localhost:ipfs joe$ ipfs add tw5.htm
added QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD tw5.htm
localhost:ipfs joe$ ipfs pin add QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD
pinned QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD recursively
localhost:ipfs joe$ ipfs name publish QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD
Published to Qme67efGcE9iX6r8Wk6CrHUsmWckLbnMHQ19g5YK15doUY: QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD
localhost:ipfs joe$ ipfs object stat QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD
NumLinks: 13
BlockSize: 633
LinksSize: 574
DataSize: 59
CumulativeSize: 3306059

localhost:ipfs joe$ ipfs name resolve Qme67efGcE9iX6r8Wk6CrHUsmWckLbnMHQ19g5YK15doUY

/ipfs/QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD

in the browser the name resolves and the object loads on localhost
http://127.0.0.1:8080/ipns/Qme67efGcE9iX6r8Wk6CrHUsmWckLbnMHQ19g5YK15doUY

at the gateway the object loads:
https://gateway.ipfs.io/ipfs/QmVmTrmgWHz7RsaG9hQRwWyF4iESW1GS38rKs69EgMuTrD

but the name does not resolve:

https://gateway.ipfs.io/ipns/Qme67efGcE9iX6r8Wk6CrHUsmWckLbnMHQ19g5YK15doUY/
Path Resolve error: could not resolve name.

https://gateway.ipfs.io/ipns/Qme67efGcE9iX6r8Wk6CrHUsmWckLbnMHQ19g5YK15doUY/tw5.htm
Path Resolve error: could not resolve name.

Am I doing something wrong?

@Kubuxu
Copy link
Member

Kubuxu commented Dec 28, 2015

Link you gave is working now.

@jbshirk
Copy link
Author

jbshirk commented Dec 29, 2015

@Kubuxu ok, good. Thanks. I guess it's just slow propagation.

@jbshirk jbshirk closed this as completed Dec 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants