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

I can't get a second instance of the docker to work on unRAID.

Since I am already running one instance of this docker, the new one would have conflicting port numbers.  

 

I decided to add a "1" in front of all of them since they are available. I added the same LAN_NETWORK subnets that are on my other one. I am using AirVPN, if that matters.

I followed this guide (Q4); at least, I think I did it correctly.

 

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

 

I removed "Port Web Interface"

image.png.940b2ffbbe5de570ed4a04c07c74252f.png


I changed "Variable: WEBUI_PORT:" to 18080

image.png.439378284a4df93b64f56b646ba4fb83.png

 


I added a port Container:18080 Host: 18080

image.png.b45020d082d84264c1591142447761d4.png

 

I applied everything, put in the VPN info, and it started the docker. There are a couple of problems.

 

1. When you go under the icon on the docker page and hover over the "WebUI" the link is still to 8080

 

image.png.ac62b275e892fb0c703967e71b144f8a.png


2. When I manually type IP:18080 in the browser, it goes to the login page. I use the default admin/pw, which shows me the qbittorrent screen.  It immediately says "qbittorrent client is not reachable" on the bottom left.  If go to the menu and select "about" and it gives a popup error window with "n".  Any other menu selection I get the same error.


One thing I did notice is this line when it created the docker.

 

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

 

I'm not sure where it is getting that 8080 from, but I am betting wherever this is happening is the source of my issue.  
  
I'm not sure what else to try. This is with the latest version (5.0.1) as of today and unRAID version 6.12.13.
 

 

docker run
  -d
  --name='binhex-qbittorrentvpn-test'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="ByteBunker"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn-test"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='[REMOVED]'
  -e 'VPN_PASS'='[REMOVED]'
  -e 'VPN_PROV'='airvpn'
  -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,192.168.254.0/24,198.18.3.0/24'
  -e 'WEBUI_PORT'='18080'
  -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 '18118:8118/tcp'
  -p '19118:9118/tcp'
  -p '18080:18080/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn-test':'/config':'rw'
  -v '/mnt/user/data/':'/data':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'
5d99a8d48703316dcb96b47d5ff355466dc5501d74b47210f6895d97ee5833d7

The command finished successfully!

 

supervisord.log

Edited by J4bber

  • Replies 5.3k
  • Views 1.2m
  • 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

  • Author
41 minutes ago, J4bber said:

When you go under the icon on the docker page and hover over the "WebUI" the link is still to 8080

This is because the web ui link will be using the default value for the port, to fix it click on 'edit' for the container, then toggle 'advanced view' and then change the value for 'WebUI' to the web ui port you want, for example:-

http://[IP]:[PORT:18080]

Note sure what is going on for your second question, can you post some more screenshots showing the issue.

  • Author
On 11/1/2024 at 8:33 AM, Hardcover9641 said:

The arm64 docker image 5.0.1-1-01 is still using qBit 5.0.0

investigating this.

 

Edit - Looks like a timing issue with upstream, re-kicked off the image build and i now see 5.0.1 is installed, please pull the latest image and try again.

1 hour ago, binhex said:

This is because the web ui link will be using the default value for the port, to fix it click on 'edit' for the container, then toggle 'advanced view' and then change the value for 'WebUI' to the web ui port you want, for example:-

http://[IP]:[PORT:18080]

Note sure what is going on for your second question, can you post some more screenshots showing the issue.

 

Ok, that fixed the WebUI. 

 

Now for the second question.  I figured out how to reproduce it.

 

I cleared all cookies associated with my server. 

 

I then opened the webui for the second instance (18080).  Everything works fine.  No errors.   While this one is open, I open the first instance (8080).  The second instance gives the "can't connect" error when the first instance opens.  Trying the about gives the popup.:

 

image.thumb.png.51178182932ea510114806dc8741974c.png

 

I tested this on chrome and firefox with the same results.

 

If the first instance (8080) is already open, and I open the second instance (18080) webui, the second instance has the error.  The first instance seems always to be the priority.

 

 

 

15 minutes ago, J4bber said:

 

If the first instance (8080) is already open, and I open the second instance (18080) webui, the second instance has the error.  The first instance seems always to be the priority.

 

 

 

Ok, I see what's happening.  The SID cookie is getting overwritten when the second one comes online.  I am guessing this is what is causing the problem because it thinks they are the same instance when they are not.

 

Before on 8080:

 

image.thumb.png.6aad14283758dbc3120085f43412c5de.png

 

open 18080 before login:

 

image.thumb.png.32f86458b0f4aa687554f0263ef9aa51.png

 

Log into 18080 and the cookie for both changes:

 

image.thumb.png.e78662934513dc0c325e145e5248b811.png

 

image.thumb.png.7cb27ba1e1ab6ea2c3f66401a5bdf2d6.png

Getting some odd behavior, image launches fine, but the WebUI times out (ERR_CONNECTION_TIMED_OUT). I tried it without VPN enabled and it launched without issue so I checked my credentials/ovpn files and refreshed those through my provider. I'm seeing the changed IP from the provider with curl ifconfig.me and I am able to ping 8.8.8.8 successfully from within the docker image. 
Relevant files requested are attached.

cmdexec.txt supervisord.log

same issue myself and a few others have, no one can seem to sort it.

48 minutes ago, ja444 said:

Getting some odd behavior, image launches fine, but the WebUI times out (ERR_CONNECTION_TIMED_OUT). I tried it without VPN enabled and it launched without issue so I checked my credentials/ovpn files and refreshed those through my provider. I'm seeing the changed IP from the provider with curl ifconfig.me and I am able to ping 8.8.8.8 successfully from within the docker image. 
Relevant files requested are attached.

cmdexec.txt 1.31 kB · 1 download supervisord.log 13.1 kB · 1 download

Your log shows a successful start. Are you trying to access the webUI from your LAN?

Edited by wgstarks

7 hours ago, binhex said:

That is the issue in a nutshell, Please see Q23 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Great, it worked. But why all of a sudden is this line required. My container was running fine without the two lines for a long time and on multiple docker hosts. Just curious :)

2 hours ago, wgstarks said:

Your log shows a successful start. Are you trying to access the webUI from your LAN?

Correct. Left clicking on the icon -> WebUI just leads to a timeout. 

I am running qbittorrent version 4.5.4 on unRAID. I use this version because of compatibility with trackers with whitelists.

 

Do we have to worry about this vulnerability as we are on a Linux base? 

Edited by urbanracer34

  • Author
On 11/1/2024 at 10:20 AM, nerbonne said:

and I worry that all the activity is hiding the fact that multiple people are having this problem.

 

6 hours ago, nerbonne said:

same issue myself and a few others have, no one can seem to sort it.

Multiple people have the same symptom, as in the inability to view the web ui, this does not mean they have the same problem, in most cases they do not, there are literally dozens of reasons for the vpn tunnel to not come up (web ui will not load until the tunnel is up to prevent ip leakage), i shall take a look at your specific problem when i get some free time (it's late here).

 

10 hours ago, binhex said:

investigating this.

 

Edit - Looks like a timing issue with upstream, re-kicked off the image build and i now see 5.0.1 is installed, please pull the latest image and try again.

Excellent, thank you!

  • Author
8 hours ago, binhex said:

 

Multiple people have the same symptom, as in the inability to view the web ui, this does not mean they have the same problem, in most cases they do not, there are literally dozens of reasons for the vpn tunnel to not come up (web ui will not load until the tunnel is up to prevent ip leakage), i shall take a look at your specific problem when i get some free time (it's late here).

 

 @nerbonne OK so taken a look, the issue is that you are specifying an IP address for the docker container that also exists within the LAN, from your command execution.txt file:-
 

  --net='br0'
  --ip='10.10.6.184'


So your options are:-

  • Switch to 'bridge' network, this image was designed around bridge network and is setup to use this.
  • Switch to wireguard (noted you are using openvpn), this should (when last tested) permit LAN access to the web ui with your configuration.
  • Create a secondary VLAN that is separate to your LAN range and use that specify an IP for the container
2 hours ago, binhex said:

 @nerbonne OK so taken a look, the issue is that you are specifying an IP address for the docker container that also exists within the LAN, from your command execution.txt file:-
 

  --net='br0'
  --ip='10.10.6.184'


So your options are:-

  • Switch to 'bridge' network, this image was designed around bridge network and is setup to use this.
  • Switch to wireguard (noted you are using openvpn), this should (when last tested) permit LAN access to the web ui with your configuration.
  • Create a secondary VLAN that is separate to your LAN range and use that specify an IP for the container

I keep very good records of the IPs on my LAN, the IP is most definitely not in use already.  If I disable the VPN, the GUI works.  That being said, I set it to bridge as you suggest and that is working.  Wireguard won't download the configuration file, it's possibly blocked in the country I'm in. 

 

Thanks for your assistance!

  • Author
9 minutes ago, nerbonne said:

I keep very good records of the IPs on my LAN, the IP is most definitely not in use already

I'm not suggesting it's in use, what I'm saying is that this image does not work if you specify a static IP for the container AND the IP address you have specified is also in the LAN_NETWORK range (which it is), it is designed to work in a bridge network (network of container and LAN are different), glad it's working in bridge mode.

I'm unable to access my webUI while connected to a VPN. I can however access the webui when I set VPN_ENABLED to "no" in the container settings. With VPN enabled, I keep getting a "gateway does not support nat-pmp" error in my qbit log, even when I enable NAT-PMP and select a P2P-enabled Proton server in the config.

 

Sorry for not attaching Supervisor log! I followed your instructions, but I found no supervisord.log file in Qbittorrent's /config. Not sure what to do about that, so I attached the qbittorrentvpn debug log instead.

Posted this back in September and never got a reply. If I could get some insights on this, that'd be much appreciated! Thank you.

Qbit debug log (1).docx Command execution (1).docx

 

On 11/3/2024 at 11:09 AM, J4bber said:

Ok, I see what's happening.  The SID cookie is getting overwritten when the second one comes online.  I am guessing this is what is causing the problem because it thinks they are the same instance when they are not.

 

 

After further testing this morning, I found that once I changed the WEBUI password on the second instance from the temporary credentials in the supervisord.log, the SIDs were different, and I could now open both at the same time.

 

So, I guess this is either the fix or the workaround. Regardless, I'll let you decide if any code changes, etc., need to be made on the backend.

Edited by J4bber

Switched to airvpn for  the port forwarding.  It seems to work and I tested it with a leak tester, but this one line in my logs has me suspect that I am missing something.


 

2024-11-04 12:44:13,104 DEBG 'start-script' stdout output:
[info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment


I got a port in my account on the airvpn site, I added it in the qbittorrent gui under connections and I also created a new port in unraid with this port, but I still get this during startup.  Am I reading too much into this or am I missing something ?

I do see a number of tracker timeouts or operation not permitted or host not found (authoritative), but not sure if that's just common.  I mainly use pubic torrents as I don't have access to any private sites.

 

TIA, Opie

 

Edited by opiekeith

On 11/3/2024 at 5:46 PM, urbanracer34 said:

I am running qbittorrent version 4.5.4 on unRAID. I use this version because of compatibility with trackers with whitelists.

 

Do we have to worry about this vulnerability as we are on a Linux base? 

Can someone please answer this for me? 

On 11/4/2024 at 5:37 PM, Andible said:

I'm unable to access my webUI while connected to a VPN. I can however access the webui when I set VPN_ENABLED to "no" in the container settings. With VPN enabled, I keep getting a "gateway does not support nat-pmp" error in my qbit log, even when I enable NAT-PMP and select a P2P-enabled Proton server in the config.

 

Sorry for not attaching Supervisor log! I followed your instructions, but I found no supervisord.log file in Qbittorrent's /config. Not sure what to do about that, so I attached the qbittorrentvpn debug log instead.

Posted this back in September and never got a reply. If I could get some insights on this, that'd be much appreciated! Thank you.

Qbit debug log (1).docxUnavailable Command execution (1).docxUnavailable

 

I have the exact same problem and I have followed the FAQ and input my CIDR correctly but it still does not work. There's something like 50+ other complaints over the years, on the forum here, Github and Reddit about the exact same issue due to the aggressive VPN/firewall blocking everything locally. So I have really checked and read through everything before coming here to request help.

 

Container IP and Port Mappings:

AA373E35-2D92-4C98-83DE-04C0E811A41F.png.2090e868a9fd583424650d59966264cc.png

 

Custom Docker network for all my publicly accessible apps:

319410CF-3416-4543-9D6D-50D6D69D7391.png.267d7229475d68066d104531ef242889.png

 

I have the WebUI port set to 8128:

148F35C8-1136-4A95-8768-9B50A1886764.thumb.png.65f0cdc7af043c67b9c55affcdfac721.png

 

LAN network variable is correct according to the FAQ:
86BC6EAA-3B06-4F9A-8F31-01A664801C4C.thumb.png.7339b2740921370acaeb5523be315641.png

 

Unraid is running on: 192.168.1.50 and qbittorrentvpn has the same IP address, and should be accessible at: 192.168.1.50:8128

 

But I get the usual:

85460126-3FB6-4A0C-ABD3-8AE1ED0BB2EB.png.884048118f9b428ebb6044412bb878dd.png

 

Using cloudflare I can of course access qbittorrent via the internet, however I have this behind zero trust cloudflare access. So I have to auth into that first and then into qbittorrent.

 

I still need local network access so I can use Radarr/Sonarr/Bazarr and the Flood WebUI.

 

@binhex I am really sorry to ping you mate, but can you explain why this doesn't work still, even after putting in the right values?

Edited by plantsandbinary

  • Author
2 hours ago, urbanracer34 said:

Can someone please answer this for me? 

 

2 hours ago, urbanracer34 said:

Do we have to worry about this vulnerability as we are on a Linux base? 

By the looks of this article I would say it is advisable to update, yes:- https://sharpsec.run/rce-vulnerability-in-qbittorrent/

AFAIK there have been no attacks in the wild yet, but it's better to be safe than sorry (i have updated).

2 hours ago, binhex said:

 

By the looks of this article I would say it is advisable to update, yes:- https://sharpsec.run/rce-vulnerability-in-qbittorrent/

AFAIK there have been no attacks in the wild yet, but it's better to be safe than sorry (i have updated).

I went to check my qbit and it shows version 4.6.3. I tried running a check for updates, force updating, and I even removed the container/image and pulled it from "previous apps". It still shows the same as what is in my screenshots. Am I missing something? Is the web UI version number different than the actual qbit version? Does this have anything to do with being on the binhex/arch-qbittorrentvpn:libtorrentv1 repo? Just want to make sure I don't leave myself open to the current vulnerability.

 

 image.png.1995963b2d7ede1721dab6030dd6f01f.pngimage.png.8025de0e0e2d75555445ea5292afea73.png

14 minutes ago, Zacaronii said:

Does this have anything to do with being on the binhex/arch-qbittorrentvpn:libtorrentv1 repo?

Yes, you've forced it to a 10 month old tag.

 

image.png.91fa1819b866819a94558236f8507bf4.png

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.