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

32 minutes ago, wgstarks said:

Afraid I’m out of ideas. Usually when people have this sort of issue it’s because they’re trying to login from outside the configured LAN network.

thanks for trying - its very fustrating.

The most annoying bit is that it worked before just fine.

its when i changed everything to align to the trash guides, that it suddentlly broke

I think that sonarr and radarr and prowlar are all connunicating just fine, althoght I have stopped any activity there whilist im trying to get the webgui to behave.

Everythig is working fine - I just cant get in to it to actually use it as intended!

IM going to try another computer and login with that - incase my regular desktop has something buried somewhre that is causing problems.

After that - ill delete it and try again to see if that fixes it

ill update once i have soemthing to share

thanks again

  • Replies 5.2k
  • 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

You might try getting help on whatever forum trash uses.

52 minutes ago, dolphinspanker said:

After that - ill delete it and try again to see if that fixes it

If you get to this point be sure to rename your qbit appdata folder to something like old_qBittorrent so that the install won’t re-use the old settings. That should eliminate anything you might have set from the trash guide. If a fresh install works you can delete the old folder once you’re sure you no longer need anything in it. You may want to re-use your ovpn/wg0 file.

On 7/30/2026 at 3:31 AM, dolphinspanker said:

thanks for trying - its very fustrating.

The most annoying bit is that it worked before just fine.

its when i changed everything to align to the trash guides, that it suddentlly broke

I think that sonarr and radarr and prowlar are all connunicating just fine, althoght I have stopped any activity there whilist im trying to get the webgui to behave.

Everythig is working fine - I just cant get in to it to actually use it as intended!

IM going to try another computer and login with that - incase my regular desktop has something buried somewhre that is causing problems.

After that - ill delete it and try again to see if that fixes it

ill update once i have soemthing to share

thanks again

Hello.

I had a similar problem today. I have been running Unraid for over 3 years now with zeros issues on this container.

Here is what I did to get it resolved:

Fix: grab a fresh .ovpn from your provider (different city, in case a whole site was retired), drop it in /config/openvpn/, delete the old one — binhex containers pick at random when several are present, which makes the fault look intermittent — and restart. Connected first try.

Shout if you need further assistance

16 hours ago, wgstarks said:

Try changing your PIA endpoint.

I tried six different endpoints in multiple countries, including ones labeled "streaming optimized", still can't open the UI.

1 hour ago, bcr621 said:

I tried six different endpoints in multiple countries, including ones labeled "streaming optimized", still can't open the UI.

I changed it three more times and now it's working ???

I guess I'll come back when it stops again.

My suspicion is that it’s a PIA issue.

On 8/3/2026 at 11:44 AM, wgstarks said:

My suspicion is that it’s a PIA issue.

I think more than just me would be having problems if it was a PIA issue.

For the record, this only started happening after my flash drive failed and had to be replaced. I was using the container for six months without an issue.

10 minutes ago, bcr621 said:

For the record, this only started happening after my flash drive failed and had to be replaced. I was using the container for six months without an issue.

Probably won’t ever know for sure. Obviously not something on your end though or it would still be broken.

On 8/3/2026 at 3:56 PM, bcr621 said:

I tried six different endpoints in multiple countries, including ones labeled "streaming optimized", still can't open the UI.

I am facing the same issue

15 minutes ago, janfredrik said:

I am facing the same issue

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

I was having an issue with qbittorent showing that it was disconnected. I restarted the docker container, and now I can no longer access the web UI.

Looking in the logs it appears this is the issue, but I am unsure how to proceed:

2026-08-07 23:36:50,573 DEBG 'start-script' stdout output:
2026-08-07 23:36:50 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2026-08-07 23:36:50 TLS Error: TLS handshake failed

2026-08-07 23:36:50,573 DEBG 'start-script' stdout output:
2026-08-07 23:36:50 SIGHUP[soft,tls-error] received, process restarting

I am using NordVPN, I re-entered the credentials for it in case there was an issue with them, but no change.

2 hours ago, VulpesDormiens said:

I was having an issue with qbittorent showing that it was disconnected. I restarted the docker container, and now I can no longer access the web UI.

Looking in the logs it appears this is the issue, but I am unsure how to proceed:

2026-08-07 23:36:50,573 DEBG 'start-script' stdout output:
2026-08-07 23:36:50 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2026-08-07 23:36:50 TLS Error: TLS handshake failed

2026-08-07 23:36:50,573 DEBG 'start-script' stdout output:
2026-08-07 23:36:50 SIGHUP[soft,tls-error] received, process restarting

I am using NordVPN, I re-entered the credentials for it in case there was an issue with them, but no change.

Download a new .ovpn file from your vpn provider and try again.

On 7/30/2026 at 9:31 AM, dolphinspanker said:

thanks for trying - its very fustrating.

The most annoying bit is that it worked before just fine.

its when i changed everything to align to the trash guides, that it suddentlly broke

I think that sonarr and radarr and prowlar are all connunicating just fine, althoght I have stopped any activity there whilist im trying to get the webgui to behave.

Everythig is working fine - I just cant get in to it to actually use it as intended!

IM going to try another computer and login with that - incase my regular desktop has something buried somewhre that is causing problems.

After that - ill delete it and try again to see if that fixes it

ill update once i have soemthing to share

thanks again

So - Have an update

Turns out, Tailscale was stopping the connection to QBitorrent. It doesn't seem to stop anything else working, just QBitorrent.

I worked this out, when my daughter logged into her account, and tailscale started - creating an endpoint in her name.

When I went to use my account (with her logged in already) , Tailscale wouldnt start - and QBitorrent webui works!

Turning Tailscale on and off blocks/lets me in!

Even when I am on the same network as the server, Tailscale still prevents connection to qbitorrent.

PIA also stops all connections to the server, even with split tunnel and local networks allowed - so I turn this off when Im working on the server - but this wasnt my problem - I already knew this.

Now just to find a way to get the webui to open to 8085 instead of 8080 by default - 8085 connects and my arr stack points to 8085 and all works - just the webui defaults to 8080 still! - not the end of the world, just annoying!

Thanks to everyone who help troubleshoot.

Edited by dolphinspanker
added in extra info

2 hours ago, dolphinspanker said:

Now just to find a way to get the webui to open to 8085 instead of 8080 by default - 8085 connects and my arr stack points to 8085 and all works - just the webui defaults to 8080 still! - not the end of the world, just annoying!

I’m guessing you’re referring to the link from the docker tab??? If you want to change this open the docker configuration, set the switch in the top right corner to advanced and look for the WebUI field.

IMG_0945.jpeg

Set the port number to 8085 and click Apply.

6 hours ago, strike said:

Download a new .ovpn file from your vpn provider and try again.

That was it! Thank you.

19 hours ago, wgstarks said:

I’m guessing you’re referring to the link from the docker tab??? If you want to change this open the docker configuration, set the switch in the top right corner to advanced and look for the WebUI field.

IMG_0945.jpeg

Set the port number to 8085 and click Apply.

Thanks - found it! id set every other port variable I could find - just not that one! All sorted!

  • 2 weeks later...

-edit- Uuuhhhh, since doing the debug report it seems like the problem has massively decreased. Now it can handle 150 connections and while that thrashes CPU2 (6 core CPU) it doesn't interfere with the operation of unraid. I changed nothing else and this is not the first time I restarted it or changed any settings. So. Uh. I'll let you know. -edit-

Just started using a new tracker and now binhex-qbittorrentvpn hogs the CPU to the point of nothing else on the unraid server works for about 10-30 minutes when unraid crashes out completely.

In Glaces it seems like the openvpn task is the main hog but qbittorrent-nox is doing a lot too. If I reduce the max global connections to 10 it makes the server usable. 20 is enough for CPU overrun and crash.

Using the torguard magnet link it is successfully using the VPN.

I'm a beginner in both unraid and linux generally. Thanks for your time.

unraidqbitexecution.txt qbitdebug.log

Edited by bonzamate
Update on status

Hello, today I have issues with PIA Wireguard setup. looks like PIA is changing domains? Any endpoint with .privacy.network still works but the endpoint I use changed to .pvt.site and any of these I try will not work?

When using a .pvt.site address I always get: [warn] Unable to successfully download PIA json payload from URL 'https://10.173.0.1:19999/getSignature' using token

2026-08-19 06:29:37,042 DEBG 'start-script' stdout output:

These are working still

[info] cyprus.privacy.network all

[info] ca-montreal.privacy.network

[info] venezuela.privacy.network

[info] de-germany-so.privacy.network

[info] ca-toronto.privacy.network

[info] nl-netherlands-so.privacy.network

[info] ca-vancouver.privacy.network

[info] ua.privacy.network

[info] panama.privacy.network

[info] morocco.privacy.network

[info] nl-amsterdam.privacy.network

Anything like this is not working

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.pvt.site

[info] armenia.pvt.site

having trouble after a reboot of the server...this is all I am getting

2026-08-23 15:28:32,574 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2026-08-23 15:28:32,574 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2026-08-23 15:28:32,584 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-08-23 15:28:32,588 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2026-08-23 15:28:32,588 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2026-08-23 15:28:32,589 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2026-08-23 15:28:32,595 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2026-08-23 15:28:32,605 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-08-23 15:28:32,618 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2026-08-23 15:28:32,622 DEBG 'start-script' stderr output:

[#] wg addconf wg0 /dev/fd/63

2026-08-23 15:28:32,624 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.2.0.2/32 dev wg0

2026-08-23 15:28:32,636 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

2026-08-23 15:28:32,650 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

2026-08-23 15:28:32,652 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

2026-08-23 15:28:32,654 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

2026-08-23 15:28:32,656 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2026-08-23 15:28:32,662 DEBG 'start-script' stderr output:

[#] nft -f /dev/fd/63

2026-08-23 15:28:32,668 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

and WebUI isnt loading...

then the rest of this shows up after a long wait...

any ideas?

2026-08-23 16:23:23,620 DEBG 'start-script' stdout output:

[info] Successfully brought Wireguard interface 'down'

2026-08-23 16:23:23,620 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2026-08-23 16:23:23,631 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2026-08-23 16:23:23,644 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2026-08-23 16:23:23,659 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2026-08-23 16:23:23,662 DEBG 'start-script' stderr output:

[#] wg addconf wg0 /dev/fd/63

2026-08-23 16:23:23,665 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.2.0.2/32 dev wg0

2026-08-23 16:23:23,678 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

2026-08-23 16:23:23,695 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

2026-08-23 16:23:23,697 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

2026-08-23 16:23:23,699 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

2026-08-23 16:23:23,702 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2026-08-23 16:23:23,710 DEBG 'start-script' stderr output:

[#] nft -f /dev/fd/63

2026-08-23 16:23:23,717 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

2026-08-23 16:25:03,274 DEBG 'start-script' stdout output:

initnatpmp() returned 0 (SUCCESS)

using gateway : 10.2.0.1

sendpublicaddressrequest returned 2 (SUCCESS)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -7 (FAILED)

2026-08-23 16:25:03,274 DEBG 'start-script' stderr output:

readnatpmpresponseorretry() failed : the gateway does not support nat-pmp

errno=11 'Resource temporarily unavailable'

and I figured it out, I had to get a new wg0.conf file from proton and now it works, sorry if I bothered anyone.

also there was no clickable link binhex, but ty anyway

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.