V 2025 does not listen on localhost anymore

[ghost]

Hi,
I am running docker image of Seq. When I was setting up my environment cca a year ago, my docker compose pulled the 2024.3 version.
Recently I had to celanup my images, and since my docker compose file has datalust/seq:latest tag it pulled the 2025.2 version.
Now I cannot access the UI via the http://localhost:5341 and I must use http://127.0.0.1:5341 now.

I tried to add a env vairable SEQ_API_LISTENURIS: "http://0.0.0.0:80,http://0.0.0.0:5341,https://0.0.0.0:443,https://0.0.0.0:45341". The setting was applied on the container start, but it still didn't listen to localhost. I also tried to add [::1] instead of 0.0.0.0 in the listen URI

If I pull again the 2024.3 version, the localhost is resolved correctly without changing hosts file or anything?

[nblumhardt]

Hi @gregor-tusar-sowa,

Do you have any logs from the container? When you try to start it under the v2025.2 image, you should get some regular diagnostics via stdout (docker logs). HTH!

[ghost]

Yes, I got this, all looks good. When I access it via IP I also get a bunch of INF logs about the requests made to the server.

I suspect there might be something with resolving localhost to IPv6 address - [::1] ?

But I don't know why there would be difference between SEQ versions.

[mloskot]

As a curious Seq user, I've checked that on my Ubuntu 25.04 machine with Docker Engine 28.4.0, and access via http://localhost works for me:

docker run -d --name seq -d \
  -e ACCEPT_EULA=Y \
  -p 5341:5341 \
  -p 8080:80 \
  -v "$(pwd)/data":/data \
  docker.io/datalust/seq:latest

[ghost]

It is Docker on Windows 11.

[nblumhardt]

Hi @gregor-tusar-sowa; I can't find much related to localhost being blocked, but 127.0.0.1 still being accessible on Windows, but digging around in Windows Firewall might be worthwhile.

Otherwise, Compose is a possible factor - it would be good to know if, after restarting your machine, the plain docker run command shown in Mateusz's response above leads to the container being successfully exposed. HTH!

[mloskot]

FYI, I've just run my test on Windows using the latest Docker Desktop v4.46.0 and I can access Seq via localhost without any problems

I suspect the issue in @gregor-tusar-sowa environment is due to Windows Firewall or some WSL misconfiguration.

[ghost]

Then I think there is something wrong with my configuration.

Thanks for having a look.