This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
IPNS Resolves only CLI, not Gateway #3793
Comments
@johnnyshankman please reinstall (update to the latest patch of js-ipfs) – it should include relevant IPNS fix, then you need to republish IPNS record using the latest version. lmk if this helped. |
Doesn't seem to be working still, latest patch |
lidel
added
need/analysis
Needs further analysis before proceeding
and removed
need/author-input
Needs input from the original author
labels
Sep 10, 2021
Ok, it seems the problem you are experiencing is caused by the lack of full DHT support in js-ipfs (see #3722). tldr blocked by #3722 ← lets continue there |
lidel
removed
need/analysis
Needs further analysis before proceeding
need/triage
Needs initial labeling and prioritization
labels
Sep 10, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version:
0.56.1
Platform:
OSX Mojave
Subsystem:
Severity:
Medium
Description:
I cannot get IPNS content that resolves locally in the CLI to resolve on the gateway even after waiting 24hrs for propagation.
I added and pinned content to IPFS successfully.
I then used
name publish
to reference that content via IPNS.The IPFS Gateway resolves original IPFS pinned content
https://ipfs.io/ipfs/QmbatBaJZCpEDoDx8CrFSM4NVaH9MnbbGL58JonoJaNnCu
CLI resolves the IPNS reference:
but Gateways refuse to resolve:
https://ipfs.io/ipns/QmfSPG1QgJM9oEHsLvH1rZ4qH7WESGjiq1p5TZuXdg6b4f
https://gateway.ipfs.io/ipns/QmfSPG1QgJM9oEHsLvH1rZ4qH7WESGjiq1p5TZuXdg6b4f
It loads for a few minutes then eventually times out and says:
Which is the exact command that resolves for me using the CLI.
Daemon is running the whole time, I have 5 peers.
Also not sure how I'm supposed to access file using 127.0.0.1 webui
Steps to reproduce the error:
The text was updated successfully, but these errors were encountered: