Could not connect to the IPFS API from WebUI at http://0.0.0.0:5001/webui

[gillbates]

Checklist

• This is a bug report, not a question. Ask questions on discuss.ipfs.tech.
• I have searched on the issue tracker for my bug.
• I am running the latest kubo version or have an issue updating.

Installation method

built from source

Version

No response

Config

No response

Description

using the original docker-compose.yml to start. it shows

do we need some other init process for this compose?

[lidel]

@gillbates i was not able to reproduce

$ > docker compose up
Attaching to kubo-ipfs-1
kubo-ipfs-1  | Changing user to ipfs
kubo-ipfs-1  | ipfs version 0.31.0-dev
kubo-ipfs-1  | generating ED25519 keypair...
kubo-ipfs-1  | done
kubo-ipfs-1  | peer identity: 12D3KooWFiiVnrcncbCmiVMbsrMyYG4CHPH75gUopvmMdnuSY7KJ
kubo-ipfs-1  | initializing IPFS node at /data/ipfs
kubo-ipfs-1  | Initializing daemon...
kubo-ipfs-1  | Kubo version: 0.31.0-dev-4236207
kubo-ipfs-1  | Repo version: 16
kubo-ipfs-1  | System version: amd64/linux
kubo-ipfs-1  | Golang version: go1.22.7
kubo-ipfs-1  | PeerID: 12D3KooWFiiVnrcncbCmiVMbsrMyYG4CHPH75gUopvmMdnuSY7KJ
kubo-ipfs-1  | Swarm listening on 127.0.0.1:4001 (TCP+UDP)
kubo-ipfs-1  | Swarm listening on [::1]:4001 (TCP+UDP)
kubo-ipfs-1  | Run 'ipfs id' to inspect announced and discovered multiaddrs of this node.
kubo-ipfs-1  | RPC API server listening on /ip4/0.0.0.0/tcp/5001
kubo-ipfs-1  | WebUI: http://0.0.0.0:5001/webui
kubo-ipfs-1  | Gateway server listening on /ip4/0.0.0.0/tcp/8080
kubo-ipfs-1  | Daemon is ready

Accessing WebUI via http://127.0.0.1:5001/webui works just fine:

I guess your setup looks different?
Do you mind providing reproduction steps of your problem?

[gillbates]

@gillbates i was not able to reproduce

$ > docker compose up
Attaching to kubo-ipfs-1
kubo-ipfs-1  | Changing user to ipfs
kubo-ipfs-1  | ipfs version 0.31.0-dev
kubo-ipfs-1  | generating ED25519 keypair...
kubo-ipfs-1  | done
kubo-ipfs-1  | peer identity: 12D3KooWFiiVnrcncbCmiVMbsrMyYG4CHPH75gUopvmMdnuSY7KJ
kubo-ipfs-1  | initializing IPFS node at /data/ipfs
kubo-ipfs-1  | Initializing daemon...
kubo-ipfs-1  | Kubo version: 0.31.0-dev-4236207
kubo-ipfs-1  | Repo version: 16
kubo-ipfs-1  | System version: amd64/linux
kubo-ipfs-1  | Golang version: go1.22.7
kubo-ipfs-1  | PeerID: 12D3KooWFiiVnrcncbCmiVMbsrMyYG4CHPH75gUopvmMdnuSY7KJ
kubo-ipfs-1  | Swarm listening on 127.0.0.1:4001 (TCP+UDP)
kubo-ipfs-1  | Swarm listening on [::1]:4001 (TCP+UDP)
kubo-ipfs-1  | Run 'ipfs id' to inspect announced and discovered multiaddrs of this node.
kubo-ipfs-1  | RPC API server listening on /ip4/0.0.0.0/tcp/5001
kubo-ipfs-1  | WebUI: http://0.0.0.0:5001/webui
kubo-ipfs-1  | Gateway server listening on /ip4/0.0.0.0/tcp/8080
kubo-ipfs-1  | Daemon is ready

Accessing WebUI via http://127.0.0.1:5001/webui works just fine:

I guess your setup looks different? Do you mind providing reproduction steps of your problem?

haha, I found the issue.
it works with the url: http://127.0.0.1:5001/
but it doesnot work with url: http://0.0.0.0:5001/

however the docker logs shows we should access the ipfs using http://0.0.0.0:5001/
maybe we should adjust some params in docker-compose? @lidel

[lidel]

Ah, makes sense.

This is a cosmetic issue with text printed on daemon start.

Docker image config has all listeners, including Addresses.API set to catch-all 0.0.0.0 (here, /ip4/0.0.0.0/tcp/5001), and the WebUI URL should be normalized to useful local URL. In the past, browsers interpreted 0.0.0.0 as loopback and things "just worked", but now things break due to https being default, and also origin isolation finally doing the right thing.

Fixed in #10520, thank you for reporting this papercut.