[Support] binhex - qBittorrentVPN


binhex

1327 posts in this topic Last Reply

Recommended Posts

  • 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

6 hours ago, philippneistat said:

 

I have binhex-qbittorrentvpn installed with a pia vpn, that so far works flawlessly.

However, i tried to map another container's network to that of the binhex-qbittorrentvpn, Jdownloader2, with --network=container:binhex-qbittorrentvpn.

But with Jdownloader i can't access the web-gui and it doesnt recieve any ports or ip.

You need to delete the port mappings from the Jdownloader container and add them instead to the qbittorrentvpn container, instructions here: https://www.reddit.com/r/unRAID/comments/ejeo20/how_to_pass_any_docker_container_through_a_vpn_on/

Link to post
59 minutes ago, FearlessAttempt said:

Very interested in how you got this working.

 

Create a necessary folder in

 

\\yourservername\appdata\binhex-qbittorrentvpn\qBittorrent 

 

Create a folder called ssl

 

Capture2.thumb.JPG.63ddfff532ccd9910d3412c15682b6ed.JPG

 

Open up terminal and type,

 

cd /mnt/user/appdata/binhex-qbittorrentvpn/qBittorrent/ssl

 

This will make it so the directory is now active.  

 

Now we can generate the self signed key and certificate pair.

 

In terminal add this command.

 

openssl req -new -x509 -nodes -out server.crt -keyout server.key

 

Answer the questions or press enter to leave blank.

You should now have two files in your ssl folder.

 

server.crt

server.key

 

Now go to your qbittorrent web-interface then open the Tools -> Options... in the menu bar (or click the screwdriver or cogwheel icon depending on your version), and click on the tab labelled WebUI. Enable HTTPS and add the location of the files.  

 

Add to the boxes,

 

/config/qBittorrent/ssl/server.crt

/config/qBittorrent/ssl/server.key

 

Capture.thumb.JPG.14a7bd07cd6c5b2a9ffdbe03567667e5.JPG

 

Close the page and edit the qbittorrent container in advance mode and on the line WebU:

 

Change http://[IP]:[PORT:8080] / to https://[IP]:[PORT:8080]/

 

Capture3.thumb.JPG.470e5aa0f1a7a0adbe74fd1be62375f7.JPG

 

when you go to the docker webui you will now see this page.

 

Capture4.thumb.JPG.cb8d9f31119c4c4c529a725d14323302.JPG

 

Select advanced and proceed to the docker login page, you will notice it still says not secure ( https:// ) don't worry thats because of the self signed certificate. 

Because its self signed its not been verified by a third party, so will show not secure ( to my knowledge ) 

 

Now when you click on register to handle magnets a pop up box will apper.

 

Capture5.JPG.0f73dd42061b7e7bc04c3c2b21666e99.JPG

 

Click allow,

A pop up box ( user account control ) will open click yes to continue

you can now open magnets, that will open qbittorrent stright away with the necessary URL

 

Have tested this with Google Chrome and Microsoft Edge. 

 

Hope this makes sense.

 

Link to post
On 8/30/2020 at 11:20 AM, thatsthefrickenlightning said:

Switched to this endpoint on the legacy network. Working for now. Not ideal, because trackers expect me on a different ip (range), but it'll do for now. Thank you!

Getting this now: '[warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...'

 

Will wait a bit but maybe this is the end of QBVPN until the migration to next gen is complete?

Link to post

Since around the time of the last update, qBitTorrent is stuck at 'Downloading metadata' after the internect connection reestablishes every 2 hours, only a container restart fixes this. Strangely enough, other containers, which use the containers network stack, actually can establish connections.

 

Nothing conclusive in the log afaict, but here it is anyways:

 

log.txt

Link to post

I made the mistake of updating all dockers and am seeing a similar issue today as well. It was working fine before the update but after updating and restarting I an now seeing this

 


2020-09-05 16:18:18,585 DEBG 'start-script' stdout output:
Sat Sep 5 16:18:18 2020 Initialization Sequence Completed

2020-09-05 16:18:18,710 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled...

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com

2020-09-05 16:18:19,641 DEBG 'start-script' stdout output:
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-05 16:18:19,898 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

2020-09-05 16:18:30,019 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

2020-09-05 16:18:30,019 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

2020-09-05 16:18:40,143 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received
[info] 10 retries left
[info] Retrying in 10 secs...

It just keeps repeating this and qbittorrent never starts.

 

Is there a way to revert the update?

Link to post

Changing to nextgen servers and disabling port forwarding got it working for now but as we know port forwarding is much better.

Might try some different servers tomorrow to see if any of them have port forwarding working.

 

Did I read something earlier about someone getting port forwarding working on next gen servers?

Edited by TexasUnraid
Link to post

I am having an issue with getting the docker to start once I have setup deluge. Any idea what the issue could be? I have followed SpaceInvader's setup to the T, but am getting the following log when I try to start.

 

ErrorWarningSystemArrayLogin


Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-09-06 01:50:01.287247 [info] System information Linux f30c979bb6bb 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-09-06 01:50:01.314155 [info] OS_ARCH defined as 'x86-64'
2020-09-06 01:50:01.340994 [info] PUID defined as '99'
2020-09-06 01:50:01.626608 [info] PGID defined as '100'
2020-09-06 01:50:02.156853 [info] UMASK defined as '000'
2020-09-06 01:50:02.182614 [info] Permissions already set for volume mappings
2020-09-06 01:50:02.211232 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-09-06 01:50:02.237022 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-09-06 01:50:02.262823 [info] VPN_ENABLED defined as 'yes'
2020-09-06 01:50:02.295832 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/France.ovpn
2020-09-06 01:50:02.341363 [info] VPN remote line defined as 'remote france.privateinternetaccess.com 1198'
2020-09-06 01:50:02.367423 [info] VPN_REMOTE defined as 'france.privateinternetaccess.com'
2020-09-06 01:50:02.394289 [info] VPN_PORT defined as '1198'
2020-09-06 01:50:02.423255 [info] VPN_PROTOCOL defined as 'udp'
2020-09-06 01:50:02.449068 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-09-06 01:50:02.474697 [info] VPN_PROV defined as 'pia'
2020-09-06 01:50:02.500930 [info] LAN_NETWORK defined as '192.168.1.0/24'
2020-09-06 01:50:02.526794 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-09-06 01:50:02.552320 [info] VPN_USER defined as 'p4864713'
2020-09-06 01:50:02.578280 [info] VPN_PASS defined as '2015VWgti'
2020-09-06 01:50:02.604208 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-09-06 01:50:02.629936 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-09-06 01:50:02.655791 [info] ENABLE_PRIVOXY defined as 'yes'
2020-09-06 01:50:02.682117 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-09-06 01:50:02.717536 [info] Deleting files in /tmp (non recursive)...
2020-09-06 01:50:02.741923 [info] Starting Supervisor...
2020-09-06 01:50:03,269 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-09-06 01:50:03,269 INFO Set uid to user 0 succeeded
2020-09-06 01:50:03,272 INFO supervisord started with pid 6
2020-09-06 01:50:04,274 INFO spawned: 'start-script' with pid 179
2020-09-06 01:50:04,275 INFO spawned: 'watchdog-script' with pid 180
2020-09-06 01:50:04,275 INFO reaped unknown pid 7 (exit status 0)
2020-09-06 01:50:04,280 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-09-06 01:50:04,280 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-09-06 01:50:04,281 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-09-06 01:50:04,327 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-09-06 01:50:04,329 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-09-06 01:50:04,332 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-09-06 01:50:04,334 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-09-06 01:50:04,337 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-09-06 01:50:04,339 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-09-06 01:50:04,342 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-09-06 01:50:04,344 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-09-06 01:50:04,346 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-09-06 01:50:04,560 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-09-06 01:50:04,562 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-09-06 01:50:04,563 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-09-06 01:50:04,564 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
192.168.1.0/24 via 172.17.0.1 dev eth0

2020-09-06 01:50:04,564 DEBG 'start-script' stdout output:
--------------------

2020-09-06 01:50:04,566 DEBG 'start-script' stdout output:
iptable_mangle 16384 1
ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle

2020-09-06 01:50:04,566 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-09-06 01:50:04,596 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-09-06 01:50:04,597 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2020-09-06 01:50:04,597 DEBG 'start-script' stdout output:
--------------------

2020-09-06 01:50:04,598 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-09-06 01:50:04,616 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:04 2020 WARNING: file 'credentials.conf' is group or others accessible
Sun Sep 6 01:50:04 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Sun Sep 6 01:50:04 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-09-06 01:50:04,617 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:04 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-09-06 01:50:04,617 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-09-06 01:50:04,618 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:04 2020 CRL: loaded 1 CRLs from file [[INLINE]]

2020-09-06 01:50:04,618 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:04 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]156.146.63.1:1198
Sun Sep 6 01:50:04 2020 UDP link local: (not bound)
Sun Sep 6 01:50:04 2020 UDP link remote: [AF_INET]156.146.63.1:1198

2020-09-06 01:50:05,360 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:05 2020 [3f0edd05aed8840796b92f7ad3bc83bd] Peer Connection Initiated with [AF_INET]156.146.63.1:1198

2020-09-06 01:50:06,676 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:06 2020 TUN/TAP device tun0 opened
Sun Sep 6 01:50:06 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-09-06 01:50:06,677 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:06 2020 /usr/bin/ip addr add dev tun0 local 10.43.12.6 peer 10.43.12.5

2020-09-06 01:50:06,678 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:06 2020 /root/openvpnup.sh tun0 1500 1558 10.43.12.6 10.43.12.5 init

2020-09-06 01:50:06,683 DEBG 'start-script' stdout output:
Sun Sep 6 01:50:06 2020 Initialization Sequence Completed

2020-09-06 01:50:06,793 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'france.privateinternetaccess.com' is port forward enabled...

2020-09-06 01:50:08,894 DEBG 'start-script' stdout output:
[info] PIA endpoint 'france.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-09-06 01:50:08,895 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-06 01:50:09,574 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

Link to post
10 hours ago, TexasUnraid said:

Did I read something earlier about someone getting port forwarding working on next gen servers?

Doubt it. On august 25th PIA said 'Next Generation servers do not currently offer port-forwarding outside of the application'.

10 hours ago, TexasUnraid said:

Changing to nextgen servers and disabling port forwarding got it working for now but as we know port forwarding is much better.

Might try some different servers tomorrow to see if any of them have port forwarding working.

Without port forwarding, I can't get any traffic going at all, neither in nor out.

Link to post

After messing with it, it seems that the Montreal server is down or something. I tried Vancouver and it worked but in the past I saw significantly worse performance with it but should work for now. Will try Montreal again at some point.

 

It is still really strange how binhex sabnzb worked with Montreal but qbittorrent did not. I guess that sab does not use port forwarding and that was causing the issue? Could be so many people have moved to Montreal there are no ports left?

Edited by TexasUnraid
Link to post

Updated to latest qbittorrent now unable to connect to webUI.  I changed nothing in the config just updated to latest version. I am using pia and tried to turn off vpn and still unable to connect to the WebUI. It was working but all of a sudden I cannot connect to it either with or without vpn enabled.  I also noticed that remote torrent adder is unable to contact my server. I have a exception added to my bit torrent application for online threat prevention. Is anyone else having issues with the latest update?  Any ideas on how to fix this issue?

 

I see this in the logs not sure what it means:

Sun Sep 6 11:12:02 2020 WARNING: file 'credentials.conf' is group or others accessible

 

Edited by whitewraith
incomplete information
Link to post
41 minutes ago, thatsthefrickenlightning said:

I'll have a go at that. No clue why one server would work and the other would not if the port forwarding api was down. Unless servers have their own api.

 

E: current-gen Vancouver works like a charm. So either the error is untrue (no hate) or there are multiple port forward apis.

Yeah, I found it strange as well, best guess is that increased load on the Montreal server has causes it to either run out of ports or crash the port forwarding.

Link to post

Is there a way to use a static IP for the VPN Ip address. I need it to do Port Forwarding in the VPN provider, i'm using TorGuard. I tried to google a solution and seemed to have found a way, but it required making changes in the openvpn/credentials.conf file. But that file is overwritten by the docker on every restart.
The TorGuard app on windows had a built in way to set this static ip, never had to deal with the OpenVPN files.
Btw the docker is working fine, I get a VPN ip address as planned, I just want it to be static and not change on every restart.

Link to post
On 9/8/2020 at 2:48 AM, whitewraith said:

Cannot access the webUI no matter what I do?  It was working perfect, I updated and now it will not connect at all to the webUI. With or without VPN enabled no luck. Any ideas or helpful hints?

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

Link to post

I aswell am having issues today relating to it seems the PIA port forwarding API. Getting curl error code 56 when starting the docker container. Issue is resolved following disabling port forwarding. Any workaround for the issue to get back up and running, or just have to wait on PIA?

 

Thanks for the great work!

 

Edit: Have tried switching to 3 other servers (Germany, Spain, and Israel) as others have tried, with no luck. Now receiving exit code 52 and getting the same result. Have tried both third and fourth generation.

Edited by TheOgre
Updated troubleshooting
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.