I’m trying to get Qbittorrent set up within Docker on my home server and want to configure port forwarding through my VPN for all of those Linux ISOs. Ideally, I also want to get a pipeline going with the *arr stack. I’ve heard the easiest way to do this is with Gluetun but I can’t for the life of me figure it out or know how to test it. Anyone been through something similar?
Here is my current Docker Compose for reference:
services:
gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun
cap_add:
- NET_ADMIN
environment:
- VPN_SERVICE_PROVIDER=airvpn
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY="[redacted]"
- WIREGUARD_PRESHARED_KEY="[redacted]
- WIREGUARD_ADDRESSES=10.131.184.14/32
- FIREWALL_VPN_INPUT_PORTS=8069
- SERVER_COUNTRIES=United States
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- /home/fenndev/.config/gluetun:/config
ports:
- 9091:9091 # WebUI
- 6881:6881
- 6881:6881/udp
restart: unless-stopped
qbit:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbit
network_mode: "service:gluetun"
environment:
- PUID=1000
- PGID=1000
- TZ=America/Los_Angeles # Timezone set to Los A>
- WEBUI_PORT=9091 # Qbittorrent webUI port
volumes:
- /home/fenndev/.config/qbit:/config # Configura>
- /home/fenndev/torrents:/downloads # Torrent da>
depends_on:
glueten:
condition: service_healthy
Honestly, not sure. What you did looks close to what I’d expect reading the airvpn doc.
-
Is port 6881 something unrelated? I think only local ports go there (e.g. your webui)
-
obviously make sure you set the forwarded port in qbittorrent, then maybe try some external tool like ipleak.net which can give you a magnet link you can put in qbittorrent to see the reported geo location. Not sure if that perfectly vets the port you intend to use, though.
-
glueten->gluetun in depends_on
If you attach to your docker as you launch, you might see some helpful output from either qbittorrent or gluetun (I think the “-it” flags
-