22 minutes ago, plantsandbinary said:

Why is this suddenly happening? QBT has stopped working entirely.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Scroll down to Q29.

45 minutes ago, wgstarks said:

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Scroll down to Q29.

 

Hi thanks, I changed the endpoint but it still won't work. Same error that it couldn't generate a token.

 

 

Nevermind, I forgot that I changed my VPN password lmao, but didn't update it in the docker container. Oof. Works fine now.

Edited April 20, 20242 yr by plantsandbinary

I've had this docker container for a long while now.  Recently (today) when I try to open binhex-qbittorrentvpn it won't open the GUI anymore.  It says Unauthorized now and doesn't open the UI at all.  When I try to use like in command window curl ifconfig.io to see if it is grabbing an ip fron PIA vpn it shows that it is grabbing an ip etc just won't open the UI anymore.  Any help would be much appreciated, thank you so much!

 

Well editing a bit, I finally got the UI to show the username and password area but now my password i had set a long while back is not working, and no idea how to reset it. Maybe delete and start container completely over?

Edited April 22, 20242 yr by SaberTreasures

51 minutes ago, SaberTreasures said:

I've had this docker container for a long while now.  Recently (today) when I try to open binhex-qbittorrentvpn it won't open the GUI anymore.  It says Unauthorized now and doesn't open the UI at all.  When I try to use like in command window curl ifconfig.io to see if it is grabbing an ip fron PIA vpn it shows that it is grabbing an ip etc just won't open the UI anymore.  Any help would be much appreciated, thank you so much!

Recent versions of qbittorrent will no longer allow access using the default password. Have you changed the password?

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1332654

So I've been trying to setup qbittorrentvpn per AlienTech42's youtube video, but cannot actually get to the GUI. I've tried from a few different computers running both Windows and MacOS but all of them result in connection time out, even though the container seems to be up according to the logs. This is a fresh unRAID server.

 

I've attached the execution command and the supervisord.log, but I don't see anything that sticks out to me in either about why the GUI would time out when trying to load.

 

The only other thing I've done is to update the wg0.conf to use the toronto endpoint (ca-toronto.privacy.network:1337), per AlienTech42's video. I did check comments on his video and the binhex-qbittorrentvpn FAQ's to see if there was anything that sounded similar but no joy there either.

Any help is greatly appreciated!

 

executionCommand.log supervisord.log

20 hours ago, wgstarks said:

Recent versions of qbittorrent will no longer allow access using the default password. Have you changed the password?

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1332654

I had set it to a different password long ago, but it's not working for some reason.  Is there a way to reset it potentially somehow ?  Even reverting to an older version is not going to help me since I changed it from the default password long ago.

3 minutes ago, SaberTreasures said:

I had set it to a different password long ago, but it's not working for some reason.  Is there a way to reset it potentially somehow ?  Even reverting to an older version is not going to help me since I changed it from the default password long ago.

See the link in my previous post.

 

If that doesn’t work post your supervisord log.  Be sure to redact users/passwords.

7 minutes ago, tytalus said:

Any help is greatly appreciated!

Did you use the temp password supplied in the supervisord log to access the webUI and reset the password? Looks like the app is running properly but you have to use the temp password from the log for initial access.

5 minutes ago, wgstarks said:

See the link in my previous post.

 

If that doesn’t work post your supervisord log.  Be sure to redact users/passwords.

The first time i put it in it didn't work but eh, did it a second time and restarted the docker and it worked, thanks so much for your help.  I'll change the password right now as well ☺️

1 hour ago, wgstarks said:

Did you use the temp password supplied in the supervisord log to access the webUI and reset the password? Looks like the app is running properly but you have to use the temp password from the log for initial access.

I'll take a look at docs to see how to use that, the thing is I thought I would at least see the login screen, but I don't ever get that far. The page just never loads so I can't even enter credentials. Is there some programatic place I need to put the password to?

It's one of those pages 'Sorry the page took too long to load' sort of affairs that I see. Doesn't seem to matter device between Windows or Mac.

6 minutes ago, tytalus said:

I'll take a look at docs to see how to use that, the thing is I thought I would at least see the login screen, but I don't ever get that far. The page just never loads so I can't even enter credentials. Is there some programatic place I need to put the password to?

It's one of those pages 'Sorry the page took too long to load' sort of affairs that I see. Doesn't seem to matter device between Windows or Mac.

Just to be sure, you are attempting to access from the lan network you have configured (192.168.1.0/24)?

That's a thought, I'm on a VLAN (default, 192.168.0.0/24), so I'm at 192.168.0.156, and allow access to my other VLAN the server is on (192.168.1.0/24).

46 minutes ago, tytalus said:

That's a thought, I'm on a VLAN (default,

Add any networks you want to be able to access qbit from to the lan_network setting. Comma separated.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q33.

11 hours ago, wgstarks said:

Add any networks you want to be able to access qbit from to the lan_network setting. Comma separated.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q33.

That's sorted me, thanks! Coffee coming your way!

This is less a question for this specific container, but applies none the less, so hoping someone can point me in the right direction.

 

I have a bunch of containers running through binhex-qbittorrentvpn, and they work fine, the problem is when I need to specify a custom port for a container that I am lost. For example, lets say I want to route Tor-Browser container through this container as well, it has a default port of 8080, and once I remove the custom port definition in the template, it will no longer honour the customized port. Is there a way around this? Some applications I can setup, go into their own GUI and customize the port and it works, but for apps like the aforementioned Tor-Browser, I can't customize the port, so it defaults.

 

 

I know I'm missing something super obvious here.  Everything has been running smooth for a while now, but recently all downloads have ceased, and newly added downloads are stuck at "downloading metadata".  I'm using Mullvad VPN.  What have(n't) I done to break it?

 

EDIT: I did a little more digging, and discovered that Mullvad has removed support for port forwarding.  Is this my issue?  What's the alternative?  They support WG.  Can that be a replacement?  Sadly, I've never really understood the difference, or how QBt makes use of the VPN, it just....works.

Edited April 29, 20242 yr by Elmojo
added details

51 minutes ago, Elmojo said:

EDIT: I did a little more digging, and discovered that Mullvad has removed support for port forwarding.

You might get it working but it will be VERY slow speeds. I would recommend switching to another provider that supports port forwarding.

 

If you want to give it a try set STRICT_PORT_FORWARDING to “NO” in the container settings.

1 hour ago, wgstarks said:

You might get it working but it will be VERY slow speeds. I would recommend switching to another provider that supports port forwarding.

 

If you want to give it a try set STRICT_PORT_FORWARDING to “NO” in the container settings.

Bummer.  I'm already invested in Mullvad for some other services.

I already have STRICT_PORT_FORWARDING set to "No".  It's been that way since setup.

 

If I was to switch to a different VPN, is there one that has gotten the stamp of approval from users here?  I'm not super familiar, but I've been very happy with Mullvad in general, for their price, service, and general setup.  I use it for a couple different things, but this is perhaps the most important, so I guess I need to consider another option.  Is Wireguard an alternative?  I've never been clear on exactly what that is or how it works, or if it's really even a VPN in the traditional sense.

Edited April 29, 20242 yr by Elmojo

10 hours ago, Elmojo said:

If I was to switch to a different VPN, is there one that has gotten the stamp of approval from users here?

PIA is widely used with many servers that support port forwarding. Easy to setup since the docker is pre-configured for it.

 

10 hours ago, Elmojo said:

Is Wireguard an alternative?  I've never been clear on exactly what that is or how it works, or if it's really even a VPN in the traditional sense.

Wireguard and OpenVPN are two different protocols used to connect to VPN servers. I know that PIA (and probably most other providers) supports both methods. I’ve never used wireguard though so not really qualified to answer questions about it.

 

10 hours ago, Elmojo said:

I already have STRICT_PORT_FORWARDING set to "No".  It's been that way since setup.

Attach your logs to your next post if you like. There is probably something in there to indicate the cause of the failure. If Mullvad is no longer supporting port forwarding they may have taken the server you have been using off-line and you’ll need to pick another one.

 

Be sure to redact users/passwords in the logs.

Edited April 29, 20242 yr by wgstarks

10 hours ago, Elmojo said:

I already have STRICT_PORT_FORWARDING set to "No".

FYI - if your vpn provider is NOT PIA or ProtonVPN then STRICT_PORT_FORWARDING does nothing.

Hello all - having a weird issue ever since I moved my dockers over to a VLAN network, hope you can help. Used to have all the *arrs running on br0 on 192.168.0.0/24, moved them to 172.16.20.0/24 on br3.1620. Sonarr and Radarr work just fine (they are privoxy routed through qbittorrentvpn). Per my router's log files, qbittorrentvpn seems to be looking for DNS on 192.168.0.53, and so fails to start unless I allow it to access that IP with my firewall rules. I'm using PIA / OpenVPN config. I can run VMs or other dockers just fine on this VLAN, is there a way I can force qbittorrent to not look at 192.168.0.53 for DNS?

 

EDIT: Looking at Radarr and Sonarr now in more detail - their webuis are available, but I am seeing the same requests to access 192.168.0.53 on my router log, which is being blocked by default since they are not on the same VLAN. Thoughts on why they are doing this?

 

EDIT: Managed to get the dockers working by redirecting all DNS requests (port 53) on the VLAN to the pfSense DNS resolver. Still don't understand why the dockers are looking to 192.168.0.53 for DNS requests, instead of 1.1.1.1 and 1.0.0.1 which are in the NAME_SERVERS field. Are there any other alternatives available here? Thanks.

Edited April 29, 20242 yr by artdepart

My VPN provider has optional OPVN configs for each server location which includes a line for a scramble option.  Is the OpenVPN client here patched to allow for this parameter? 

Second qq - how to tell which version OpenVPN is running? 

Thanks!

 

Hi folks,

I'm not sure if this an issue with qBit or Proton, but I have to start somewhere, so here it is:

When i start the container, everything runs smoothly for hours, until at some point, port forwarding does not work correctly anymore. qBit recognizes, that the port is closed and marks it for reconfigure, but then just keeps going and doesn't actually resolve the issue.

 

Restarting the container temporarily fixes this, but that's obvioulsy not a long term solution.

 

As per your github instructions, qbit_docker contains the docker command to run the container, qbit_debug is the supervisord log. I'm afraid the debug log is very long, since the issue only appears after hours and i didnt want to cut anything out in case its important. First occurance of port closure appears to happen around 20:10 (line 44530).

qbit_docker.txt qbit_debug.log

9 hours ago, Zimeic said:

Hi folks,

I'm not sure if this an issue with qBit or Proton, but I have to start somewhere, so here it is:

When i start the container, everything runs smoothly for hours, until at some point, port forwarding does not work correctly anymore. qBit recognizes, that the port is closed and marks it for reconfigure, but then just keeps going and doesn't actually resolve the issue.

 

Restarting the container temporarily fixes this, but that's obvioulsy not a long term solution.

 

As per your github instructions, qbit_docker contains the docker command to run the container, qbit_debug is the supervisord log. I'm afraid the debug log is very long, since the issue only appears after hours and i didnt want to cut anything out in case its important. First occurance of port closure appears to happen around 20:10 (line 44530).

qbit_docker.txt 1.39 kB · 0 downloads qbit_debug.log 2.02 MB · 0 downloads

I have taken a look at this and its a bug in my code, I will fix it up and push out a new image shortly.

 

EDIT - new image pushed, please pull down at your convenience.

My container won't start. I am using PIA. I tried updating the OPVPN files from PIA, but that did not help.

OpenSSL: error:068000E9:asn1 encoding routines::utctime is too short:
OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revocationDate, Type=X509_REVOKED
OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revoked, Type=X509_CRL_INFO
OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=crl, Type=X509_CRL

 

I went back to binhex/arch-qbittorrentvpn:4.6.4-1-01 to resolve this, so I know this is must only be an issue with 4.6.4-1-02 or my appdata somewhere.

 

Edit: Added redacted supervisord.log and Command Execution

Edit 2: I wrote out the error messages in case someone tries searching this topic or google to find what the error means.

 

Here is my Command execution.
docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="YeetUnraid"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='REMOVED FOR SECURITY'
  -e 'VPN_PASS'='REMOVED FOR SECURITY'
  -e 'VPN _PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.1.0/24'
  -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 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -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 '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8585:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/Seeding Torrents/':'/data':'rw'
  -v '/mnt/user/Seeding Torrents/':'/seeding':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

9a258e96adc3c32057ccd9972e8dab39a8b33185c6f4038dd68e0bce61bcdee8

yeetunraid-diagnostics-20240430-1657.zip supervisord.log

Edited May 1, 20242 yr by SentientNut