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

Ok and Thanks!

Will do some more testing to see if I can replicate the issues myself. The last time it happened to me it was actually a power failure and a crash and not a normal reboot. I will try to see if that is the case that makes the config disappear. Can't do the test this evening but will conduct it tomorrow and report back.

  • 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

I use an external drive mounted via UD for /data. It’s set to r/w slave in the docker configuration. I’m in the process of moving /data to a cache pool mounted via unRAID webUI. Does this also need to be r/w slave when I edit the docker configuration?

Can someone tell me if the qbittorrentVPN container is impacted by the Log4j vulnerability?

Hello.  I recently have not been able to login to the web ui.  I am using the defaults user: admin and pass: adminadmin, but it is no longer working.  Any thoughts?  Thank you in advance for any assistance.

49 minutes ago, Rojen Mcche said:

Hello.  I recently have not been able to login to the web ui.  I am using the defaults user: admin and pass: adminadmin, but it is no longer working.  Any thoughts?  Thank you in advance for any assistance.

Attach the supervisord log to your next post. It’s in the appdata folder.

1 hour ago, Rojen Mcche said:

Hello.  I recently have not been able to login to the web ui.  I am using the defaults user: admin and pass: adminadmin, but it is no longer working.  Any thoughts?  Thank you in advance for any assistance.

 

I am having same issue, I thought it was just a bad config so started fresh and still no gui

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='REMOVED' -e 'VPN_PASS'='REMOVED' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.168.1.0/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:8081]/' -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:8081/tcp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/data/':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

fc518df496afdbf3232614dd222f65b2b313e80fc07197bcb5d81fb1abfbdf6c

The command finished successfully!

 

Also tried changing ports just incase theirs a conflict with another container but to be fair nothing has changed.

supervisord.zip

Edited by bally12345

20 minutes ago, bally12345 said:

am having same issue, I thought it was just a bad config so started fresh and still no gui

That log shows a successful start. Have you tried a different browser?

That log shows a successful start. Have you tried a different browser?
Oddly I later connect to my VM and it works! But on my 2 laptops and desktop it wouldn't connect. Weird...

Sent from my SM-G991B using Tapatalk

4 minutes ago, bally12345 said:

Oddly I later connect to my VM and it works! But on my 2 laptops and desktop it wouldn't connect. Weird...

Sent from my SM-G991B using Tapatalk
 

We’re you connecting from the same network?

Hey @binhex and all other who might help me.

 

I successfully got the qbittorrent docker running also with connectiong my *arr services to it. 

 

I have two (only one, privoxy works fine :) ) problems which i couldnt resolve yet. 

 

First one is to access qbittorrent and the *arrs (since these are now part of the qbittorrent net) through nginxproxymanager via domain: Accessing the services (torrent and *arrs) via [IP-Adrress]:[Port] works just fine. But i have set up my home network to resolve domain names and proxied them through nginxproxymanager. But this does not work, i always get a timeout when trying to access via domain. Is there any setting necessary to get this to work?

 

Second one is privoxy: NVM it just works now. 

Hi - I'm reviewing through the pages of this threat but just wanted to ask if anyone had any info - what size are you guys usually seeing on your container? mine is coming in at about 1gb which seems large, I'm trying to diagnose this or see if it's normal for the container.

For the last few weeks I have had issues with the privoxy HTTP proxy in qbittorrent. the *arr's can't seem to connect to anything through it most of the time.

 

I tried using the binhex dedicated privoxy container that supported Socks5 proxy and they work fine through that but that is another VPN connection I have running.

 

Does anyone know why the HTTP proxy in qbittorrent stopped working? Or does anyone know how to enable a socks5 proxy in it?

 

I have not changed any settings in months and it was working fine.

Seeing same issue myself, haven't touched config in months and it's been working but now it seems nothing is connecting and I cannot view web UI.

 

Edit: Rebooted Unraid, left this docker stopped, did a force update, then started again watching logs and now it's got an accessible web GUI again. Very odd but can't say the force update definitively helped it or was just coincidence.

Edited by Econaut

I'm having some weird issues with speed.

 

I have a gigabit connection. When starting a large torrent, the speed will shoot up to ~80-100 MBps no problem, stay there for a few seconds, and then plummet back down to the single digits, sometimes as low as 2 MBps. It'll stay there for the rest of the download, not speeding up.

 

This even happens with slower torrents. A bad torrent might start at around 15 MB/s, then also drop down after a few percent has finished to the single digits.

 

I'm using wireguard with mullvad. I can confirm the server I'm connecting to is capable of gigabit speeds, so I'm not really sure what the issue is.

 

Connections status is green, so the port is properly forwarded. I also set the protocol to TCP only, but no luck with either TCP or TCP/uTP

 

Edit: Just bought a month of PIA, same issue. The speed will shoot up, then drop significantly.

 

Edit2: Just tested a torrent on my desktop using the same wireguard config. It's not as aggressive, but it still dropped from 80 MB/s to ~20 MB/s. So I guess it isn't an unraid-specific issue. Maybe something to do with my ISP? Weird that VPN traffic would be throttled though

Edited by lp0101

I seem to be having general PIA wireguard VPN issues in addition to the prioxy issues above as well. Takes a long time for the qbittorrent to start up and it seems to be during the VPN setup. Then the connection seems really unstable with downloads sometimes not starting at all, others going very slow and other working normally.

 

Once it starts working normally, it seems to stay that way as long as I don't touch anything. Very inconsistent though.

Edited by TexasUnraid

I'm having trouble downloading. I've switched between OpenVPN and wireguard and different locations doesn't change anything.

3 minutes ago, Eclection said:

I'm having trouble downloading. I've switched between OpenVPN and wireguard and different locations doesn't change anything.

Attach your supervisord log to your next post. Be sure to redact user/password.

5 hours ago, wgstarks said:

Attach your supervisord log to your next post. Be sure to redact user/password.

I can't upload log.

9 hours ago, Eclection said:

I can't upload log.

Just use the “choose file” button to select it and then “insert” to add it to your post.

An alternative would be to paste it into a code window. Just click the “</>” button at the top of your reply.

Any help

2 hours ago, Eclection said:

Any help

I don’t know what’s going on with your connection but you should probably change your user name and password since they weren’t redacted.

 

Have you tried switching PIA servers. Just a wild guess.

Hello,

 

I updated my Docker container to the latest qBT release (4.4.0) and for some reason it changed some of my config settings. The paths for completed, temporary, copy torrents to and copy finished torrents to folders had all been reset to locations inside the container. It also reset my rate limits on the speed tab. The more serious configuration setting was that it reverted to using any available interface instead of tun0. I caught it after about 2 hrs of run-time.

 

It's working as expected now that I've reset everything, but I just wanted to mention it in case others experience the same issue.

 

49 minutes ago, AgentXXL said:

Hello,

 

I updated my Docker container to the latest qBT release (4.4.0) and for some reason it changed some of my config settings. The paths for completed, temporary, copy torrents to and copy finished torrents to folders had all been reset to locations inside the container. It also reset my rate limits on the speed tab. The more serious configuration setting was that it reverted to using any available interface instead of tun0. I caught it after about 2 hrs of run-time.

 

It's working as expected now that I've reset everything, but I just wanted to mention it in case others experience the same issue.

 

I have a similar issue, the config file doesn't seems to have changed, but the save path of each torrent as been change to /config/qBittorrent/downloads and qbitorrent is now moving all the files to the inside of the container (into my cache drive). Reverting to the previous image (4.3.9-2-01) seems to fix the issue.

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.