Wireguard dyonr-qbittorrent container not launching

Currently reading
Wireguard dyonr-qbittorrent container not launching

Well, spoke to soon unfortunately. The same problem is back again. Pretty much all torrents just stay on finding metadata. But when I change the port in the qbittorrent settings, they immediately find peers/seeds and start downloading.

Any idea how to fix this? Or better to ask this on qmcgaw gluetuns website?
 
Well, spoke to soon unfortunately. The same problem is back again. Pretty much all torrents just stay on finding metadata. But when I change the port in the qbittorrent settings, they immediately find peers/seeds and start downloading.

Any idea how to fix this? Or better to ask this on qmcgaw gluetuns website?
What VPN service are you using? Could it be that the contianer had some idle time and the provider terminated the connection?
 
What VPN service are you using? Could it be that the contianer had some idle time and the provider terminated the connection?
I'm using the wireguard protocol from Surfshark. Torrents just do not start and stay stuck on finding metadata. Although sometimes a torrent does start if I manually change the port in the Qbittorrent settings.

Here is the log from the gluetun container, which I copied from portainer.

| ├── Unbound settings:
| | ├── Authoritative servers:
| | | └── cloudflare
| | ├── Caching: yes
| | ├── IPv6: no
| | ├── Verbosity level: 1
| | ├── Verbosity details level: 0
| | ├── Validation log level: 0
| | ├── System user: root
| | └── Allowed networks:
| | ├── 0.0.0.0/0
| | └── ::/0
| └── DNS filtering settings:
| ├── Block malicious: yes
| ├── Block ads: no
| ├── Block surveillance: no
| └── Blocked IP networks:
| ├── 127.0.0.1/8
| ├── 10.0.0.0/8
| ├── 172.16.0.0/12
| ├── 192.168.0.0/16
| ├── 169.254.0.0/16
| ├── ::1/128
| ├── fc00::/7
| ├── fe80::/10
| ├── ::ffff:7f00:1/104
| ├── ::ffff:a00:0/104
| ├── ::ffff:a9fe:0/112
| ├── ::ffff:ac10:0/108
| └── ::ffff:c0a8:0/112
├── Firewall settings:
| └── Enabled: yes
├── Log settings:
| └── Log level: INFO
├── Health settings:
| ├── Server listening address: 127.0.0.1:9999
| ├── Target address: cloudflare.com:443
| ├── Read header timeout: 100ms
| ├── Read timeout: 500ms
| └── VPN wait durations:
| ├── Initial duration: 6s
| └── Additional duration: 5s
├── Shadowsocks server settings:
| └── Enabled: no
├── HTTP proxy settings:
| └── Enabled: no
├── Control server settings:
| ├── Listening address: :8000
| └── Logging: yes
├── OS Alpine settings:
| ├── Process UID: 1000
| └── Process GID: 1000
├── Public IP settings:
| ├── Fetching: every 12h0m0s
| └── IP file path: /tmp/gluetun/ip
└── Version settings:
└── Enabled: yes
2022-12-02T07:10:24Z INFO IPv6 is not supported
2022-12-02T07:10:24Z INFO [routing] default route found: interface eth0, gateway 192.168.240.1 and assigned IP 192.168.240.2
2022-12-02T07:10:24Z INFO [routing] adding route for 0.0.0.0/0
2022-12-02T07:10:24Z INFO [firewall] setting allowed subnets...
2022-12-02T07:10:24Z INFO [routing] default route found: interface eth0, gateway 192.168.240.1 and assigned IP 192.168.240.2
2022-12-02T07:10:24Z INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it...
2022-12-02T07:10:24Z INFO [pprof] http server listening on [::]:6060
2022-12-02T07:10:24Z INFO [dns over tls] using plaintext DNS at address 1.1.1.1
2022-12-02T07:10:24Z INFO [http server] http server listening on [::]:8000
2022-12-02T07:10:24Z INFO [healthcheck] listening on 127.0.0.1:9999
2022-12-02T07:10:24Z INFO [firewall] allowing VPN connection...
2022-12-02T07:10:24Z INFO [wireguard] Using available kernelspace implementation
2022-12-02T07:10:24Z INFO [wireguard] Connecting to 81.19.209.20:51820
2022-12-02T07:10:24Z INFO [wireguard] Wireguard is up
2022-12-02T07:10:24Z INFO [dns over tls] downloading DNS over TLS cryptographic files
2022-12-02T07:10:32Z INFO [healthcheck] program has been unhealthy for 6s: restarting VPN
2022-12-02T07:10:32Z INFO [vpn] stopping
2022-12-02T07:10:32Z ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled
2022-12-02T07:10:32Z INFO [vpn] starting
2022-12-02T07:10:32Z INFO [firewall] allowing VPN connection...
2022-12-02T07:10:32Z INFO [wireguard] Using available kernelspace implementation
2022-12-02T07:10:32Z INFO [wireguard] Connecting to 81.19.209.20:51820
2022-12-02T07:10:32Z INFO [wireguard] Wireguard is up
2022-12-02T07:10:34Z WARN [dns over tls] cannot update files: Get "https://www.internic.net/domain/named.root": dial tcp: lookup www.internic.net on 1.1.1.1:53: read udp 10.14.0.2:57173->1.1.1.1:53: i/o timeout
2022-12-02T07:10:34Z INFO [dns over tls] attempting restart in 10s
2022-12-02T07:10:43Z INFO [healthcheck] program has been unhealthy for 11s: restarting VPN
2022-12-02T07:10:43Z INFO [vpn] stopping
2022-12-02T07:10:43Z INFO [vpn] starting
2022-12-02T07:10:43Z INFO [firewall] allowing VPN connection...
2022-12-02T07:10:43Z INFO [wireguard] Using available kernelspace implementation
2022-12-02T07:10:43Z INFO [wireguard] Connecting to 178.239.173.43:51820
2022-12-02T07:10:43Z INFO [wireguard] Wireguard is up
2022-12-02T07:10:44Z INFO [healthcheck] healthy!
2022-12-02T07:10:44Z INFO [dns over tls] downloading DNS over TLS cryptographic files
2022-12-02T07:10:46Z INFO [dns over tls] downloading hostnames and IP block lists
2022-12-02T07:10:52Z INFO [healthcheck] unhealthy: cannot dial: dial tcp4: lookup cloudflare.com: i/o timeout(see Healthcheck · qdm12/gluetun Wiki)
2022-12-02T07:10:53Z INFO [dns over tls] init module 0: validator
2022-12-02T07:10:53Z INFO [dns over tls] init module 1: iterator
2022-12-02T07:10:53Z INFO [dns over tls] start of service (unbound 1.15.0).
2022-12-02T07:10:53Z INFO [dns over tls] generate keytag query _ta-4a5c-4f66. NULL IN
2022-12-02T07:10:53Z INFO [dns over tls] generate keytag query _ta-4a5c-4f66. NULL IN
2022-12-02T07:10:53Z INFO [dns over tls] ready
2022-12-02T07:10:53Z INFO [healthcheck] healthy!
 
I've had this with certain qbittorrent builds.. restarting the container then gets them to download the metadata and get going. It's one of the reasons I keep my qbit and wireguard proxy container seperate.
 
Last edited:
That's what has worked perfectly fine previously, but I cannot get the qbittorrent container added in portainer any more. I then get this error:
failed to deploy a stack: service "torrent" depends on undefined service vpn: invalid compose project

And im using these separate compose codes to create the stacks, but then it gives the error when creating the qbittorrent one.

Code:
version: "3.5"
services:
  vpn:
    image: qmcgaw/gluetun
    container_name: gluetun-wireguard
    cap_add:
      - net_admin
    environment:
      - VPN_SERVICE_PROVIDER=surfshark
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY={key}
      - WIREGUARD_ADDRESSES=10.14.0.2/16
      - SERVER_COUNTRIES=Netherlands
      - SERVER_HOSTNAMES=nl-ams-mp001.prod.surfshark.com,nl-ams-st001.prod.surfshark.com,nl-ams.prod.surfshark.com
    ports:
      - 8080:8080
      - 6881:6881/tcp
      - 6881:6881/udp
    restart: always

Code:
version: "3.5"
services:
  torrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: container:gluetun-wireguard
    environment:
      - WEBUI_PORT=8080
      - PUID=1027
      - PGID=100
      - TZ=Europe/Amsterdam
    volumes:
      - /volume1/docker/qbittorrent:/config
      - /volume1/video/downloads:/video/downloads
    depends_on:
      - vpn
    restart: always
 
Code:
version: "3.5"
services:
  vpn:
    image: qmcgaw/gluetun
    container_name: gluetun-wireguard
    cap_add:
      - net_admin
    environment:
      - VPN_SERVICE_PROVIDER=surfshark
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY={key}
      - WIREGUARD_ADDRESSES=10.14.0.2/16
      - SERVER_COUNTRIES=Netherlands
      - SERVER_HOSTNAMES=nl-ams-mp001.prod.surfshark.com,nl-ams-st001.prod.surfshark.com,nl-ams.prod.surfshark.com
    ports:
      - 8080:8080
      - 6881:6881/tcp
      - 6881:6881/udp
    restart: always

  torrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: container:gluetun-wireguard
    environment:
      - WEBUI_PORT=8080
      - PUID=1027
      - PGID=100
      - TZ=Europe/Amsterdam
    volumes:
      - /volume1/docker/qbittorrent:/config
      - /volume1/video/downloads:/video/downloads
    depends_on:
      - vpn
    restart: always

Simple as that ;)
 
I mean an older version. I believe hotio is offering a container with a legacy version of qbittorrent due to issues.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Question! maybe someone know if it is possible... At the moment I'm using VDSM as a VPN Gateway for my...
Replies
8
Views
6,510
It keeps stopping working between the 2 Synologys, and I have to keep running commands in the Terminal to...
Replies
21
Views
17,188
  • Question
Are you able to expand on this part? Make it more step by step? I spent the last week doing what you...
Replies
20
Views
7,369

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top