docker-wireguard-pia
docker-wireguard-pia copied to clipboard
qBittorrent can't access trackers/internet while other containers can
I can connect to PIA via Wireguard and get a forwarded port. All my other containers (aar, Webtop, etc.) can connect to the internet and are getting the PIA IP. When I add in the PIA forwarded port into qBittorrrent all of the trackers are listed as unreachable/not working. qBittorrent did work previously with glueton and OpenVPN. Docker composer for PIA and qBittorrent are as follows.
Thoughts?
services:
piawireguard:
image: thrnz/docker-wireguard-pia
container_name: piawireguard
cap_add:
- NET_ADMIN
restart: unless-stopped
devices:
- /dev/net/tun:/dev/net/tun
ports:
- 8085:8085 # qbittorrent
- 8989:8989 # Sonarr
- 9696:9696 # Prowlarr
- 7878:7878 # Radarr
- 8990:8990 # SonarrUHD
- 7879:7879 # RadarrUHD
- 3000:3000 # Webtop GUI
- 3001:3001 # Webtop GUI HTTPS
volumes:
- /home/debian/docker/aar-stack/pia:/pia
- /home/debian/docker/aar-stack/pia-shared:/pia-shared
environment:
- LOC=*some location*
- USER=*some user*
- PASS=*some password*
- LOCAL_NETWORK=10.19.88.0/24
- PORT_FORWARDING=1
- PORT_FILE=/pia-shared/port.dat
- PORT_PERSIST=1
sysctls:
- net.ipv4.conf.all.src_valid_mark=1
- net.ipv6.conf.default.disable_ipv6=1
- net.ipv6.conf.all.disable_ipv6=1
- net.ipv6.conf.lo.disable_ipv6=1
healthcheck:
test: ping -c 1 www.google.com || exit 1
interval: 30s
timeout: 10s
retries: 3
qbittorrent:
image: lscr.io/linuxserver/qbittorrent
container_name: qbittorrent
network_mode: "service:piawireguard"
environment:
- PUID=1000
- PGID=1000
- TZ=America/Toronto
- WEBUI_PORT=8085
volumes:
- /home/debian/docker/arr-stack/qbittorrent:/config
- /mnt/Temp/Downloads:/downloads
- /mnt/Media1-1/Media:/mnt/Media1-1
- /mnt/Media1-2/Media:/mnt/Media1-2
- /mnt/Media2-1/Media:/mnt/Media2-1
- /mnt/Media2-2/Media:/mnt/Media2-2
depends_on:
- piawireguard
restart: always
Is qBittorrent bound to the wireguard interface wg0
? That's one thing that comes to mind that I vaguely recall being an issue in the past. IIRC it uses all network interfaces by default, and outgoing internet connections (eg. tracker/peers) on the non-wireguard interface/s would likely fail.