IPFS UI + HTTPs API are always pointing to port 80

Version information: 0.4.13

Type: Bug

Severity: Medium

Description:

When I am exposing the API behind a reverse proxy via HTTPS (nginx), the API call coming from the /webui interface are all failing as they are trying to get to port :80. In the logs of the browser it looks like this:

GET https://ipfs-api.myawesomewebsite:80/api...

What should I do to allow the UI to talk to the HTTPS correctly? If I am disabling HTTPS it works perfectly.

To reproduce you can spin up a container, set up nginx to point :443 to :5001. Even with a fake certificate you will see the problem by browsing to https://localhost/webui.

(clones https://github.com/ipfs/go-ipfs/issues/4488 as this probably is the right place to submit the issue)

[olizilla]

👋 v2 of the Web UI is out, which is a significant re-write. It’ll be released with v0.4.18 of go-ipfs. You can also try out a recent build at https://webui.ipfs.io

In general, the Web UI expects accessed via 127.0.0.1, on the same port as the API. There is currently no access control or authentication for the http API, so it is not advised that you proxy access to it to the public internet. See https://github.com/ipfs-shipyard/ipfs-webui/issues/836

[danc86]

I tried master (commit 3d8aa07) built as QmULQD1iBBkxWkzb7nsyxpLqivjdfp4D1w2ctC8wRz8jJD. It’s definitely different, but not fixed 😃

It seems to have the opposite problem now. I see Firefox blocking the AJAX requests like this:

Blocked loading mixed active content “http://ipfs.djc.id.au:443/api/v0/id?stream-channels=true”

Note port 443 but scheme http.