[Support] binhex - qBittorrentVPN - Page 201 - Docker Containers

May 12May 12

Hi,

I updated Unraid to 7.2.6 and after rebooting the server after the upgrade, I cannot access qbittorrent. I deleted the folder in app data and reinstalled and still no joy.
Is there an incompatiblilty with the latest Unraid?
Thank you for any help you can provide

Quote

May 12May 12

15 minutes ago, crowdx42 said:
Is there an incompatiblilty with the latest Unraid?

No, but there is an issue with 7.2.5+ that sometimes prevents dockers from starting. You’ll need to attach your entire supervisord log and docker run command to your next post if you want assistance with this issue. Be sure to redact any users/passwords.

Quote

May 12May 12

Below I have attached my log.

supervisord.log

Quote

May 12May 12

5 minutes ago, crowdx42 said:
Below I have attached my log.
supervisord.log

From your log-

2026-05-11 16:21:34,652 DEBG 'start-script' stdout output:

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

2026-05-11 16:21:37,448 DEBG 'start-script' stdout output:

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

2026-05-11 16:21:37,449 DEBG 'start-script' stdout output:

[info] srilanka.privacy.network

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

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

[info] ca-toronto.privacy.network

[info] cyprus.privacy.network

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

[info] monaco.privacy.network

[info] austria.privacy.network

[info] cambodia.privacy.network

[info] sanjose.privacy.network

[info] fi-2.privacy.network

[info] in.privacy.network

[info] man.privacy.network

[info] ba.privacy.network

[info] yerevan.privacy.network

[info] ca-ontario-so.privacy.network

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

[info] bangladesh.privacy.network

[info] uk-2.privacy.network

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

[info] vietnam.privacy.network

[info] kazakhstan.privacy.network

[info] liechtenstein.privacy.network

[info] macau.privacy.network

[info] hk.privacy.network

[info] ca-vancouver.privacy.network

[info] lu.privacy.network

[info] ca-montreal.privacy.network

[info] morocco.privacy.network

[info] kr-south-korea-pf.privacy.network

[info] venezuela.privacy.network

[info] malta.privacy.network

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

[info] ca-ontario.privacy.network

[info] bahamas.privacy.network

[info] panama.privacy.network

[info] santiago.privacy.network

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

[info] montenegro.privacy.network

[info] mongolia.privacy.network

[info] nl-amsterdam.privacy.network

[info] ua.privacy.network

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

[info] ad.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] argentina.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] 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

[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

2026-05-11 16:21:37,449 DEBG 'start-script' stdout output:

[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] 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

[info] Script finished to assign incoming port

You’ll need to edit your endpoint in the ovpn file to match one from the list and restart the container.

Edited May 12May 12 by wgstarks

Quote

May 12May 12

So here is the updated log, from the esponse above, I believe I needed to copy an ovpn file from PIA that allows port forwarding as shown in the list?

I did a full fresh install and still no success.

supervisord.log

Quote

May 12May 12

48 minutes ago, wgstarks said:
From your log-
2026-05-11 16:21:34,652 DEBG 'start-script' stdout output:
[info] PIA endpoint 'al.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-
2026-05-11 16:21:37,448 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
2026-05-11 16:21:37,449 DEBG 'start-script' stdout output:
[info] srilanka.privacy.network
[info] gt-guatemala-pf.privacy.network
[info] uy-uruguay-pf.privacy.network
[info] ca-toronto.privacy.network
[info] cyprus.privacy.network
[info] np-nepal-pf.privacy.network
[info] monaco.privacy.network
[info] austria.privacy.network
[info] cambodia.privacy.network
[info] sanjose.privacy.network
[info] fi-2.privacy.network
[info] in.privacy.network
[info] man.privacy.network
[info] ba.privacy.network
[info] yerevan.privacy.network
[info] ca-ontario-so.privacy.network
[info] ec-ecuador-pf.privacy.network
[info] bangladesh.privacy.network
[info] uk-2.privacy.network
[info] de-germany-so.privacy.network
[info] vietnam.privacy.network
[info] kazakhstan.privacy.network
[info] liechtenstein.privacy.network
[info] macau.privacy.network
[info] hk.privacy.network
[info] ca-vancouver.privacy.network
[info] lu.privacy.network
[info] ca-montreal.privacy.network
[info] morocco.privacy.network
[info] kr-south-korea-pf.privacy.network
[info] venezuela.privacy.network
[info] malta.privacy.network
[info] bo-bolivia-pf.privacy.network
[info] ca-ontario.privacy.network
[info] bahamas.privacy.network
[info] panama.privacy.network
[info] santiago.privacy.network
[info] pe-peru-pf.privacy.network
[info] montenegro.privacy.network
[info] mongolia.privacy.network
[info] nl-amsterdam.privacy.network
[info] ua.privacy.network
[info] nl-netherlands-so.privacy.network
[info] ad.privacy.network
[info] albania.pvt.site
[info] algeria.pvt.site
[info] argentina.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] 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
[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
2026-05-11 16:21:37,449 DEBG 'start-script' stdout output:
[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] 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
[info] Script finished to assign incoming port
You’ll need to edit your endpoint in the ovpn file to match one from the list and restart the container.

A few endpoints changed recently in the list of those supporting port forwarding, I experienced the same issue with swiss.privacy.network. That was not that easy to find out at first glance.

Quote

May 12May 12

6 minutes ago, crowdx42 said:
So here is the updated log, from the esponse above, I believe I needed to copy an ovpn file from PIA that allows port forwarding as shown in the list?
I did a full fresh install and still no success.
supervisord.log

You are still using an endpoint that doesn’t support port forwarding. All you need to do is edit the ovpn file using a text editor to change the endpoint to one from the list I provided earlier.

Quote

May 12May 12

2 minutes ago, wgstarks said:
You are still using an endpoint that doesn’t support port forwarding. All you need to do is edit the ovpn file using a text editor to change the endpoint to one from the list I provided earlier.

See https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q11.

Quote

May 12May 12

Still no joy connecting, I updated teh ovpn file and I think in the attached log it shows it is working?

supervisord.log

Quote

May 12May 12

Author

7 hours ago, wgstarks said:
No, but there is an issue with 7.2.5+ that sometimes prevents dockers from starting.

I was not aware of this bug, do you have any more details?, links?

Quote

May 12May 12

Author

5 hours ago, crowdx42 said:
Still no joy connecting, I updated teh ovpn file and I think in the attached log it shows it is working?
supervisord.log

What is the ip address of the machine/device you are using to attempt connection to the qbittorrent web ui?.

Quote

May 12May 12

2 hours ago, binhex said:
I was not aware of this bug, do you have any more details?, links?

With some of my dockers I get an invalid port warning when/if the docker is restarted. All I have to do is re-apply the existing settings and I get a successful start. I don’t recall all the dockers this applies to but qbit and prowler are included. This started with 7.2.5 and continues with 7.2.6.

Edit: Just tested again. This error only seems to happen when docker is cycled (server reboot, array stop/start, etc). Not seeing it when restarting individual dockers or even with stop all start all. Qbitvpn wasn’t one of the affected dockers in my test.

Diagnostic attached if you’re interested. I know there was a breaking change in 7.2.5 that applied to dockers with custom MAC addresses. Maybe this is somehow related?

brunnhilde-diagnostics-20260512-0746.zip

Quote

1

May 12May 12

On 5/3/2026 at 12:05 AM, JBanner said:
I am also having issues after upgrading to unraid 7.2.5.
After the update I could not start the container, similar to above "docker: Error response from daemon: invalid port specification: "0/tcp""
I tried to remove the container and reinstall using "Previously Apps", and tried using "Add Container", both methods end with: (Username and Password have been obscured)
docker run
-d
--name='binhex-qbittorrentvpn'
--net='bridge'
--pids-limit 2048
--privileged=true
-e TZ="Europe/London"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Tower"
-e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
-e 'VPN_ENABLED'='yes'
-e 'VPN_USER'='OBSCURED'
-e 'VPN_PASS'='OBSCURED'
-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'='false'
-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: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"
Run 'docker run --help' for more information
The command failed.
I''m not really sure what to try next...

Ok this is all sorted now. Replaced the Wireguard Config, and added the tailscale net address to the allowed LAN's and updated to latest.

Quote

1

May 12May 12

20 minutes ago, wgstarks said:
I know there was a breaking change in 7.2.5 that applied to dockers with custom MAC addresses. Maybe this is somehow related?

Just realized that the affected dockers are all the members of my VPN network provided by PrivoxyVPN.

Quote

May 12May 12

3 hours ago, binhex said:
What is the ip address of the machine/device you are using to attempt connection to the qbittorrent web ui?.

The laptop ip is 192.168.1.65 and the Unraid ip is 192.168.1.55.

Quote

May 12May 12

11 minutes ago, crowdx42 said:
The laptop ip is 192.168.1.65 and the Unraid ip is 192.168.1.55.

Are you able to access the login page and using the credentials shown in the log-

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

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

The WebUI administrator username is: admin

The WebUI administrator password was not set. A temporary password is provided for this session: TTxF4NqkV

I also see that you are using a custom port for the webUI. See https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

and scroll down to Q4 to be sure it is configured correctly. I don't think you provided your docker run command so I can't tell.

Quote

May 12May 12

Nope, I get site cannot be reached timeout. As for the ports, I have Port: Web Interface: set to 8687 and also the Variable: WEBUI_PORT: set to 8687. As stated previously, I have done a full reinstall of the docker with no joy. This was all working fine before I updated Unraid to 7.2.6.

Below is the config for the docker.
[AutoRun]

enabled=false

program=

[BitTorrent]

Session\AddTorrentStopped=false

Session\Interface=tun0

Session\InterfaceName=tun0

Session\Port=49560

Session\QueueingSystemEnabled=true

Session\SSL\Port=8930

Session\ShareLimitAction=Stop

Session\UseRandomPort=false

[Meta]

MigrationVersion=8

[Network]

Cookies=@Invalid()

PortForwardingEnabled=false

Proxy\HostnameLookupEnabled=false

Proxy\Profiles\BitTorrent=true

Proxy\Profiles\Misc=true

Proxy\Profiles\RSS=true

[Preferences]

Connection\Interface=tun0

Connection\InterfaceName=tun0

Connection\PortRangeMin=6881

Connection\UPnP=false

General\Locale=en

General\UseRandomPort=false

WebUI\Address=*

WebUI\CSRFProtection=false

WebUI\LocalHostAuth=false

WebUI\Port=8687

WebUI\ServerDomains=*

WebUI\UseUPnP=false

Edited May 12May 12 by crowdx42

Quote

May 12May 12

29 minutes ago, crowdx42 said:
Below is the config for the docker.

This doesn’t show the port mappings but I suspect that if you follow the instructions that I linked previously it’ll correct your issue. If not please attach your docker run command to your next post. As always, be sure to redact users/passwords.

Quote

May 12May 12

Does the below log show what is needed?
2026-05-12 07:17:35,597 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 26082

[debug] qBittorrent incoming port is 26082

[debug] VPN IP is 10.19.112.199

[debug] qBittorrent IP is 10.19.112.199

2026-05-12 07:18:05,602 DEBG 'watchdog-script' stdout output:

[debug] Checking we can resolve name 'www.google.com' to address...

2026-05-12 07:18:05,650 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.155.119 142.251.151.119 142.251.154.119 142.251.156.119 142.251.153.119 142.251.157.119 142.251.150.119'

2026-05-12 07:18:05,651 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2026-05-12 07:18:05,662 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-05-12 07:18:05,667 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 26082

[debug] qBittorrent incoming port is 26082

[debug] VPN IP is 10.19.112.199

2026-05-12 07:18:05,667 DEBG 'watchdog-script' stdout output:

[debug] qBittorrent IP is 10.19.112.199

2026-05-12 07:18:33,775 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2026-05-12 07:18:35,673 DEBG 'watchdog-script' stdout output:

[debug] Checking we can resolve name 'www.google.com' to address...

2026-05-12 07:18:35,720 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.156.119 142.251.155.119 142.251.152.119 142.251.150.119 142.251.157.119 142.251.151.119 142.251.153.119 142.251.154.119'

2026-05-12 07:18:35,721 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2026-05-12 07:18:35,731 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-05-12 07:18:35,737 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 26082

[debug] qBittorrent incoming port is 26082

[debug] VPN IP is 10.19.112.199

2026-05-12 07:18:35,738 DEBG 'watchdog-script' stdout output:

[debug] qBittorrent IP is 10.19.112.199

2026-05-12 07:19:05,744 DEBG 'watchdog-script' stdout output:

[debug] Checking we can resolve name 'www.google.com' to address...

2026-05-12 07:19:05,792 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.155.119 142.251.156.119 142.251.150.119 142.251.157.119 142.251.153.119 142.251.154.119 142.251.151.119'

2026-05-12 07:19:05,792 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2026-05-12 07:19:05,803 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-05-12 07:19:05,809 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 26082

[debug] qBittorrent incoming port is 26082

2026-05-12 07:19:05,809 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.19.112.199

[debug] qBittorrent IP is 10.19.112.199

2026-05-12 07:19:35,815 DEBG 'watchdog-script' stdout output:

[debug] Checking we can resolve name 'www.google.com' to address...

2026-05-12 07:19:35,863 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.153.119 142.251.150.119 142.251.156.119 142.251.154.119 142.251.157.119 142.251.151.119 142.251.155.119'

2026-05-12 07:19:35,863 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

2026-05-12 07:19:35,871 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-05-12 07:19:35,877 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 26082

[debug] qBittorrent incoming port is 26082

[debug] VPN IP is 10.19.112.199

[debug] qBittorrent IP is 10.19.112.199

Quote

May 12May 12

8 minutes ago, crowdx42 said:
Does the below log show what is needed?

No. The words docker run are a link to instructions for getting this text.

Edited May 12May 12 by wgstarks

Quote

May 12May 12

I believe below is what is requested:

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="UNRAID"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxxxxxx'
  -e 'VPN_PASS'='xxxxxx'
  -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'='8688'
  -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'='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 '8688: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/Finished_Torrents/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

bc177e209e8ba18f88d0178a28caa3fad51a5ba6672e6d4bb483b763a46ea249

Quote

May 12May 12

7 minutes ago, crowdx42 said:
-p '8688:8080/tcp

This is an issue. You have port 8688 mapped to port 8080. You’ll need to delete this port mapping in the docker configuration and then create a new port mapping by clicking “Addanother path, port, label, variable or device” near the bottom of the page. Select “port” at the top of the window, “name” can be whatever you like, “container port” will be 8688, “host port” will be 8688, “default value” can be 8688 or leave blank, “connection type” will be TCP, “description” is whatever you want to put. Click the “add” button and then the “apply” button.

Quote

May 12May 12

13 minutes ago, wgstarks said:
This is an issue. You have port 8688 mapped to port 8080. You’ll need to delete this port mapping in the docker configuration and then create a new port mapping by clicking “Addanother path, port, label, variable or device” near the bottom of the page. Select “port” at the top of the window, “name” can be whatever you like, “container port” will be 8688, “host port” will be 8688, “default value” can be 8688 or leave blank, “connection type” will be TCP, “description” is whatever you want to put. Click the “add” button and then the “apply” button.

I tried above and it resulted in the torrent webui showing as sabnzbd instead (it is the docker that uses port 8080). I then removed the torrent docker, did a fresh install using the default ports ( I changed sabnzbd port to 8081) and this finally worked. I then updated all my other dockers to connect using the 8080 port and all seems well.

Thank you for all your help

Quote

May 12May 12

Hey there,

Following a reassignment of my Unraid IP from 192.168.1.2 to 192.168.1.100 I cannot reach my WebUI anymore.
All other services/dockers seem to have had no issue with the change and are running just fine as far as I can tell.

Not being too much into networking or programming knowledge, I tried tackling it with Claude & the Github but just couldn't get there.
Right now, when entering the IP for the WebUI, I get an error message that it cannot be reached no matter the browser.

While Claude was hyper fixated on solving the DNS issue (which is not resolved), I also tried a rollback to version 5.1 (as mentioned for other pending issues) and of course reinstalling the docker.
Nothing worked.

When starting I get the following log:

2026-05-12 19:12:22,387 DEBG 'start-script' stdout output:
--------------------

2026-05-12 19:12:22,389 DEBG 'start-script' stdout output:
[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2026-05-12 19:12:22,389 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...
[debug] Running WireGuard kernel implementation...

2026-05-12 19:12:22,399 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2026-05-12 19:12:22,404 DEBG 'start-script' stderr output:
wg-quick: `wg0' is not a WireGuard interface

2026-05-12 19:12:22,404 DEBG 'start-script' stdout output:
[warn] Failed to bring 'down' WireGuard kernel implementation

2026-05-12 19:12:22,405 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2026-05-12 19:12:22,417 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
[debug] Running WireGuard kernel implementation...

2026-05-12 19:12:22,428 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2026-05-12 19:12:22,440 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard

2026-05-12 19:12:22,443 DEBG 'start-script' stderr output:
[#] wg addconf wg0 /dev/fd/63

2026-05-12 19:12:22,445 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2026-05-12 19:12:22,455 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2026-05-12 19:12:22,468 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2026-05-12 19:12:22,470 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2026-05-12 19:12:22,472 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2026-05-12 19:12:22,474 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2026-05-12 19:12:22,481 DEBG 'start-script' stderr output:
[#] nft -f /dev/fd/63

2026-05-12 19:12:22,486 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2026-05-12 19:12:22,493 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2026-05-12 19:12:23,502 DEBG 'start-script' stdout output:
[debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2'

2026-05-12 19:12:24,509 DEBG 'start-script' stdout output:
[debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1'

2026-05-12 19:12:24,509 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2026-05-12 19:12:39,530 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2026-05-12 19:12:59,551 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 10 retries left

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Gordon"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxx
  -e 'VPN_PASS'='xxx
  -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'
  -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'='10.2.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:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/Downloads/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

3c07c9936ce35c9a69229207ff5f74e75322d7376a254033d7a7a6b1fc2deb55

In addition, I attached my current docker settings.
Any help is appreciated 🙏

/edit: Docker Run was added

Edited May 12May 12 by IMACRAB

Quote

May 12May 12

It seems like to maybe the list of servers have changed (see below)

Also the names ending in pvt.site feels newish.

This is the list in the logs, and my chosen server (from my wg0.conf) no longer exists, not sure if binhex grabs the list dynamically from an api or included it when the container gets updated

[info] fi-2.privacy.network
[info] srilanka.privacy.network
[info] cyprus.privacy.network
[info] mongolia.privacy.network
[info] np-nepal-pf.privacy.network
[info] ba.privacy.network
[info] ua.privacy.network
[info] sanjose.privacy.network
[info] ca-toronto.privacy.network
[info] morocco.privacy.network
[info] gt-guatemala-pf.privacy.network
[info] de-germany-so.privacy.network
[info] kazakhstan.privacy.network
[info] montenegro.privacy.network
[info] nl-amsterdam.privacy.network
[info] bangladesh.privacy.network
[info] ca-ontario.privacy.network
[info] ca-montreal.privacy.network
[info] malta.privacy.network
[info] bahamas.privacy.network
[info] ec-ecuador-pf.privacy.network
[info] liechtenstein.privacy.network
[info] yerevan.privacy.network
[info] lu.privacy.network
[info] albania.pvt.site
[info] algeria.pvt.site
[info] argentina.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] 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
[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] 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] 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-05-12 11:20:45,373 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

Quote

[Support] binhex - qBittorrentVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

ulkesh

nraygun

gustyScanner

Posted Images

Hey there,

When starting I get the following log:

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

ulkesh

nraygun

gustyScanner

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)