6 hours ago, bidalos said:

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:

Ok fixed it by deleting the wg0.conf then restart

cp wg0.conf wg0.conf.bak

rm wg0.conf

Incredibly thankful how easy this was to setup!
I ran "curl https://am.i.mullvad.net/connected" in the container's console and confirmed I was connected via Mullvad VPN.
I didn't add any inbound ports in the container's config.
At this point can I be confident that there will be no leaks? Even if I forgot to add time to my VPN and it expired?

I recently had my qbittorrentvpn docker blow up on my Unraid 7.2.4 server. Turned out that my Proton VPN cert had expired. I renewed it and recopied the new cert wg0 file into the directory but then I couldn't access the qbittorrent UI. I was finally able to get it and get everything connected back to all my Arr apps after deleting ten wg0 file and then restarting the container. Since then, I had a few downloads complete but now all are stuck at "Downloading metadata". I'm having no problems with Sonarr/Prowlarr finding and send the torrents over but qbit just won't download them at all. I could really use some help here if anyone has any ideas.

1 minute ago, PakledVueAdmin said:

I recently had my qbittorrentvpn docker blow up on my Unraid 7.2.4 server. Turned out that my Proton VPN cert had expired. I renewed it and recopied the new cert wg0 file into the directory but then I couldn't access the qbittorrent UI. I was finally able to get it and get everything connected back to all my Arr apps after deleting ten wg0 file and then restarting the container. Since then, I had a few downloads complete but now all are stuck at "Downloading metadata". I'm having no problems with Sonarr/Prowlarr finding and send the torrents over but qbit just won't download them at all. I could really use some help here if anyone has any ideas.

Ok, after about 10 mins the 3 test files that were stuck, started downloading on their own and the speeds were pretty quick. The files were moved into Plex pretty quickly as well. Do I just need a new set of trackers or something? I'm on the latest build (v5.1.4) so not sure if maybe I need to roll back to an earlier repository and if so, which one?

Hello @binhex . I've been using this container for years with openVPN and PIA with no issues at all. Recently, I switched to wiregard, and I updated the container because the template was not up to date anymore. In a nutshell, I had to switch network type from bridge to br0 and assign an ip, and I now feel a bit nervous because my true ip address may appear in Qbittorent WebUi...
XXX.XXX.XXX.XXX

How is it possible, and is there a risk for a leak using br0 as a network interface ?

Edit: Forgot to mention, I switched to br0 because I could not get wiregard working. In bridge mode, the container is stuck at

[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'... and webUI is never accessible.

Edited April 16Apr 16 by potjoe

Hi folks!

Looking for some assistance - I had a power outage recently and after everything was rebooted, qbit was pretty broken. I can't download anything from the webUI search function and I am getting the following error:

Failed to add torrent. Source: "[torrent name]". Reason: "expected value (list, dict, int or string) in bencoded string [bdecode:4]"

Fortunately I can still use .torrent files and have them download successfully, but then I noticed my up speed is extremely slow (maxes out at 30 KiB/s from what I can see). Not sure if these are related, but any guidance would be appreciated! Logs attached.

Thank you!

Edit: Wellp I feel a fool, rebuilt the container and still had the same issue but it turns out the search plugin I was using was bad. Everything seems fixed now at least.

Edited May 2May 2 by Jaxtah

Hi

I'm having the problem where the webui won't connect unless I turn VPN off.

I don't recall changing anything, just stopped working one day. I've been through the FAQ's and posts in this thread and tried lots of things that looked relevant, but nothing seems to work.

Looking at the log it seems like part of the setup is to call an API at PIA that returns properties of the server, but this call fails for some reason and the VPN doesn't start and so the webui also won't start. I tried just dropping the address into a web browser to see if the system was down and I get back a bunch of plausible looking text.

I have removed the plugin and started afresh, but no change.

Any ideas for what to try next?

supervisord.log command execution.txt

8 hours ago, joehbad said:

I'm having the problem where the webui won't connect unless I turn VPN off

I had the same problem and managed to solve it. I rebuilt the container and had the same issue but found the fix in the new container.

I had an issue in my wg0.conf file found here appdata/binhex-qbittorrentvpn/wireguard
I used this server list to find the new endpoint for that conf file. https://serverlist.piaservers.net/vpninfo/servers/v6

NOTE: MAKE SURE TO STOP THE CONTAINER BEFORE PROCEEDING

1) Find your endpoint from the PIA server list here https://serverlist.piaservers.net/vpninfo/servers/v6 You will want to get the name after the "dns:" variable of the selected region/server.

e.g if you wanted south hampton UK you would end up with "uk-southampton.pvt.site"

2) Navigate to the appdata/binhex-qbittorrentvpn/wireguard and open wg0.conf

3) Edit Endpoint to have that server name and save. e.g Endpoint = uk-southampton.pvt.site:1337

4) Start the container and open the webui.

This worked for me I hope it works for you as well.

Any questions let me know.

Edited May 1May 1 by baldmo
Editied as I didnt quote properly. changed to a better section to quote

After updating to 7.2.5 the template no longer works for me, and throws this error:

docker: Error response from daemon: invalid port specification: "0/tcp"

presumably because of the docker update to version 29

11 hours ago, Tethgar said:

After updating to 7.2.5 the template no longer works for me, and throws this error:

docker: Error response from daemon: invalid port specification: "0/tcp"

presumably because of the docker update to version 29

Having the same issue, but mine shows as "0/udp"

Were you able to solve this issue or waiting for an update on the container?

On 4/30/2026 at 5:49 PM, baldmo said:

I had the same problem and managed to solve it. I rebuilt the container and had the same issue but found the fix in the new container.

I had an issue in my wg0.conf file found here appdata/binhex-qbittorrentvpn/wireguard
I used this server list to find the new endpoint for that conf file. https://serverlist.piaservers.net/vpninfo/servers/v6

NOTE: MAKE SURE TO STOP THE CONTAINER BEFORE PROCEEDING

1) Find your endpoint from the PIA server list here https://serverlist.piaservers.net/vpninfo/servers/v6 You will want to get the name after the "dns:" variable of the selected region/server.

e.g if you wanted south hampton UK you would end up with "uk-southampton.pvt.site"

2) Navigate to the appdata/binhex-qbittorrentvpn/wireguard and open wg0.conf

3) Edit Endpoint to have that server name and save. e.g Endpoint = uk-southampton.pvt.site:1337

4) Start the container and open the webui.

This worked for me I hope it works for you as well.

Any questions let me know.

Seeing the same issue after updating to 7.2.5 and this didn't work for me.

5 minutes ago, Sigvard said:

Seeing the same issue after updating to 7.2.5 and this didn't work for me.

There are many reasons why you wouldn’t be able to connect with VPN enabled and presumably can connect with VPN disabled (since you say you have the same issue). If you need help with this you’ll need to attach your docker run command and full supervisord log to your next post. Be sure to redact users/passwords.

I am also having issues after upgrading to unraid 7.2.5.

After the update I could not start the container, similar to above "docker: Error response from daemon: invalid port specification: "0/tcp""

I tried to remove the container and reinstall using "Previously Apps", and tried using "Add Container", both methods end with: (Username and Password have been obscured)

docker run

-d

--name='binhex-qbittorrentvpn'

--net='bridge'

--pids-limit 2048

--privileged=true

-e TZ="Europe/London"

-e HOST_OS="Unraid"

-e HOST_HOSTNAME="Tower"

-e HOST_CONTAINERNAME="binhex-qbittorrentvpn"

-e 'VPN_ENABLED'='yes'

-e 'VPN_USER'='OBSCURED'

-e 'VPN_PASS'='OBSCURED'

-e 'VPN_PROV'='pia'

-e 'VPN_CLIENT'='wireguard'

-e 'STRICT_PORT_FORWARD'='yes'

-e 'ENABLE_PRIVOXY'='yes'

-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'='false'

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

-p '8118:8118/tcp'

-p '9118:9118/tcp'

-p '58946:000/tcp'

-v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'

-v '/mnt/user/data':'/data':'rw'

-v '/mnt/user/binhex-shared/':'/shared':'rw'

--sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

docker: Error response from daemon: invalid port specification: "0/tcp"

Run 'docker run --help' for more information

The command failed.

I''m not really sure what to try next...

Edited May 2May 2 by JBanner

1 hour ago, JBanner said:

I am also having issues after upgrading to unraid 7.2.5.

I had a similar error after the update but resolved it by re-applying the settings. Make a change to any setting and then revert it and click “apply”. I think I picked a setting at random, typed in a space and then deleted it so nothing was actually changed but it will trigger the “apply” button to appear. After re-applying the same settings everything worked.

1 minute ago, wgstarks said:

I had a similar error after the update but resolved it by re-applying the settings. Make a change to any setting and then revert it and click “apply”. I think I picked a setting at random, typed in a space and then deleted it so nothing was actually changed but it will trigger the “apply” button to appear. After re-applying the same settings everything worked.

Thanks for the reply.... I've already tried toggling a few different things off , applying or reinstalling and still get the same... I've tried toggling the vpn off and on and tried several network types. I have reset everything back to how it was for now, but still can't get it to work.

2 minutes ago, JBanner said:

Thanks for the reply.... I've already tried toggling a few different things off , applying or reinstalling and still get the same... I've tried toggling the vpn off and on and tried several network types. I have reset everything back to how it was for now, but still can't get it to work.

Have you tried reverting to the prior OS?

1 minute ago, wgstarks said:

Have you tried reverting to the prior OS?

Nope, not yet. I was going to see if there were any other options first.

Tools>Downgrade OS

On 5/1/2026 at 3:23 AM, Tethgar said:

After updating to 7.2.5 the template no longer works for me, and throws this error:

docker: Error response from daemon: invalid port specification: "0/tcp"

presumably because of the docker update to version 29

I've narrowed this issue down to the port mapping for 58946/tcp, the broken configuration shows "-p '58946:000/tcp'" based on the error logs.

While troubleshooting I some how managed to remove mine completely, after I added it back in via "Community Applications" now when expanding the "more settings" no longer have 58946 showing the "000" ports and its now running again on 7.2.5. Hope this helps someone!

4 hours ago, JBanner said:

  4 hours ago, wgstarks said:

Have you tried reverting to the prior OS?

Can confirm downgrading OS then re-installing from Previous Apps fixes the issue

Hi, I've got qbittorrent-vpn up and running. And I have a few questions.

1) I have a container set to bridge mode, is there any way to make it work with its own IP address - macvlan?

2) On one tracker it tells me that I'm connecting via multiple IP addresses. Is this okay? I'm using PIA.

3) Can you check the logs? When I start the container, I have to wait 2-5 minutes for qbittorrent to connect via OpenVPN to PIA. Is this normal?

<font dir="auto" style="vertical-align: inherit;"><font dir="auto" style="vertical-align: inherit;">pia-log.txt</font></font>

qBittorentvpn hangs

supervisord (2).log

2 hours ago, mburlia said:

qBittorentvpn hangs

supervisord (2).log

Not sure what you mean by “hangs”. Your log shows a successful startup.

To control qBittorrent, access the WebUI at: http://localhost:8080

The WebUI administrator username is: admin

The WebUI administrator password was not set. A temporary password is provided for this session: ZsQ2egABs

You should set your own password in program preferences.

2026-05-03 11:31:46,349 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process listening on port 8080

Are you using the temp user and password shown in the log? The qBittorrent devs require their use and setting of a new password on first launch.

15 minutes ago, Fin745 said:

Just updated to the latest version of qbittorrent v5.2.0 and I keep getting this over and over, downgraded back to v5.1.4 and everything now works.

Edit changed to VPN_AUTO_PORT_FORWARD=false from true and it started up fine, 5.1.4 it was true.

[2026-05-04 03:12:59] [INF] [FORWARDER] Checking if forwarded port [37001] is reachable...
[2026-05-04 03:13:00] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:01] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:01] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:03] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:03] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:05] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:05] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:06] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:06] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:08] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:08] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:10] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:10] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:11] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:11] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:13] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:13] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:15] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:15] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:16] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:16] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:18] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:18] [INF] [QBITTORRENT] Starting with forwarded port [37001].
[2026-05-04 03:13:20] [INF] [QBITTORRENT] Delaying start until forwarded port is available.
[2026-05-04 03:13:20] [INF] [QBITTORRENT] Starting with forwarded port [37001].

not sure who's image your using but its not mine, that env var doesn't exist and i havent pushed out 5.2.0 yet.

binhex/arch-qbittorrentvpn:latest or 5.2 is broken, had to downgrade to binhex/arch-qbittorrentvpn:5.1