14 minutes ago, wgstarks said:

The template you have for this container is newer than the instructions in the FAQ. You didn’t need to add any port mappings since they already exist in the template. You just need to edit the existing mapping. WebUI port just needs to match the host and container port numbers in Port: Web Interface.

If it’s still not working attach your docker run command and supervisord log to your next post. Be sure to redact users/passwords.

I'll attach some screenshots below, I deleted the image and cleared out the appdata and started fresh and put in the required data, the only defaults I changed were setting anything that was 8080 to instead be 8083. which were the two values in my original post.

Docker Run: I can see in the run command there is still a value set to 8080, but I did set both values in the setup to 8083.

Screengrab of the log

3 hours ago, TestingUser said:

I can see in the run command there is still a value set to 8080, but I did set both values in the setup to 8083

This is likely your issue. Possibly a typo when you configured the port. I would double check it since it isn’t configured correctly.

1 hour ago, wgstarks said:

This is likely your issue. Possibly a typo when you configured the port. I would double check it since it isn’t configured correctly.

That's the issue though, I am changing the settings it says to change and they aren't changing, when I try to edit the port I can see 8080 listed but it's greyed out and I can't change it. Maybe this is stupid simple, but I am new to docker so I don't know what I'm suppose to do here. Do I delete the Port: Web Interface config and make a new one where I can set the port? I don't know what I can change and not break the container.

To be clearer (I hope 😁), the problem is that the Port: Web Interface has container set to 8083 but the host port is still 8080. Click edit next to this setting and switch both to 8083.

The setting you marked in your screenshot is for the link to the webUI from the docker tab. You can change it by going to the Unraid docker tab, opening the configuration for this docker and then switch from basic to advanced view (upper right). Near the top of the page you’ll see another webUI entry (here is mine)-

Change the port number in that entry to 8083 for yours.

11 minutes ago, TestingUser said:

Do I delete the Port: Web Interface config and make a new one where I can set the port?

Yes. Grab a screenshot of the edit pane and then delete it and add a new port mapping with the correct numbers.

5 minutes ago, wgstarks said:

To be clearer (I hope 😁), the problem is that the Port: Web Interface has container set to 8083 but the host port is still 8080. Click edit next to this setting and switch both to 8083.

The setting you marked in your screenshot is for the link to the webUI from the docker tab. You can change it by going to the Unraid docker tab, opening the configuration for this docker and then switch from basic to advanced view (upper right). Near the top of the page you’ll see another webUI entry (here is mine)-

Change the port number in that entry to 8083 for yours.

Alright, so I went to the advanced view and changed the 8080 to 8083 and it still didn't work.

So I shutdown all of my docker containers, deleted the qbit container and it's appdata folder. Then started again from scratch and left everything as default, even with it set to 8080 the webUI still won't load.

I went and downloaded and setup the Marcus docker container

and got it all hooked up and the webUI started immediately no issues at all.

@binhex at this point I think there is a bug with your container or something because even when leaving the ports all default the webUI still doesn't load.

Edited April 7Apr 7 by TestingUser
Add screenshot of webUI

When I do an ss -lntu in the console for binhex, it doesn't list the port

When I do an ss -lntu in the console for Marcus, it lists the port

@binhex I noticed in your install script on line 110 you set the webui and log out some infos and warns so I attempted to run the script again to see what it gave and it errors out because the buildx args are no longer present. I was able to verify that values are in the image-build-info so I think it has ran at least once. In all of my logs though I never found the info for line 112 even with debug set to true.

I even went and edited my container and deleted the WEBUI_PORT config to try and trigger the warning on line 114 but never saw the warning in the logs.

@wgstarks I don't know if you have any other ideas on what might be going on here or what I might be missing, I have several other binhex containers running and they've all worked without any issue. This is the only one where I can't get the webUI to work. I even changed my container that was using 8080 to use a different port so that I can try to get this qbitVPN running on 8080.

The binhex non VPN version loads up no issue, other versions of qbitvpn work but I can't get this one to work with the webui.

12 minutes ago, TestingUser said:

@wgstarks I don't know if you have any other ideas on what might be going on here or what I might be missing, I have several other binhex containers running and they've all worked without any issue. This is the only one where I can't get the webUI to work. I even changed my container that was using 8080 to use a different port so that I can try to get this qbitVPN running on 8080.

The binhex non VPN version loads up no issue, other versions of qbitvpn work but I can't get this one to work with the webui.

attach your docker run command agian for the container, it sounds like you have changed some settings but i assume you have missed something, Q4 is still relevant:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

5 minutes ago, binhex said:

attach your docker run command agian for the container, it sounds like you have changed some settings but i assume you have missed something, Q4 is still relevant:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Q4 is still relevant, I was referring to answer for it line 3. Find Container Port: 8080 and click on Remove. Unless I am missing something, there is no Container Port: 8080 to click remove on. Even when I click on advanced, there is no listing for container port. Though I may be missing something super obvious?

DOCKER RUN:

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="HOSTNAME"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'=' USER'
  -e 'VPN_PASS'='PASSWORD'
  -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'='10.10.0.0/24'
  -e 'WEBUI_PORT'='8080'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1'
  -e 'ENABLE_HEALTHCHECK'='yes'
  -e 'HEALTHCHECK_COMMAND'=''
  -e 'HEALTHCHECK_ACTION'=''
  -e 'HEALTHCHECK_HOSTNAME'='google.com'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/templates/main/unraid/binhex/images/qbittorrent-icon.png'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/NAS1/Entertainment/working/qbit/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

c2f35c1f0d9d498c1c89b97ceb342264cb2d1395868fdced593aa7f72e14d093

The command finished successfully!

16 minutes ago, TestingUser said:

  -e 'WEBUI_PORT'='8080'

17 minutes ago, TestingUser said:

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

17 minutes ago, TestingUser said:

  -p '8080:8080/tcp'

ok so right now all 3 are in sync and set correctly to use port 8080, so if you fire up your browser should be able to access the web ui on port 8080, is this the case?, if not then something else is going on.

To answer your question:

18 minutes ago, TestingUser said:

I was referring to answer for it line 3. Find Container Port: 8080 and click on Remove. Unless I am missing something, there is no Container Port: 8080

The container used to simply be named as Container Port: 8080 it's now instead named Port: Web Interface:, see screenshot below, this is what you should delete IF you want to change the web ui port from the default of 8080:

So if for example you want to change the port to 8999

• you would delete the port above, re-add a config type port and set the host AND container ports to 8999

• then change the value for Variable: WEBUI_PORT:to a value of 8999

• and lastly if you want the web ui link to work when you left click the container icon then switch to advanced view (top right) and then edit the Web UI: to a value of http://[IP]:[PORT:8999]

• click apply at the bottom and fire up your web browser and go to http://[server ip]:8999 (or left click the container and select web ui).

51 minutes ago, TestingUser said:

@wgstarks I don't know if you have any other ideas on what might be going on here or what I might be missing

There is one problem in the little log snippet you posted-

You don’t have your user name appended properly to use ProtonVPN. There may be other issues but you’ll need to attach your entire supervisord.log file from appdata to let others review it (not just a screenshot of a snippet).

Also, I believe Step 3 is referring to any container port 8080 assignment regardless of the name (which is user definable).

4 minutes ago, binhex said:

The container used to simply be named as Container Port: 8080 it's now instead named Port: Web Interface:

All references to the old names has been updated to reflect the template name changes, so you should be able to follow this step by step now.

1 hour ago, binhex said:

ok so right now all 3 are in sync and set correctly to use port 8080, so if you fire up your browser should be able to access the web ui on port 8080, is this the case?, if not then something else is going on.

To answer your question:

The container used to simply be named as Container Port: 8080 it's now instead named Port: Web Interface:, see screenshot below, this is what you should delete IF you want to change the web ui port from the default of 8080:

So if for example you want to change the port to 8999

• you would delete the port above, re-add a config type port and set the host AND container ports to 8999

• then change the value for Variable: WEBUI_PORT:to a value of 8999

• and lastly if you want the web ui link to work when you left click the container icon then switch to advanced view (top right) and then edit the Web UI: to a value of http://[IP]:[PORT:8999]

• click apply at the bottom and fire up your web browser and go to http://[server ip]:8999 (or left click the container and select web ui).

I can not fire up the webUI and see it when configured like above, I get this error.

Thank you for clarifying the answer there, that's what I had originally tried.

On 3/21/2026 at 9:44 AM, jhe- said:

I see you have stopped releasing docker images for arm64. Any particular reason for this? It has stopped both on binhex/arch-qbittorrentvpn and on binhex/arch-sonarr but I can not find any announcements about it. It's a shame because it has been running solid on my Raspberry Pi 5

@binhex Not to nag, but wonder if you have any comments on this? Do you think arm64 images will come back, or should I consider migrating to something running x64?

14 hours ago, TestingUser said:

I can not fire up the webUI

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

3 hours ago, binhex said:

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

Here is the supervisord.log

supervisord.log

7 minutes ago, TestingUser said:

Here is the supervisord.log

supervisord.log

Last lines inthe log file:

[debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1'

[info] ProtonVPN username 'U_NAME' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...

[info] Script finished to assign incoming port

So does your username for proton have a suffix of +pmp?

1 hour ago, binhex said:

Last lines inthe log file:

[debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1'

[info] ProtonVPN username 'U_NAME' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...

[info] Script finished to assign incoming port

So does your username for proton have a suffix of +pmp?

My username is just an email address and it does not have a suffix of +pmp

6 minutes ago, TestingUser said:

My username is just an email address and it does not have a suffix of +pmp

add +pmp to your username.

9 minutes ago, binhex said:

add +pmp to your username.

If I and that and start it up, the last few lines change to below and webui still doesn't load.
[warn] ProtonVPN endpoint '95.173.217.187' is not enabled for P2P port forwarding, skipping port forward assignment...

[info] Script finished to assign incoming port

If I disable Variable: STRICT_PORT_FORWARD: by setting it to no, web UI loads and I get this output for the last lines repeating every now and again
2026-04-08 10:49:56,615 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-04-08 10:49:56,618 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 6881

[debug] qBittorrent incoming port is 6881

2026-04-08 10:49:56,618 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.2.0.2

[debug] qBittorrent IP is 10.2.0.2

Do I need to have STRICT_PORT_FORWARD set to yes to use P2P? The pirmary purpose of this container is to hook it up the radarr and sonarr images you made and use P2P torrents, but if I don't need STRICT_PORT_FORWARD I'll just leave that to no. I do'nt even know what it does.

6 minutes ago, TestingUser said:

Do I need to have STRICT_PORT_FORWARD set to yes to use P2P?

you need it if you need an incoming port (which you do for torrenting) to allow you to connect to the maximum number of peers, if you aren't torrenting then feel free to set it to no. if you do need an incoming port then you will need to download the correct wiregurd configuration for a p2p enabled endpoint - see proton's documentation.

12 minutes ago, binhex said:

you need it if you need an incoming port (which you do for torrenting) to allow you to connect to the maximum number of peers, if you aren't torrenting then feel free to set it to no. if you do need an incoming port then you will need to download the correct wiregurd configuration for a p2p enabled endpoint - see proton's documentation.

Awesome thank you.
https://protonvpn.com/support/port-forwarding-manual-setup
here is the link to the docs that tell how to set it up for proton if you want to add it to your docs somewhere for others who may run into this issue.

Hi, just started using this docker, I think I have everything configured correctly; however, speeds are slow, and the incoming port check reports the port is closed. I am using PIA with WireGuard, and the logs show a port forwarding supported host, successful connection and port assignment. That port also shows in the qbittorrent settings. I have tested against all the UK, Netherlands, and Ireland endpoints and the same occurs. I installed PIA client and qbittorrent on my laptop and requested the incoming port, manually assigned this to qbittorrent, and it works - it passes the incoming port test and speeds are good. So I don't think it is PIA or any particular endpoint.

I have attached my run command and logs. Can anyone help please?

logs.txt docker run.txt

Hmm, I'm also unable to access the UI. I started with a clean template

2026-04-10 09:55:55,865 DEBG 'start-script' stderr output: 
Line unrecognized: `PublicKey='
Configuration parsing error
2026-04-10 09:55:55,867 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2026-04-10 09:55:55,924 DEBG 'start-script' stdout output:
[warn] Failed to bring 'up' WireGuard kernel implementation
2026-04-10 09:56:25,930 DEBG 'start-script' stdout output:
[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...
2026-04-10 09:56:25,930 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...
2026-04-10 09:56:25,940 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible
2026-04-10 09:56:25,943 DEBG 'start-script' stderr output:
wg-quick: `wg0' is not a WireGuard interface
2026-04-10 09:56:25,943 DEBG 'start-script' stdout output:
[warn] Failed to bring 'down' WireGuard kernel implementation
2026-04-10 09:56:25,943 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...
2026-04-10 09:56:26,095 DEBG 'start-script' stdout output:
[info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
2026-04-10 09:56:26,099 DEBG 'start-script' stdout output:
[info] Successfully generated PIA token for wireguard
2026-04-10 09:56:26,099 DEBG 'start-script' stdout output: