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

1 hour ago, Lacouenne said:
-p '8180:8080/tcp'

Just took a quick look but this may be your issue. I think you meant to map host port 8180 to container port 8180.

  • Replies 5.1k
  • Views 1.1m
  • 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

4 hours ago, wgstarks said:

Just took a quick look but this may be your issue. I think you meant to map host port 8180 to container port 8180.

Everything seemed to be set to 8180 in my Unraid config page for this docker, so I just went the other route, changed another container that was already using 8080, and then set 8080 on qbit, I can get to the login page of qbit now 😅

Not really the way that I like to fix things, but I have so little time to focus on this that I'll take it as a win. Thanks, and maybe see you soon when I'll run into the next issue!

My container is on version 5.1.2. It has shown "Update Available" for the last few weeks but every time I update it, it doesn't actually update. No errors shown on the update screen as it pulls everything.

It runs entirely fine and works great, just never actually updates.

Here is what's running after it successfully pulls the image. (some things redacted)

docker create
  --name='binhex-qbittorrentvpn'
  --net='docker_network'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME=""
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'=''
  -e 'VPN_PASS'=''
  -e 'VPN_PROV'='custom'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'=''
  -e 'NAME_SERVERS'=''
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -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/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/data/downloads/':'/downloads':'rw'
  -v '/mnt/user/data/torrents/':'/data/torrents/':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1"
  --log-opt max-size=50m
  --log-opt max-file=1 'binhex/arch-qbittorrentvpn:latest' 
f572e76cb6c2e0abd23dd077a35c59d2d1dc199861f0fc2c255877c164a17d62

The command finished successfully!

Whelp, here I am again after enabling the VPN. Again, I can't access the WebUI at all.

I had a "the gateway does not support nat-pmp" at first, I recreated a wireguard conf as recommended on another post. And I can't seem to find an error in the log. Is there anything out of the ordinary?

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-11-20 19:08:08.876799 [info] Host is running unRAID
2025-11-20 19:08:08.890080 [info] System information: Linux 336aa7698fe6 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May  3 00:12:52 PDT 2025 x86_64 GNU/Linux
2025-11-20 19:08:08.903155 [info] Image architecture: 'amd64'
2025-11-20 19:08:08.916488 [info] Application name: 'qbittorrentvpn'
2025-11-20 19:08:08.929691 [info] Base image release tag: '2025110901'
2025-11-20 19:08:08.942626 [info] Application image release tag: '5.1.3-1-01'
2025-11-20 19:08:08.958512 [info] PUID defined as '99'
2025-11-20 19:08:08.974480 [info] PGID defined as '100'
2025-11-20 19:08:09.129398 [info] UMASK defined as '000'
2025-11-20 19:08:09.144277 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-20 19:08:09.159647 [info] Deleting files in /tmp (non recursive)...
2025-11-20 19:08:09.177771 [info] VPN_ENABLED defined as 'yes'
2025-11-20 19:08:09.193383 [info] VPN_CLIENT defined as 'wireguard'
2025-11-20 19:08:09.208201 [info] VPN_PROV defined as 'protonvpn'
2025-11-20 19:08:09.226041 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2025-11-20 19:08:09.247284 [info] VPN_REMOTE_SERVER defined as '146.70.198.50'
2025-11-20 19:08:09.262173 [info] VPN_REMOTE_PORT defined as '51820'
2025-11-20 19:08:09.275284 [info] VPN_DEVICE_TYPE defined as 'wg0'
2025-11-20 19:08:09.288421 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2025-11-20 19:08:09.303327 [info] USERSPACE_WIREGUARD defined as 'no'
2025-11-20 19:08:09.319971 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2025-11-20 19:08:09.444037 [info] LAN_NETWORK defined as '192.168.4.0/22'
2025-11-20 19:08:09.464129 [info] LAN_NETWORK exported as '192.168.4.0/22'
2025-11-20 19:08:09.478983 [info] VPN_USER defined as '[email protected]+pmp'
2025-11-20 19:08:09.494155 [info] VPN_PASS defined as 'XXX'
2025-11-20 19:08:09.512406 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2025-11-20 19:08:09.528971 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2025-11-20 19:08:09.545551 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2025-11-20 19:08:09.562291 [info] ENABLE_SOCKS defined as 'no'
2025-11-20 19:08:09.577609 [info] ENABLE_PRIVOXY defined as 'no'
2025-11-20 19:08:09.592754 [info] WEBUI_PORT defined as '8080'
2025-11-20 19:08:09.608244 [info] Starting Supervisor...
2025-11-20 19:08:09,670 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2025-11-20 19:08:09,670 INFO Set uid to user 0 succeeded
2025-11-20 19:08:09,672 INFO RPC interface 'supervisor' initialized
2025-11-20 19:08:09,672 INFO supervisord started with pid 7
2025-11-20 19:08:10,673 INFO spawned: 'start-script' with pid 250
2025-11-20 19:08:10,674 INFO spawned: 'watchdog-script' with pid 251
2025-11-20 19:08:10,674 INFO reaped unknown pid 8 (exit status 0)
2025-11-20 19:08:10,677 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2025-11-20 19:08:10,677 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-20 19:08:10,677 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-20 19:08:10,766 DEBG 'start-script' stdout output:
[info] Adding 192.168.4.0/22 as route via adapter eth0

2025-11-20 19:08:10,766 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2025-11-20 19:08:10,767 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.9 
192.168.4.0/22 via 172.17.0.1 dev eth0 
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.9 dev eth0 table local proto kernel scope host src 172.17.0.9 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.9 
local ::1 dev lo table local proto kernel metric 0 pref medium

2025-11-20 19:08:10,767 DEBG 'start-script' stdout output:
--------------------

2025-11-20 19:08:10,769 DEBG 'start-script' stdout output:
iptable_mangle         12288  1
ip_tables              32768  4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               53248  20 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2025-11-20 19:08:10,769 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2025-11-20 19:08:10,797 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2025-11-20 19:08:10,798 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 146.70.198.50/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 146.70.198.50/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -d 146.70.198.50/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 146.70.198.50/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

2025-11-20 19:08:10,798 DEBG 'start-script' stdout output:
--------------------

2025-11-20 19:08:10,800 DEBG 'start-script' stdout output:
[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2025-11-20 19:08:10,800 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2025-11-20 19:08:10,805 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-11-20 19:08:10,806 DEBG 'start-script' stderr output:
wg-quick: `wg0' is not a WireGuard interface

2025-11-20 19:08:10,806 DEBG 'start-script' stdout output:
[warn] Failed to bring 'down' WireGuard kernel implementation

2025-11-20 19:08:10,806 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-11-20 19:08:10,812 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2025-11-20 19:08:10,817 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-11-20 19:08:10,820 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard

2025-11-20 19:08:10,821 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2025-11-20 19:08:10,822 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2025-11-20 19:08:10,826 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2025-11-20 19:08:10,831 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2025-11-20 19:08:10,831 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2025-11-20 19:08:10,832 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2025-11-20 19:08:10,833 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2025-11-20 19:08:10,834 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-11-20 19:08:10,835 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2025-11-20 19:08:10,836 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2025-11-20 19:08:27,964 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 146.70.198.53 from URL 'http://checkip.amazonaws.com'

2025-11-20 19:08:27,964 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'protonvpn'

2025-11-20 19:08:27,965 DEBG 'start-script' stdout output:
[info] Successfully brought Wireguard interface 'up'

2025-11-20 19:08:29,996 DEBG 'start-script' stdout output:
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.2.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : 146.70.198.53
epoch = 1203258
closenatpmp() returned 0 (SUCCESS)

2025-11-20 19:08:30,960 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.2.0.2 different, marking for reconfigure

2025-11-20 19:08:30,962 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2025-11-20 19:08:30,962 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 38656 different, marking for reconfigure

2025-11-20 19:08:30,963 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy

2025-11-20 19:08:30,963 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2025-11-20 19:08:30,978 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2025-11-20 19:08:30,981 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...


*** 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...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080
The WebUI administrator username is: XXX
The WebUI administrator password was not set. A temporary password is provided for this session: XXX
You should set your own password in program preferences.
2025-11-20 19:08:31,087 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080
9 hours ago, Lacouenne said:
To control qBittorrent, access the WebUI at: http://localhost:8080
The WebUI administrator username is: XXX
The WebUI administrator password was not set. A temporary password is provided for this session: XXX
You should set your own password in program preferences.
2025-11-20 19:08:31,087 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

This may be your issue. Are you using the temporary password that you redacted?

2 hours ago, wgstarks said:

This may be your issue. Are you using the temporary password that you redacted?

The webpage isn't loading at all

image.png

3 minutes ago, Lacouenne said:

The webpage isn't loading at all

And you are accessing from LAN?

4 hours ago, wgstarks said:

And you are accessing from LAN?

Yes, from my home network. Same as I was testing when VPN was off

If you can access the GUI with VPN set to Off but not when it’s On that usually suggests that either the LAN Network is misconfigured in the docker or you are connecting from something other than LAN (guest network, WiFi network, IoT network, etc). What is the IP you are connecting from?

Oh ok so how it looks exactly:

Internet router --LAN--> Unraid server
Internet router --LAN--> EERO Wifi AP --WiFi--> Laptop

I'm trying to connect through my laptop. Which IP do you need? Local? Of which device?

Edited by Lacouenne

The laptop IP.

Local is inet 192.168.4.85

That’s the right network. Afraid I’m out of ideas.

Wizards of digitry....

I am flummoxed. I cannot figure out what I do that fixed a problem that seems to be happening when I restart my server or complete a firmware update. Both scenarios. Here's what I have...

UNRAID v.7.2.2

Running binhex-qbittorrentvpn with PIA and Privoxy enabled (has worked, does work most of the time)

I am unable to access the WebGUI with vpn enabled after restarting the server with our without a firmware update. Logs do not show any errors. I get the usually connections and resolutions I would expect. But GUI no Loady.

When I deactivate the VPN and set enabled to No, I can log in just fine as expected. I have restarted the Server, my PC, the network. No joy. I know I have fixed this before, and most recently it was last week it "fixed itself". But I have no idea why it is happening on restarts, what I am doing to fix it, or how to prevent it going forward.

I tried removing the images, and using their templates.

I replaced the ovpn files with new ones from PIA.

Using port 8210 and have a WebUI_Port Variable setup and the Web Interface Port configured as well.

Have the Lan_Network set to 192.168.0.0/22

HAve this in Extra Parameters: --sysctl="net.ipv4.conf.all.src_valid_mark=1"

No Input Or Output ports listed either.

Debug set to true

At a loss on this and could use some assistance. What other information can I provide for anyone to see what I am not?

Maybe something to do with Tailscale? Using local IP to access qbittorrent while local PC as part of Tailnet? How would rebooting and firmware changes affect both devices on the same Tailnet? Currently both IPs (local IP and Tailnet IP with the port work to access the WebGUI. But I have no idea what I did to make it work.

Also, updated the container to pull the :latest image. Running qBittorrent v5.1.4 WebUI (64-bit)

Edited by danimal_0119

On 11/21/2025 at 4:15 AM, Lacouenne said:

Whelp, here I am again after enabling the VPN. Again, I can't access the WebUI at all.

I had a "the gateway does not support nat-pmp" at first, I recreated a wireguard conf as recommended on another post. And I can't seem to find an error in the log. Is there anything out of the ordinary?

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-11-20 19:08:08.876799 [info] Host is running unRAID
2025-11-20 19:08:08.890080 [info] System information: Linux 336aa7698fe6 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May  3 00:12:52 PDT 2025 x86_64 GNU/Linux
2025-11-20 19:08:08.903155 [info] Image architecture: 'amd64'
2025-11-20 19:08:08.916488 [info] Application name: 'qbittorrentvpn'
2025-11-20 19:08:08.929691 [info] Base image release tag: '2025110901'
2025-11-20 19:08:08.942626 [info] Application image release tag: '5.1.3-1-01'
2025-11-20 19:08:08.958512 [info] PUID defined as '99'
2025-11-20 19:08:08.974480 [info] PGID defined as '100'
2025-11-20 19:08:09.129398 [info] UMASK defined as '000'
2025-11-20 19:08:09.144277 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-20 19:08:09.159647 [info] Deleting files in /tmp (non recursive)...
2025-11-20 19:08:09.177771 [info] VPN_ENABLED defined as 'yes'
2025-11-20 19:08:09.193383 [info] VPN_CLIENT defined as 'wireguard'
2025-11-20 19:08:09.208201 [info] VPN_PROV defined as 'protonvpn'
2025-11-20 19:08:09.226041 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2025-11-20 19:08:09.247284 [info] VPN_REMOTE_SERVER defined as '146.70.198.50'
2025-11-20 19:08:09.262173 [info] VPN_REMOTE_PORT defined as '51820'
2025-11-20 19:08:09.275284 [info] VPN_DEVICE_TYPE defined as 'wg0'
2025-11-20 19:08:09.288421 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2025-11-20 19:08:09.303327 [info] USERSPACE_WIREGUARD defined as 'no'
2025-11-20 19:08:09.319971 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2025-11-20 19:08:09.444037 [info] LAN_NETWORK defined as '192.168.4.0/22'
2025-11-20 19:08:09.464129 [info] LAN_NETWORK exported as '192.168.4.0/22'
2025-11-20 19:08:09.478983 [info] VPN_USER defined as '[email protected]+pmp'
2025-11-20 19:08:09.494155 [info] VPN_PASS defined as 'XXX'
2025-11-20 19:08:09.512406 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2025-11-20 19:08:09.528971 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2025-11-20 19:08:09.545551 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2025-11-20 19:08:09.562291 [info] ENABLE_SOCKS defined as 'no'
2025-11-20 19:08:09.577609 [info] ENABLE_PRIVOXY defined as 'no'
2025-11-20 19:08:09.592754 [info] WEBUI_PORT defined as '8080'
2025-11-20 19:08:09.608244 [info] Starting Supervisor...
2025-11-20 19:08:09,670 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2025-11-20 19:08:09,670 INFO Set uid to user 0 succeeded
2025-11-20 19:08:09,672 INFO RPC interface 'supervisor' initialized
2025-11-20 19:08:09,672 INFO supervisord started with pid 7
2025-11-20 19:08:10,673 INFO spawned: 'start-script' with pid 250
2025-11-20 19:08:10,674 INFO spawned: 'watchdog-script' with pid 251
2025-11-20 19:08:10,674 INFO reaped unknown pid 8 (exit status 0)
2025-11-20 19:08:10,677 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2025-11-20 19:08:10,677 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-20 19:08:10,677 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-20 19:08:10,766 DEBG 'start-script' stdout output:
[info] Adding 192.168.4.0/22 as route via adapter eth0

2025-11-20 19:08:10,766 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2025-11-20 19:08:10,767 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.9 
192.168.4.0/22 via 172.17.0.1 dev eth0 
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.9 dev eth0 table local proto kernel scope host src 172.17.0.9 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.9 
local ::1 dev lo table local proto kernel metric 0 pref medium

2025-11-20 19:08:10,767 DEBG 'start-script' stdout output:
--------------------

2025-11-20 19:08:10,769 DEBG 'start-script' stdout output:
iptable_mangle         12288  1
ip_tables              32768  4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               53248  20 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2025-11-20 19:08:10,769 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2025-11-20 19:08:10,797 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2025-11-20 19:08:10,798 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 146.70.198.50/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 146.70.198.50/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -d 146.70.198.50/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 146.70.198.50/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

2025-11-20 19:08:10,798 DEBG 'start-script' stdout output:
--------------------

2025-11-20 19:08:10,800 DEBG 'start-script' stdout output:
[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2025-11-20 19:08:10,800 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2025-11-20 19:08:10,805 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-11-20 19:08:10,806 DEBG 'start-script' stderr output:
wg-quick: `wg0' is not a WireGuard interface

2025-11-20 19:08:10,806 DEBG 'start-script' stdout output:
[warn] Failed to bring 'down' WireGuard kernel implementation

2025-11-20 19:08:10,806 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-11-20 19:08:10,812 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2025-11-20 19:08:10,817 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-11-20 19:08:10,820 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard

2025-11-20 19:08:10,821 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2025-11-20 19:08:10,822 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2025-11-20 19:08:10,826 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2025-11-20 19:08:10,831 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2025-11-20 19:08:10,831 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2025-11-20 19:08:10,832 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2025-11-20 19:08:10,833 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2025-11-20 19:08:10,834 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-11-20 19:08:10,835 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2025-11-20 19:08:10,836 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2025-11-20 19:08:27,964 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 146.70.198.53 from URL 'http://checkip.amazonaws.com'

2025-11-20 19:08:27,964 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'protonvpn'

2025-11-20 19:08:27,965 DEBG 'start-script' stdout output:
[info] Successfully brought Wireguard interface 'up'

2025-11-20 19:08:29,996 DEBG 'start-script' stdout output:
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.2.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : 146.70.198.53
epoch = 1203258
closenatpmp() returned 0 (SUCCESS)

2025-11-20 19:08:30,960 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.2.0.2 different, marking for reconfigure

2025-11-20 19:08:30,962 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2025-11-20 19:08:30,962 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 38656 different, marking for reconfigure

2025-11-20 19:08:30,963 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy

2025-11-20 19:08:30,963 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2025-11-20 19:08:30,978 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2025-11-20 19:08:30,981 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...


*** 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...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080
The WebUI administrator username is: XXX
The WebUI administrator password was not set. A temporary password is provided for this session: XXX
You should set your own password in program preferences.
2025-11-20 19:08:31,087 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

You're running 5.1.3-1-01 that was buggy due to Qbittorrent.
Try RELEASETAG=5.1.4-1-01 instead or latest.....

5 hours ago, Rikul said:

You're running 5.1.3-1-01 that was buggy due to Qbittorrent.
Try RELEASETAG=5.1.4-1-01 instead or latest.....

Tried to add this as a variable in the docker config of binhex-qbit, but it's still using 5.1.3. What am I missing?

Can't access WebUI. PIA VPN. Long time user of an older container which started having the issue, installed this newer binhex version to troubleshoot and have the same issue. WebUI works when VPN_ENABLED='no', which makes me think it's a VPN connection issue.

Changed VPN password, verified credentials on other devices, changed OpenVPN files. Looking for options here. Thanks!

supervisord.logdocker run.txt

EDIT: I am using Tailscale on the server but not in the container. I keep getting an activity timeout from the VPN server every minute, and the process seems to restart:

2025-12-01 11:22:43,314 DEBG 'start-script' stdout output:

2025-12-01 11:22:43 [UNDEF] Inactivity timeout (--ping-restart), restarting

2025-12-01 11:22:43,314 DEBG 'start-script' stdout output:

2025-12-01 11:22:43 SIGHUP[soft,ping-restart] received, process restarting

Edited by Andiroo2
updated supervisor.d file

2 minutes ago, Andiroo2 said:

Can't access WebUI. PIA VPN. Long time user of an older container which started having the issue, installed this newer binhex version to troubleshoot and have the same issue. WebUI works when VPN_ENABLED='no', which makes me think it's a VPN connection issue.

Changed VPN password, verified credentials on other devices, changed OpenVPN files. Looking for options here. Thanks!

supervisord.logdocker run.txt

I just had the same issue. The VPN was not connecting or connecting inconsistently. Are you running Tailscale? I found it I had an advertised route that was messing things up.

Just now, danimal_0119 said:

I just had the same issue. The VPN was not connecting or connecting inconsistently. Are you running Tailscale? I found it I had an advertised route that was messing things up.

Yes, I use Tailscale baked into Unraid to access my server remotely. I don’t want to turn this off for fear of losing access while troubleshooting.

EDIT to add, I am NOT using Tailscale in the Docker container.

Edited by Andiroo2

Same here, using Tailscale in Unraid, not in Docker.
Is it possible to disable it for a moment and see if things are running better? I don't have access to my server for a couple days 😬

I am local to my machine, but I also use Teamviewer to remotely access a machine that is local if I ever lose connectivity and am remote. If you depend on Tailscale for access, I wouldn't attempt to bring it down until you are on the same network to avoid disconnection.

I'm sure there is a better expert to explain but in UnRaid, once you add the App using the built in app (not the docker) you have to run the Tailscale Up command with a couple flags depending on your setup. Then approve it in the Admin panel in Tailscale. What I found was Tailscale wasn't configured properly (pretty sure I over engineered the "Up" command with some flags I didn't need). In my case, I had too many things. The one that worked for me... so far ... was...
tailscale up --reset --advertise-routes=192.168.0.0/22

This is advertising my router subnet. Now, I can access any LAN or the IP of the Tailscale page. For example, I can access the same applications in the following scenarios:

  1. On the same WiFi with Tailscale ON - 192.168.0.2:1111 & 100.1.1.3:1111 pull up the same page

  2. When outside the network - with Tailscale ON - 192.168.0.2:1111 & 100.1.1.3:1111 pull up the same page

  3. On the same WifFi with Tailscale OFF - only 192.168.0.2:1111 works

  4. When outside the network - with Tailscale OFF - neither works

To achieve this, I basically, used the command above to reset all the exit-nodes and other garbage I initially configured. Then had to blow away the QbitVPN container and pretty much resurrect it from scratch. Not just Stop it and Restart. Something got out of whack between the two things and the subnet routing. I also had to make sure each client checked the box for "Allow LAN Access" and the check boxes for Use Tailscale DNS and Tailscale subnets were checked as well. I also turned on Magic DNS in the Admin Panel of Tailscale on their website.

Again, I am not an engineer but like most, just know enough to keep learning and have been working on this for a couple weeks to triage.

Edited by danimal_0119

46 minutes ago, Lacouenne said:

Same here, using Tailscale in Unraid, not in Docker.
Is it possible to disable it for a moment and see if things are running better? I don't have access to my server for a couple days 😬

I just went to the house, got on local network, disabled Tailscale in Unraid, restarted docker containers, same issue.

As I was walking back I thought, maybe I should have rebooted the server with Tailscale disabled before trying again…I will try this next time I am back at the house.

For me... Restarting the container did not do it. I had to remove it completely with the image, then use the template to bring it back AFTER I reset tailscale. Again, I have no idea what this did or how it worked, but I am now about a week or two with no issues with the GUI for Qbit or Tailscale.

11 hours ago, Andiroo2 said:

Can't access WebUI. PIA VPN.

We’ll, one of my older qbit instances just started working again like nothing happened. No additional lines in the logs. Other instances are still down. It’s got to be an issue connecting to VPN somewhere.

Been working on this one all day. Still no progress. I have gone through all 30 FAQs and added/removed/updated things to no avail. I can’t explain why one container works and another does not. The minute i disable VPN_ENABLED, it works immediately.

Could there be an issue with PIA? Keep in mind this is affecting my binhex and non-binhex qbit containers (except one that inexplicably started working??)…

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.