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

But I am getting the error below, shoudl I not be able to get to the web-ui regardless?
image.png

  • 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

19 minutes ago, crowdx42 said:

But I am getting the error below, shoudl I not be able to get to the web-ui regardless?
image.png

If you have VPN enabled then the qbit app will not start until it connects to the endpoint. Without any logs or a docker run command it’s hard for others to know what’s going on.

below is from the log, I am using the most recent docker, I changed the qBittorent IP in the log to 99.99.99.99 for privacy:
026-02-19 15:22:34,723 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process listening on port 8585

2026-02-19 15:22:35,186 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 22084

[debug] qBittorrent incoming port is 22084

[debug] VPN IP is 99.99.99.99

[debug] qBittorrent IP is 99.99.99.99

2026-02-19 15:23:05,192 DEBG 'watchdog-script' stdout output:

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

2026-02-19 15:23:05,388 DEBG 'watchdog-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.183.36'

2026-02-19 15:23:05,388 DEBG 'watchdog-script' stdout output:

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

2026-02-19 15:23:05,399 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-02-19 15:23:05,408 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is 22084

[debug] qBittorrent incoming port is 22084

[debug] VPN IP is 99.99.99.99

[debug] qBittorrent IP is 99.99.99.99

9 minutes ago, crowdx42 said:

[debug] VPN IP is 99.99.99.99

[debug] qBittorrent IP is 99.99.99.99

That doesn't look right.

And no as mentioned the webui will not come up if your VPN connection fails.

the IP shown is what I updated, the correct IP for the VPN shows correctly in the log.

I too am unable to see the webgui, unraid has not been touched for weeks. The VPN/proxivy connection still works here as far as I can see/test, but the webgui is not showing up?

well I finally got the WebUI working, but only with the VPN turned off. I use Private Internet Access, I have downloaded the OpenVPN files from their site and put them in the OpenVPN folder and from the logs it looks like it connected and was assigned an IP, but the WebUI still gives a page not found error.
Thoughts? What should I be checking on the VPN side to make sure everything is working?

3 hours ago, crowdx42 said:

well I finally got the WebUI working, but only with the VPN turned off. I use Private Internet Access, I have downloaded the OpenVPN files from their site and put them in the OpenVPN folder and from the logs it looks like it connected and was assigned an IP, but the WebUI still gives a page not found error.
Thoughts? What should I be checking on the VPN side to make sure everything is working?

Are you accessing the webUI from LAN?

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

I finally got it working, I changed Variable: LAN_NETWORK: setting to my network range and now it works, default was 192.168.1.0/24, I updated it to 192.168.1.2/24 .

That is the only thing that got it working for the WebUI.

7 hours ago, crowdx42 said:

That is the only thing that got it working for the WebUI.

Meaning that it should be 192.168.1.0/24, not 192.168.1.2/24. But it probably fixes it in the background.

With 192.168.1.0/24 the WebUI was getting page not found, whereas changing it to 192.168.1.2/24 fixed the issue and WebUI works. I am not sure of the reason why, only that it works now. Could it be that my gateway is 192.168.1.1 and so the router did not like having it's IP address included in the IP range?

I was having trouble accessing my WebUI also and claude opus 4.6 walked me through a fix fairly painlessly. I use PIA for my VPN. Here is the AIs summary FYI

If your binhex-qbittorrentvpn WebUI suddenly stopped loading with PIA:

  • Check your supervisord.log for the line: PIA endpoint '...' is NOT in the list of endpoints that support port forwarding

  • PIA has been quietly removing port forwarding support from certain endpoints (e.g., japan.privacy.network). If you have STRICT_PORT_FORWARD=yes, qBittorrent will silently fail to start.

  • Fix: edit the remote line in your .ovpn file to a supported endpoint from the list in your log. Stick with .privacy.network domains — the .pvt.site ones may not work with OpenVPN configs.

  • Restart your arr containers after so they reconnect cleanly.

If you need help parsing your logs, claude.ai is surprisingly good at it.

  • 2 weeks later...

@binhex Any clue as to what is going on? It seems the container has not been updated recently either.

I am using Mullvad, could it be a problem there?
Or is OpenVPN deprecated and we should all use Wireguard setups?

I just recently started using this container to start migrating from rtorrent and get better integration with the other *arr stacks. I'm currently running without any VPN's.

I decided to try and run a few instances to break up my torrents by categories and have run into an issue running two instances together. They spin up fine and as long as I don't try and add a torrent manually or access the settings, everything seems to be ok. As soon as I do one of these two things, it kills the web instances on the second one requiring a refresh of both.

I did some searching and it seems to be a problem similar to this linuxserver issue. https://github.com/linuxserver/docker-qbittorrent/issues/423

Has anyone else run into something similar? I was under the impression that running multiple instances shouldn't be a problem.

Ive been using this container for over a year but i cant login now. Anyway to reset the webui password and username?

"Invalid Username or Password. Server response: Fails."

Edited by dsharpe89

25 minutes ago, dsharpe89 said:

Ive been using this container for over a year but i cant login now. Anyway to reset the webui password and username?

"Invalid Username or Password. Server response: Fails."

Check the supervisord log and see if it contains a temporary user/password.

Hello,

I'm trying to use this container, but even though the connection to ProtonVPN using Wireguard seems ok, I can't access the Web UI.

I've defined the Wireguard config in config/wireguard/wg0.conf after downloading the file from ProtonVPN site.

If I disable the VPN, the Web UI works fine.

Here is my docker run command, I have a doubt on VPN_USER and VPN_PASS, but I think they are useless when using Wireguard ?

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='my-custom-network'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="My-NAS"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='unused'
  -e 'VPN_PASS'='unused'
  -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'='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/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/downloads/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

Here are the logs from the container :

2026-03-10 21:56:58,850 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-03-10 21:56:59,863 DEBG 'start-script' stdout output:

[debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2'

2026-03-10 21:57:00,875 DEBG 'start-script' stdout output:

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

2026-03-10 21:57:00,875 DEBG 'start-script' stdout output:

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

2026-03-10 21:57:00,907 DEBG 'start-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.22.164'

2026-03-10 21:57:01,024 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 146.70.194.110 from URL 'http://checkip.amazonaws.com'

2026-03-10 21:57:01,025 DEBG 'start-script' stdout output:

[info] Script started to assign incoming port for 'protonvpn'

[debug] Waiting for valid VPN gateway IP addresses from tunnel...

[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2026-03-10 21:57:01,027 DEBG 'start-script' stdout output:

[info] Successfully brought Wireguard interface 'up'

2026-03-10 21:57:02,040 DEBG 'start-script' stdout output:

[debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2'

2026-03-10 21:57:03,050 DEBG 'start-script' stdout output:

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

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

2026-03-10 21:57:03,050 DEBG 'start-script' stdout output:

[info] Script finished to assign incoming port

Do you have any idea about what I am doing wrong ?

Thanks in advance.

Edited by Wirby

I don’t use Proton so perhaps someone who does could give you better info but this jumped out at me from your log-

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

If you have force port forwarding set and it fails then the qbit app doesn’t start IIRC.

I'm in the group of qbit not connecting now. Thought it would be as simple as updating the openvpn folder to a new PIA endpoint, but no such luck. Below are my logs, any thoughts on what I've got wrong?

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="Tower"

-e HOST_CONTAINERNAME="binhex-qbittorrentvpn"

-e 'VPN_ENABLED'='yes'

-e 'VPN_USER'='XXXXXXX'

-e 'VPN_PASS'='XXXXXXX'

-e 'VPN_PROV'='pia'

-e 'VPN_CLIENT'='openvpn'

-e 'VPN_OPTIONS'=''

-e 'STRICT_PORT_FORWARD'='yes'

-e 'ENABLE_PRIVOXY'='no'

-e 'WEBUI_PORT'='8081'

-e 'LAN_NETWORK'='10.0.0.1/24'

-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 '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 '8081:8080/tcp'

-p '8118:8118/tcp'

-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" 'binhex/arch-qbittorrentvpn:4.6.7-1-01'

bd6bb10bbe0098088c5f39948df6f80911895e286bc0c3fe3839beadc29ba46e

QBit log is here-

Pastebin

QBit Log - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Would appreciate any thoughts, thanks!

Edit- So it's weird, on my trackers they now show I am seeding. But I still cannot access the webGUI.

Edited by Matt0925

Hello @wgstarks , thanks for the reply. Unfortunately no luck, their guide gave me the same numbers I already had.

7 hours ago, Matt0925 said:

Hello @wgstarks , thanks for the reply. Unfortunately no luck, their guide gave me the same numbers I already had.

7 hours ago, Matt0925 said:

Hello @wgstarks , thanks for the reply. Unfortunately no luck, their guide gave me the same numbers I already had.

What IP Address and Subnet Mask are you using for the calculation?

On 3/11/2026 at 12:12 AM, wgstarks said:

I don’t use Proton so perhaps someone who does could give you better info but this jumped out at me from your log-

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

If you have force port forwarding set and it fails then the qbit app doesn’t start IIRC.

Thanks, after disabling strict port forward I'm able to access the web UI. Unfortunately, the default login/password does not seem to be admin/adminadmin and I can't see any default password in the logs :(

Edited by Wirby

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.