Same issue as well, cant access the GUI.

I have tried all the above suggested fixes with no improvement.

All the log shows its connected to PIA VPN Network, however nothing works - no GUI and no communication to other dockers like Radarr and Sonarr :(

In the same boat as well. All the fixes tried, no access to GUI.

18 hours ago, wgstarks said:

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

also having the no web gui issues, rolling back to older container did not help. supervisord.log

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='redacted'
  -e 'VPN_PASS'='redacted'
  -e 'VPN_PROV'='protonvpn'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.1.0/24, 10.253.0.0/24'
  -e 'WEBUI_PORT'='8080'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -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/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '8080:8080/tcp'
  -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/media/':'/data':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:5.2.0-1-05'

292561549a997af18c054c4355bff0a0da76faf2f17b7d4cc86116fba2dc2540

The command finished successfully!

Hi, I have been getting startup problem with the latest image since 2 days ago as well. I can't reach the Web UI unless I disable the VPN. I have attached the docker run command and supervisord.log below. I hope they will help with diagnosing.

docker run
  -d
  --name='qbittorrent'
  --net='bridge'
  --cpuset-cpus='1,2,3'
  --pids-limit 2048
  --privileged=true
  -e TZ="Asia/Tokyo"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="qbittorrent"
  -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 'WEBUI_PORT'='31000'
  -e 'LAN_NETWORK'='52.46.69.0/24'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'VPN_OPTIONS'=''
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:31000]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '31001:6881/tcp'
  -p '31001:6881/udp'
  -p '31002:8118/tcp'
  -p '31000:31000/tcp'
  -p '8080:8080/tcp'
  -p '9118:9118/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/Flowy/':'/media':'rw'
  -v '/mnt/user/appdata/qbittorrent':'/config':'rw'
  -v '/mnt/user/Flowy/':'/data':'rw'
  -v '/mnt/user/Torrent/':'/incomplete':'rw'
  -v '/mnt/user/Torrent/':'/cache':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1"
  -m 4G
  --log-driver syslog
  --log-opt syslog-address=udp://127.0.0.1:541
  --health-interval=60m 'binhex/arch-qbittorrentvpn:latest'

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
fbbc01d550b5c8f1b6d9af0a8f814bc82e547fb7ac957bda12323f40e3778bd8

The command finished successfully!

supervisord.log

I had the same issue in local to access GUI : but its was ok from internet
I add in config file : qBittorrent.conf
WebUI\HostHeaderValidation=false
maybe this can help ?

Edited May 8May 8 by Lemars

6 hours ago, Kagoromo said:

 -e 'LAN_NETWORK'='52.46.69.0/24'

I highly doubt that is your lan network right?, that is not in the reserved ranges (192.168.x.x, 172 etc etc).

in any case from your log:

2026-05-08 11:20:32,573 DEBG 'start-script' stdout output:

2026-05-08 11:20:32 UDPv4 link local: (not bound)

2026-05-08 11:20:32 UDPv4 link remote: [AF_INET]104.19.240.167:1198

2026-05-08 11:21:33,054 DEBG 'start-script' stdout output:

2026-05-08 11:21:33 [UNDEF] Inactivity timeout (--ping-restart), restarting

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

6 hours ago, Chris238 said:

also having the no web gui issues, rolling back to older container did not help

from your log:

2026-05-07 19:00:21.175408 [info] VPN_REMOTE_SERVER defined as '104.234.212.26'

Hard coding ip endpoints is NEVER a good idea!, most probably that endpoint is shutdown or having issues, switch to a named endpoint such as nl-amsterdam.privacy.network will probably get you going.
FYI - want to see an up to date list of all endpoints?, look at my live gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

21 hours ago, tnig said:

In the same boat as well. All the fixes tried, no access to GUI.

no logs, no fix:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

On 5/7/2026 at 8:34 AM, METAL13 said:

Same issue as well, cant access the GUI.

I have tried all the above suggested fixes with no improvement.

All the log shows its connected to PIA VPN Network, however nothing works - no GUI and no communication to other dockers like Radarr and Sonarr :(

no logs, no fix:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

On 5/6/2026 at 6:11 PM, deeveeance said:

My GUI is still unaccessible. Tried rolling back both Unraid OS and container, lockfile delete, ensuring ports are entered correctly, everything short of voodoo.

What files/text do I need to copy paste here for some help?

no logs, no fix:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

57 minutes ago, binhex said:

I highly doubt that is your lan network right?, that is not in the reserved ranges (192.168.x.x, 172 etc etc).

in any case from your log:

2026-05-08 11:20:32,573 DEBG 'start-script' stdout output:

2026-05-08 11:20:32 UDPv4 link local: (not bound)

2026-05-08 11:20:32 UDPv4 link remote: [AF_INET]104.19.240.167:1198

2026-05-08 11:21:33,054 DEBG 'start-script' stdout output:

2026-05-08 11:21:33 [UNDEF] Inactivity timeout (--ping-restart), restarting

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

It is actually my LAN network I chose that precisely to avoid ambiguity with the typical LAN IP ranges like 192.168.x.x.

Thank you for pointing out the relevant FAQ, I will give that a try.

Edit: Yeah that was it, the PIA server I was using wasn't available anymore it seems. I edited the ovpn file to point to a different server and now it works again.

Edited May 8May 8 by Kagoromo

7 hours ago, binhex said:

from your log:

2026-05-07 19:00:21.175408 [info] VPN_REMOTE_SERVER defined as '104.234.212.26'

Hard coding ip endpoints is NEVER a good idea!, most probably that endpoint is shutdown or having issues, switch to a named endpoint such as nl-amsterdam.privacy.network will probably get you going.
FYI - want to see an up to date list of all endpoints?, look at my live gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

I'm using protonvpn not pia and it seems like they disabled named servers a while ago from a quick search https://share.google/aimode/cFM4JynEzuxhUg9dV. I had been using the wireguard configuration they provided for a long time now, did something change where this no longer works? I also tried another configuration file but got the same result

Edited May 8May 8 by Chris238
typo

Also, where is this lockfile people are mentioning? I don't see it anywhere within my appdata folder

docker run

-d

--name='binhex-qbittorrentvpn'

--net='bridge'

--cpuset-cpus='0,1,2,3,4,5,6,7,8,9,10,11'

--pids-limit 2048

--privileged=true

-e TZ="America/New_York"

-e HOST_OS="Unraid"

-e HOST_HOSTNAME="Server"

-e HOST_CONTAINERNAME="binhex-qbittorrentvpn"

-e 'VPN_ENABLED'='yes'

-e 'VPN_USER'='REDACTED'

-e 'VPN_PASS'='REDACTED

-e 'VPN_PROV'='pia'

-e 'VPN_CLIENT'='wireguard'

-e 'STRICT_PORT_FORWARD'='yes'

-e 'ENABLE_PRIVOXY'='yes'

-e 'ENABLE_SOCKS'='no'

-e 'SOCKS_USER'='admin'

-e 'SOCKS_PASS'='socks'

-e 'LAN_NETWORK'='192.168.1.0/24'

-e 'WEBUI_PORT'='8080'

-e 'VPN_INPUT_PORTS'=''

-e 'VPN_OUTPUT_PORTS'=''

-e 'DEBUG'='true'

-e 'VPN_OPTIONS'=''

-e 'ENABLE_STARTUP_SCRIPTS'='no'

-e 'USERSPACE_WIREGUARD'='no'

-e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'

-e 'PUID'='99'

-e 'PGID'='100'

-e 'UMASK'='022'

-l net.unraid.docker.managed=dockerman

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

-l net.unraid.docker.icon=''

-p '8080:8080/tcp'

-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/maindata':'/data':'rw'

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

b6e6f1f680ec3346afaaf3ba798ae3424f7d1be18fbd8fecd239592cb51def61

The command finished successfully!

supervisord.log

@tnig

Your log shows a successful start followed by a manual shutdown. Are you attempting to access the GUI from another machine on the same LAN network?

Attempting to access it over Tailscale (WAN). I have no LAN access to the Unraid server at the moment. Other docker apps are accessible.

Edited May 9May 9 by tnig

1 hour ago, tnig said:

Attempting to access it over Tailscale (WAN). I have no LAN access to the Unraid server at the moment. Other docker apps are accessible.

You need to add the Tailscale network to the LAN_NETWORK setting. Comma separated. The UI can only be accessed from networks defined in that setting.

Edited May 9May 9 by wgstarks

That worked, never had to do that before but it makes sense. Thank you very much!

Does it works version 5.2 ?

9 minutes ago, Lemars said:

Does it works version 5.2 ?

I haven’t had any issues.

I have the same issue with v5.2 :
[crit] iptables default policies not available, exiting script...

iptables v1.8.13 (nf_tables): Could not fetch rule set generation id: Invalid argument

# Warning: iptables-legacy tables present, use iptables-legacy to see them

On 5/8/2026 at 4:59 PM, binhex said:

no logs, no fix:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

On 5/8/2026 at 4:58 PM, binhex said:

no logs, no fix:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

As requested, see attached.

Command Execution - METAL13.txt supervisord METAL13.log

12 minutes ago, METAL13 said:

As requested, see attached.

Command Execution - METAL13.txt supervisord METAL13.log

From your log: '2026-05-11 17:30:49 [UNDEF] Inactivity timeout (--ping-restart), restarting'

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Do we still have to use arch-qbittorrentvpn:libtorrentv1 these days?

I don't even remember what was fixed by using the libtorrentv1 version. My Qbittorrent container shows it using version 4.6.3.

If I don't need to use the libtorrentv1 version, can I just go to the latest without changing my appdata?

Then again, if it's not broken, don't fix it?