Gluetun with Proton VPN with qBittorrent with Docker

[DancingPotatoes]

Hello, total beginner here.

I'm trying to set up ProtonVPN, Gluetun, and qBittorrent with a properly forwarded port, but I can't figure it out. Since Proton assigns a random port, is there a compose file or guide that explains how to set this up?

I found some guides, but they seem outdated, and I'm not sure how to adapt them to the latest setup.

Also, as a side question—do Prowlarr, Sonarr, and Radarr need to run through Gluetun as well, or do they just communicate with qBittorrent? I'm a bit confused about how this works.

Any help would be greatly appreciated!

[tfp1]

Here's a docker-compose.yml that's 90% of the way there. Look to update all the variables ($wgPublicKey) with your values.

For servarr services, you can run them through gluetun as well. All ports need to be added to the gluetun container. If those services are not running in the same docker-compose.yml, change network_mode: "service:gluetun" to network_mode: "container:gluetun" assuming you name the gluetun container gluetun.

Gluetun will write the port you receive from protonvpn to a file and the gluetun-qbittorrent-port-manager container will read that file then write to qBittorrent for you every 60s.

In qbittorrent, make sure you check Bypass authentication for clients on localhost, then you don't need to worry about passing auth into the port manager container.

services:
  gluetun:
    image: qmcgaw/gluetun:v3.39.0 # Pinned to this version to avoid issues in v3.40+ specific to protonvpn
    container_name: gluetun
    restart: always
    stdin_open: true
    tty: true
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    ports:
      - 8778:8888/tcp  # HTTP proxy
      - 8001:8000/tcp  # GT Control Server
      - 8080:8080      # QB
      - 6881:6881      # QB
      - 6881:6881/udp  # QB
    volumes:
      - $ledger/gluetun:/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=protonvpn
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
      - VPN_PORT_FORWARDING_STATUS_FILE=/gluetun/forwarded_port
      - TZ=UTC/UTC
      - UPDATER_PERIOD=24h
      - FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24,10.0.0.0/16,172.21.0.0/16
      - DOT_PROVIDERS=cloudflare,google
      - PUBLICIP_API=ip2location
### Wireguard Settings
      - VPN_TYPE=wireguard
      - WIREGUARD_PUBLIC_KEY=$wgPublicKey
      - WIREGUARD_PRIVATE_KEY=$wgPrivateKey
      - WIREGUARD_ENDPOINT_IP=$endpointIP
      - WIREGUARD_ADDRESSES=$wgAddresses
      - DNS_ADDRESS=$dnsAddress
      - LOG_LEVEL=debug
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    network_mode: "service:gluetun" #only allowed to use the gluetun network
    container_name: gt-qb
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC/UTC
      - WEBUI_PORT=8080
    volumes:
      - $ledger/gluetun:/gluetun
      - $ledger/qbittorent/config:/config
      - $content/media:/media
      - $content/qbittorent/active:/active
    restart: unless-stopped

  gluetun-qbittorrent-port-manager:
    image: patrickaclark/gluetun-qbittorrent-port-manager:latest
    restart: unless-stopped
    container_name: gt-port-manager
    network_mode: "service:gluetun"
    environment:
      - QBITTORRENT_SERVER=localhost  # IP Address of qbittorrent
      - QBITTORRENT_PORT=8080
      - PORT_FORWARDED=/tmp/gluetun/forwarded_port
      - HTTP_S=http  # Select 'http' or 'https' depending on if you use certificates.
      - GLUETUN_HOST=localhost  # IP or FQDN of gluetun control server
      - GLUETUN_PORT=8000  # port of gluetun control server
      - RECHECK_TIME=60  # number of seconds between checks to gluetun server for port
      - TZ=America/Chicago
    healthcheck:
      test: ["CMD", "curl", "-H", "Authorization: $controlServerAuthKey", "-s", "http://localhost:8000/v1/openvpn/status", "|", "grep", "-q", '{"status":"running"}']
      interval: 30s
      timeout: 10s
      start_period: 60s
      retries: 3

[Quitlox]

However one issue still remains, seeding barely works with this setup. I get 30 MB/s downloads just fine, but I can not seed, which is a big issue for my private linux iso trackers. I have not found a solution for this yet.

Currently, this is not supported by this project, see ProtonVPN port forwarding which states:

Redirection might not be sufficient in all cases, as the software (i.e. Torrenting) may broadcast the port it's listening on which is not the redirected port.

I haven't quite looked into it, but it seems that the port which qbittorrent is configured to on listen is broadcasted to seeders, but this is not necessarily the port on which qbittorrent is reachable externally.

[casudo]

Update to my prior comment: I've managed to fix all of the above problems, even the seeding problems.

qBittorrent depends on Gluetun, and Gluetuns port forwarding healthchecks depends on a healthy qBittorrent container to update the listening port for incoming connections via the API.

Once you start the Gluetun container and the failed port forwarding log lines appear...

2025-08-08T11:27:10+02:00 INFO [port forwarding] --2025-08-08 11:27:10-- (try: 5) http://127.0.0.1:8124/api/v2/app/setPreferences
2025-08-08T11:27:10+02:00 INFO [port forwarding] Connecting to 127.0.0.1:8124... failed: Connection refused.
2025-08-08T11:27:10+02:00 INFO [port forwarding] Retrying.

... you need to restart your qBittorrent container. There is a split second where the qBittorrent container is healthy and Gluetun can reach the API endpoint, successfully updating the listening port. Now qBittorrent is healthy and Gluetun too, making the depends on connection to Gluetun from qBittorrent valid.

For seedings, I haven't had any issues with Proton since. I am seeding with max. upload speeds at all times now (when there are enough peers obviously).

[watchingdogs]

How did you exactly solve the seeding issues @casudo ?

Also which version, I am running the latest from LinuxServer.

After enabling local access for the QB API, the port is updated with my setup, but I still can't seed.

My logs also differ:

2025-08-23T20:03:06Z INFO [ip getter] Public IP address is IPHERE (LOCATION - source: ipinfo)
2025-08-23T20:03:06Z INFO [port forwarding] starting
2025-08-23T20:03:06Z INFO [port forwarding] gateway external IPv4 address is IPHERE
2025-08-23T20:03:06Z INFO [port forwarding] port forwarded is 35206
2025-08-23T20:03:06Z INFO [firewall] setting allowed input port 35206 through interface tun0...
2025-08-23T20:03:06Z INFO [port forwarding] writing port file /tmp/gluetun/forwarded_port
2025-08-23T20:03:06Z INFO [port forwarding] --2025-08-23 20:03:06--  http://127.0.0.1:8085/api/v2/app/setPreferences
2025-08-23T20:03:06Z INFO [port forwarding] Connecting to 127.0.0.1:8085... connected.
2025-08-23T20:03:06Z INFO [port forwarding] HTTP request sent, awaiting response... 200 OK
2025-08-23T20:03:06Z INFO [port forwarding] Length: 0 [text/plain]
2025-08-23T20:03:06Z INFO [port forwarding] Saving to: 'STDOUT'
2025-08-23T20:03:06Z INFO [port forwarding] 
2025-08-23T20:03:06Z INFO [port forwarding]      0K                                                        0.00 =0s
2025-08-23T20:03:06Z INFO [port forwarding] 
2025-08-23T20:03:06Z INFO [port forwarding] 2025-08-23 20:03:06 (0.00 B/s) - written to stdout [0/0]
2025-08-23T20:03:06Z INFO [port forwarding] 
2025-08-23T20:03:07Z WARN [dns] dialing tls server for request IN A cloudflare.com.: context deadline exceeded
2025-08-23T20:03:07Z WARN [dns] dialing tls server for request IN A cloudflare.com.: dial tcp 1.0.0.1:853: i/o timeout
2025-08-23T20:06:57Z INFO [healthcheck] healthy!

[casudo]

@watchingdogs Can't you seed AT ALL, or with low speeds? I haven't really had any issues since both containers ran flawlessly. I seed at full upload speed by my ISP at all times (given there are peers).

[watchingdogs]

@casudo There are times when it does seeding at low speeds, but there were quite many occasions where it never ever began uploading anything. QB connection says it's OK and the ports are changed when IP gets switched.

[testc2n14]

hello i keep having issues with proton vpn and glueton working and i belive from the logs that the vpn conencts but then it can't ping 1.1.1.1 so it then trys again here are the 2 docker.yml files i gave tried

c2@gentoobtw ~/docker-torrent $ cat docker-compose.yml
version: "3.8"
services:
  gluetun:
      image: qmcgaw/gluetun
      cap_add:
        - NET_ADMIN
      devices:
        - /dev/net/tun:/dev/net/tun
      environment:
        - VPN_SERVICE_PROVIDER=protonvpn
        - VPN_TYPE=wireguard
        - WIREGUARD_PRIVATE_KEY=
        - VPN_PORT_FORWARDING=on
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: "service:gluetun"
    depends_on:
      - gluetun
    volumes:
      # Creates a persistent folder for qBittorrent's config
      - /home/c2/docker-torrent/config/qbittorrent/config:/config
      # Your existing folder for downloads
      - /home/c2/Videos:/downloads
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
      - WEBUI_PORT=8080
    restart: unless-stopped

  gluetun-port-manager:
    image: patrickaclark/gluetun-qbittorrent-port-manager:latest
    container_name: port-manager
    network_mode: "service:gluetun"
    restart: always
    depends_on:
      - gluetun
      - qbittorrent
    volumes:
      # Gives the port manager read-only access to the folder where Gluetun saves the port
      - /home/c2/docker-torrent/config/gluetun:/gluetun:ro
    environment:
      - QBITTORRENT_SERVER=localhost
      - QBITTORRENT_PORT=8080
      - PORT_FILE_PATH=/gluetun/forwarded_port
      - TZ=America/Chicago
c2@gentoobtw ~/docker-torrent $ 

version: "3.8"
services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    restart: always
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    ports:
      # Exposes the qBittorrent Web UI through the VPN container
      - 8080:8080
    volumes:
      # Gives Gluetun access to the host's WireGuard kernel module (read-only)
      - /lib/modules:/lib/modules:ro
      # Creates a persistent folder for Gluetun's config (read-write)
      - /home/c2/docker-torrent/config/gluetun:/gluetun
    environment:
      # --- VPN Settings ---
      - VPN_SERVICE_PROVIDER=protonvpn
      - VPN_TYPE=wireguard
      - WIREGUARD_PUBLIC_KEY=
      - WIREGUARD_PRIVATE_KEY=
      - WIREGUARD_ENDPOINT_IP=156.146.54.81
      - WIREGUARD_ADDRESSES=10.2.0.2/32
      # --- Port Forwarding ---
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_STATUS_FILE=/gluetun/forwarded_port
      # --- DNS Fix ---
      - DOT=off
      #- DNS_ADDRESS=1.1.1.1
      # --- Other Settings ---
      - TZ=America/Chicago
      - HEALTHCHECKER=off
      #- DNS_ADDRESS=10.2.0.2/32
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: "service:gluetun"
    depends_on:
      - gluetun
    volumes:
      # Creates a persistent folder for qBittorrent's config
      - /home/c2/docker-torrent/config/qbittorrent/config:/config
      # Your existing folder for downloads
      - /home/c2/Videos:/downloads
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
      - WEBUI_PORT=8080
    restart: unless-stopped

  gluetun-port-manager:
    image: patrickaclark/gluetun-qbittorrent-port-manager:latest
    container_name: port-manager
    network_mode: "service:gluetun"
    restart: always
    depends_on:
      - gluetun
      - qbittorrent
    volumes:
      # Gives the port manager read-only access to the folder where Gluetun saves the port
      - /home/c2/docker-torrent/config/gluetun:/gluetun:ro
    environment:
      - QBITTORRENT_SERVER=localhost
      - QBITTORRENT_PORT=8080
      - PORT_FILE_PATH=/gluetun/forwarded_port
      - TZ=America/Chicago
      ```
      ```
      gluetun-1  | 2025-07-14T23:49:54Z INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
gluetun-1  | 2025-07-14T23:49:54Z INFO [routing] adding route for 0.0.0.0/0
gluetun-1  | 2025-07-14T23:49:54Z INFO [firewall] setting allowed subnets...
gluetun-1  | 2025-07-14T23:49:54Z INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
gluetun-1  | 2025-07-14T23:49:54Z INFO [dns] using plaintext DNS at address 1.1.1.1
gluetun-1  | 2025-07-14T23:49:54Z INFO [http server] http server listening on [::]:8000
gluetun-1  | 2025-07-14T23:49:54Z INFO [healthcheck] listening on 127.0.0.1:9999
gluetun-1  | 2025-07-14T23:49:54Z INFO [firewall] allowing VPN connection...
gluetun-1  | 2025-07-14T23:49:54Z INFO [wireguard] Using available kernelspace implementation
gluetun-1  | 2025-07-14T23:49:54Z INFO [wireguard] Connecting to 79.135.105.88:51820
gluetun-1  | 2025-07-14T23:49:54Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
gluetun-1  | 2025-07-14T23:49:54Z INFO [dns] downloading hostnames and IP block lists
gluetun-1  | 2025-07-14T23:49:54Z WARN [http server] route GET /v1/openvpn/portforwarded is unprotected by default, please set up authentication following the documentation at https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md#authentication since this will become no longer publicly accessible after release v3.40.
gluetun-1  | 2025-07-14T23:49:54Z INFO [http server] 200 GET /portforwarded wrote 11B to 127.0.0.1:56454 in 36.59µs
gluetun-1  | 2025-07-14T23:50:04Z INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (healthcheck error: dialing: dial tcp4: lookup cloudflare.com: i/o timeout)
gluetun-1  | 2025-07-14T23:50:04Z INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
gluetun-1  | 2025-07-14T23:50:04Z INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
gluetun-1  | 2025-07-14T23:50:04Z INFO [vpn] stopping
gluetun-1  | 2025-07-14T23:50:04Z ERROR [vpn] getting public IP address information: context canceled
gluetun-1  | 2025-07-14T23:50:04Z ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled
gluetun-1  | 2025-07-14T23:50:04Z INFO [port forwarding] starting
gluetun-1  | 2025-07-14T23:50:04Z ERROR [vpn] starting port forwarding service: getting VPN assigned IP address: network interface tun0 not found: route ip+net: no such network interface
gluetun-1  | 2025-07-14T23:50:04Z WARN [dns] cannot update filter block lists: Get "https://raw.githubusercontent.com/qdm12/files/master/malicious-hostnames.updated": dial tcp: lookup raw.githubusercontent.com on 1.1.1.1:53: read udp 10.2.0.2:54753->1.1.1.1:53: i/o timeout, Get "https://raw.githubusercontent.com/qdm12/files/master/malicious-ips.updated": dial tcp: lookup raw.githubusercontent.com on 1.1.1.1:53: read udp 10.2.0.2:54753->1.1.1.1:53: i/o timeout
gluetun-1  | 2025-07-14T23:50:04Z INFO [dns] attempting restart in 10s
gluetun-1  | 2025-07-14T23:50:04Z INFO [vpn] starting
gluetun-1  | 2025-07-14T23:50:04Z INFO [firewall] allowing VPN connection...
gluetun-1  | 2025-07-14T23:50:04Z INFO [wireguard] Using available kernelspace implementation
gluetun-1  | 2025-07-14T23:50:04Z INFO [wireguard] Connecting to 146.70.133.130:51820
gluetun-1  | 2025-07-14T23:50:04Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
c2@gentoobtw ~/docker-torrent $ docker compose logs qbittorrent

gluetun  | 2025-07-14T18:24:49-05:00 INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
gluetun  | 2025-07-14T18:24:49-05:00 INFO [routing] adding route for 0.0.0.0/0
gluetun  | 2025-07-14T18:24:49-05:00 INFO [firewall] setting allowed subnets...
gluetun  | 2025-07-14T18:24:49-05:00 INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
gluetun  | 2025-07-14T18:24:49-05:00 INFO [dns] using plaintext DNS at address 1.1.1.1
gluetun  | 2025-07-14T18:24:49-05:00 INFO [http server] http server listening on [::]:8000
gluetun  | 2025-07-14T18:24:49-05:00 INFO [healthcheck] listening on 127.0.0.1:9999
gluetun  | 2025-07-14T18:24:49-05:00 INFO [firewall] allowing VPN connection...
gluetun  | 2025-07-14T18:24:49-05:00 INFO [wireguard] Using available kernelspace implementation
gluetun  | 2025-07-14T18:24:49-05:00 INFO [wireguard] Connecting to 138.199.33.236:51820
gluetun  | 2025-07-14T18:24:49-05:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
gluetun  | 2025-07-14T18:24:49-05:00 WARN [http server] route GET /v1/openvpn/portforwarded is unprotected by default, please set up authentication following the documentation at https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md#authentication since this will become no longer publicly accessible after release v3.40.
gluetun  | 2025-07-14T18:24:49-05:00 INFO [http server] 200 GET /portforwarded wrote 11B to 127.0.0.1:60900 in 36.191µs
gluetun  | 2025-07-14T18:24:59-05:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (healthcheck error: dialing: dial tcp4: lookup cloudflare.com: i/o timeout)
gluetun  | 2025-07-14T18:24:59-05:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
gluetun  | 2025-07-14T18:24:59-05:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
gluetun  | 2025-07-14T18:24:59-05:00 INFO [vpn] stopping
gluetun  | 2025-07-14T18:24:59-05:00 ERROR [vpn] waiting for DNS to be ready: context canceled
gluetun  | 2025-07-14T18:24:59-05:00 ERROR [vpn] getting public IP address information: context canceled
gluetun  | 2025-07-14T18:24:59-05:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled
gluetun  | 2025-07-14T18:24:59-05:00 INFO [port forwarding] starting
gluetun  | 2025-07-14T18:24:59-05:00 ERROR [vpn] starting port forwarding service: getting VPN local gateway IP: VPN local gateway IP address not found: in 9 routes
gluetun  | 2025-07-14T18:24:59-05:00 INFO [vpn] starting
gluetun  | 2025-07-14T18:24:59-05:00 INFO [firewall] allowing VPN connection...
gluetun  | 2025-07-14T18:24:59-05:00 INFO [wireguard] Using available kernelspace implementation
gluetun  | 2025-07-14T18:24:59-05:00 INFO [wireguard] Connecting to 79.135.105.204:51820
gluetun  | 2025-07-14T18:24:59-05:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
gluetun  | 2025-07-14T18:25:11-05:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN (healthcheck error: dialing: dial tcp4: lookup cloudflare.com: i/o timeout)
gluetun  | 2025-07-14T18:25:11-05:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
gluetun  | 2025-07-14T18:25:11-05:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
gluetun  | 2025-07-14T18:25:11-05:00 INFO [vpn] stopping
gluetun  | 2025-07-14T18:25:11-05:00 ERROR [vpn] waiting for DNS to be ready: context canceled
gluetun  | 2025-07-14T18:25:11-05:00 ERROR [vpn] getting public IP address information: context canceled
gluetun  | 2025-07-14T18:25:11-05:00 INFO [port forwarding] starting
gluetun  | 2025-07-14T18:25:11-05:00 ERROR [vpn] starting port forwarding service: getting VPN local gateway IP: VPN local gateway IP address not found: in 9 routes
gluetun  | 2025-07-14T18:25:12-05:00 INFO [vpn] starting
gluetun  | 2025-07-14T18:25:12-05:00 INFO [firewall] allowing VPN connection...
gluetun  | 2025-07-14T18:25:12-05:00 INFO [wireguard] Using available kernelspace implementation
gluetun  | 2025-07-14T18:25:12-05:00 INFO [wireguard] Connecting to 190.2.132.139:51820
gluetun  | 2025-07-14T18:25:12-05:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
c2@gentoobtw ~/docker-torrent $

[RDust4]

I've rewritten SnoringDragon/gluetun-qbittorrent-port-manager in Python. The goal was to make the integration between Gluetun and qBittorrent a bit more robust and configurable.

Key improvements:

• Regular port file checks to detect changes and keep qBittorrent aligned automatically.
• Confirmation via GET request to ensure that qBittorrent has actually accepted the updated port.
• Improved error handling so failures are reported more clearly and retried.
• More configuration options for timeouts, retries, etc.

You can find the repository here: jopiermeier/gluetun-qbittorrent-port-manager

I'd be happy on some feedback!

[Gluemon96]

Yes exactly. It sets the port that qbittorrent uses for its connections to the one randomly assigned by proton.

Hi!
I've set this up with my Gluetun/qBittorrent and all the containers started fine, but it's not finding the port or writing that forwarded port field. Not sure what I'm doing wrong. I've connected to the same server on my Windows machine and I'm provided a port right away so I don't think it's a server issue.

[RDust4]

What does "docker compose logs -f" tell you? Does gluetun tell which port was forwarded?

[Gluemon96]

2025-10-02T07:06:01-05:00 INFO [port forwarding] starting
2025-10-02T07:08:09-05:00 ERROR [vpn] starting port forwarding service: port forwarding for the first time: getting external IPv4 address: executing remote procedure call: connection timeout: failed attempts: read udp 172.18.0.2:34534->10.2.0.1:5351: i/o timeout (tries 1, 2, 3, 4, 5, 6, 7, 8, 9)

This is all I find about port forwarding in the logs.
Are you all running this with vpn_provider=custom and using a wg0.conf file? I still am doing that.

[Gluemon96]

If it helps.. this is my working Gluetun / qBittorrent set up with AirVPN, before trying ProtonVPN.. and I am on Synology, which I'm wondering is the cause for my issues..

version: "3.9"

services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    environment:
      - TZ=America/Bogota
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - FIREWALL_VPN_INPUT_PORTS=xxxxx
      - VPN_INTERFACE_MTU=1400
      - FIREWALL_OUTBOUND_SUBNETS=192.168.0.0/16,10.0.0.0/8,172.16.0.0/12
    volumes:
      - /volume1/docker/gluetun:/gluetun
    ports:
      - "8080:8080"            # qBittorrent WebUI exposed via Gluetun
      - "xxxxx:xxxxx/tcp"     # AirVPN forwarded port
      - "xxxxx:xxxxx/udp"
    healthcheck:
      test: ["CMD-SHELL", "wget -q --spider https://1.1.1.1 || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 3
    restart: unless-stopped

  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: "service:gluetun"
    depends_on:
      gluetun:
        condition: service_healthy
    environment:
      - PUID=1026
      - PGID=100
      - TZ=America/Bogota
      - WEBUI_PORT=8080
      - WEBUI_USERNAME=admin
      - WEBUI_PASSWORD=
    volumes:
      - /volume1/docker/qbittorrent/config:/config
      - /volume1/Documents/Torrents:/downloads
      - /volume2/Documents 2/Torrents:/downloads2
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped

[magrhino]

Hello, I spun up your container. it successfully updated once but then failed to update a second time, any guidance would be appreciated.

gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    environment:
      - VPN_PORT_FORWARDING_STATUS_FILE=/gluetun/forwarded_port
    ports:
      - "8080:8080"       # qBittorrent Web UI
      - "9191:9191"       # dispatcharr
    volumes:
      - /qbittorrent/gluetun:/gluetun
    restart: unless-stopped

  qbittorrent:
    image: linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: service:gluetun
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=${TZ}
      - WEBUI_PORT=8080
      - DOCKER_MODS=ghcr.io/vuetorrent/vuetorrent-lsio-mod:nightly
    volumes:
    depends_on:
      gluetun:
         condition: service_healthy
    healthcheck:
      test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8080/api/v2/app/version || exit 1"]
      interval: 30s
      timeout: 5s
      retries: 5
    restart: unless-stopped

#---------------SUPERVISOR STACK-----------------------------
  gluetun-qbittorrent-port-manager:
    image: jopiermeier/gluetun-qbittorrent-port-manager:latest
    network_mode: "service:gluetun"
    container_name: proton-port-manager
    user: "1000:1000"
    depends_on:
      gluetun:
        condition: service_started
        restart: true
      qbittorrent:
        condition: service_started
        restart: true
    environment:
      - QBITTORRENT_USER=${QBITTORRENT_USER}
      - QBITTORRENT_PASS=${QBITTORRENT_PASS}
      - PORT_FILE=/forwarded_port
    volumes:
      - /qbittorrent/gluetun/forwarded_port:/forwarded_port
    restart: unless-stopped

Logs for full 9hr run:

waiting for qBittorrent WebUI...
waiting for qBittorrent WebUI...
qBittorrent WebUI is ready (authenticated).
gluetun provided forwarded port: 52611
syncing port 52611 to qBittorrent...
successfully updated qBittorrent to port 52611 (confirmed)

[Gluemon96]

Seems my issue was because the below in FIREWALL_OUTBOUND_SUBNETS=192.168.0.0/16,172.16.0.0/12

10.0.0.0/8

All is well in the world now :)

[cordlord]

For anyone else seeking an easy way to do this, here's how I did it with v3.40.0+

This env variable adds a command that runs once port forwarding starts and was added in v3.40.0. The command used updates the forward port that qBittorrent uses automatically with no need for any extra containers or anything else.

- VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORTS}}}" http://127.0.0.1:8181/api/v2/app/setPreferences 2>&1'

I also made sure to add the qBittorrent web ui port to the ports in gluetun
- "8181:8181/tcp"

[NeyNey]

For anyone else seeking an easy way to do this, here's how I did it with v3.40.0+

This env variable adds a command that runs once port forwarding starts and was added in v3.40.0. The command used updates the forward port that qBittorrent uses automatically with no need for any extra containers or anything else.

- VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORTS}}}" http://127.0.0.1:8181/api/v2/app/setPreferences 2>&1'

I also made sure to add the qBittorrent web ui port to the ports in gluetun - "8181:8181/tcp"

I was wondering why the command didn't work. I run 3.39 because the notes said 3.40 specifically broke Proton. Corious why the logs does not say something about the command not being viable or something ... shrugs

Thanks for the heads up!