qbittorrent not downloading

[danielo515]

Hello.
I have an instance of qbittorrent running in a docker container inside my qnap nas, but it is not downloading anything.
I don't see any error logs, permissions are correct (I can see other files in the downloads folder from the web-ui) and this was previously working, but suddenly it has stopped working.
I thought it could be some issue with network firewalls or something, but using another device in the same network (desktop client) I can download without a problem from the same torrent files.
I don't know what else to check.

For reference, here is the compose part of the torrent client:

    container_name: "qbittorrent"
    volumes:
      - ${USERDIR}/qbittorrent:/config
      - ${MEDIADIR}/Downloads:/media/downloads
    ports:
      - "6881:6881"
      - "6881:6881/udp"
    restart: always
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - UMASK_SET=002
    networks:
      - traefik_proxy

[drizuid]

I would suggest coming on discord for live support but i can tell you there is no issue with the container (thousands of people use it without issue)
unfortunately, you've not provided any errors that occur so this is just guess work for us.

[danielo515]

Any idea where I can get any logs? As I said, I get no errors and no issues. This is all what I see in the docker logs:

[migrations] started
[migrations] no migrations found
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 5.1.2-r3-ls422
Build-date: 2025-10-26T06:58:02+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
WebUI will be started shortly after internal preparations. Please wait...
******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080
The WebUI administrator username is: myuser
The WebUI administrator password was not set. A temporary password is provided for this session: aN8GZdFZT
You should set your own password in program preferences.
Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!
[ls.io-init] done.

[drizuid]

qbittorrent has their own logs, likely somewhere in /config (i dont use qbit)
but suddenly it has stopped working. what does stopped working mean exactly?
what is the output of uname -mr && docker version
are you using anything unsupported, like portainer?

[danielo515]

I am indeed using portainer, not sure why it is unsupported.
That said, this particular stack was deployed a long time ago using just docker-compose.
It seems the container has some issues with name resolution:

[drizuid]

I am indeed using portainer, not sure why it is unsupported.

because we don't support deploying our images with it. it causes numerous issues for non-experts. https://docs.linuxserver.io/misc/support-policy/#unsupported
it tells you why it's not working, either bt1.archive.org:6969 is down or you have a dns issue

docker exec -it qbittorrent ping bt1.archive.org see if that works

[danielo515]

That command indeed didn't work. I tried a dnslookup and same issue:

docker exec -it qbittorrent nslookup bt1.archive.org
Server:         127.0.0.11
Address:        127.0.0.11:53

;; connection timed out; no servers could be reached

[drizuid]

try with something you know works like google.com if google.com also fails you have a dns issue, if it works, bt1.archive.org is the issue

[danielo515]

Ok, found the issue.
The container was only in the traefik_proxy network, and it didn't had access to the normal DNS and other stuff. I made it join the bridge network, restarted the container and now it is able to reach the servers.
I expected that having the ports published was enough for the client to be reachable from the outside, but it seems I was wrong.

[danielo515]

Thank you very much for your assistance

[drizuid]

no problem, glad you got it sorted! please remember to close this out if you're all set