59 minutes ago, kingfenix said:

also there was no clickable link binhex, but ty anyway

You’re probably referring to the post pinned at the top of this page. They were all broken when LimeTech switched providers for the user forum. The posts got preserved but the links were all broken.

Basically it says that those seeking help should attach their full supervisord log and docker run command. I recommend redacting users/passwords as well.

I'm going back to my server after taking some time away, and there's been some changes.

I've got most of what I need back up and running, but like other's I'm having difficulty with getting the webui working for qbitorrent.

I think these are the correct files to attach for troubleshooting.

docker run.txt

1 hour ago, wlpaul4 said:

I'm going back to my server after taking some time away, and there's been some changes.

I've got most of what I need back up and running, but like other's I'm having difficulty with getting the webui working for qbitorrent.

I think these are the correct files to attach for troubleshooting.

You should change your PIA password asap, as you forgot to remove it from the log. Which IP and port are you trying to reach the webui on?

7 hours ago, strike said:

You should change your PIA password asap, as you forgot to remove it from the log. Which IP and port are you trying to reach the webui on?

Dangit. I thought I'd pulled it out, but I must have missed it somewhere else. Thank you for letting me know.

I've tried to change it to 10.0.0.10:8085 and access it there.

57 minutes ago, wlpaul4 said:

I've tried to change it to 10.0.0.10:8085 and access it there.

From your docker run command-

 -p '8085:8080/tcp

Looks like you set the webUI to 8085 in the container but then mapped the 8085 host port to 8080 in the container.

It should be 8085:8085 tcp.

Thank you! I'll try to correct it when I get home from the office this evening.

Slava Ukraini!

Is anyone else having issues connecting to qbit with PIA vpn enabled? Ive tried changing the endpoint but webui still wont load.

7 hours ago, 555768 said:

Is anyone else having issues connecting to qbit with PIA vpn enabled? Ive tried changing the endpoint but webui still wont load.

If you want help with this you’ll need to attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

On 9/4/2026 at 3:40 AM, 555768 said:

Is anyone else having issues connecting to qbit with PIA vpn enabled? Ive tried changing the endpoint but webui still wont load.

Yes i'm having the same issue aswell. it worked until a couple of days ago but now the webui wont load and the other -arr apps wont connect to it either.
already tried using newly downloaded ovpn files.
see my docker run and log attached.

docker run.txt log.txt

2 hours ago, bibek108 said:

Yes i'm having the same issue aswell. it worked until a couple of days ago but now the webui wont load and the other -arr apps wont connect to it either.
already tried using newly downloaded ovpn files.
see my docker run and log attached.

docker run.txt log.txt

The log snippet you attached doesn’t show much other than the fact that the container is failing to connect to the server. You could try connecting to a different server if you haven’t already. Otherwise you need to attach the entire supervisord log to your next post. As always, be sure to redact users/passwords.

17 hours ago, wgstarks said:

The log snippet you attached doesn’t show much other than the fact that the container is failing to connect to the server. You could try connecting to a different server if you haven’t already. Otherwise you need to attach the entire supervisord log to your next post. As always, be sure to redact users/passwords.

thanks for looking at it, i see that it tries to connect to the same server every time. how do i change this? see the supervisord logs below.

supervisord.log supervisord.log.1 supervisord.log.2

1 hour ago, bibek108 said:

thanks for looking at it, i see that it tries to connect to the same server every time. how do i change this? see the supervisord logs below.

supervisord.log supervisord.log.1 supervisord.log.2

The server is defined in the oven file.

I also see a warning that you have special characters in your user name that may cause problems.

2 hours ago, wgstarks said:

The server is defined in the oven file.

I also see a warning that you have special characters in your user name that may cause problems.

thank you so much!! i changed the username and tried a new ovpn file and it worked

On 5/26/2026 at 8:48 PM, rophel said:

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.

Did you ever find a solution for this? I'm having the same issue.

Something strange maybe with my install, i've been using this for years and been through various vpn providers in that time. I'm with PIA now, and I used to be able to connect with alot of end points. However that slowly has decreased and now it seems the docker only loads up fully and gives me the webpage (i'm assuming because the VPN isn't up) when connected to the few privacy.network entries in the log. If i use a ovpn file for anything else it fails. Any ideas why? I've use ovpn files with hard coded IPs which doesn't work and also tried changing the ip to what the corresponding link below resolves to and it also doesn't work

2026-09-23 20:02:21,551 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-09-23 20:02:21,551 DEBG 'start-script' stdout output:

[info] ca-montreal.privacy.network

[info] cyprus.privacy.network

[info] ca-vancouver.privacy.network

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

[info] il-israel-2-pf.privacy.network

[info] nl-amsterdam.privacy.network

[info] morocco.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.pvt.site

[info] armenia.pvt.site

[info] austria.pvt.site

[info] au-adelaide.pvt.site

[info] au-brisbane.pvt.site

[info] au-melbourne.pvt.site

[info] au-perth.pvt.site

etc etc

I turned off STRICT_PORT_FORWARD and there was no change, still not working. I then changed VPN_PROV from pia to custom and it worked as normal. I then reverted STRICT_PORT_FORWARD back to yes and it still worked as normal. Going back to VPN_PROV as pia then makes it not work. Which leads me to believe theres something in this VPN_PROV setting specific to PIA that is making it fail? For now it'll keep it on custom.

Edited September 23Sep 23 by Gammawolf

19 minutes ago, Gammawolf said:

I turned off STRICT_PORT_FORWARD and there was no change, still not working. I then changed VPN_PROV from pia to custom and it worked as normal. I then reverted STRICT_PORT_FORWARD back to yes and it still worked as normal. Going back to VPN_PROV as pai then makes it not work. Which leads me to believe theres something in this VPN_PROV setting specific to PIA that is making it fail? For now it'll keep it on custom.

With strict port forwarding enabled and PIA enabled the docker will check that you are using a server from the list of servers that support port forwarding. If you disable those settings you can use any available server regardless of whether it supports port forwarding.

14 hours ago, wgstarks said:

With strict port forwarding enabled and PIA enabled the docker will check that you are using a server from the list of servers that support port forwarding. If you disable those settings you can use any available server regardless of whether it supports port forwarding.

Do you know why that list generates mostly x.pvt.site addresses now when the ovpn files from PIA still uses x.privacy.network network? How is it finding/keeping this domain list updated as that discrepancy seems like it would cause an issue? Also as mentioned, turning off strict port forwarding but leaving it selected on PIA also doesn't work, unless selecting PIA inherently uses strict port forwarding anyway?

51 minutes ago, Gammawolf said:

Do you know why that list generates mostly x.pvt.site addresses now when the ovpn files from PIA still uses x.privacy.network network? How is it finding/keeping this domain list updated as that discrepancy seems like it would cause an issue? Also as mentioned, turning off strict port forwarding but leaving it selected on PIA also doesn't work, unless selecting PIA inherently uses strict port forwarding anyway?

PIA has been changing the DNS addresses for its servers while your ovpn file is static. The list is downloaded from PIA so it should be current. You can edit your ovpn file to point to any server from the list.

Didn't change any settings but noticed for at least a few days now my web gui isn't loading and doesn't seem to be downloading. Anyone experiencing anything similar?

14 minutes ago, rvlution said:

Didn't change any settings but noticed for at least a few days now my web gui isn't loading and doesn't seem to be downloading. Anyone experiencing anything similar?

I was downloading up until lastnight with absolutely no issues. When I checked it after work, I have a bunch of torrents that are now errored out. I rebooted the container and now can't even access the WebUI. I'm using PIA / Wireguard.

The issue I'm seeing is the following:

2026-09-24 21:15:32,712 DEBG 'start-script' stdout output:

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

If I go to that site, I get the following:

{
    "status": "ERROR",
    "message": "no auth data"
}

Edited September 25Sep 25 by coreydurbin

32 minutes ago, rvlution said:

Didn't change any settings but noticed for at least a few days now my web gui isn't loading and doesn't seem to be downloading. Anyone experiencing anything similar?

15 minutes ago, coreydurbin said:

I was downloading up until lastnight with absolutely no issues. When I checked it after work, I have a bunch of torrents that are now errored out. I rebooted the container and now can't even access the WebUI. I'm using PIA / Wireguard

If you would like help with this you’ll need to attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

I am having the same issue. WebUI won't load. I have PIA.

Edit: I fixed it. PIA took port forwarding away from the location I was set up with. I had to go to PIA website and download a new file. Go to OpenVPN Configuration Generator section on PIA website and select another location that has port forwarding and generate that file. and swap out the .opvn file in \appdata\binhex-qbittorrentvpn\openvpn

I was using Toronto and changing to Montreal fixed it.

Edited September 25Sep 25 by yosoyfiesta

I just noticed this issue on my configuration too, using the Wireguard configuration. I was using ca toronto with port forwarding. Toronto is still on the binhex list of published endpoints (updated today, 9/25), but the container logs say that it's not part of the list anymore. I also tried the ...pvt.site version which also didn't work. I changed the Endpoint line in wg0.conf to ca-montreal.privacy.network:1337 and got it going again.

20 minutes ago, ccwod said:

I just noticed this issue on my configuration too, using the Wireguard configuration. I was using ca toronto with port forwarding. Toronto is still on the binhex list of published endpoints (updated today, 9/25), but the container logs say that it's not part of the list anymore. I also tried the ...pvt.site version which also didn't work. I changed the Endpoint line in wg0.conf to ca-montreal.privacy.network:1337 and got it going again.

There have been similar complaints for a while now. I suspect PIA is gradually changing the VPN naming for all their servers. Perhaps if you contact their customer service you might be able to get a confirmation of that. Hopefully PIA will update the list soon.