Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - qBittorrentVPN

Featured Replies

arch-qbittorrentvpn:4.3.9-2-01 reverted back no issues

  • Replies 5.2k
  • Views 1.2m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I rolled back to tag 5.1.1-1-01 which fixed the issue for me. I guess the new update wasn't tested for wireguard connections. Edit the docker container and change "Repository" from binhex/arch-qbitt

  • FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.   Add this line under [Preferences]

  • gustyScanner
    gustyScanner

    Hello! I have been using wireguard successfully for a long time with this container, today though when the container restarted I got the following error: 2025-06-27 10:35:26,490 DEBG 'start-script'

Posted Images

24 minutes ago, cattledog said:

[info] PIA endpoint 'aus-melbourne.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-

2026-07-13 11:32:06,565 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-07-13 11:32:06,565 DEBG 'start-script' stdout output:

[info] bahamas.privacy.network

[info] ca-montreal.privacy.network

[info] yerevan.privacy.network

[info] montenegro.privacy.network

[info] venezuela.privacy.network

[info] np-nepal-pf.privacy.network

[info] panama.privacy.network

[info] pe-peru-pf.privacy.network

[info] mongolia.privacy.network

[info] in.privacy.network

[info] hk.privacy.network

[info] ca-toronto.privacy.network

[info] monaco.privacy.network

[info] kazakhstan.privacy.network

[info] vietnam.privacy.network

[info] man.privacy.network

[info] liechtenstein.privacy.network

[info] srilanka.privacy.network

[info] malta.privacy.network

[info] bangladesh.privacy.network

[info] uk-2.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] macau.privacy.network

[info] morocco.privacy.network

[info] ba.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] ca-vancouver.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] cambodia.privacy.network

[info] de-germany-so.privacy.network

[info] sanjose.privacy.network

[info] nl-netherlands-so.privacy.network

[info] ua.privacy.network

[info] cyprus.privacy.network

[info] nl-amsterdam.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.pvt.site

[info] austria.pvt.site

[info] au-adelaide.pvt.site

[info] au-brisbane.pvt.site

[info] au-melbourne.pvt.site

[info] au-perth.pvt.site

[info] au-sydney.pvt.site

[info] belgium.pvt.site

[info] brazil.pvt.site

[info] bulgaria.pvt.site

[info] ca-ontario.pvt.site

[info] chile.pvt.site

[info] china.pvt.site

[info] colombia.pvt.site

[info] croatia.pvt.site

2026-07-13 11:32:06,565 DEBG 'start-script' stdout output:

[info] czech-republic.pvt.site

[info] de-berlin.pvt.site

[info] de-frankfurt.pvt.site

[info] denmark.pvt.site

[info] egypt.pvt.site

[info] es-madrid.pvt.site

[info] es-valencia.pvt.site

[info] estonia.pvt.site

[info] fi-helsinki.pvt.site

[info] france.pvt.site

[info] georgia.pvt.site

[info] greece.pvt.site

[info] greenland.pvt.site

[info] hungary.pvt.site

[info] iceland.pvt.site

[info] indonesia.pvt.site

[info] ireland.pvt.site

[info] israel.pvt.site

[info] it-milano.pvt.site

[info] jp-tokyo.pvt.site

[info] latvia.pvt.site

[info] lithuania.pvt.site

[info] luxembourg.pvt.site

[info] malaysia.pvt.site

[info] mexico.pvt.site

[info] moldova.pvt.site

[info] new-zealand.pvt.site

[info] nigeria.pvt.site

[info] north-macedonia.pvt.site

[info] norway.pvt.site

[info] philippines.pvt.site

[info] poland.pvt.site

2026-07-13 11:32:06,565 DEBG 'start-script' stdout output:

[info] portugal.pvt.site

[info] qatar.pvt.site

[info] romania.pvt.site

[info] saudi-arabia.pvt.site

[info] se-stockholm.pvt.site

[info] serbia.pvt.site

[info] singapore.pvt.site

[info] slovakia.pvt.site

[info] slovenia.pvt.site

[info] south-africa.pvt.site

[info] south-korea.pvt.site

[info] switzerland.pvt.site

[info] taiwan.pvt.site

[info] turkey.pvt.site

[info] uk-london.pvt.site

[info] uk-manchester.pvt.site

[info] uk-southampton.pvt.site

[info] united-arab-emirates.pvt.site

2026-07-13 11:32:06,566 DEBG 'start-script' stdout output:

[info] Script finished to assign incoming port

Here is your problem. You’ll need to edit your ovpn file and change the endpoint to one from the list. PIA has changed the naming on some of their endpoints.

2 hours ago, wgstarks said:

Here is your problem. You’ll need to edit your ovpn file and change the endpoint to one from the list. PIA has changed the naming on some of their endpoints.

And this will allow web gui again? By the way thanks for help

52 minutes ago, cattledog said:

And this will allow web gui again? By the way thanks for help

I downloaded new ovpn and it is the same remote aus-melbourne.privacy.network 1198

So got it sorted but am a little worried to update to latest, by doing so I will be able to reach web gui?

2 minutes ago, cattledog said:

So got it sorted but am a little worried to update to latest, by doing so I will be able to reach web gui?

No way to tell unless you try. If you wait a couple of minutes and still can't connect attach your docker run command and supervisord log to your next post. Be sure to redact users/passwords.

Well seems to be running fine now, thanks for your help

😀

29 minutes ago, cattledog said:

Well seems to be running fine now, thanks for your help

😀

Glad you got it.

Hi Binhex (and Unraid Community),

I'm trying to understand the reason for using custom name servers on the qbitorrentvpn container instead of using the local Docker DNS server (127.0.0.11). This came up because I want Qbit to run a script to another container (cross-seed) on the same custom docker network (172.18.0.0/16), however, name resolution fails because the qbit container is using Cloudflare name servers in my case.

As a workaround, I can just set a static Docker IP for cross-seed and use that in the script command but I would prefer to use the docker hostname instead. For reference, I am running Proton VPN on the Qbit container.

Can I just change the name servers to 127.0.0.11 and have it route to my routers DNS (also Cloudflare) or will this cause some IP leakage?

I can not access the WEBUI when in bridge mode. I added both my Unraids IP Range, my Clients IP Range and 172.17.0.0/16 to the LAN Networks but I still can not access the WEB UI. Other Bridget clients can talk to it when using the internal IP (in that case 172.17.0.5) but ofc I cant use that on my Client. Any idea what I can do to resolve this?

Fix your VPN config, can't reach the webui until VPN is connected.

2 hours ago, Kilrah said:

Fix your VPN config, can't reach the webui until VPN is connected.

as soon as i put it back on the docker network that unraid itself is connected to my router through it works fine. it's only unreachable from the bridge setting

Edited by babyhuehnchen

2 hours ago, babyhuehnchen said:

as soon as i put it back on the docker network that unraid itself is connected to my router through it works fine. it's only unreachable from the bridge setting

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Top Of The Day To Everyone!

I have a problem with the binhex-qbittorrent/delugevpn when I input the information for the VPN client, which is Private Internet Access. The container will not load on the web GUI, but when I turn off the VPN, the Web GUI works just fine. I have tried different versions of the container, but to no JOY! It happens to both binhex-qbittorrent/delugevpn, and yes, one torrent is shut down, so I try the other one, so there is no conflict with the ports. I really am at my wits' end with this; any help would be great.

Very Respectfully

24 minutes ago, wilekcmc said:

Top Of The Day To Everyone!

I have a problem with the binhex-qbittorrent/delugevpn when I input the information for the VPN client, which is Private Internet Access. The container will not load on the web GUI, but when I turn off the VPN, the Web GUI works just fine. I have tried different versions of the container, but to no JOY! It happens to both binhex-qbittorrent/delugevpn, and yes, one torrent is shut down, so I try the other one, so there is no conflict with the ports. I really am at my wits' end with this; any help would be great.

Very Respectfully

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Here is the Docker run file. I hope I did this correctly?

Update Container

Stopping container: binhex-qbittorrentvpn

Successfully stopped container 'binhex-qbittorrentvpn'


Removing container: binhex-qbittorrentvpn

Successfully removed container 'binhex-qbittorrentvpn'


Command executiondocker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='olympus'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Olympus"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'=
  -e 'VPN_PASS'=
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.76.0/24'
  -e 'WEBUI_PORT'='8080'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1'
  -e 'ENABLE_HEALTHCHECK'='yes'
  -e 'HEALTHCHECK_COMMAND'=''
  -e 'HEALTHCHECK_ACTION'=''
  -e 'HEALTHCHECK_HOSTNAME'='google.com'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/templates/main/unraid/binhex/images/qbittorrent-icon.png'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:99/tcp'
  -p '58946:100/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/data/torrents/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

3343852f1b7df2b51371ed42604343598dace3f9a17ba9a08825ce339d2226e3

The command finished successfully!

This is the log file again. I hope it's right

-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.37.206/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.150.50/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

-A OUTPUT -o wg0 -j ACCEPT

2026-07-18 21:51:37,599 DEBG 'start-script' stdout output:

--------------------

2026-07-18 21:51:37,601 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2026-07-18 21:51:37,601 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2026-07-18 21:51:37,611 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-07-18 21:51:37,614 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2026-07-18 21:51:37,614 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2026-07-18 21:51:37,614 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2026-07-18 21:51:37,918 DEBG 'start-script' stdout output:

[info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2026-07-18 21:51:37,922 DEBG 'start-script' stdout output:

[info] Successfully generated PIA token for wireguard

2026-07-18 21:51:37,922 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'japan-2.privacy.network'...

2026-07-18 21:53:50,932 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2026-07-18 21:53:50,940 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-07-18 21:53:50,948 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2026-07-18 21:53:50,951 DEBG 'start-script' stderr output:

[#] wg addconf wg0 /dev/fd/63

2026-07-18 21:53:50,952 DEBG 'start-script' stderr output:

Line unrecognized: `PublicKey='

Configuration parsing error

2026-07-18 21:53:50,954 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0

2026-07-18 21:53:51,012 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

2026-07-18 21:54:21,015 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2026-07-18 21:54:21,015 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2026-07-18 21:54:21,023 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-07-18 21:54:21,026 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2026-07-18 21:54:21,027 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2026-07-18 21:54:21,027 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2026-07-18 21:54:21,303 DEBG 'start-script' stdout output:

[info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2026-07-18 21:54:21,306 DEBG 'start-script' stdout output:

[info] Successfully generated PIA token for wireguard

2026-07-18 21:54:21,306 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'japan-2.privacy.network'...

14 hours ago, wgstarks said:

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Docker Run

docker run

-d

--name='binhex-qbittorrentvpn'

--net='bridge'

--pids-limit 2048

--privileged=true

-e TZ="REDACTED"

-e HOST_OS="Unraid"

-e HOST_HOSTNAME="Cormorant"

-e HOST_CONTAINERNAME="binhex-qbittorrentvpn"

-e 'VPN_ENABLED'='yes'

-e 'VPN_USER'='REDACTED'

-e 'VPN_PASS'='REDACTED'

-e 'VPN_PROV'='pia'

-e 'VPN_CLIENT'='openvpn'

-e 'STRICT_PORT_FORWARD'='yes'

-e 'ENABLE_PRIVOXY'='no'

-e 'ENABLE_SOCKS'='no'

-e 'SOCKS_USER'='admin'

-e 'SOCKS_PASS'='socks'

-e 'LAN_NETWORK'='172.16.17.0/24'

-e 'WEBUI_PORT'='7777'

-e 'VPN_INPUT_PORTS'=''

-e 'VPN_OUTPUT_PORTS'=''

-e 'DEBUG'='false'

-e 'WEBUI_PORT'='7777'

-e 'VPN_OPTIONS'=''

-e 'ENABLE_STARTUP_SCRIPTS'='no'

-e 'USERSPACE_WIREGUARD'='no'

-e 'NAME_SERVERS'='1.1.1.1,1.0.0.1'

-e 'ENABLE_HEALTHCHECK'='yes'

-e 'HEALTHCHECK_COMMAND'=''

-e 'HEALTHCHECK_ACTION'=''

-e 'HEALTHCHECK_HOSTNAME'='google.com'

-e 'PUID'='99'

-e 'PGID'='100'

-e 'UMASK'='000'

-l net.unraid.docker.managed=dockerman

-l net.unraid.docker.webui='http://[IP]:[PORT:8080]'

-l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/templates/main/unraid/binhex/images/qbittorrent-icon.png'

-p '8118:8118/tcp'

-p '9118:9118/tcp'

-p '58946:58946/tcp'

-p '58946:58946/udp'

-v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'

-v '/mnt/user/':'/data':'rw'

--sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

7de25104774a79b6d6f7c7057160d6ca93b6f0f5697a6aa1e545b95a19500470

The command finished successfully!

superversiord

2026-07-19 08:32:45,628 INFO reaped unknown pid 70 (terminated by SIGTERM)

2026-07-19 08:32:45,629 WARN received SIGTERM indicating exit request

2026-07-19 08:32:45,629 DEBG killing watchdog-script (pid 417) with signal SIGTERM

2026-07-19 08:32:45,629 INFO waiting for start-script, watchdog-script to die

Catching signal: SIGTERM

Exiting cleanly

2026-07-19 08:32:45,630 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23168571120912 for <Subprocess at 23168571114832 with name watchdog-script in state STOPPING> (stdout)>

2026-07-19 08:32:45,630 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 23168571073216 for <Subprocess at 23168571114832 with name watchdog-script in state STOPPING> (stderr)>

2026-07-19 08:32:45,631 WARN stopped: watchdog-script (exit status 143)

2026-07-19 08:32:45,631 DEBG received SIGCHLD indicating a child quit

2026-07-19 08:32:45,631 DEBG killing start-script (pid 416) with signal SIGTERM

2026-07-19 08:32:46,649 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23168571201184 for <Subprocess at 23168572488880 with name start-script in state STOPPING> (stdout)>

2026-07-19 08:32:46,650 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23168571119952 for <Subprocess at 23168572488880 with name start-script in state STOPPING> (stderr)>

2026-07-19 08:32:46,650 WARN stopped: start-script (terminated by SIGTERM)

2026-07-19 08:32:46,650 DEBG received SIGCHLD indicating a child quit

Created by...

___. .__ .__

\_ |__ |__| ____ | |__ ____ ___ ___

| __ \| |/ \| | \_/ __ \\ \/ /

| \_\ \ | | \ Y \ ___/ > <

|___ /__|___| /___| /\___ >__/\_ \

\/ \/ \/ \/ \/

https://hub.docker.com/u/binhex/

2026-07-19 08:32:54.827532 [info] Host is running unRAID

2026-07-19 08:32:54.855873 [info] System information: Linux 7de25104774a 6.18.38-Unraid #1 SMP PREEMPT_DYNAMIC Mon Jul 6 15:22:03 PDT 2026 x86_64 GNU/Linux

2026-07-19 08:32:54.871519 [info] Image architecture: 'amd64'

2026-07-19 08:32:54.887610 [info] Application name: 'qbittorrentvpn'

2026-07-19 08:32:54.903680 [info] Base image release tag: '2026062801'

2026-07-19 08:32:54.919036 [info] Application image release tag: '5.2.3-1-01'

2026-07-19 08:32:54.962368 [info] PUID defined as '99'

2026-07-19 08:32:55.003810 [info] Executing usermod for PUID '99'...

2026-07-19 08:32:55.423055 [info] usermod completed successfully

2026-07-19 08:32:55.440044 [info] PGID defined as '100'

2026-07-19 08:32:55.524993 [info] Executing groupmod for PGID '100'...

2026-07-19 08:32:56.039910 [info] groupmod completed successfully

2026-07-19 08:32:56.055956 [info] UMASK defined as '000'

2026-07-19 08:32:56.072886 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'

2026-07-19 08:32:56.207724 [info] Deleting files in /tmp (non recursive)...

2026-07-19 08:32:56.272926 [info] VPN_ENABLED defined as 'yes'

2026-07-19 08:32:56.290637 [info] VPN_CLIENT defined as 'openvpn'

2026-07-19 08:32:56.307769 [info] VPN_PROV defined as 'pia'

2026-07-19 08:32:56.369357 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/isle_of_man.ovpn

2026-07-19 08:32:56.417717 [info] VPN remote server(s) defined as 'man.privacy.network,'

2026-07-19 08:32:56.433568 [info] VPN remote port(s) defined as '502,'

2026-07-19 08:32:56.449306 [info] VPN remote protcol(s) defined as 'tcp-client,'

2026-07-19 08:32:56.466399 [info] VPN_DEVICE_TYPE defined as 'tun0'

2026-07-19 08:32:56.483012 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)

2026-07-19 08:32:56.499704 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'

2026-07-19 08:32:56.555231 [info] iptables backend selected: nft

2026-07-19 08:32:57.365652 [info] LAN_NETWORK defined as '172.16.17.0/24'

2026-07-19 08:32:57.385761 [info] LAN_NETWORK exported as '172.16.17.0/24'

2026-07-19 08:32:57.416623 [info] VPN_USER defined as 'REDACTED'

2026-07-19 08:32:57.433691 [info] VPN_PASS defined as 'REDACTED'

2026-07-19 08:32:57.450386 [info] STRICT_PORT_FORWARD defined as 'yes'

2026-07-19 08:32:57.468345 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports

2026-07-19 08:32:57.485145 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports

2026-07-19 08:32:57.502006 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'

2026-07-19 08:32:57.519106 [info] ENABLE_SOCKS defined as 'no'

2026-07-19 08:32:57.536097 [info] ENABLE_PRIVOXY defined as 'no'

2026-07-19 08:32:57.553595 [info] WEBUI_PORT defined as '7777'

2026-07-19 08:32:57.574637 [info] Starting Supervisor...

2026-07-19 08:32:58,901 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing

2026-07-19 08:32:58,901 INFO Set uid to user 0 succeeded

2026-07-19 08:32:58,908 INFO RPC interface 'supervisor' initialized

2026-07-19 08:32:58,909 INFO supervisord started with pid 7

2026-07-19 08:32:59,910 INFO spawned: 'start-script' with pid 416

2026-07-19 08:32:59,911 INFO spawned: 'watchdog-script' with pid 417

2026-07-19 08:32:59,912 INFO reaped unknown pid 8 (exit status 0)

2026-07-19 08:32:59,925 DEBG 'start-script' stdout output:

[info] VPN is enabled, beginning configuration of VPN

2026-07-19 08:32:59,925 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2026-07-19 08:32:59,925 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2026-07-19 08:32:59,928 DEBG 'start-script' stdout output:

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2026-07-19 08:33:00,087 DEBG 'start-script' stdout output:

[info] Adding 172.16.17.0/24 as route via adapter eth0

2026-07-19 08:33:00,087 DEBG 'start-script' stdout output:

[info] ip route defined as follows...

--------------------

2026-07-19 08:33:00,088 DEBG 'start-script' stdout output:

default via 172.17.0.1 dev eth0

172.16.17.0/24 via 172.17.0.1 dev eth0

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.5

local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1

local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1

broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1

local 172.17.0.5 dev eth0 table local proto kernel scope host src 172.17.0.5

broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.5

local ::1 dev lo table local proto kernel metric 0 pref medium

2026-07-19 08:33:00,088 DEBG 'start-script' stdout output:

--------------------

2026-07-19 08:33:00,089 DEBG 'start-script' stdout output:

[info] iptable_mangle support detected, adding fwmark for tables

2026-07-19 08:33:00,161 DEBG 'start-script' stdout output:

[info] iptables defined as follows...

--------------------

2026-07-19 08:33:00,162 DEBG 'start-script' stdout output:

-P INPUT DROP

-P FORWARD DROP

-P OUTPUT DROP

-A INPUT -s 91.90.124.30/32 -i eth0 -j ACCEPT

-A INPUT -s 91.90.124.18/32 -i eth0 -j ACCEPT

-A INPUT -s 91.90.124.48/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT

-A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT

-A INPUT -s 172.64.150.50/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.37.206/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT

-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT

-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A INPUT -s 91.90.124.30/32 -i eth0 -j ACCEPT

-A INPUT -s 91.90.124.18/32 -i eth0 -j ACCEPT

-A INPUT -s 91.90.124.48/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT

-A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT

-A INPUT -s 172.64.150.50/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.37.206/32 -i eth0 -j ACCEPT

-A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT

-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 7777 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --dport 7777 -j ACCEPT

-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A INPUT -i tun0 -j ACCEPT

-A OUTPUT -d 91.90.124.30/32 -o eth0 -j ACCEPT

-A OUTPUT -d 91.90.124.18/32 -o eth0 -j ACCEPT

-A OUTPUT -d 91.90.124.48/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.150.50/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.37.206/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT

-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A OUTPUT -d 91.90.124.30/32 -o eth0 -j ACCEPT

-A OUTPUT -d 91.90.124.18/32 -o eth0 -j ACCEPT

-A OUTPUT -d 91.90.124.48/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.150.50/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.37.206/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 7777 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --sport 7777 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

-A OUTPUT -o tun0 -j ACCEPT

2026-07-19 08:33:00,162 DEBG 'start-script' stdout output:

--------------------

2026-07-19 08:33:00,163 DEBG 'start-script' stdout output:

[info] Starting OpenVPN (non daemonised)...

2026-07-19 08:33:00,625 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 DEPRECATED OPTION: --persist-key option ignored. Keys are now always persisted across restarts.

2026-07-19 08:33:00,626 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (DEFAULT). OpenVPN ignores --cipher for cipher negotiations.

2026-07-19 08:33:00,626 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 WARNING: file 'credentials.conf' is group or others accessible

2026-07-19 08:33:00,626 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 OpenVPN 2.7.5 [git:makepkg/b25bb2a8bda814ed+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jul 1 2026

2026-07-19 08:33:00 library versions: OpenSSL 3.6.3 9 Jun 2026, LZO 2.10

2026-07-19 08:33:00 DCO version: N/A

2026-07-19 08:33:00,626 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2026-07-19 08:33:00,627 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 TCP/UDP: Preserving recently used remote address: [AF_INET]91.90.124.18:502

2026-07-19 08:33:00,627 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 Attempting to establish TCP connection with [AF_INET]91.90.124.18:502

2026-07-19 08:33:00,664 DEBG 'start-script' stdout output:

2026-07-19 08:33:00 TCP connection established with [AF_INET]91.90.124.18:502

2026-07-19 08:33:00 TCPv4_CLIENT link local: (not bound)

2026-07-19 08:33:00 TCPv4_CLIENT link remote: [AF_INET]91.90.124.18:502

2026-07-19 08:33:01,032 DEBG 'start-script' stdout output:

2026-07-19 08:33:01 [douglas403] Peer Connection Initiated with [AF_INET]91.90.124.18:502

2026-07-19 08:33:01,070 DEBG 'start-script' stdout output:

2026-07-19 08:33:01 TUN/TAP device tun0 opened

2026-07-19 08:33:01 tun/tap device [tun0] opened

2026-07-19 08:33:01 net_iface_mtu_set: mtu 1500 for tun0

2026-07-19 08:33:01 net_iface_up: set tun0 up

2026-07-19 08:33:01,070 DEBG 'start-script' stdout output:

2026-07-19 08:33:01 net_addr_v4_add: 10.16.111.42/24 dev tun0

2026-07-19 08:33:01 /root/openvpnup.sh tun0 1500 0 10.16.111.42 255.255.255.0 init

2026-07-19 08:33:01,072 DEBG 'start-script' stdout output:

2026-07-19 08:33:01 Initialization Sequence Completed

2026-07-19 08:33:03,700 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 91.90.124.18 from URL 'http://checkip.amazonaws.com'

2026-07-19 08:33:03,700 DEBG 'start-script' stdout output:

[info] Script started to assign incoming port for 'pia'

2026-07-19 08:33:03,700 DEBG 'start-script' stdout output:

[info] Port forwarding is enabled

[info] Checking endpoint 'man.privacy.network' is port forward enabled...

2026-07-19 08:33:04,735 DEBG 'start-script' stdout output:

[info] PIA endpoint 'man.privacy.network' is in the list of endpoints that support port forwarding shown below:-

2026-07-19 08:33:05,735 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-07-19 08:33:05,735 DEBG 'start-script' stdout output:

[info] yerevan.privacy.network

[info] monaco.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] ua.privacy.network

[info] panama.privacy.network

[info] ca-vancouver.privacy.network

[info] liechtenstein.privacy.network

[info] ca-toronto.privacy.network

[info] kazakhstan.privacy.network

[info] morocco.privacy.network

[info] malta.privacy.network

[info] nl-amsterdam.privacy.network

[info] montenegro.privacy.network

[info] cambodia.privacy.network

[info] bangladesh.privacy.network

[info] srilanka.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] ca-montreal.privacy.network

[info] venezuela.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] de-germany-so.privacy.network

[info] nl-netherlands-so.privacy.network

[info] in.privacy.network

[info] vietnam.privacy.network

[info] cyprus.privacy.network

[info] macau.privacy.network

[info] bahamas.privacy.network

[info] hk.privacy.network

[info] mongolia.privacy.network

[info] man.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] np-nepal-pf.privacy.network

[info] sanjose.privacy.network

[info] pe-peru-pf.privacy.network

[info] ba.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.pvt.site

[info] austria.pvt.site

[info] au-adelaide.pvt.site

[info] au-brisbane.pvt.site

[info] au-melbourne.pvt.site

[info] au-perth.pvt.site

[info] au-sydney.pvt.site

[info] belgium.pvt.site

[info] brazil.pvt.site

[info] bulgaria.pvt.site

[info] ca-ontario.pvt.site

[info] chile.pvt.site

[info] china.pvt.site

[info] colombia.pvt.site

[info] croatia.pvt.site

[info] czech-republic.pvt.site

[info] de-berlin.pvt.site

[info] de-frankfurt.pvt.site

[info] denmark.pvt.site

[info] egypt.pvt.site

[info] es-madrid.pvt.site

[info] es-valencia.pvt.site

[info] estonia.pvt.site

[info] fi-helsinki.pvt.site

[info] france.pvt.site

[info] georgia.pvt.site

[info] greece.pvt.site

[info] greenland.pvt.site

[info] hungary.pvt.site

2026-07-19 08:33:05,736 DEBG 'start-script' stdout output:

[info] iceland.pvt.site

[info] indonesia.pvt.site

[info] ireland.pvt.site

[info] israel.pvt.site

[info] it-milano.pvt.site

[info] jp-tokyo.pvt.site

[info] latvia.pvt.site

[info] lithuania.pvt.site

[info] luxembourg.pvt.site

[info] malaysia.pvt.site

[info] mexico.pvt.site

[info] moldova.pvt.site

[info] new-zealand.pvt.site

[info] nigeria.pvt.site

[info] north-macedonia.pvt.site

[info] norway.pvt.site

[info] philippines.pvt.site

[info] poland.pvt.site

[info] portugal.pvt.site

[info] qatar.pvt.site

[info] romania.pvt.site

[info] saudi-arabia.pvt.site

[info] se-stockholm.pvt.site

[info] serbia.pvt.site

[info] singapore.pvt.site

[info] slovakia.pvt.site

[info] slovenia.pvt.site

[info] south-africa.pvt.site

[info] south-korea.pvt.site

[info] switzerland.pvt.site

[info] taiwan.pvt.site

[info] turkey.pvt.site

[info] uk-london.pvt.site

[info] uk-manchester.pvt.site

[info] uk-southampton.pvt.site

[info] united-arab-emirates.pvt.site

2026-07-19 08:33:06,709 DEBG 'start-script' stdout output:

[info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2026-07-19 08:33:06,711 DEBG 'start-script' stdout output:

[info] Successfully generated PIA token for wireguard

2026-07-19 08:33:07,238 DEBG 'watchdog-script' stdout output:

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.16.111.42 different, marking for reconfigure

2026-07-19 08:33:07,273 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2026-07-19 08:33:07,273 DEBG 'watchdog-script' stdout output:

[info] qBittorrent incoming port 6881 and VPN incoming port 42507 different, marking for reconfigure

2026-07-19 08:33:07,279 DEBG 'watchdog-script' stdout output:

[info] qBittorrent config file already exists, skipping copy

[info] Removing session lock file (if it exists)...

2026-07-19 08:33:07,280 DEBG 'watchdog-script' stdout output:

[info] Removing qbittorrent lock file (if it exists)...

2026-07-19 08:33:07,293 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2026-07-19 08:33:07,449 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

*** Legal Notice ***

qBittorrent is a file sharing program. When you run a torrent, its data will be made available to others by means of upload. Any content you share is your sole responsibility.

If you have read the legal notice, you can use command line option --confirm-legal-notice to suppress this message.

WebUI will be started shortly after internal preparations. Please wait...

2026-07-19 08:33:08,297 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

[info] Waiting for qBittorrent process to start listening on port 7777...

******** Information ********

To control qBittorrent, access the WebUI at: http://localhost:7777

2026-07-19 08:33:19,658 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process listening on port 7777

Thanks, both attached

My Client is on 172.16.17.0/24

My Unraid Server is on 172.16.70.0/24

When I do the container onto the Network Card in my Server, I can access it no problem (in my example 172.16.70.170) but if I do that, apps like Qui can not talk to it when on the same network (in my example 172.16.70.177) due to connection time out. When I do it and Qui on the Docker Bridge, the exact opposite happens, Qui can talk to it no problem but I can not access it anymore from my client. However, I have to use the internal container IP (in my example 172.17.0.5) cause doing localhost:7777 causes a timeout.

I also curld all of the above scenarios and whenever the client or a container cant access qbit, curl fails with a timeout also. And on the opposite, when it works, curl also does

Edited by babyhuehnchen

Argh. Made the mistake of updating my fully working docker container and the update has borked my config :(

Hopefully someone can help me, first part im struggling with is Variable: LAN_NETWORK. I've tried ifconfig eth0 in terminal and get the following, but I don't think there's anything there of use?

Screenshot 2026-07-19 093546.png

5 hours ago, wilekcmc said:

Here is the Docker run file. I hope I did this correctly?

Attach your entire supervisord log from your appdata folder.

4 hours ago, babyhuehnchen said:

When I do the container onto the Network Card in my Server, I can access it no problem (in my example 172.16.70.170) but if I do that, apps like Qui can not talk to it when on the same network (in my example 172.16.70.177) due to connection time out. When I do it and Qui on the Docker Bridge, the exact opposite happens, Qui can talk to it no problem but I can not access it anymore from my client. However, I have to use the internal container IP (in my example 172.17.0.5) cause doing localhost:7777 causes a timeout.

From looking at your docker run command it appears that you haven’t changed the webUI port correctly. You have the variable webUI configured twice and you are missing the port mapping for the new webUI port.

See the documentation- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Scroll down to Q4.

38 minutes ago, wgstarks said:

From looking at your docker run command it appears that you haven’t changed the webUI port correctly. You have the variable webUI configured twice and you are missing the port mapping for the new webUI port.

See the documentation- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Scroll down to Q4.

thanks, i got it working, for some reason it bound Container Port 3 to google.com (???) and after removing and re-adding it again it is now working fine

9 hours ago, wgstarks said:

Hey, thank you! I got past this part.

Stiill have some problems though :(

Problem 1 - My data is stored in /mnt/user/Jellyfin/Shared, I set Path: /data to this location in the config. Now in the WebUI, the client says no files found :/ In the "downloads" tab of options in the WebUI, I have the default path as mnt/Shared...not sure if this is correct based on my data location?

Problem 2 - New torrents willl not download. I've set my VPN (PIA) to wireguard and input/output ports as 1337.

24 minutes ago, ASTM said:

Problem 1

Jellyfin and qbit must use the same /data path (host and container). For example if Jellyfin is using a container path /data with host path /mnt/user/Jellyfin/Shared then qbit must also have the same.

32 minutes ago, ASTM said:

Problem 2

PIA uses port forwarding so no need to set ports.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.