9 minutes ago, cprn.1337 said:

binhex/arch-qbittorrentvpn:latest or 5.2 is broken, had to downgrade to binhex/arch-qbittorrentvpn:5.1

Same here. Most recent Unraid version, had no issues prior to this mornings update. VPN and other containers connected through QB appear to work but the web GUI can't be accessed. Looking through the logs it stopped at this entry, everything else appeared normal:

Waiting for qBittorrent process to start listening on port 8080...

Manually changing the repository to ghcr.io/binhex/arch-qbittorrentvpn:5.1.4-2-01 resolved the error and GUI is accessible.

17 minutes ago, cprn.1337 said:

binhex/arch-qbittorrentvpn:latest or 5.2 is broken, had to downgrade to binhex/arch-qbittorrentvpn:5.1

Yeah, I had the same issue :

- qBittorrent process starts but never finishes listening on port 8080

- WebUI completely inaccessible

- Watchdog loops indefinitely on "Waiting for qBittorrent process to start listening on port 8080..."

- No explicit error in logs, silent crash

Workaround: delete the lockfile in the conf folder. But this issue appear after every container restart. The lockfile is not deleted when the container shutdown or restart

Edited May 4May 4 by unraid.even992

Exacrtly the same here, never gets past the 'Waiting for qBittorrent process to start listening on port xxxx' message. All was fine until today's update and now it's dead.

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

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

2026-05-04 14:26:23,427 DEBG 'watchdog-script' stdout output:

[info] qBittorrent config file already exists, skipping copy

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

2026-05-04 14:26:23,449 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2026-05-04 14:26:23,452 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

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

Then nothing, it just sits there, no further updates appear in the log.

36 minutes ago, Azzazeal said:

Exacrtly the same here, never gets past the 'Waiting for qBittorrent process to start listening on port xxxx' message. All was fine until today's update and now it's dead.

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

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

2026-05-04 14:26:23,427 DEBG 'watchdog-script' stdout output:

[info] qBittorrent config file already exists, skipping copy

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

2026-05-04 14:26:23,449 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2026-05-04 14:26:23,452 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

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

Then nothing, it just sits there, no further updates appear in the log.

same

1 hour ago, Azzazeal said:

Exacrtly the same here, never gets past the 'Waiting for qBittorrent process to start listening on port xxxx' message. All was fine until today's update and now it's dead.

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2026-05-04 14:26:23,426 DEBG 'watchdog-script' stdout output:

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

2026-05-04 14:26:23,427 DEBG 'watchdog-script' stdout output:

[info] qBittorrent config file already exists, skipping copy

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

2026-05-04 14:26:23,449 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2026-05-04 14:26:23,452 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

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

Then nothing, it just sits there, no further updates appear in the log.

Tell a lie, if you wait long enough, every 10 mins you get this...

2026-05-04 14:44:09,924 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

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

2026-05-04 14:54:09,957 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:04:10,089 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:14:10,224 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:24:10,356 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:34:10,492 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:44:10,624 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-04 15:54:10,760 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

same for me as everyone posting above and using this repository

binhex/arch-qbittorrentvpn

Can confirm this workaround works for me - Thanks @unraid.even992 !!

Workaround: delete the lockfile in the conf folder. But this issue appear after every container restart. The lockfile is not deleted when the container shutdown or restart

Edited May 4May 4 by kingfenix

Even after deleting the lockfile to get things running, it seems to consume more CPU than usual.
It has one of my cores pinned.

Might roll back until this gets sorted.

Encountered the same errors myself this morning, rolled back one version and it is back up and running.

Yeah 5.2 is busted at least with the latest unraid version. 5.1.4-2-01 works fine

2 hours ago, DaWord2011 said:

Encountered the same errors myself this morning, rolled back one version and it is back up and running.

15 minutes ago, UnJustice said:

Yeah 5.2 is busted at least with the latest unraid version. 5.1.4-2-01 works fine

on it guys, the below does seem to be the fix, confirmed building a new image right now...

6 hours ago, unraid.even992 said:

Workaround: delete the lockfile in the conf folder. But this issue appear after every container restart. The lockfile is not deleted when the container shutdown or restart

15 minutes ago, binhex said:

confirmed building a new image right now...

ok and it's built, please do a 'force update' to ensure you pull down the 'latest' tagged image.

latest build fixes it. Thanks binhex.

latest build did resolve my error

thanks for the quick fix binhex

Thanks for the quick update. Just to confirm, does this fix both the issues encountered with unraid 7.2.5 and qbit moving to 5.2.0 or just the latter?

Morning all, I'm having a different issue after upgrading to the latest version, please see error below. I haven't run this update on my unRAID server, this is from my Synology NAS from Portainer:

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

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

2026-05-05 09:41:07.267129 [crit] iptables default policies not available, exiting script...

If I install to a new folder, I get the same error. The container keeps restarting.

Edited May 5May 5 by sv000008

On 5/3/2026 at 12:05 AM, JBanner said:

-p '58946:000/tcp'

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

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

-v '/mnt/user/binhex-shared/':'/shared':'rw'

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

docker: Error response from daemon: invalid port specification: "0/tcp"

red text is the problem here, so you have an invalid port defined, '0000' is not a valid port, delete that from your container and re-add the port, host and container side set to 58946, please note this port is NOT used if you have vpn_enabled set to yes, so you can simply delete it as another option.

23 minutes ago, sv000008 said:

Morning all, I'm having a different issue after upgrading to the latest version, please see error below. I haven't run this update on my unRAID server, this is from my Synology NAS from Portainer:

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

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

2026-05-05 09:41:07.267129 [crit] iptables default policies not available, exiting script...

If I install to a new folder, I get the same error. The container keeps restarting.

do a google search for 'synology (nf_tables): Could not fetch rule set generation id: Invalid argument' the AI generated result (top of the results) will tell you what to do.

1 hour ago, binhex said:

do a google search for 'synology (nf_tables): Could not fetch rule set generation id: Invalid argument' the AI generated result (top of the results) will tell you what to do.

Thank you, didn't consider that it could be a Synology issue.

Update: The solution I found is to force legacy iptables withing the container. Unfortunately, the container restarts once that error is displayed and I cannot access the container console long enough to make the changes. I have reverted to version 5.1.4-2-01 for now.

Edited May 5May 5 by sv000008

4 hours ago, binhex said:

do a google search for 'synology (nf_tables): Could not fetch rule set generation id: Invalid argument' the AI generated result (top of the results) will tell you what to do.

3 hours ago, sv000008 said:

Thank you, didn't consider that it could be a Synology issue.

Update: The solution I found is to force legacy iptables withing the container. Unfortunately, the container restarts once that error is displayed and I cannot access the container console long enough to make the changes. I have reverted to version 5.1.4-2-01 for now.

Had to make a script that does this on my QNAP:

#!/bin/bash
yes|pacman -S iptables-legacy
mv /usr/bin/nft /usr/bin/nft.disabled 2>/dev/null || true

But also had to change the container command in docker-compose to this because the ENABLE_STARTUP_SCRIPTS hook runs after the VPN/iptables setup:

command: ["/bin/bash", "-c", "/config/scripts/iptables-legacy.sh && init.sh"]

Hello, I can't connect via vpn. I'm using PIA. I have Unraid virtualized in proxmox. My router is pfsense. Can you check the logs for me. Thanks

2026-05-05 19:22:35,796 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2026-05-05 19:22:35,945 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 DEPRECATED OPTION: --persist-key option ignored. Keys are now always persisted across restarts. 

2026-05-05 19:22:35,947 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (DEFAULT). OpenVPN ignores --cipher for cipher negotiations. 

2026-05-05 19:22:35,948 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 WARNING: file 'credentials.conf' is group or others accessible
2026-05-05 19:22:35 OpenVPN 2.7.0 [git:makepkg/ee1577744fb09af7+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Feb 11 2026
2026-05-05 19:22:35 library versions: OpenSSL 3.6.1 27 Jan 2026, LZO 2.10

2026-05-05 19:22:35,948 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 DCO version: N/A

2026-05-05 19:22:35,950 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2026-05-05 19:22:35,953 DEBG 'start-script' stdout output:
2026-05-05 19:22:35 TCP/UDP: Preserving recently used remote address: [AF_INET]172.64.150.50:1198
2026-05-05 19:22:35 UDPv4 link local: (not bound)
2026-05-05 19:22:35 UDPv4 link remote: [AF_INET]172.64.150.50:1198

2026-05-05 19:23:36,013 DEBG 'start-script' stdout output:
2026-05-05 19:23:36 [UNDEF] Inactivity timeout (--ping-restart), restarting
2026-05-05 19:23:36 SIGHUP[soft,ping-restart] received, process restarting

2026-05-05 19:23:36,017 DEBG 'start-script' stdout output:
2026-05-05 19:23:36 DEPRECATED OPTION: --persist-key option ignored. Keys are now always persisted across restarts. 

2026-05-05 19:23:36,021 DEBG 'start-script' stdout output:
2026-05-05 19:23:36 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (DEFAULT). OpenVPN ignores --cipher for cipher negotiations. 

2026-05-05 19:23:36,024 DEBG 'start-script' stdout output:
2026-05-05 19:23:36 WARNING: file 'credentials.conf' is group or others accessible
2026-05-05 19:23:36 OpenVPN 2.7.0 [git:makepkg/ee1577744fb09af7+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Feb 11 2026

2026-05-05 19:23:36,024 DEBG 'start-script' stdout output:
2026-05-05 19:23:36 library versions: OpenSSL 3.6.1 27 Jan 2026, LZO 2.10
2026-05-05 19:23:36 DCO version: N/A

2026-05-05 19:23:38,024 DEBG 'start-script' stdout output:
2026-05-05 19:23:38 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2026-05-05 19:23:38,025 DEBG 'start-script' stdout output:
2026-05-05 19:23:38 TCP/UDP: Preserving recently used remote address: [AF_INET]104.18.37.206:1198
2026-05-05 19:23:38 UDPv4 link local: (not bound)

2026-05-05 19:23:38,025 DEBG 'start-script' stdout output:
2026-05-05 19:23:38 UDPv4 link remote: [AF_INET]104.18.37.206:1198

2026-05-05 19:24:39,031 DEBG 'start-script' stdout output:
2026-05-05 19:24:39 [UNDEF] Inactivity timeout (--ping-restart), restarting

My docker-compose.

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/Budapest"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Unraid"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='toneuhodnes'
  -e 'VPN_PASS'='toneuhodnes'
  -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'='192.168.1.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'='1000'
  -e 'PGID'='1000'
  -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:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/Seriály/':'/192.168.1.8/Seriály':'rw'
  -v '/mnt/user/Backup/qBittorrent-container/torrenty/':'/torrenty':'rw'
  -v '/mnt/user/Software/':'/192.168.1.8/Software':'rw'
  -v '/mnt/user/music/rutracker/':'/192.168.1.8/music/rutracker':'rw'
  -v '/mnt/user/music/Orpheus/':'/192.168.1.8/music/Orpheus':'rw'
  -v '/mnt/user/music/CZTorrent/':'/192.168.1.8/music/CZTorrent':'rw'
  -v '/mnt/user/Hry/':'/192.168.1.8/Hry':'rw'
  -v '/mnt/user/Stahování/':'/192.168.1.8/Stahování':'rw'
  -v '/mnt/user/Dokumentární filmy/':'/192.168.1.8/Dokumentární filmy':'rw'
  -v '/mnt/user/Emovies/Anime/':'/192.168.1.8/Emovies/Anime':'rw'
  -v '/mnt/user/Emovies/Collection/':'/192.168.1.8/Emovies/Collection':'rw'
  -v '/mnt/user/Emovies/Ebooks/':'/192.168.1.8/Emovies/Ebooks':'rw'
  -v '/mnt/user/Emovies/Filmy/':'/192.168.1.8/Emovies/Filmy':'rw'
  -v '/mnt/user/Emovies/Klipy/':'/192.168.1.8/Emovies/Klipy':'rw'
  -v '/mnt/user/Filmy/':'/192.168.1.8/Filmy':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn@sha256:56630778214670820ffe546a2f0e072b3b8b2a516a08130b213b32bf0bed666d'
ded1d57f6f1737fea46278f113db5a7d89ac8643737e3f6fddefeebc97bd1f3d

OpenVPN settings:

client
dev tun
proto udp
remote czech-republic.pvt.site 1198
resolv-retry infinite
nobind
persist-key
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server

auth-user-pass credentials.conf
comp-lzo no
verb 1

<ca>
-----BEGIN CERTIFICATE-----
MIIFqzCCBJOgAwIBAgIJAKZ7D5Yv87qDMA0GCSqGSIb3DQEBDQUAMIHoMQswCQYD
......................................................

19 hours ago, sv000008 said:

Thank you, didn't consider that it could be a Synology issue.

Update: The solution I found is to force legacy iptables withing the container. Unfortunately, the container restarts once that error is displayed and I cannot access the container console long enough to make the changes. I have reverted to version 5.1.4-2-01 for now.

Thanks for your help,

I have a question : with 5.1... version it's ok : it works : I have reverted to version 5.1.4-2-01 like you

but it's broken with 5.2 version ? In 5.2 version the image docker change by using iptables or nftables ? The issue is here to my mind (and the IA mind)

Maybe is it possible for Synology, QNAP, ... users to use in the next version the same version of iptables or nftables like in 5.1... version ?

Thanks

7 hours ago, Lemars said:

Thanks for your help,

I have a question : with 5.1... version it's ok : it works : I have reverted to version 5.1.4-2-01 like you

but it's broken with 5.2 version ? In 5.2 version the image docker change by using iptables or nftables ? The issue is here to my mind (and the IA mind)

Maybe is it possible for Synology, QNAP, ... users to use in the next version the same version of iptables or nftables like in 5.1... version ?

Thanks

It's because the iptables packages changed names recently in arch and the new push from binhex "merged" those changes in the docker image

https://archlinux.org/news/iptables-now-defaults-to-the-nft-backend/

iptables-nft became iptables

iptables became iptables-legacy

And Synology and QNAP do not update like in arch then the docker image could not works on these NAS

We need to wait the NAS are updated ---> maybe in a few months ?

Or manually like in a the post of Fl4shBack

There is no other solution ?

Sorry for my English....

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?

1 hour ago, deeveeance said:

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

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