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

IPFS does not work after upgrade #5499

Closed
timthelion opened this issue Sep 20, 2018 · 2 comments
Closed

IPFS does not work after upgrade #5499

timthelion opened this issue Sep 20, 2018 · 2 comments

Comments

@timthelion
Copy link
Contributor

Version information:

> ipfs version --all
go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/linux
Golang version: go1.10.3

Type: Bug

Description:

After upgrading to the latest version of IPFS, it does not work. If I go to any ifps or ipns link in the browser I see: Cannot GET /ipns/Qme48wyZ7LaF9gC5693DZyJBtehgaFhaKycESroemD5fNX/post/putting_this_blog_on_ipfs/.

Note: the hash changes based on the content ;)

Note 2: I did not test immediately before the upgrade. I test IPFS every now and then to see if it has gotten fast enough to be usable and I upgrade immediately every time I try it out again. This time there was some kind of repo migration done.

@rob-deutsch
Copy link
Contributor

Hey, could you jump over to the command line and try:

ipfs get /ipns/Qme48wyZ7LaF9gC5693DZyJBtehgaFhaKycESroemD5fNX/post/putting_this_blog_on_ipfs/

This ought to give more information about what's gone wrong.

@timthelion
Copy link
Contributor Author

That works, which lead me to realize what the problem is, and it's not a bug in ipfs-go at all, but rather ipfs-companion in chromium. The companion is redirecting me to the port 8080 (where node.js runs), when my ipfs gateway is on port 9001.

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