Just updated to lastest version.
Container now stalls on "[info] NAME_SERVERS defined as....."

Disabling VPN makes it so it can start again.

I'm having same issue wirh webui inaccessible when VPN enabled.

 

I use a Surfshark wg0 custom config.

 

Debug log shows this 

4

2025-02-18 08:22:54.215194 [debug] Having issues resolving name ' ca-tor.prod.surfshark.com', sleeping before retry...

 

but its using namesevers 1.1.1.1,9.9.9.9 that should be able to resolve it

Could access UI on sunday, can't remember when I updated. Can't access now

Worked fine 15 minutes ago, updated and UI is unresponsive.  Looks like they broke something.

Can confirm. Updated this docker this morning, and VPN is broken. Only way to get to web UI is to disable VPN.

 

Until its fixed, you can roll back the container by putting "binhex/arch-qbittorrentvpn:5.0.3-1-01" into the repository field.

Edited February 18, 20251 yr by NotYet

Worked fine until it updated, can't get to the UI. Something broke. Container now stalls on "[info] NAME_SERVERS defined as....."

 

Reverting to 5.0.3-1-01 got it working again for now. 

Edited February 18, 20251 yr by PartyingChair

qBittorrent wont load web ui when the vpn is active set it to no vpn and it works fine

 

supervisord(1).log

Edited February 18, 20251 yr by carhartt45
new log

ive spotted the issue, just running tests on a fix.

4 minutes ago, binhex said:

ive spotted the issue, just running tests on a fix.

Thanks binhex!

1 hour ago, binhex said:

ive spotted the issue, just running tests on a fix.

ok new image has been built, please pull down.

 

EDIT - My new friend is \K flag for grep ;-), ain't regex a bitch.

still isnt working after update

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.13.128.173 different, marking for reconfigure

could this be the issue?

3 minutes ago, carhartt45 said:

still isnt working after update

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.13.128.173 different, marking for reconfigure

could this be the issue?

nope, that is normal behaviour.

 

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

5 minutes ago, binhex said:

nope, that is normal behaviour.

 

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

here are the files

useing torguard if that matters

supervisord(1).log Command execution.txt

Edited February 18, 20251 yr by carhartt45

1 hour ago, binhex said:

ok new image has been built, please pull down.

 

EDIT - My new friend is \K flag for grep ;-), ain't regex a bitch.

Works great here, thanks!

9 minutes ago, carhartt45 said:

here are the files

useing torguard if that matters

supervisord(1).log 11.25 kB · 0 downloads Command execution.txt 1.41 kB · 0 downloads

no issues there, you get assigned an ip, and qbittorrent is up  and running, what is the ip address of the machine you are using to attempt connection to the web ui?

7 minutes ago, binhex said:

no issues there, you get assigned an ip, and qbittorrent is up  and running, what is the ip address of the machine you are using to attempt connection to the web ui?

192.168.4.33

Just now, carhartt45 said:

192.168.4.33

yep as suspected, LAN_NETWORK is wrong, see Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

from your log:- LAN_NETWORK defined as '192.168.1.0/24'
 

2 hours ago, binhex said:

ok new image has been built, please pull down.

that fixed it.  Much appreciated.

42 minutes ago, binhex said:

yep as suspected, LAN_NETWORK is wrong, see Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

from your log:- LAN_NETWORK defined as '192.168.1.0/24'
 

That fixed it thank you binhex!

So I've had some vpn(?) issues a while now. It feels like it started when I was running 4.3.9 together with ovpn. Sometimes it worked a few days, sometimes about a day. Didn't work to just restart the container. Had to generate new config and new port. 

 

I thought it would be better to update qbit. So now im running 5.0.3 and also changed vpn to Proton. But seems like kind of the same problem now. It works for maybe a day, and sometimes a few days. Then it gets stuck. Can manually restart to get it working. But after a few restarts, I try another server. But always the same problem. 

 

I thought it maybe had something to do with my unifi udmp and ids/ips. So I tried to exclude my unraid server ip. But still the same problem. 

 

Seems to be similar to this:

https://github.com/binhex/arch-qbittorrentvpn/issues/298

 

How to best solve this? 

Try hotio instead? 

Edited February 19, 20251 yr by sillstrybarn

This is a solution that worked for me when getting this error using PIA VPN, as my container was running fine for a long time without any changes or issues; it suddenly stopped working this week.

 

Error:

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

 

Attempts that didn't work for me:

Changing Name Servers to just 1.1.1.1

Verifying if https://www.privateinternetaccess.com was blocked on any network services, firewall(no blocking on my end)

Changing wg0.conf endpoint to another endpoint that could work ( from Q29 Github Documentation VPN FAQ )

 

Solution:

Change your PIA account password, and it will authenticate and allow you to generate token for wireguard. Unsure why it stopped authenticating, as I tested my old password and could log in perfectly fine and use PIA VPN desktop software. It was until I changed my password to a new one and replaced it in the container, it started working again.

 

 

 

Edited February 22, 20251 yr by gamer1pc

On 1/29/2025 at 6:34 PM, wgstarks said:

Try whitelisting your LAN in qbit settings. This will skip the login when accessing from LAN.

appdata/binhex-qbittorrentvpn/qBittorrent/config

Edit WebUI\AuthSubnetWhitelistEnabled=  add your LAN (line 84 in my screenshot). Also be sure AuthSubnetWhitelistEnabled is set to true (line 85).

 

 

You should also ensure AlternativeUIEnabled is set to false (line 83).

 

Restart the container to apply the new settings.

 

 

Hey sorry, I think I actually ended up doing this a while back and it resolved my issue. I appended all my VLANs I might access the docker from into the LAN_NETWORK variable to have the docker allow traffic from those vlans. Thanks for reaching out again though!

 

 

Not sure why I just now got the notification about you responding though...

Edited February 23, 20251 yr by Tygerial

On 11/16/2024 at 6:02 AM, binhex said:

WARNING

 

I am seeing an influx of malware via torrents using the trick of creating the payload as a mkv file with a 'lnk' extension (Windows Link) , if you double click what appears to be a video file (windows hides lnk extension) on a Windows machine then the embedded script will run creating an executable from the payload ('video' file), see here, and here and here for a few examples of people reporting this.

Best way to stop this is to set qbittorrent to exclude lnk files from downloading, you can do this by going to Tools/Options/Downloads tab then tick 'exclude file names' and enter in the extensions you do not want to download (will be unselected automatically for you in the files list for the torrent).

This is what i have set, up to you what extensions you want to ignore so tailor to your liking, but i would highly recommend putting in *.lnk as a bare minimum:-



Note:- You may notice that you start seeing torrents listed in qbittorrent with 0 bytes downloaded but your status is set to seeding, this means the torrent contained only file extensions listed in the exclude file names list and thus you downloaded 0 bytes, simply delete the torrent and move on, example:-

 

As you can see from the above stats, there is a scary number of people downloading this, probably triggered via sonarr.

 

My tracker shows that I am not connectable, I have port forwarding on with proton, do I need to enter the port from the wireguard exit point into "Variable: VPN_INPUT_PORTS" ?? I just switched it before posting this log. I don't know if that was correct or not..


 

 

Edited February 25, 20251 yr by danheinz

49 minutes ago, danheinz said:

do I need to enter the port from the wireguard exit point into "Variable: VPN_INPUT_PORTS" ??

No that env var has nothing to do with port forwarding/incoming port, Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md