IPFS returning: "Error: not a valid proquint string" when doing "ipfs name resolve /ipfs/hash"

[obo20]

Throwing this bug report up at request of @Stebalien.

The error message here is a bug and should be fixed.

[raarts]

Using ipfs from Brave, and I get this error all the time. Googling got me here, but it was the only hit... now what?

[Stebalien]

I assumed you tried to visit ipns://something? You'll get that error if something doesn't parse as a domain with a known TLD, nor valid IPNS key. If you don't mind saying, what URL did you visit?

Also note:

1. Proquint support will be gone from go-ipfs 0.9.0 so this issue (the bad error message) will effectively be fixed.
2. We're loosening the restrictions on what counts as a valid domain (no longer checking a TLD list) (again, in the next release).

Release tracking issue: #8058

[raarts]

It's my first dive into ipfs. On my linux machine I did:

root@pve:~# ipfs add -r spaceship-launch.jpg
added QmSgvgwxZGaBLqkGyWemEDqikCqU52XxsYLKtdy3vGZ8uq spaceship-launch.jpg
 269.90 KiB / 269.90 KiB [====================================================================================================================================] 100.00%

Next in my browser I went to https://ipfs.io/ipfs/QmSgvgwxZGaBLqkGyWemEDqikCqU52XxsYLKtdy3vGZ8uq and I ended up with the above error.

Apparently I was too eager, because it's working now. Anyway, it was a nonsensical error for me as a user.

I tried again with a different file, and then Brave hung forever in 'Waiting for ipfs.io'. But that's probably not something I should bug you with.

Thanks for responding!

(Brave still has usability issues though, like suggesting to open an ipfs addressed resource using ipfs:)

[Stebalien]

🤷‍♂️ Well, I'm glad it's working now. Unfortunately, I can't help you with the brave issue.

[ThomasFreedman]

I ran into this error on one of my servers. I published a website on another IPFS node and when I tried to pin it on another got this error. Both servers involved are running the same 0.8.0-rc2 version. I will be updating them this weekend.

I've always been puzzled by the CIDs returned on one of my nodes, it doesn't conform to the Qm... 42 character CID format I see everywhere else. The ipns "published to" keys from that node start with k and are very long, and the peerID starts with 12. I'm getting the error on the node with the typical Qm CID structure, but the key it's trying to resolve that produces the error is: /ipns/k51qzi5uqu5dmdr312hi2slkfhc2e4dxbm55inrhdqkr0z8ly51evcyrj8tr1k

[Winterhuman]

Checking with https://cid.ipfs.io/#k51qzi5uqu5dmdr312hi2slkfhc2e4dxbm55inrhdqkr0z8ly51evcyrj8tr1k shows that it is a valid IPNS address. Also, it's completely normal that IPNS keys start k51... and PeerIDs 12D3KooW....

EDIT: Proquint support was removed in go-ipfs v0.9.0 (https://github.com/ipfs/go-ipfs/releases/tag/v0.9.0), updating to the latest version should fix your error.

[aschmahmann]

As @Winterhuman correctly mentioned Proquint support has been removed for a while and your error is likely due to you entering an invalid key (e.g. commonly something like a copy-paste error).

Closing this issue since "Error: not a valid proquint string" is no longer in the codebase 😄.