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

WebUI unable to browse file contents of remote IPFS node #5821

Closed
MidnightLightning opened this issue Dec 5, 2018 · 1 comment
Closed

WebUI unable to browse file contents of remote IPFS node #5821

MidnightLightning opened this issue Dec 5, 2018 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws) not our bug

Comments

@MidnightLightning
Copy link

Version information:

v0.4.18

Type:

Bug

Description:

When connecting to the WebUI of an IPFS node that's not running on localhost, when connecting you can set up the path to the IPFS node from your workstation with a configuration string like /ip4/192.168.0.101/tcp/5001. That allows the WebUI to show the "Files" directory listings appropriately, but if you navigate to a particular file and then click to view it, it does not work.

It seems the WebUI, after connecting to the "API" port (5001 typically) of the node, it looks up the node's own config file to find the configured "Gateway" port (8080 typically) of the node. However, when viewing a remote node, that doesn't work. The remote IPFS node may have something like /ip4/0.0.0.0/tcp/8080 (bind to all IPs it has, on port 8080), which then causes the WebUI to try and connect to http://0.0.0.0:8080/.., which is not the proper URL (should be http://192.168.0.101:8080, combining the IP address from the "API" configuration, and the port from the "Gateway").

@Stebalien Stebalien added kind/bug A bug in existing code (including security flaws) not our bug labels Dec 5, 2018
@Stebalien
Copy link
Member

This looks like: ipfs/ipfs-webui#836. Closing as this is a bug in the webui.

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) not our bug
Projects
None yet
Development

No branches or pull requests

2 participants