What's wrong?
I was told to open a new issue since I mentioned things in #281. There seems to be a lot of overlap between that issue and this one. I and other users (qdm12/gluetun#3260) keep getting a qbittorrent crash when making API calls via wget.
Docker compose up starts qbit and gluetun container at same time; gluetun gets wireguard info and tries to set IP + Port in qbit via wget API call.
I've tried qbittorrent:test qbittorrent:latest qbittorrent:releasev5 and they all had this issue.
Currently I'm using qbittorrent:release-9673f7a which works fine. In qdm12/gluetun#3260 users reported switching to lscr.io images also works fine.
Compose File:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- ${CONFIG_FOLDER}/gluetun:/gluetun
environment:
- PUID=13002
- PGID=${PGID}
- TZ=${TZ}
- LOG_LEVEL=debug
- VPN_SERVICE_PROVIDER=protonvpn
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY=${WIREGUARD_PRIVATE_KEY}
- BLOCK_MALICIOUS=off
- PORT_FORWARD_ONLY=on
- VPN_PORT_FORWARDING=on
- SERVER_COUNTRIES=Germany
- VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORT}},\"current_network_interface\":\"{{VPN_INTERFACE}}\",\"random_port\":false,\"upnp\":false}" http://127.0.0.1:8082/api/v2/app/setPreferences'
- VPN_PORT_FORWARDING_DOWN_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":0,\"current_network_interface\":\"lo\"}" http://127.0.0.1:8082/api/v2/app/setPreferences'
ports:
- 5010:5010
- 8082:8082
qbittorrent:
image: ghcr.io/hotio/qbittorrent:release-9673f7a
container_name: qbittorrent
network_mode: service:gluetun
depends_on:
gluetun:
condition: service_healthy
environment:
- PUID=13015
- PGID=${PGID}
- UMASK=${UMASK}
- TZ=${TZ}
- WEBUI_PORTS=8082/tcp
- WEBUI_HOST=*
volumes:
- ${CONFIG_FOLDER}/qbittorrent:/config
- ${MEDIA_FOLDER}/data:/data
restart: unless-stopped
qBittorrent logs when ran look just fine initially.
Donate: https://hotio.dev/donate
Documentation: https://hotio.dev/containers/qbittorrent
Support: https://hotio.dev/discord
Image: hotio/qbittorrent:release
Revision: c1cfba9
Version: 5.1.4
OS: Linux 6.17.9-1-pve x86_64
----------------------------------------------------------------------
ENVIRONMENT BASE
----------------------------------------------------------------------
PUID=13015
PGID=13000
UMASK=002
TZ=Europe/Amsterdam
PRIVOXY_ENABLED=false
UNBOUND_ENABLED=false
UNBOUND_NAMESERVERS=
VPN_ENABLED=false
----------------------------------------------------------------------
[2026-03-31 07:26:17] [INF] Executing usermod...
[2026-03-31 07:26:17] [INF] Executing groupmod...
[2026-03-31 07:26:17] [INF] Looking for hardware devices...
[2026-03-31 07:26:17] [INF] Taking ownership of [/config].
s6-rc: info: service init-setup successfully started
s6-rc: info: service init-setup-app: starting
----------------------------------------------------------------------
ENVIRONMENT APP
----------------------------------------------------------------------
WEBUI_PORTS=8082/tcp
LIBTORRENT=v1
----------------------------------------------------------------------
s6-rc: info: service init-setup-app successfully started
s6-rc: info: service init-wireguard: starting
s6-rc: info: service init-wireguard successfully started
s6-rc: info: service service-qbittorrent: starting
s6-rc: info: service service-qbittorrent successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
WebUI will be started shortly after internal preparations. Please wait...
******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8082
But after that it starts looping:
qbittorrent | s6-rc: info: service init-wireguard: starting
qbittorrent | s6-rc: info: service init-wireguard successfully started
qbittorrent | s6-rc: info: service service-qbittorrent: starting
qbittorrent | s6-rc: info: service service-qbittorrent successfully started
qbittorrent | s6-rc: info: service legacy-services: starting
qbittorrent | s6-rc: info: service legacy-services successfully started
qbittorrent | WebUI will be started shortly after internal preparations. Please wait...
gluetun | 2026-03-31T07:23:12+02:00 ERROR [port forwarding] failed: Connection refused.
qbittorrent |
qbittorrent | ******** Information ********
qbittorrent | To control qBittorrent, access the WebUI at: http://localhost:8082
gluetun | 2026-03-31T07:23:15+02:00 ERROR [port forwarding] No data received.
qbittorrent | WebUI will be started shortly after internal preparations. Please wait...
qbittorrent |
qbittorrent | ******** Information ********
qbittorrent | To control qBittorrent, access the WebUI at: http://localhost:8082
gluetun | 2026-03-31T07:23:19+02:00 ERROR [port forwarding] No data received.
qbittorrent | WebUI will be started shortly after internal preparations. Please wait...
qbittorrent |
qbittorrent | ******** Information ********
qbittorrent | To control qBittorrent, access the WebUI at: http://localhost:8082
I cannot use qbittorrent:test since it won't even establish a connection. If I do I only get the logs:
End alert sequence. Alert: state_update Count: 1
End alert sequence. Alert: session_stats Count: 1
End alert sequence. Alert: state_update Count: 1
End alert sequence. Alert: session_stats Count: 1
End alert sequence. Alert: state_update Count: 1
End alert sequence. Alert: session_stats Count: 1
End alert sequence. Alert: state_update Count: 1
End alert sequence. Alert: session_stats Count: 1
End alert sequence. Alert: state_update Count: 1
End alert sequence. Alert: session_stats Count: 1
What's wrong?
I was told to open a new issue since I mentioned things in #281. There seems to be a lot of overlap between that issue and this one. I and other users (qdm12/gluetun#3260) keep getting a qbittorrent crash when making API calls via wget.
Docker compose up starts qbit and gluetun container at same time; gluetun gets wireguard info and tries to set IP + Port in qbit via wget API call.
I've tried
qbittorrent:testqbittorrent:latestqbittorrent:releasev5and they all had this issue.Currently I'm using
qbittorrent:release-9673f7awhich works fine. In qdm12/gluetun#3260 users reported switching to lscr.io images also works fine.Compose File:
qBittorrent logs when ran look just fine initially.
But after that it starts looping:
I cannot use
qbittorrent:testsince it won't even establish a connection. If I do I only get the logs: