[BUG] Unable to connect to WebUI

[mayurrenr]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When using the default 8080 port to access WebUI, firefox gives me "Unable to connect" error, edge gives "refused to connect' error.

If I remove qb and start another container for a different app using port 8080, this works fine (eg. stirling-pdf).

My setup currently is docker installed on debian 12 VM with only the qbittorrent container running via docker compose:

services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - ./qbittorrent_data/config:/config
      - /data/mystorage/private/torrents:/downloads
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped
    networks:
      - dockernet

networks:
  dockernet:
    name: dockernet
    external: true

Additionally, I have added the following lines to the qbittorrent.conf file located in the config folder:

WebUI\CSRFProtection=false
WebUI\HostHeaderValidation=false

Finally, I have deleted the entire VM and reconfigured a new one, from scratch, and still unable to connect to WebUI. Other apps have all worked fine (NPM, cloudflared, portainer, stirling-pdf). Please note, all of these have now been removed in favour of troubleshooting qbittorrent.

Firewall/ufw disabled.
Ipv6 disabled.

Expected Behavior

WebUI should load on server-local-ip:8080

Steps To Reproduce

1. ESXi hypervisor
2. Debian 12
3. Docker via standard CLI instructions on official website
4. Qb as per above docker compose file

Environment

- OS: Debian 12
- How docker service was installed: CLI as per official guide

CPU architecture

x86-64

Docker creation

services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - ./qbittorrent_data/config:/config
      - /data/mystorage/private/torrents:/downloads
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped
    networks:
      - dockernet

networks:
  dockernet:
    name: dockernet
    external: true

Container logs

To control qBittorrent, access the WebUI at: http://localhost:8080

The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: XA83mHutz
You should set your own password in program preferences.
Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[mayurrenr]

Update: I ran the same compose using tag '4.6.0' and it worked without any issue whatsoever. Could this be a problem with the 'latest' version?

[mayurrenr]

Update2: Tags '4.6.1' and '4.6.2' work fine too.
'4.6.3' and above give the same error as described in my OP.

[thespad]

I can't replicate this, latest starts up and is reachable as expected:

[Otts86]

I'm having the same issue with latest build

[Punk7050]

Actually, please disregard, I totally misunderstood the post.

[j0nnymoe]

"8282:8080/tcp" is wrong as explained in the readme.

[Punk7050]

"8282:8080/tcp" is wrong as explained in the readme.

EDIT: You are correct @j0nnymoe GUI not even loading is an issue with the ports. I misunderstood the OP.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[drod3763]

I'm having the same issue.

[rasmusbe]

Same for me, 4.6.2 works, but every version after that crashes and restarts the webui over and over again

[thespad]

OK, I'm going to close this now because OP never responded and everyone else is just "me too"ing without providing even the most basic of information necessary to try and troubleshoot any potential issue.

If people are having problems please either open a new issue with a correctly-filled issue template, or seek support in our Discord or Discourse servers.