I am using the golang version of ipfs installed with ipfs-update. Go version 1.12.7, ipfs version 0.4.22-, repo version 7.
By “not working” I mean the browser just hangs indefinitely waiting for a response that never comes (I’m using Raspbian’s default Chromium browser).
I first setup and test the installed code with the node configured as a normal public IPFS daemon. http://127.0.0.1:5001/webui works as expected out of the box, so whatever version of the webui that gets installed with ipfs tests good.
There are a few more details in the article that includes ipfs-cluster related to the Addresses section of config file, saying the API and Gateway IPv4 addresses should be changed from localhost to the system’s IP address. I see no info in config related to webui, but as a test I switched the API and gateway IPs back to localhost but the daemon start log still shows API and WebUI uses the same port.
I log the daemon start output, which says the API and webui ports are the same (5001)! That is true whether started as a public or private node.
I must assume that’s correct, since http://localhost:5001/webui works in public mode even tho that is the same ip/port as API in config/addresses.
Although very basic, I would like to use the webui to add files or folders, and it doesn’t work in a private IPFS network configuration.
I looked in the ipfs-shipyard/webui on github, but thought I should ask here before I write this up as an issue.
Any suggestions related to this would be greatly appreciated!