Alright I have a different issue now: I cannot log in.
Solved ✅

I tried earlier login data, and the default username and password: "admin" // "adminadmin".

I also tried deleting user/appdata/binhex-qbittorrentvpn/qBittorrent/config/qBittorrent.conf + restart to generate a new one - didn't work.

I also tested adding either of these two ideas as lines into the .conf - also to no avail.

[Preferences]
WebUI\AuthSubnetWhitelist=192.168.1.0/24 #use your local subnet
WebUI\AuthSubnetWhitelistEnabled=true

WebUI\User=admin
WebUI\Password_PBKDF2="@bytearray(72ycFfm20SU9J1917+v4rg==:rmIGmlb3YZukCUlIghBhnu/8ovMGEqloSqoIlga7Tfh/tm0m7uGgHibe/B/rpn7Bs65+SrVcp1AAtPKm5AoVfw==)"

When deleting the .conf file, a file with the following info is created:

qBittorrent.conf

[AutoRun]

enabled=false

program=

[BitTorrent]

Session\AddTorrentStopped=false

Session\Interface=wg0

Session\InterfaceName=wg0

Session\Port=45130

Session\QueueingSystemEnabled=true

Session\SSL\Port=31869

Session\ShareLimitAction=Stop

Session\UseRandomPort=false

[Meta]

MigrationVersion=8

[Network]

PortForwardingEnabled=false

Proxy\HostnameLookupEnabled=false

Proxy\Profiles\BitTorrent=true

Proxy\Profiles\Misc=true

Proxy\Profiles\RSS=true

[Preferences]

Connection\Interface=wg0

Connection\InterfaceName=wg0

Connection\PortRangeMin=6881

Connection\UPnP=false

General\Locale=en

General\UseRandomPort=false

WebUI\Address=*

WebUI\CSRFProtection=false

WebUI\LocalHostAuth=false

WebUI\ServerDomains=*

WebUI\UseUPnP=false

I tested logging in from different browsers and OS.

Am I overlooking anything? Do I need to rollback to an earlier version?

[EDIT] Found the solution.

What worked for me:

Downgraded to 4.6.0-1-01 binhex/arch-qbittorrentvpn:4.6.0-1-01 as mentioned here and followed it's step.
I could log in right away using the default username and password: "admin" // "adminadmin".

It all works now. Finally.

Edited May 16May 16 by IMACRAB

About a year or so ago the devs for qBittorrent decided that everyone must have a secure password so the old default password won’t work with current versions of the app. There should be a temporary password in the supervisord.log file which will allow you to login and create a permanent password.

On 5/11/2026 at 7:19 PM, nraygun said:

Do we still have to use arch-qbittorrentvpn:libtorrentv1 these days?

I don't even remember what was fixed by using the libtorrentv1 version. My Qbittorrent container shows it using version 4.6.3.

If I don't need to use the libtorrentv1 version, can I just go to the latest without changing my appdata?

Then again, if it's not broken, don't fix it?

I went to binhex/arch-qbittorrentvpn:latest and it seems fine. It went from 4.6.3 to 5.2.0 with no problems. :-)

8 hours ago, nraygun said:

Do we still have to use arch-qbittorrentvpn:libtorrentv1 these days?

if you are on unraid v7.x.x then you do not need to use libtorrentv1

6 hours ago, binhex said:

if you are on unraid v7.x.x then you do not need to use libtorrentv1

Thanks, I went ahead and loaded the non-libtorrentv1 container and all seems well. Looks like it's using libtorrent 2.0.12.0.

am i the only one who isnt a fan of the dialog box that pops up when you add torrents now?

Recently having issues with phantom hit and run issues on a UNIT3D tracker. Client says its seeding, but the tracker thinks it is not. Hours seeding is not matching up.

Never seen this before and tracker support isn't able to help me. I have to randomly restart seeding to get it to register.

Hi, anyone gotten mousehole to work with qbittorrentvpn? what steps did you take to make it work? tnx

I'm having problems with ProtonVPN using a OpenVPN config file, it will start up but will show Firewalled. I've tried looking it up and looking around the forms but couldn't find anything that worked.

Docker.txt supervisord.log

So Left it to site for a few hours, and it just started working... No idea why but I'm all good.

Edited May 31May 31 by Fadeless
Problem fixed its self.

Hello,

after updating unraid OS from 7.2.3 to 7.2.6 I have noticed qBittorrent stops working after (almost exactly) 15 minutes. I am now running latest unraid 7.3.1 but the issues persists.

I'm using PIA with Wireguard. The debug logs and the qBittorrent logs do not show any error. The watchdog keeps checking port and IP. The web interface just becomes unavailable.

Can you help me where I should start investigating?

Container logs:

2026-06-01 09:39:13,560 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:39:13,570 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-06-01 09:39:13,578 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is (same port)

[debug] qBittorrent incoming port is (same port)

[debug] VPN IP is (same public IP)

[debug] qBittorrent IP is (same public IP)

2026-06-01 09:39:43,586 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:39:43,621 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:39:43,622 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:39:43,631 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-06-01 09:39:43,639 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is (same port)

[debug] qBittorrent incoming port is (same port)

[debug] VPN IP is (same public IP)

[debug] qBittorrent IP is (same public IP)

2026-06-01 09:40:13,647 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:40:13,682 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:40:13,683 DEBG 'watchdog-script' stdout output:

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

2026-06-01 09:40:13,692 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

2026-06-01 09:40:13,700 DEBG 'watchdog-script' stdout output:

[debug] VPN incoming port is (same port)

[debug] qBittorrent incoming port is (same port)

[debug] VPN IP is (same public IP)

2026-06-01 09:40:13,700 DEBG 'watchdog-script' stdout output:

[debug] qBittorrent IP is (same public IP)

Thanks!!

binhex-qbittorrentvpn.xml

Edited June 9Jun 9 by 3dee

On 5/14/2026 at 8:38 AM, crowdx42 said:

So I tried the latest Unraid update, 7.2.6 to 7.3.0 and had the issue with webui not working, reverted to previous version and everything works again. Weird.

Has anyone figured out why Unraid 7.3.0 is breaking the VPN functionality? I can't access webUI either or resolve IP via console, but if I turn off VPN and restart the container it will work normally.

25 minutes ago, Randyd718 said:

Has anyone figured out why Unraid 7.3.0 is breaking the VPN functionality? I can't access webUI either or resolve IP via console, but if I turn off VPN and restart the container it will work normally.

Working just fine for me on 7.3.1. Enable VPN and restart the docker then attach your docker run command and entire supervisord log to your next post. Be sure to redact users/passwords.

20 hours ago, wgstarks said:

Working just fine for me on 7.3.1. Enable VPN and restart the docker then attach your docker run command and entire supervisord log to your next post. Be sure to redact users/passwords.

Appreciate the reply. Here is my docker run https://pastebin.com/cBfKVpR3

And I've attached my entire supervisord log. I don't think there are users/passwords in here based on a quick skim so please let me know if I should delete it lol.

supervisord.log

40 minutes ago, Randyd718 said:

Appreciate the reply. Here is my docker run https://pastebin.com/cBfKVpR3

And I've attached my entire supervisord log. I don't think there are users/passwords in here based on a quick skim so please let me know if I should delete it lol.

supervisord.log

There was a post a few weeks ago with the same problems as you. No valid WireGuard connection. You should download a new WireGuard configuration file from ProtonVPN and install it.

7 minutes ago, wgstarks said:

There was a post a few weeks ago with the same problems as you. No valid WireGuard connection. You should download a new WireGuard configuration file from ProtonVPN and install it.

Confirming this did fix it. Sorry. I have had this exact issue before and it was actually the container's fault, with updating config having no effect. I should have checked

58 minutes ago, Randyd718 said:

Confirming this did fix it. Sorry. I have had this exact issue before and it was actually the container's fault, with updating config having no effect. I should have checked

There are many situations that can cause the failure to connect when VPN is enabled. Anything that prevents the VPN tunnel from connecting will stop the qbit app from starting and as a result there is no webUI to connect to. So many issues can cause this symptom.

Hello,

may you assist me? The container started at 9:40 and the web interface became unavailable at 9:41. qbittorrent works for like 10-15 minutes after starting it up and then suddenly stops working.

Thanks!

On 6/4/2026 at 12:15 PM, 3dee said:

Hello,

may you assist me? The container started at 9:40 and the web interface became unavailable at 9:41. qbittorrent works for like 10-15 minutes after starting it up and then suddenly stops working.

Thanks!

Deleting the container with image and running docker system prune -a --volumes did not help

Same issue with OpenVPN

I just don't understand why it stops working after a while, debug logging continues to check IP as if it was continuing to work. Is it possible to enable some advanced debugging?

I'm having issues but they seem to be related to duckdns.org. I've tried on multiple devices on different networks but continually getting a 404 Not Found error. Can anyone else confirm?

Yup, same here, seems they're down. Kinda known for that happening.

17 minutes ago, Kilrah said:

Yup, same here, seems they're down. Kinda known for that happening.

Ok, good. I wanted to make sure it wasn't just me. Ironically enough, I've been using duckdns for several years and first time I notice it's down. Guess I was just lucky...

On 6/5/2026 at 5:55 PM, 3dee said:

Deleting the container with image and running docker system prune -a --volumes did not help

Same issue with OpenVPN

I just don't understand why it stops working after a while, debug logging continues to check IP as if it was continuing to work. Is it possible to enable some advanced debugging?

Issue could not be retraced. Deleting the containers appdata folder (containers /config) fixed it.

16 hours ago, betaman said:

Ok, good. I wanted to make sure it wasn't just me. Ironically enough, I've been using duckdns for several years and first time I notice it's down. Guess I was just lucky...

Still down for me. Starting to wonder if something more long term is up with duckdns?

Just installed this on UNRAID 7.3.1. Had to switch to Usermode for Wireguard to work. Also, Web UI never loads. I tried connecting the port 8085, but it never loads. LAN is set to proper LAN in the Vars.

Is this still working on UNRAID 7.3.1 ??

I can run binhex-delugevpn no issues, but wanted to try switching to qbittorrentvpn.

2026-06-09 20:50:29,373 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8085...

2026-06-09 20:50:29,753 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8085

1 minute ago, Pducharme said:

Is this still working on UNRAID 7.3.1 ??

Yes. Not sure it’ll work with WireGuard though. The log snippet you posted shows a successful start. You should be able to connect to the webUI from your local network.

Edited June 10Jun 10 by wgstarks