Binding qbittorrent with privadovpn on Synology NAS

Site Feedback
1

Hi,

Still quiet new to this and to start with: I’ve followed the pinned guide… :wink:

However I only see 2 network interfaces, 1 called “lo” and 2nd called “eth0”. Whether I connect to the vpn or not, it remains unchanged and I only see these 2 network interfaces. I already tried rebooting, deleting/readding the VPN and restarted Qbittorrent container several times during all my trial and errors.

My setup is a synology DS920+ nas, qbittorrent installed in docker container and I’d like to use PrivadoVPN (I know not ideal, but I got that one for free).

Mostly using newssites, but from time to time I’d like to download a torrent in a safe way.

Any idea what I’m doing wrong?
Tx

2

qbittorrent installed in docker container

privadovpn isn’t on the gluetun provider list but you can use a custom one. gluetun-wiki/setup/providers/custom.md at main · qdm12/gluetun-wiki · GitHub

Docker compose example;

services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun-torrent
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    devices:
      - /dev/net/tun:/dev/net/tun
    ports:
      - 6363:6363/tcp # qBittorrent WebUI
    volumes:
      - /gluetun:/gluetun
      - /etc/localtime:/etc/localtime:ro
      - /lib/modules:/lib/modules:ro
    environment:
      - PUID=1000
      - PGID=1001
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - VPN_ENDPOINT_IP=1.2.3.4
      - VPN_ENDPOINT_PORT=51820
      - WIREGUARD_PUBLIC_KEY=wAUaJMhAq3NFutLHIdF8AN0B5WG8RndfQKLPTEDHal0=
      - WIREGUARD_PRIVATE_KEY=wOEI9rqqbDwnN8/Bpp22sVz48T71vJ4fYmFWujulwUU=
      - WIREGUARD_PRESHARED_KEY=xOEI9rqqbDwnN8/Bpp22sVz48T71vJ4fYmFWujulwUU=
      - WIREGUARD_ADDRESSES=10.64.222.21/32
  qbittorrent:
    image: linuxserver/qbittorrent:latest
    container_name: qbittorrent
    depends_on:
      gluetun:
        condition: service_healthy
        restart: true
    network_mode: "service:gluetun"
    environment:
      - PUID=1000
      - PGID=1001
      - WEBUI_PORT=6363 # qBittorrent WebUI
    volumes:
      - /config:/config
      - /downloads:/downloads
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped

No need to bind when doing it this way. qB container depends on gluetun container to be running for its network.

Edit/change to suit your needs.

NB Not my wireguard config, I replaced it with the snippet from the above given link.

3

well, qbittorent has some problems with refreshing the screen so i close qbittorent and then start the vpn and then start qbittorent and then the vpn will be listed. If you started the vpn after you started qbittorent then you have problems like this

4

Another option is to do it via docker where qbittorrent container depends on VPN container. If VPN loses connectivity then qbittorrent will lose connection immediately as well.

Should be pretty easy to do on Synology NAS.