[Support] binhex - DelugeVPN


Recommended Posts

6 minutes ago, jebusfreek666 said:

 

Wow, everyone on this site is leagues ahead of me when it comes to this stuff. I will play around with it a bit when I get home tonight, and I am grateful for the help. But I feel like a 10 year old sitting in a college lecture.....

 

It helps to do it wrong 700 times and then pop up on forums trying to explain it to others.. Some of these guys are way ahead. As wgstarks says, you can also give deluge (via gui) a torrent file. This also downloads the .torrent file via your VPN as it's all done in the Docker container. 

Link to comment
30 minutes ago, jebusfreek666 said:

I am guessing now that it has to do with the indexer I have added. I would like to add more, but could not figure out how to do that last night.

@gridrunner (spaceinvader one) has many other videos including one for adding Sonarr which is a tv show indexer. Binhex also has supplied a RadarrVPN indexer which is for movies but is almost completely identical to Sonarr. I think you’ll find that they are fairly easy to get setup.

Link to comment
On 2/4/2018 at 8:45 PM, jmbrnt said:

Argh, sorry - I thought I had debug on. Re-attached.

 

Nord I have a year of subscription left and have been using them at near-linespeed for over a year in this setup - so even if it's slow I'm keen to keep using it - at least until I can get delugevpn to load again! :)

 

Thanks for your time

supervisord_debug.log

 

Sorry to bump this, but I really have no idea what's wrong

Link to comment

jmbrnt, I would be interested to hear what speeds you achieve once you have this setup working.  I'm currently using the recommended PIA, but that doesn't enable me to access BBC iPlayer in the UK.  I see NordVPN are promising a SmartDNS service later this year, which may allow access to the BBC site.  However, I'm only interested if I can still get my 5MB/s torrent downloads (on a 50Mbps FTTH connection).

Link to comment
5 minutes ago, PeterB said:

jmbrnt, I would be interested to hear what speeds you achieve once you have this setup working.  I'm currently using the recommended PIA, but that doesn't enable me to access BBC iPlayer in the UK.  I see NordVPN are promising a SmartDNS service later this year, which may allow access to the BBC site.  However, I'm only interested if I can still get my 5MB/s torrent downloads (on a 50Mbps FTTH connection).

 

Well.. I have a 100M FTTH connection and I can hit 9.8MB/s using the Switzerland node I have picked (having just tested an Ubuntu ISO). However, it tends to hover around 1-3MB/s 

 

I'm connected via a 'Powerline' ethernet adaptor, which I suspect is introducing some loss. My recent house move has caused my speeds to deteriorate as well. Any TCP transmission is going to get hammered by packet loss, so I don't think blaming NordVPN for the speeds I get is entirely fair. However, I tend to automate any downloads I have, so I'm not sitting in front of the TV waiting for things to complete - in my use-case the speeds I get are more than enough.

 

If you like I can switch to a UK based endpoint and have a go, but as I'm in the UK the test won't be fair either :) 

 

Link to comment
19 minutes ago, PeterB said:

jmbrnt, I would be interested to hear what speeds you achieve once you have this setup working.  I'm currently using the recommended PIA, but that doesn't enable me to access BBC iPlayer in the UK.  I see NordVPN are promising a SmartDNS service later this year, which may allow access to the BBC site.  However, I'm only interested if I can still get my 5MB/s torrent downloads (on a 50Mbps FTTH connection).

 

question is, does nordvpn support port forwarding? if the answer is no then you wont get decent download/upload rates, its as simple as that.

Link to comment
27 minutes ago, binhex said:

 

question is, does nordvpn support port forwarding? if the answer is no then you wont get decent download/upload rates, its as simple as that.

 

And the answer to that is "not yet". I am OK with the speeds I get and have a year left on my subscription :)

 

 

Link to comment
26 minutes ago, binhex said:

 

question is, does nordvpn support port forwarding? if the answer is no then you wont get decent download/upload rates, its as simple as that.

 

Hmmm ... I need a service which will allow me decent speed up and down AND let me access BBC from here in Philippines.  I had a trial of unlocator (a smart DNS service?) which did enable access to BBC iPlayer, but the price of US$99 a year is a bit high!  PIA don't appear to offer SmartDNS.

Link to comment
24 minutes ago, PeterB said:

 

Hmmm ... I need a service which will allow me decent speed up and down AND let me access BBC from here in Philippines.  I had a trial of unlocator (a smart DNS service?) which did enable access to BBC iPlayer, but the price of US$99 a year is a bit high!  PIA don't appear to offer SmartDNS.

 

I've previously had great success with Unblock.us from New Zealand - don't remember it being expensive. 

Link to comment
1 hour ago, binhex said:

 

question is, does nordvpn support port forwarding? if the answer is no then you wont get decent download/upload rates, its as simple as that.

 

Speaking of which, is there something I can read to explain this further? What I mean is, everything I have ever seen about port forwarding states that you have to set it up through your router and designate a port to be open. But according to the info I have read on here, with the delugevpn docker, as long as you have STRICT_PORT_FORWARDING and subscribe to PIA, and pick one of the locations that allow port forwarding, you are good to go. I would really like to read about how that is possible. TBH, I don't fully understand port forwarding to begin with and I am in no way an advanced (or even competent) user. But it seems like this is side stepping a necessary process somehow.

 

Edit: This is strictly for informational/educational purposes. Don't mean to imply that the software is faulty in anyway. I just like to understand how things work.

Edited by jebusfreek666
update
Link to comment
2 hours ago, jebusfreek666 said:

 

Speaking of which, is there something I can read to explain this further? What I mean is, everything I have ever seen about port forwarding states that you have to set it up through your router and designate a port to be open. But according to the info I have read on here, with the delugevpn docker, as long as you have STRICT_PORT_FORWARDING and subscribe to PIA, and pick one of the locations that allow port forwarding, you are good to go. I would really like to read about how that is possible. TBH, I don't fully understand port forwarding to begin with and I am in no way an advanced (or even competent) user. But it seems like this is side stepping a necessary process somehow.

 

Edit: This is strictly for informational/educational purposes. Don't mean to imply that the software is faulty in anyway. I just like to understand how things work.

 

Physically, the packets leaving your docker, on your unraid server do run through your home router - however the beauty of tunneling (VPN) is that extra padding is added on the outside of your normal packets, encapsulating what you are sending/receiving with the tunnel provider (this extra padding also has its own ports).. This is what gives you the additional security - it also extends a logical connection from the VPN endpoint (in this case, the Docker container) and the other endpoint (PIA's machine elsewhere). This can be thought of as a single long piece of network cable, with no interfering routers/firewalls in the way. Thinking of it like this, the PIA endpoint is the router for this connection, so the port-forwarding needs to be done there.

 

A packet comes in from some source with port 55588.. PIA allows forwarding of that packet on to you, so it hits your docker and Deluge with that src port.. If your provider doesn't allow forwarding, the port number is changed and as a result Deluge doesn't perform as well.. This is the same as if you were doing the port forwarding on your router for another service.. Except that when using VPN, your router has no idea what ports you're exchanging with the outside world.. All it sees is encrypted packets heading off toward PIA's IP (and coming back).

 

 

Edited by jmbrnt
  • Like 1
Link to comment

I've had issues deleting items in Deluge, whether it's a few or many (80-100s). When I select all, right click "Remove Torrent" and select "Remove With Data", I've never got a rapid response. The menu stays up, and clicking a second or third time still doesn't remove the menu. Often a few seconds later, I get a weird "The connection to the webserver has been lost!" and get kicked out of the webserver. When I go back in a few seconds later the files are usually removed. I don't think this an issue unique to binhex's version, but what are others doing to cleanup occasionally? Maybe skip the webserver connection to delete files?

 

I don't expect Deluge to be changed to resolve this anytime soon, and modifications inside the docker container seem to put unnecessary request/burden on Binhex, so does anyone have a simple script to list all those that are status "Queued" and Progress=100% ? An 8 year old example I found here depends on deluge python modules which means it would be a long one-liner to go in and out of the container:

docker exec -ti binhex-delugevpn bash && python2.7 /mounted-array/.bin/script.py && exit

I'm a bit nervous to try the script, but inside the python2.7 interpreter, all 5 lines of module imports work successfully.

Link to comment

After upgrading to unraid 6.4.1 (from 6.4.0) my deluge webgui is no longer accessible, and it appears inactive on my tracker.
The docker log is below, but nothing in there seemed to stand out.
Are there any known issues with this docker image on the latest unraid?

Thanks

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

2018-02-09 18:20:26.070858 [info] Host is running unRAID
2018-02-09 18:20:26.095977 [info] System information Linux 43313008e7f4 4.14.16-unRAID #1 SMP PREEMPT Wed Jan 31 08:51:39 PST 2018 x86_64 GNU/Linux
2018-02-09 18:20:26.133134 [info] PUID defined as '99'
2018-02-09 18:20:26.178612 [info] PGID defined as '100'
2018-02-09 18:20:26.260002 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2018-02-09 18:20:26.288966 [info] Permissions already set for volume mappings
2018-02-09 18:20:26.320803 [info] VPN_ENABLED defined as 'yes'
2018-02-09 18:20:26.371032 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...
2018-02-09 18:20:26.402966 [info] VPN remote line defined as 'nl.privateinternetaccess.com 1198'
2018-02-09 18:20:26.434083 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
2018-02-09 18:20:26.462048 [info] VPN_PORT defined as '1198'
2018-02-09 18:20:26.492825 [info] VPN_PROTOCOL defined as 'udp'
2018-02-09 18:20:26.521557 [info] VPN_DEVICE_TYPE defined as 'tun'
2018-02-09 18:20:26.549207 [info] VPN_PROV defined as 'pia'
2018-02-09 18:20:26.579061 [info] LAN_NETWORK defined as '192.168.0.1/24'
2018-02-09 18:20:26.609072 [info] NAME_SERVERS defined as '8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177'
2018-02-09 18:20:26.637627 [info] VPN_USER defined as ''
2018-02-09 18:20:26.668203 [info] VPN_PASS defined as ''
2018-02-09 18:20:26.697073 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-02-09 18:20:26.723637 [warn] STRICT_PORT_FORWARD not defined (via -e STRICT_PORT_FORWARD), defaulting to 'yes'
2018-02-09 18:20:26.752911 [info] ENABLE_PRIVOXY defined as 'no'
2018-02-09 18:20:26.777259 [info] Setting permissions on files/folders inside container...
2018-02-09 18:20:26.811452 [info] Starting Supervisor...
2018-02-09 18:20:27,128 CRIT Set uid to user 0
2018-02-09 18:20:27,128 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2018-02-09 18:20:27,131 INFO supervisord started with pid 7
2018-02-09 18:20:28,133 INFO spawned: 'start-script' with pid 131
2018-02-09 18:20:28,135 INFO spawned: 'deluge-script' with pid 132
2018-02-09 18:20:28,136 INFO spawned: 'deluge-web-script' with pid 133
2018-02-09 18:20:28,137 INFO spawned: 'privoxy-script' with pid 134
2018-02-09 18:20:28,137 INFO reaped unknown pid 8
2018-02-09 18:20:28,142 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2018-02-09 18:20:28,142 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2018-02-09 18:20:28,144 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2018-02-09 18:20:28,144 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23255617743904 for <Subprocess at 23255617741528 with name privoxy-script in state RUNNING> (stderr)>
2018-02-09 18:20:28,144 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 23255617743472 for <Subprocess at 23255617741528 with name privoxy-script in state RUNNING> (stdout)>
2018-02-09 18:20:28,144 INFO exited: privoxy-script (exit status 0; expected)
2018-02-09 18:20:28,144 DEBG received SIGCLD indicating a child quit
2018-02-09 18:20:28,144 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2018-02-09 18:20:28,201 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2018-02-09 18:20:28,205 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2018-02-09 18:20:28,209 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2018-02-09 18:20:28,214 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2018-02-09 18:20:28,217 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2018-02-09 18:20:28,339 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2018-02-09 18:20:28,340 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2018-02-09 18:20:28,340 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2018-02-09 18:20:28,341 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

2018-02-09 18:20:28,341 DEBG 'start-script' stdout output:
--------------------

2018-02-09 18:20:28,346 DEBG 'start-script' stdout output:
[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

2018-02-09 18:20:28,346 DEBG 'start-script' stdout output:
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'

2018-02-09 18:20:28,367 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2018-02-09 18:20:28,474 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2018-02-09 18:20:28,477 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-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.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o 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.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2018-02-09 18:20:28,477 DEBG 'start-script' stdout output:
--------------------

2018-02-09 18:20:28,478 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 WARNING: file 'credentials.conf' is group or others accessible
Fri Feb 9 18:20:28 2018 OpenVPN 2.4.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017
Fri Feb 9 18:20:28 2018 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
[info] OpenVPN started

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2018-02-09 18:20:28,520 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]46.166.188.207:1198
Fri Feb 9 18:20:28 2018 UDP link local: (not bound)
Fri Feb 9 18:20:28 2018 UDP link remote: [AF_INET]46.166.188.207:1198

2018-02-09 18:20:29,081 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:29 2018 [ea20ec2051d1996fc127af8a0a13b9] Peer Connection Initiated with [AF_INET]46.166.188.207:1198

2018-02-09 18:20:30,384 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 auth-token received, disabling auth-nocache for the authentication token

2018-02-09 18:20:30,385 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 TUN/TAP device tun0 opened

2018-02-09 18:20:30,385 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Feb 9 18:20:30 2018 /usr/bin/ip link set dev tun0 up mtu 1500

2018-02-09 18:20:30,386 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 /usr/bin/ip addr add dev tun0 local 10.48.10.6 peer 10.48.10.5

2018-02-09 18:20:30,388 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 /root/openvpnup.sh tun0 1500 1558 10.48.10.6 10.48.10.5 init

2018-02-09 18:20:30,396 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 Initialization Sequence Completed

2018-02-09 18:20:30,424 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.48.10.6 different, marking for reconfigure

2018-02-09 18:20:30,519 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=aede12a2ecf7f4e5f761bb8ec3828ff9d54a0ce85ef053341415569bb59480a6...

2018-02-09 18:20:30,810 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 56 from curl != 0
[info] 12 retries left
[info] Retrying in 10 secs...

2018-02-09 18:20:30,811 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 212.92.115.177

2018-02-09 18:20:42,735 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=aede12a2ecf7f4e5f761bb8ec3828ff9d54a0ce85ef053341415569bb59480a6, response code 200

2018-02-09 18:20:43,440 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2018-02-09 18:20:43,941 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.14.10.6
[info] Deluge listening interface will be changed to 10.48.10.6
[info] Saving changes to Deluge config file /config/core.conf...

2018-02-09 18:20:44,392 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui...

2018-02-09 18:20:48,338 DEBG 'deluge-script' stdout output:
Setting random_port to False..
Configuration value successfully updated.

2018-02-09 18:20:48,927 DEBG 'deluge-script' stdout output:
Setting listen_ports to (38935, 38935)..
Configuration value successfully updated.

2018-02-09 18:20:48,955 DEBG 'deluge-script' stdout output:
[info] Deluge started

 

Edited by repentharlequin
Link to comment

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.