[Support] binhex - DelugeVPN

[DAVIDP]

xxDeadbolt - Yes, my main creds, the one i use for the PIA website, not the SOCKS/Proxy ones. Same credits i've been using for ages, the one that starts with Pxxxxxx. same creds i can use to connect to the same end point via a desktop openVPN client.... its so damn odd. 

 

I spat it thinking maybe something screwy somewhere, so deleted the whole container, the whole binhex-del.. folder from appdata, etc... and started over. different endpoint this time but same outcome.. I'm at a loss.

Edited November 1, 2020 by DAVIDP

[DAVIDP]

FOUND THE PROBLEM...

 

Seems like it didn't like a 99 character password all of a sudden???? I shortened my PIA password, updated the docker config and it connected instantly..... is there a limitation in the build for password length maybe? i've had the same 99 char password for about 6 months now without incident...

[bigdan1190]

5 hours ago, wgstarks said:

Try manually moving the egg file to the plugins folder and restarting the docker.

Yeeessssssssssss thank you so much, this did the trick!

 

4 hours ago, xxDeadbolt said:

I had a similar issue with Deluge & I'm also on Virgin Media. Couldn't figure out why I was getting such slow speeds (~600-800Kbps), so I ended up moving to Binhex's rTorrent container & have had no problems with speed since, downloads at around 90% of my connection speed. Keen to find it out you figure this out, it was doing my head in 😂

Yup, just sorted  I got the ITconfig installed as per the above instruction from wgstarks, disabled UTP and now i'm getting the correct speeds. The settings are in the pic below - just tick the box on the far left to enable those 2 settings and then untick the boxes in the 'settings' column.

Edited November 1, 2020 by bigdan1190

[binhex]

FOUND THE PROBLEM...
 
Seems like it didn't like a 99 character password all of a sudden? I shortened my PIA password, updated the docker config and it connected instantly..... is there a limitation in the build for password length maybe? i've had the same 99 char password for about 6 months now without incident...

The is no limit in my code, did your password contain characters that are not a-z or 0-9 if did then it's more likely that was your issue

Sent from my CLT-L09 using Tapatalk

[wgstarks]

51 minutes ago, bigdan1190 said:

Yeeessssssssssss thank you so much, this did the trick!

This is my go-to method for installing plugins. I don’t usually bother trying to install via the gui.

[xxDeadbolt]

2 hours ago, bigdan1190 said:

Yup, just sorted  I got the ITconfig installed as per the above instruction from wgstarks, disabled UTP and now i'm getting the correct speeds. The settings are in the pic below - just tick the box on the far left to enable those 2 settings and then untick the boxes in the 'settings' column.

I've tried this before with no solution... most it done was increase from 600-800Kbps to ~1.1Mbps. Cheers, though, & I'm glad you got it sorted!

[jevan23]

Hi All,

I've had delugeVPN working great for a long time, but recently added a managed switch and VLANs to the mix and now no matter what, I cannot get DelugeVPN to connect as a download client for sonarr or radarr. When testing the connection i get "Unknown exception: The operation has timed out."

Under DelugeVPN docker settings, if i set VPN_Enabled to NO, sonarr/radarr connects just fine.

 

 

DelugeVPN used to be on its own dedicated port (eth1) but is now on a VLAN network br0.50 sharing the same port as the Unraid main interface.

 

Main interface: 192.168.0.0/24

br0.50: 192.168.50.0/24 (VLAN ID 50)

Bridging is enabled

 

 

 

DelugeVPN Docker Settings:

Network type: Custom br0.50

VPN Enabled: Yes

LAN_Network: 192.168.50.0/24,192.168.0.0/24

gets assigned an IP of 192.168.50.2

 

Sonarr Docker Settings:

Network type: Custom br0.50

gets assigned an IP of 192.168.50.3

 

As far as pfsense goes, i can ping both sonarr and delugeVPN from a separate pc on VLAN ID 50 network. VLAN ID 50 can reach the internet, and the VPN portion of DelugeVPN is working just fine. From the main LAN, i can ping sonarr but not delugeVPN (webUI works fine for both)

 

 

Im new to VLANs, but testing with separate devices everything is working as it should, I'm left thinking theres some setting in Unraid that needs to be tweaked, but not sure what it could be.

 

FYI, I've also tried with Sonarr docker settings: network type Host, and network type Bridge, same issue (only works with VPN Enabled: NO). Any help would be greatly appreciated!

 

 

Edited November 1, 2020 by jevan23

[cpthook]

Hello.  As of last update I am no longer able to access WebGUI.  Been using this app for years with no issues.  Did anything change?

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

2020-11-01 23:17:14.287604 [info] System information Linux 2cc8f7986f84 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-11-01 23:17:14.315545 [info] OS_ARCH defined as 'x86-64'
2020-11-01 23:17:14.344948 [info] PUID defined as '99'
2020-11-01 23:17:14.422057 [info] PGID defined as '100'
2020-11-01 23:17:14.538747 [info] UMASK defined as '000'
2020-11-01 23:17:14.562103 [info] Permissions already set for volume mappings
2020-11-01 23:17:14.588441 [info] Deleting files in /tmp (non recursive)...
2020-11-01 23:17:14.615166 [info] VPN_ENABLED defined as 'yes'
2020-11-01 23:17:14.641098 [info] VPN_CLIENT defined as 'openvpn'
2020-11-01 23:17:14.663460 [info] VPN_PROV defined as 'pia'
2020-11-01 23:17:15.502924 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Czech Republic.ovpn
2020-11-01 23:17:15.546293 [info] VPN remote server(s) defined as 'czech.privateinternetaccess.com,'
2020-11-01 23:17:15.566425 [info] VPN remote port(s) defined as '1198,'
2020-11-01 23:17:15.586596 [info] VPN remote protcol(s) defined as 'udp,'
2020-11-01 23:17:15.610466 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-11-01 23:17:15.633721 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-11-01 23:17:15.658290 [info] LAN_NETWORK defined as '192.168.1.0/24'
2020-11-01 23:17:15.680660 [info] NAME_SERVERS defined as '209.222.18.222,209.222.18.218'
2020-11-01 23:17:15.703772 [info] VPN_USER defined as ''
2020-11-01 23:17:15.726439 [info] VPN_PASS defined as ''
2020-11-01 23:17:15.751050 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-11-01 23:17:15.775234 [info] ENABLE_PRIVOXY defined as 'yes'
2020-11-01 23:17:15.796907 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-11-01 23:17:15.820993 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-11-01 23:17:15.842706 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-11-01 23:17:15.867074 [info] Starting Supervisor...
2020-11-01 23:17:16,045 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-11-01 23:17:16,045 INFO Set uid to user 0 succeeded
2020-11-01 23:17:16,047 INFO supervisord started with pid 6
2020-11-01 23:17:17,049 INFO spawned: 'start-script' with pid 179
2020-11-01 23:17:17,050 INFO spawned: 'watchdog-script' with pid 180
2020-11-01 23:17:17,051 INFO reaped unknown pid 7 (exit status 0)
2020-11-01 23:17:17,055 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-11-01 23:17:17,055 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-11-01 23:17:17,056 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-11-01 23:17:17,099 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-11-01 23:17:17,102 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-11-01 23:17:17,202 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-11-01 23:17:17,213 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-11-01 23:17:17,215 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-11-01 23:17:17,216 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-11-01 23:17:17,217 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-11-01 23:17:17,217 DEBG 'start-script' stdout output:
--------------------

2020-11-01 23:17:17,219 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle

2020-11-01 23:17:17,220 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-11-01 23:17:17,258 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-11-01 23:17:17,259 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-11-01 23:17:17,260 DEBG 'start-script' stdout output:
--------------------

2020-11-01 23:17:17,260 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2020-11-01 23:17:17,274 DEBG 'start-script' stdout output:
Sun Nov 1 23:17:17 2020 WARNING: file 'credentials.conf' is group or others accessible

Sun Nov 1 23:17:17 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 Nov 1 23:17:17 2020 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10

2020-11-01 23:17:17,274 DEBG 'start-script' stdout output:
Sun Nov 1 23:17:17 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-11-01 23:17:17,275 DEBG 'start-script' stdout output:
Sun Nov 1 23:17:17 2020 CRL: loaded 1 CRLs from file crl.rsa.2048.pem

2020-11-01 23:17:17,275 DEBG 'start-script' stdout output:
Sun Nov 1 23:17:17 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]212.102.39.1:1198

2020-11-01 23:17:17,276 DEBG 'start-script' stdout output:
Sun Nov 1 23:17:17 2020 UDP link local: (not bound)
Sun Nov 1 23:17:17 2020 UDP link remote: [AF_INET]212.102.39.1:1198

2020-11-01 23:18:17,493 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:17 2020 [UNDEF] Inactivity timeout (--ping-restart), restarting

2020-11-01 23:18:17,493 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:17 2020 SIGHUP[soft,ping-restart] received, process restarting

2020-11-01 23:18:17,493 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:17 2020 WARNING: file 'credentials.conf' is group or others accessible

Sun Nov 1 23:18:17 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 Nov 1 23:18:17 2020 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10

2020-11-01 23:18:22,494 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:22 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-11-01 23:18:22,494 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:22 2020 CRL: loaded 1 CRLs from file crl.rsa.2048.pem

2020-11-01 23:18:22,494 DEBG 'start-script' stdout output:
Sun Nov 1 23:18:22 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]212.102.39.1:1198
Sun Nov 1 23:18:22 2020 UDP link local: (not bound)
Sun Nov 1 23:18:22 2020 UDP link remote: [AF_INET]212.102.39.1:1198

2020-11-01 23:19:22,986 DEBG 'start-script' stdout output:
Sun Nov 1 23:19:22 2020 [UNDEF] Inactivity timeout (--ping-restart), restarting

2020-11-01 23:19:22,986 DEBG 'start-script' stdout output:
Sun Nov 1 23:19:22 2020 SIGHUP[soft,ping-restart] received, process restarting

2020-11-01 23:19:22,986 DEBG 'start-script' stdout output:
Sun Nov 1 23:19:22 2020 WARNING: file 'credentials.conf' is group or others accessible

Sun Nov 1 23:19:22 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 Nov 1 23:19:22 2020 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10

2020-11-01 23:19:27,987 DEBG 'start-script' stdout output:
Sun Nov 1 23:19:27 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-11-01 23:19:27,987 DEBG 'start-script' stdout output:
Sun Nov 1 23:19:27 2020 CRL: loaded 1 CRLs from file crl.rsa.2048.pem
Sun Nov 1 23:19:27 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]212.102.39.1:1198
Sun Nov 1 23:19:27 2020 UDP link local: (not bound)
Sun Nov 1 23:19:27 2020 UDP link remote: [AF_INET]212.102.39.1:1198

 

[xxDeadbolt]

59 minutes ago, cpthook said:

Hello.  As of last update I am no longer able to access WebGUI.  Been using this app for years with no issues.  Did anything change?

2020-11-01 23:17:15.546293 [info] VPN remote server(s) defined as 'czech.privateinternetaccess.com,'

 

You're still using the legacy OVPN file/servers. You need the new 'next gen' files from PIA.

 

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

Edited November 2, 2020 by xxDeadbolt

[cpthook]

Wow....thanks for the notification!  I'm fixed now, but I wonder if this change affects the virtual VPN router setup guidance from #spaceinvaderone??

[Trech_em]

EDIT: Previous post I was responding to seems to be missing. Also... seems the issue may be resolved. Looks like possibly a problem on the provider side

Edited November 2, 2020 by Trech_em

[Kishin]

Hello, is it possible to download to the cache drive and when completed automaticaly move to another folder on the array ? This way i would be able to continue seeding indefinitely while using all the space.

[wgstarks]

21 minutes ago, Kishin said:

Hello, is it possible to download to the cache drive and when completed automaticaly move to another folder on the array ? This way i would be able to continue seeding indefinitely while using all the space.

Sure. Set a cache only share for /data and then use Sonarr and Radarr dockers to copy the completed downloads to another share.

[Magic815]

Hi there - so I just tried updating to the next gen servers (following the answer to Q19), but I seem to be having issues. This is what the log says when I try to start the docker container:

 

This is what the docker container settings look like:

 

And this is what the openvpn folder looks like (the certs and .opvn files where extracted from the nextgen zip link):

 

Any ideas on what I'm doing wrong?

[binhex]

3 minutes ago, Magic815 said:

Hi there - so I just tried updating to the next gen servers (following the answer to Q19), but I seem to be having issues. This is what the log says when I try to start the docker container:

 

This is what the docker container settings look like:

 

And this is what the openvpn folder looks like (the certs and .opvn files where extracted from the nextgen zip link):

 

Any ideas on what I'm doing wrong?

another auth failure, see Q16:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[wgstarks]

4 minutes ago, Magic815 said:

but I seem to be having issues.

The log is showing an authorization fail. Are you using the same user/password in the container that you use to login to the PIA website?

[Magic815]

Ah, gotcha. I, in-fact, did a password reset on PIA earlier, and had not changed it in the docker settings.

 

However, I just now confirmed that my PIA subscription is active, my docker settings match the username/pw needed to log in, and the credentials.conf file inside the 'openvpn' folder matches it as well. I don't see an AUTH_FAILED anymore, but the webUI still doesn't load.

 

Can you glean anything from the following? Looks like something with the cipher?

 

EDIT: Ah, is this related to Q22? I'll do some digging.

Edited November 2, 2020 by Magic815

[binhex]

2 minutes ago, Magic815 said:

EDIT: Ah, is this related to Q22? I'll do some digging.

👍

[Magic815]

4 minutes ago, binhex said:

👍

Does the below line have to get added to any particular spot in the file?

data-ciphers-fallback aes-256-gcm

[binhex]

2 minutes ago, Magic815 said:

Does the below line have to get added to any particular spot in the file?

data-ciphers-fallback aes-256-gcm

nope it can go anywhere, as long as its on a new line, dont use notepad!

[Magic815]

10 minutes ago, binhex said:

nope it can go anywhere, as long as its on a new line, dont use notepad!

Hmm, I seem to keep having the same error message, even with this being my .ovpn file:

 

And I used Notepad++ to make the edit. Should I try a different .ovpn? (I'm currently using Switzerland.ovpn).

Edited November 2, 2020 by Magic815

[binhex]

2 minutes ago, Magic815 said:

Hmm, I seem to keep having the same error message, even with this being my .ovpn file:

remove the 'cipher' line in the file.

[Magic815]

17 minutes ago, binhex said:

remove the 'cipher' line in the file.

Huh, so I tried replacing the cipher line with the new one, but same error. "Failed to negotiate cipher."

 

And I tried making this edit in the Switzerland.ovpn and Spain.opvn files - both to no avail. (And I made sure only one .opvn file was in the openvpn folder at a time).

 

Appreciate you sticking with me here.

Edited November 2, 2020 by Magic815

[diditstart]

I was having the same issue with the cipher error. Redownloaded the whole package of next gen PIA config files and replaced all three (crt, pem and ovpn) files this time. Deluge started working again.

[Magic815]

5 minutes ago, diditstart said:

I was having the same issue with the cipher error. Redownloaded the whole package of next gen PIA config files and replaced all three (crt, pem and ovpn) files this time. Deluge started working again.

Did you have to add the extra line in the opvn file per answer 22 in his FAQ?