qBittorrent (and also Deluge, i assume) Firewalled

[82t49dgXtMMx]

Hello,

there is no config or documentation about exposing your (randomized) torrent port. This leads to a firewalled status in the torrent container, and a suboptimal torrenting and seeding experience.
After adding this to my qbittorent service yaml docker exposes those ports to connections from outside, and seeding works fine.
Since these ports are randomized, i think you should at least document this step somewhere, and possibly integrate it into the .env

Snippet to add:

ports:
- 12345:12345
- 12345:12345/udp

BR

[tblaudez]

I assume what you shared works fine if the qBittorrent service is running without any VPN (vpn: false in the config.yaml).

However, if the VPN setting is enabled, qBittorent networking will be transferred to the Gluetun container and I don't know that exposing the ports of the qBittorrent container will work in order to allow incoming traffic.
To avoid Firewalling in this scenario, it'll be necessary to use a VPN that allows port forwarding.
Here's Gluetun documentation regarding that.

On my part, I used the following configuration to allow port forwarding on my Gluetun+ProtonVPN and to synchronize the randomized forwarded port to qBittorent :

# .env.custom
GLUETUN_VPN_SERVICE_PROVIDER=protonvpn
GLUETUN_VPN_TYPE=wireguard
GLUETUN_PORT_FORWARD_ONLY=on
GLUETUN_VPN_PORT_FORWARDING=on
# Send a POST request to qBittorrent to update the listen port once port forwarding is up
GLUETUN_VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORTS}}}" http://127.0.0.1:8080/api/v2/app/setPreferences 2>&1'

[82t49dgXtMMx]

Hello,

it is correct, that i am not using a VPN in my setup. Without VPN, the ports not being exposed is an issue. I'd suggest to at least document this somewhere, as it took me very long to figure out what the issue is (granted, I am rather new to docker).

BR