[Support] binhex - DelugeVPN

[thatsthefrickenlightning]

10 hours ago, itractus said:

So, I will provide an update. I did not get it to work. Besides that I am certain this image is stopping my torrent client from actually connecting to peers. After running this config for a week, I've got about 80 unfinished torrents. This would be fine, if those torrents did not have any peers, however this is not the case.

I'm getting connected to peers that have 100% of the files, and I can simply watch deluge not pull anything in.

 

So In short, The VPN connection works, some torrents work fine. The VPN connection is capped to about 1mbps normally and 2.5 on a good day. I've tried to eliminate any bottleneck from my setup, but I cannot for the life of me figure out what is causing this issue.

On QB, I solved it by enabling only TCP under the connections tab in the settings.

 

Bally12345 and I discuss a fix for Deluge here, but it's less effective than the QB fix:

 

[anylettuce]

18 hours ago, binhex said:

rookie mistake:-

LAN_NETWORK defined as '192.168.1.6/24'

 

see OP link to documentation, then VPN faq section for examples on how to configure this correctly.

changed it back to 192.168.1.0 and nothing

 

ifconfig br0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.8  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::6821:7dff:fe0b:679a  prefixlen 64  scopeid 0x20<link>
        ether 00:25:90:50:30:0b  txqueuelen 1000  (Ethernet)
        RX packets 533719233  bytes 1710461864114 (1.5 TiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 99910465  bytes 9144509531 (8.5 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[strike]

4 hours ago, anylettuce said:

changed it back to 192.168.1.0 and nothing

 

ifconfig br0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.8  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::6821:7dff:fe0b:679a  prefixlen 64  scopeid 0x20<link>
        ether 00:25:90:50:30:0b  txqueuelen 1000  (Ethernet)
        RX packets 533719233  bytes 1710461864114 (1.5 TiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 99910465  bytes 9144509531 (8.5 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br0 is not supported in this container, please change to bridge or host.

[anylettuce]

10 hours ago, strike said:

br0 is not supported in this container, please change to bridge or host.

it is in bridge mode, that is the ip I use to log into unraid

[areis]

Hi there! This is my first post; apologies in advance for any breaches of forum protocol, and thanks in advance for your help!

 

Environment:

I'm running this via docker-compose on a vanilla Ubuntu 18.04 VM running under Proxmox.

 

Kudos:

This worked! Really appreciate @binhex's work on this + many of you for already having answered so many of the questions that came up during setup.

 

Question 1: Why is my bandwidth inside the container maxing out at ~40Mbps?

I have a 1Gb asymmetrical internet connection at home, and routinely get speeds of 300Mbps+ through my VPN provider (Torguard). Inside this container, however, I can't seem to get speeds over 40Mbps (as tested via speedtest-cli and observed in deluge). I've tried several different Torguard nodes and even a few on my friend's PIA account. They all max out at 30-40Mbps within the docker container, even though I can get 150-400Mbps (via the same nodes) on my mac.

 

Might this be a symptom of my screwing up a config? Or is there a common bottleneck that I should know about?

 

Question 2: Once I have this basic setup working, what (if any) additional config do I need to set up through my VPN provider?

It's clear that VPN port forwarding is important for torrent performance. Is that all handled automagically through the openvpn configs, or do I need to manually set it up? If the latter, has anyone written a good guide/reference for the process?

 

Thanks again!

Edited May 31, 2019 by areis
Added details about how I tested my bandwidth

[anylettuce]

On 5/29/2019 at 2:29 AM, binhex said:

rookie mistake:-

LAN_NETWORK defined as '192.168.1.6/24'

 

see OP link to documentation, then VPN faq section for examples on how to configure this correctly.

just to give an update. connected to the same network my unraid server is on, deluge works fine. The problem is the site to site vpn provided by the unifi usg devices. all other dockers with the exception of plex and deluge work on the other end of the VPN

[binhex]

just to give an update. connected to the same network my unraid server is on, deluge works fine. The problem is the site to site vpn provided by the unifi usg devices. all other dockers with the exception of plex and deluge work on the other end of the VPN

if this site to site VPN creates another network then you need to add this to the LAN network environment variable, using a comma as separator.

Sent from my EML-L29 using Tapatalk

[antanoid]

hey

bit of an unraid noob here

 

I'm having some problems with my docker

 

I used to have it working via following Spaceinvader One youtube vids

but after a new router and dockers/unraid updates (all done within a week) I seem to have broken something

 

I've been putting off trying to fix it for a week/2 until this weekend

after hitting my head against the wall for the last day, iv finally decided to ask for help!

here are my problems:

I can't connect to web UI - with VPN_ENABLED = yes

radarr/sonarr cant connect to deluge

 

I believe the problem is centred around the VPN connection/settings, as when vpn_enables = no - I'm able to access the web UI

I have followed the documentation linked and believe everything to be setup correctly

 

ill post what seems to be the required info

 

VPN = PIA

openvpn folder: - new downloads from PIA

 

 

new supervisord.log - debug = enabled   -   username/pass have been removed, they both follow guidelines (no spec characters)

supervisord.log

 

any help would be muchly appreciated 

[SpencerJ]

34 minutes ago, antanoid said:

hey

bit of an unraid noob here

 

I'm having some problems with my docker

 

I used to have it working via following Spaceinvader One youtube vids

but after a new router and dockers/unraid updates (all done within a week) I seem to have broken something

 

I've been putting off trying to fix it for a week/2 until this weekend

after hitting my head against the wall for the last day, iv finally decided to ask for help!

here are my problems:

I can't connect to web UI - with VPN_ENABLED = yes

radarr/sonarr cant connect to deluge

 

I believe the problem is centred around the VPN connection/settings, as when vpn_enables = no - I'm able to access the web UI

I have followed the documentation linked and believe everything to be setup correctly

 

ill post what seems to be the required info

 

VPN = PIA

openvpn folder: - new downloads from PIA

 

 

new supervisord.log - debug = enabled   -   username/pass have been removed, they both follow guidelines (no spec characters)

supervisord.log 23.53 kB · 1 download

 

any help would be muchly appreciated 

Following 

[octalsnroses]

Hey, not sure if this was mentioned anywhere else yet, but is there a way to specify the version of deluge we want to use? I'm using a private tracker that specifies versions that are compatible, and the default one from the supplied docker image is not on that list.

[TaskMaster]

When I VPN in to my router I can bring up other web interfaces running on Docker, but not the Deluge interface (or bring it up through Android app NZB360).  I thought I saw info about this posted previously but can't find it.  Any suggestions?

[tjb_altf4]

4 hours ago, octalsnroses said:

Hey, not sure if this was mentioned anywhere else yet, but is there a way to specify the version of deluge we want to use? I'm using a private tracker that specifies versions that are compatible, and the default one from the supplied docker image is not on that list.

I find that strange, what versions do they specify?

Current stable version is 2 years old.

[binhex]

When I VPN in to my router I can bring up other web interfaces running on Docker, but not the Deluge interface (or bring it up through Android app NZB360).  I thought I saw info about this posted previously but can't find it.  Any suggestions?

See my previous comment, same for you

Sent from my EML-L29 using Tapatalk

[octalsnroses]

9 hours ago, tjb_altf4 said:

I find that strange, what versions do they specify?

Current stable version is 2 years old.

Deluge 1.3.1, 1.3.5, 1.3.6, 1.3.11

 

I agree with you. I don't really understand the reasoning as to why it's so out of date, but it's frustrating to say the least!

I'm assuming there's no way to specify older versions?

Edited June 2, 2019 by octalsnroses

[tjb_altf4]

13 minutes ago, octalsnroses said:

Deluge 1.3.1, 1.3.5, 1.3.6, 1.3.11

 

I agree with you. I don't really understand the reasoning as to why it's so out of date, but it's frustrating to say the least!

I'm assuming there's no way to specify older versions?

Double check on your tracker's forum, you might find although it's not on the specified "approved" list, it's not on the blacklist either... its just untested.

I noticed that's the case on one of my trackers.

No way to specify an older version in this container config, and going to an earlier tag would not be a viable solution.

 

If you are 100% locked to the versions stated, maybe see if binhex's rTorrentVPN or qBittorrentVPN uses a suitable version for your tracker

[anylettuce]

On 6/1/2019 at 2:44 AM, binhex said:

if this site to site VPN creates another network then you need to add this to the LAN network environment variable, using a comma as separator.

Sent from my EML-L29 using Tapatalk
 

I haven't dug into it but

unraid ip is 192.168.1.8 I go to remote site and input 192.168.1.8:8080 I can bring up sab. Create a network location of //192.168.1.8/cache I can browse the cache drive, or any drive of that matter.

 

the goal was for me to manage the server while away and add more content using the bandwidth from the 2nd location.

I am using the unifi built in site to site, might look into openvpn as I can do the same thing in theory anywhere I have internet connection. Plus my laptop has built in cell modem, just need sim card.

 

[binhex]

3 hours ago, anylettuce said:

I haven't dug into it but

unraid ip is 192.168.1.8 I go to remote site and input 192.168.1.8:8080 I can bring up sab. Create a network location of //192.168.1.8/cache I can browse the cache drive, or any drive of that matter.

 

the goal was for me to manage the server while away and add more content using the bandwidth from the 2nd location.

I am using the unifi built in site to site, might look into openvpn as I can do the same thing in theory anywhere I have internet connection. Plus my laptop has built in cell modem, just need sim card.

 

the unifi usg device must be creating another network in order to route packets over the tunnel, its probably this that needs adding to the LAN_NETWORK value, this container has strict blocking rules in place so you need to specify all networks that you are originating from if you wish to access the web ui. 

[Jacbo]

Hi! First off, thanks for this docker container, it's great! However, I cannot access any of the webui or daemon outside of my LAN. I'm running both the rtorrent and the deluge containers currently, both are working, downloading and uploading (have different ports for everything) and I can access it all perfectly locally. However, when I try to port forward anything I cannot access it. I've got SSH port forwarding setup on my router for the same server so I can't figure out the issue. ip_mangle is loaded, so I'm not sure what it could be. What can I post that might be helpful and would help solve this issue?

[Gragorg]

First off thanks binhex I use a few of your containers and they work flawlessly.  Just a quick question.  When my PIA expires will deluge automatically stop working?  I assume it will but just wanted to confirm.

[strike]

Yes, if your account expires your login credentials will be blocked by PIA causing the container to not be able to authenticate. 

[Globe89]

I'm using a Synology DSM 6.2.2 with Docker. Deluge works if I don't have my VPN (ExpressVPN) configured (false). However, when I set VPN to true I can't download anything. I followed the "Tom the Great" guide to the letter, and rebooted my Synology as well. From the supervisord.log file it appears to me as if the VPN is coming up:

 

Any ideas?

 

2019-06-06 19:41:33,991 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:33 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.48.0.1,comp-lzo no,route 10.48.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.48.0.190 10.48.0.189,peer-id 37,cipher AES-256-GCM'
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: compression parms modified
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: route options modified
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: peer-id set
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: adjusting link_mtu to 1629
Thu Jun  6 19:41:33 2019 OPTIONS IMPORT: data channel crypto options modified
Thu Jun  6 19:41:33 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu Jun  6 19:41:33 2019 NCP: overriding user-set keysize with default
Thu Jun  6 19:41:33 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jun  6 19:41:33 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jun  6 19:41:33 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
Thu Jun  6 19:41:33 2019 TUN/TAP device tun0 opened
Thu Jun  6 19:41:33 2019 TUN/TAP TX queue length set to 100
Thu Jun  6 19:41:33 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-06-06 19:41:33,994 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:33 2019 /usr/bin/ip addr add dev tun0 local 10.48.0.190 peer 10.48.0.189

2019-06-06 19:41:33,997 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:33 2019 /root/openvpnup.sh tun0 1500 1557 10.48.0.190 10.48.0.189 init

2019-06-06 19:41:34,085 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.48.0.190 different, marking for reconfigure

2019-06-06 19:41:34,092 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-06-06 19:41:34,099 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-06 19:41:34,133 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140338604935880 for <Subprocess at 140338604879376 with name privoxy-script in state RUNNING> (stdout)>
2019-06-06 19:41:34,133 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140338605036488 for <Subprocess at 140338604879376 with name privoxy-script in state RUNNING> (stderr)>
2019-06-06 19:41:34,134 INFO exited: privoxy-script (exit status 0; expected)
2019-06-06 19:41:34,134 DEBG received SIGCHLD indicating a child quit
2019-06-06 19:41:34,144 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `ns1.google.com'

2019-06-06 19:41:34,155 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `resolver1.opendns.com'

2019-06-06 19:41:34,215 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, exhausted retries setting to tunnel IP '10.48.0.190'

2019-06-06 19:41:34,313 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-06-06 19:41:35,208 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...

2019-06-06 19:41:35,938 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-06-06 19:41:36,168 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:36 2019 /usr/bin/ip route add 104.143.86.134/32 via 172.17.0.1

2019-06-06 19:41:36,176 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:36 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.48.0.189

2019-06-06 19:41:36,181 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:36 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.48.0.189

2019-06-06 19:41:36,189 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:36 2019 /usr/bin/ip route add 10.48.0.1/32 via 10.48.0.189

2019-06-06 19:41:36,191 DEBG 'start-script' stdout output:
Thu Jun  6 19:41:36 2019 Initialization Sequence Completed

2019-06-06 19:41:36,965 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-06-06 19:41:38,336 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-06 19:41:38,338 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2019-06-06 19:42:08,517 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2019-06-06 19:42:08,676 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2019-06-06 19:42:09,688 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2019-06-06 19:42:09,697 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Some configuration parameters:

 

2019-06-06 15:29:55.343993 [info] PUID defined as '1024'
2019-06-06 15:29:55.622376 [info] PGID defined as '100'
2019-06-06 15:29:55.906141 [info] UMASK defined as '000'
2019-06-06 15:29:55.980167 [info] Setting permissions recursively on volume mappings...
2019-06-06 15:29:56.181577 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2019-06-06 15:29:56.249941 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2019-06-06 15:29:56.353231 [info] VPN_ENABLED defined as 'yes'
2019-06-06 15:29:56.483139 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/my_expressvpn_usa_-_los_angeles_-_3_udp.ovpn
dos2unix: converting file /config/openvpn/my_expressvpn_usa_-_los_angeles_-_3_udp.ovpn to Unix format...
2019-06-06 15:29:56.594243 [info] VPN remote line defined as 'remote usa-losangeles-3-ca-version-2.expressnetw.com 1195'
2019-06-06 15:29:56.661266 [info] VPN_REMOTE defined as 'usa-losangeles-3-ca-version-2.expressnetw.com'
2019-06-06 15:29:56.742286 [info] VPN_PORT defined as '1195'
2019-06-06 15:29:56.867163 [warn] VPN_PROTOCOL not found in /config/openvpn/my_expressvpn_usa_-_los_angeles_-_3_udp.ovpn, assuming udp
2019-06-06 15:29:56.946233 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-06-06 15:29:57.013061 [info] VPN_PROV defined as 'custom'
2019-06-06 15:29:57.085656 [info] LAN_NETWORK defined as '10.13.2.0/24'
2019-06-06 15:29:57.160046 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2019-06-06 15:29:57.232250 [info] VPN_USER defined as 'redacted'
2019-06-06 15:29:57.300635 [info] VPN_PASS defined as 'redacted'
2019-06-06 15:29:57.374480 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-06-06 15:29:57.444065 [info] ENABLE_PRIVOXY defined as 'yes'

 

 

 

 

[strike]

ExpressVPN is not going to work well with torrenting due to the fact that they don't support port forwarding. Even if you were able to download anything it will be painfully slow and it would only work on public trackers. Do yourself a favor and change to a provider that supports port forwarding.

[Biloxi_1]

Hey guys, I'm having what I think is a networking issue. I had everything up and running fine for a long time, however I was troubleshooting an unrelated vm issue last week, and I think I mucked up a network setting somewhere. I can get my container to start, and connect to my vpn provider, but nothing will download, and all the trackers timeout. In the console I can see the connection, but I cannot ping anything outside of my network. My other containers seem to be functioning normally. Any thoughts? I am probably missing something super obvious.

deluge_log.txt

Edited June 7, 2019 by Biloxi_1

[binhex]

26 minutes ago, Biloxi_1 said:

Hey guys, I'm having what I think is a networking issue. I had everything up and running fine for a long time, however I was troubleshooting an unrelated vm issue last week, and I think I mucked up a network setting somewhere. I can get my container to start, and connect to my vpn provider, but nothing will download, and all the trackers timeout. In the console I can see the connection, but I cannot ping anything outside of my network. My other containers seem to be functioning normally. Any thoughts? I am probably missing something super obvious.

deluge_log.txt 33.79 kB · 1 download

looking at your log i would say your vpn provider is having issues:-

Fri Jun 7 07:17:14 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

try a different endpoint, or contact your vpn provider and tell them you are having TLS key negotiation failing.

[Biloxi_1]

6 minutes ago, binhex said:

looking at your log i would say your vpn provider is having issues:-

Fri Jun 7 07:17:14 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

try a different endpoint, or contact your vpn provider and tell them you are having TLS key negotiation failing.

Thank you for your response. I did try a different end point, and received the same results. I noticed while troubleshooting that if I swap the network type in the settings from "bridge" to "custom: br0" the torrents will start downloading, but I i cannot reach webui in that configuration.