[Support] binhex - qBittorrentVPN


binhex

1310 posts in this topic Last Reply

Recommended Posts

Hi @binhex,

 

I'm using this docker, and it's really awesome. I like the way you've made it so that qbittorrent can use the port forwarded by the VPN.  I'm trying to figure out how exactly you've accomplished that, because I'm trying to do something similar in one of my VMs, and I'm stumped. I've looked through the repo for this docker, but I can't seem to find where (and how) VPN_INCOMING_PORT is being set. It looks like it might be in /home/nobody/preruncheck.sh, but I can't find the source for that script in the repo. Do you think you could possibly help me figure out how to get the port my VPN is forwarding to me, either here or by linking me to the relevant code?

 

Thanks!

 

Link to post
  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

@binhex Does the container only use a single .ovpn file from the appdata directory for configuration? Can I put all of the PIA port-forwarding capable server .ovpn files in there so that it can try th

Support for multi remote endpoints and PIA 'Next-Gen' networks now complete, see Q19 and Q20 for details:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Create a necessary folder in   \\yourservername\appdata\binhex-qbittorrentvpn\qBittorrent    Create a folder called ssl     Open up terminal and type,  

Posted Images

Hello @binhex and others,

 

I have been successfully using Sonarr+Radarr+Deluge for a while now, but for a variety of reasons I recently tried to switch from Deluge to qBittorrent. I have qBittorrent installed and can access it, download, etc successfully. However when I try to add as a Download Client in Sonarr or Radarr (or presumably Lidarr) I get the error "Unknown exception: Failed to connect to qBittorrent, check your settings." This is no doubt an issue with my configuration of qBittorrent because Deluge worked without issue previously, but I cannot figure this out. Could someone provide guidance?

 

Thank you!

Screen Shot 2020-05-11 at 3.18.36 PM.png

Screen Shot 2020-05-11 at 3.19.03 PM.png

Screen Shot 2020-05-11 at 3.19.49 PM.png

Screen Shot 2020-05-11 at 3.22.38 PM.png

Link to post
17 hours ago, --Kyle-- said:

I have been successfully using Sonarr+Radarr+Deluge for a while now, but for a variety of reasons I recently tried to switch from Deluge to qBittorrent. I have qBittorrent installed and can access it, download, etc successfully. However when I try to add as a Download Client in Sonarr or Radarr (or presumably Lidarr) I get the error "Unknown exception: Failed to connect to qBittorrent, check your settings." This is no doubt an issue with my configuration of qBittorrent because Deluge worked without issue previously, but I cannot figure this out. Could someone provide guidance?

what is LAN_NETWORK set to for qbittorrentvpn?.

Link to post
1 hour ago, --Kyle-- said:

@binhex LAN_NETWORK is set to 192.168.1.0/24 in qbittorrentvpn

My server is called Tower (maybe that's true for everyone? I'm kind of new to all this), and after playing with this a bit more, putting "Tower" in the Host boxes allowed Sonarr/Radarr to find qBittorrent! I'm not sure why the IP wouldn't work, but regardless this is taken care of. Thank you @binhex for all you do for this community!

Link to post

Hello!  I've seen similar questions posted here, but they were from last year and were marked *fixed* on the github.

 

It seems that every time my container restarts, it resets all of its configs to default values.  Save location, user authentication, "execute command on completion" -- everything.  This leads to all downloads getting dumped into the /config/ directory, which is undesirable.

 

Looking through the Unraid Dashboard logs, I see that the OpenVPN and qBittorrent incoming ports seem to mismatch every half-hour, and are marked for reconfigure, but that's the only things that stands out to my eyes.

 

Any help would be appreciated, as I very much like this container when it is properly configured!  TYIA

Link to post

Install through the Docker and it won't run.   The log file shows this:

 

2020-05-14 10:57:40.620144 [info] VPN_ENABLED defined as 'yes'
2020-05-14 10:57:40.655744 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

 

If I turn off the vpn options it works perfectly.  When I turn on vpn and put in my vpn username and password I get this and then it won't run.

 

What am I doing wrong?  Thanks.

Link to post

I updated an hour ago to the latest qbittorrent and couldn't get to the webui. The log just kept repeating could not resolve www.google.com. I changed the repo to the previous version and all is back to normal. Is there something I need to change for the lastest version to work? 

Link to post
8 hours ago, Roger C said:

I updated an hour ago to the latest qbittorrent and couldn't get to the webui. The log just kept repeating could not resolve www.google.com. I changed the repo to the previous version and all is back to normal. Is there something I need to change for the lastest version to work? 

I'm in the same boat.

Link to post
11 hours ago, Roger C said:

I updated an hour ago to the latest qbittorrent and couldn't get to the webui. The log just kept repeating could not resolve www.google.com. I changed the repo to the previous version and all is back to normal. Is there something I need to change for the lastest version to work? 

 

2 hours ago, dodgypast said:

I'm in the same boat.

highly unlikely the latest change had anything to do with this, as the change was around website change for open port detection and i have had no other reports from delugevpn or rtorrentvpn (which use the same code).

 

so onto the issue, dns failure simply means the container was unable to resolve names once the tunnel is established, this is most likely a vpn provider issue, i would try switching back to 'latest' and my guess is that the container would start with no issue, if it doesnt start then please do the following:-

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

 

Edited by binhex
Link to post
On 5/14/2020 at 7:03 PM, nekko377 said:

Install through the Docker and it won't run.   The log file shows this:

 

2020-05-14 10:57:40.620144 [info] VPN_ENABLED defined as 'yes'
2020-05-14 10:57:40.655744 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

 

If I turn off the vpn options it works perfectly.  When I turn on vpn and put in my vpn username and password I get this and then it won't run.

 

What am I doing wrong?  Thanks.

did you try what the log output suggests? you need to download the openvpn config file from your vpn provider (and all required certificates).

Quote

No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container,

 

Edited by binhex
Link to post
2 hours ago, binhex said:

 

highly unlikely the latest change had anything to do with this, as the change was around website change for open port detection and i have had no other reports from delugevpn or rtorrentvpn (which use the same code).

 

so onto the issue, dns failure simply means the container was unable to resolve names once the tunnel is established, this is most likely a vpn provider issue, i would try switching back to 'latest' and my guess is that the container would start with no issue, if it doesnt start then please do the following:-

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

 

I tried latest again and it didn't work, back to 4.2.5-1-01 and it's fine.

 

I'll try and attach log files when I have a bit of time later.

 

Edit:

No log file was generated in my 

/appdata/binhex-qbittorrentvpn/qBittorrent/config

folder.

 

But I got this from my logs:
 

logfile

Edited by dodgypast
Link to post
1 hour ago, dodgypast said:

I tried latest again and it didn't work, back to 4.2.5-1-01 and it's fine.

 

I'll try and attach log files when I have a bit of time later.

 

Edit:

No log file was generated in my 


/appdata/binhex-qbittorrentvpn/qBittorrent/config

folder.

 

But I got this from my logs:
 

logfile 14.78 kB · 0 downloads

hmm ok can you try setting VPN_OPTIONS value to the following:-

--pull-filter ignore 'dhcp-option DNS'

 

Link to post
1 hour ago, dodgypast said:

Didn't like that either:
logfile2

ok remove the value for VPN_OPTIONS and then from the unraid console with the container running (NOT the containers console) run the following:-

docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'

restart container, if no go then try the following:-

docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'

then restart the container again.

 

i suspect one of these or maybe even both options are required for airvpn, i just dont know which.

Link to post

I tried the deluge plugin with the same results and have to use the earlier version. I too am on airvpn so I checked with a friend on pia and he has no problems.  I disabled ipv6 on my router and the problem goes away and the latest version works. I will try those commands when I get home and see what happens. 

Link to post
2 minutes ago, Roger C said:

I too am on airvpn so I checked with a friend on pia and he has no problems.

yes thats why its hard to debug, it only looks to affect some vpn providers, airvpn being one of them.

Link to post
6 hours ago, dodgypast said:

I tried latest again and it didn't work, back to 4.2.5-1-01 and it's fine.

 

Same here. AirVPN. Tried several new config files and get the "unable to resolve Google DNS error." Rolled back to 4.2.5-1-01 and all is good.

Link to post
4 minutes ago, jserio said:

Same here. AirVPN. Tried several new config files and get the "unable to resolve Google DNS error." Rolled back to 4.2.5-1-01 and all is good.

rather than rolling back i need somebody to do the following to work out what the issue is:-

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

 

Link to post
2 hours ago, binhex said:

ok remove the value for VPN_OPTIONS and then from the unraid console with the container running (NOT the containers console) run the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'

restart container, if no go then try the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'

then restart the container again.

 

i suspect one of these or maybe even both options are required for airvpn, i just dont know which.

 

First one didnt help, but it worked after the second! I'm back in the GUI.. thanks!

Link to post
2 hours ago, binhex said:

ok remove the value for VPN_OPTIONS and then from the unraid console with the container running (NOT the containers console) run the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'

restart container, if no go then try the following:-


docker exec -it <name of container> bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'

then restart the container again.

 

i suspect one of these or maybe even both options are required for airvpn, i just dont know which.

It worked after the second.
 

root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'
Error response from daemon: Container ce7a38e0b3115332106a1687c9c83bdcb3cd3f10f8d3e8fdba76ae86543e59c4 is not running
root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.dhcp-option\sDNS6.\s~~g" /root/openvpn.sh'
root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'
Error response from daemon: Container ce7a38e0b3115332106a1687c9c83bdcb3cd3f10f8d3e8fdba76ae86543e59c4 is not running
root@Tower:~# docker exec -it binhex-qbittorrentvpn bash -c 'sed -i -e "s~--pull-filter ignore\s.redirect-gateway\sipv6.\s~~g" /root/openvpn.sh'

Thanks for your support.

Edited by dodgypast
Link to post
53 minutes ago, dodgypast said:

It worked after the second, one thing... you need the container to be running for the command to work:

new image has been produced, can you please pull down image with tag 'latest' and let me know if it looks ok.

Link to post

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.