Hey, I've been using binhex delugevpn for a while with NordVPN.  I didn't use it for a few months and when I tried to use it again around a week ago it had stopped working.  I tried adjusting a few of the settings but no dice.  I'm able to get into the webUI and add torrents, but they just sit at 0% progress.

 

Attaching logs.  Thanks for any ideas!

Log for_ binhex-delugevpn.html

I've been having trouble moving over to wireguard... Every time I try to start up it hangs at a certain point, container keeps running it just wont go any further.

 

I get a parse error for Invalid literal at line 4, column 0

 

It seems like it connects to the server, and then it just hangs at the /root/wireguardup.sh

2020-10-28 19:52:52,396 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-10-28 19:52:52,396 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-10-28 19:52:52,400 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-10-28 19:52:52,403 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-10-28 19:52:52,406 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-10-28 19:52:52,410 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-10-28 19:52:52,413 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-10-28 19:52:52,416 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-10-28 19:52:52,419 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-10-28 19:52:52,422 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-10-28 19:52:52,521 DEBG 'start-script' stderr output:
parse error: Invalid literal at line 4, column 0


2020-10-28 19:52:53,291 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2020-10-28 19:52:53,842 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-10-28 19:52:53,291 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2020-10-28 19:52:53,842 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-10-28 19:52:53,856 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-10-28 19:52:53,860 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-10-28 19:52:53,861 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-10-28 19:52:53,862 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-10-28 19:52:53,862 DEBG 'start-script' stdout output:
--------------------

2020-10-28 19:52:53,865 DEBG 'start-script' stdout output:
iptable_mangle 16384 1
ip_tables 24576 4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle

2020-10-28 19:52:53,865 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-10-28 19:52:53,909 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-10-28 19:52:53,910 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 1337 -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 -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -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 1337 -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 -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2020-10-28 19:52:53,911 DEBG 'start-script' stdout output:
--------------------

2020-10-28 19:52:53,914 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2020-10-28 19:52:53,924 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2020-10-28 19:52:53,930 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2020-10-28 19:52:53,932 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2020-10-28 19:52:53,939 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.21.202.15 dev wg0

2020-10-28 19:52:53,945 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2020-10-28 19:52:53,958 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2020-10-28 19:52:53,959 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2020-10-28 19:52:53,960 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2020-10-28 19:52:53,961 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2020-10-28 19:52:53,964 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2020-10-28 19:52:53,965 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2020-10-28 19:52:53,967 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

It just sits there. Doesn't add anything else to the log

Everything was set up properly, I'm pretty sure I followed all the instructions on the FAQ too. 

I'm hoping it is just something silly that I overlooked. Anything I should look into?

12 hours ago, TheDanzig said:

I've been having trouble moving over to wireguard... Every time I try to start up it hangs at a certain point, container keeps running it just wont go any further.

 

I get a parse error for Invalid literal at line 4, column 0

 

It seems like it connects to the server, and then it just hangs at the /root/wireguardup.sh

 

It just sits there. Doesn't add anything else to the log

Everything was set up properly, I'm pretty sure I followed all the instructions on the FAQ too. 

I'm hoping it is just something silly that I overlooked. Anything I should look into?

The next step is usually where it uses the name server, so I would check what values you have set for NAME_SERVERS (DNS)

For DNS, I use PIA's new (internal network), Google & Cloudflare

10.0.0.242,10.0.0.243,8.8.8.8,8.8.4.4,1.1.1.1,1.0.0.1

 

Edited October 29, 20205 yr by tjb_altf4

3 hours ago, tjb_altf4 said:

The next step is usually where it uses the name server, so I would check what values you have set for NAME_SERVERS (DNS)

For DNS, I use PIA's new (internal network), Google & Cloudflare

10.0.0.242,10.0.0.243,8.8.8.8,8.8.4.4,1.1.1.1,1.0.0.1

 

Thanks! I'll look into this when I get home this afternoon. When I gave it a quick look this morning it had moved past the wireguardup.sh but looked like it went into the failure to get PIA JSON retry attempts. So we'll see whats up when I dig into it this evening.

6 hours ago, TheDanzig said:

Thanks! I'll look into this when I get home this afternoon. When I gave it a quick look this morning it had moved past the wireguardup.sh but looked like it went into the failure to get PIA JSON retry attempts. So we'll see whats up when I dig into it this evening.

Still nothing. It still sits at the wireguardup.sh for about 15min. Then it goes through and can't connect to the DNS, then it fails to download PIA JSON. 

 

49 minutes ago, TheDanzig said:

Still nothing. It still sits at the wireguardup.sh for about 15min. Then it goes through and can't connect to the DNS, then it fails to download PIA JSON. 

 

Do you have privileged enabled in the template?  Make sure you've set it as per Binhex's updated documentation for wireguard

https://hub.docker.com/r/binhex/arch-delugevpn

 

On my setup I haven't needed to use sysctl="net.ipv4.conf.all.src_valid_mark=1" arg, I'm not sure what conditions this is needed? @binhex

Just installed the docker and got it to connect using PIA defaults. After watching SpaceInvader's vid on it. Thanks.

Haven't looked into airvpn yet.

I have used another non-US VPN for years and looked for reviews of others.

I wasn't thrilled that PIA is US based and ran across this which is a bit troubling.

 

FWIW

https://restoreprivacy.com/vpn/reviews/private-internet-access/ 

 

Hope I'm not causing problems unnecessarily.

26 minutes ago, tjb_altf4 said:

Do you have privileged enabled in the template?  Make sure you've set it as per Binhex's updated documentation for wireguard

https://hub.docker.com/r/binhex/arch-delugevpn

 

On my setup I haven't needed to use sysctl="net.ipv4.conf.all.src_valid_mark=1" arg, I'm not sure what conditions this is needed? @binhex

2020-10-29 20:36:32,362 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json payload from URL 'https://10.7.128.1:19999/getSignature' using token ''
[info] 1 retries left
[info] Retrying in 10 secs...

2020-10-29 20:36:32,362 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json payload from URL 'https://10.7.128.1:19999/getSignature' using token ''
[info] 1 retries left
[info] Retrying in 10 secs...

2020-10-29 20:36:42,363 DEBG 'start-script' stdout output:
[warn] Unable to download PIA json payload, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2020-10-29 20:36:42,365 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2020-10-29 20:36:42,363 DEBG 'start-script' stdout output:
[warn] Unable to download PIA json payload, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2020-10-29 20:36:42,365 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2020-10-29 20:50:38,049 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2020-10-29 20:50:38,051 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-10-29 20:52:08,145 DEBG 'start-script' stderr output:
Error: could not find any address for the name: `ns1.google.com'


2020-10-29 20:52:08,149 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'resolver1.opendns.com'...


2020-10-29 20:52:08,145 DEBG 'start-script' stderr output:
Error: could not find any address for the name: `ns1.google.com'


2020-10-29 20:52:08,149 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'resolver1.opendns.com'...


2020-10-29 20:53:38,240 DEBG 'start-script' stderr output:
Error: could not find any address for the name: `resolver1.opendns.com'


2020-10-29 20:53:38,244 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://checkip.amazonaws.com'...


2020-10-29 20:53:38,240 DEBG 'start-script' stderr output:
Error: could not find any address for the name: `resolver1.opendns.com'


2020-10-29 20:53:38,244 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://checkip.amazonaws.com'...

Yes definitely running privileged. Probably gonna completely remove it tomorrow and try over from scratch.

8 minutes ago, TheDanzig said:

2020-10-29 20:50:38,049 DEBG 'start-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2020-10-29 20:50:38,051 DEBG 'start-script' stdout output: [info] Attempting to get external IP using Name Server 'ns1.google.com'... 2020-10-29 20:52:08,145 DEBG 'start-script' stderr output: Error: could not find any address for the name: `ns1.google.com' 2020-10-29 20:52:08,149 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'resolver1.opendns.com'... 2020-10-29 20:52:08,145 DEBG 'start-script' stderr output: Error: could not find any address for the name: `ns1.google.com'

Not sure if it's the cause of your problem but I saw this in the setup instructions-

Quote

Notes
Due to Google and OpenDNS supporting EDNS Client Subnet it is recommended NOT to use either of these NS providers. The list of default NS providers in the above example(s) is as follows:-

209.222.x.x = PIA 84.200.x.x = DNS Watch 37.235.x.x = FreeDNS 1.x.x.x = Cloudflare

It appears that you are trying to use google and OpenDNS. The recommended NS servers would be-

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

 

Is there any way to remove/disable the login password prompt?

20 hours ago, wgstarks said:

Not sure if it's the cause of your problem but I saw this in the setup instructions-

It appears that you are trying to use google and OpenDNS. The recommended NS servers would be-

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

 

Tried those, still hangs up with getting the wireguard up and running. Switched back to OpenVPN and it starts flawlessly and quickly. I'll give wireguard another visit in a few days probably. 

I'm hoping I'll notice something small I missed and it'll work. 

 

30 minutes ago, TheDanzig said:

Tried those, still hangs up with getting the wireguard up and running. Switched back to OpenVPN and it starts flawlessly and quickly. I'll give wireguard another visit in a few days probably. 

I'm hoping I'll notice something small I missed and it'll work. 

 

What version of unraid are you on?

6.8 or later is required for Wireguard

Edited October 30, 20205 yr by tjb_altf4

1 hour ago, tjb_altf4 said:

What version of unraid are you on?

6.8 or later is required for Wireguard

6.8.3

This post is to help someone who is having this error: 'UnicodeDecodeError'>: 'utf-8' codec can't decode byte 0xe3 in position 11

I was having this error and could not access web interface any more. It sometimes went away and then comeback.

Recently It was not going away. I updated the docker and used the more recent PIA nextgen servers. no fix.

Then I looked at the state folder, where the torrent files are stored. I move all files away and then deluge started fine, but without any torrents. then I added the torrents, and still nothing. then added the torrents.state file, and torrents started checking/ verifying, but after some time, the error 'UnicodeDecodeError' came again. so I wonder if it is related to this!?.

So then I removed my older torrents, I had about 150 and only keep 50, waited for the checking, and now is working fine so far...

So if you have this error, look into the state folder.

Need help here...

I recently updated to the newer version of DelugeVPN and im having issues downloading anything.

 

I have my download directory set to mnt/user/DelugeDownloads

and in deluge i have it set to /data

I have also updated the openvpn files to match the nextgen config files.

 

I have multiple torrents with active connections to peers but nothing is downloading.

 

Before upgrading, this was working... What am i missing?

On 10/19/2020 at 7:29 PM, binhex said:

you are using the old legacy network for pia, this is broken (pia issue), please move over to next-gen, see Q19 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

That was the issue, thanks for your help!

Seeing an issue from time to time where vpn connection is active, but nothing downloads or uploads.

I actually saw it in the last few days of using legacy + deluge 1.3, and assumed the old servers were cactus.

 

The only fix is to restart the container then everything comes to life again.

Is this something others are seeing? Maybe something happening in the PIA network?

Thanks for everyone that contributed to this thread recently with the PIA issues and feedback.  I just changed my files over to France with the nextgen file from PIA.  I had to restart unraid, but I can now get into the webUI and the speeds are great.  I have not changed any other setting.

 

 

Hi all - first time poster here, just setting up my first unRaid system but i have previously used Plex / sonarr / radarr and transmission to run a similar NAS/server on a ras pi 4. I am having download speed issues with binhex-DelugeVPN using PIA connected to the Sweden server next gen.

 

My ISP is Virgin Media here in the UK and i get 200Mb download speeds but on DelugeVPN i'm unable to download any faster than 1.2MB/s. I have had this problem previous with Virgin Media / PIA and the fix is to disable uTP however this is not an option on DelugeVPN.

I see that i should be able to install the plugin ITconfig (https://github.com/ratanakvlun/deluge-ltconfig/releases) but when i try to install this it pops up with "uploading plugin" for a split second and then disappears it never seems to get anywhere. Has anyone had any luck with this? I'm wondering if its just a compatibility issue with the binhex version of DelugeVPN. Any help much appreciated.

32 minutes ago, bigdan1190 said:

I see that i should be able to install the plugin ITconfig (https://github.com/ratanakvlun/deluge-ltconfig/releases) but when i try to install this it pops up with "uploading plugin" for a split second and then disappears it never seems to get anywhere. Has anyone had any luck with this

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

Hi All,

 

Im having trouble that i simply can't get past.

 

My container updates overnight, I'm running the latest. Now, the VPN won't connect. the logs are giving me an AUTH_FAILED error.

 

I've checked the FAQ and gone through the suggestions there. i've changed my password, i've tried other endpoints, i've moved over to the next-gen configs (copied the certs an the new ovpn files over), i've removed all special chars from the password, i've forced an update to ensure i was on the latest build (i was/am), etc. etc. It simply will not connect via deluge. I can however connect to the end point via a desktop openVPN client so i know the end point is up and my creds are fine. 

 

I've attached a screen shot from the log file - Im not picky at this point as to which server i connect to.. i just can't for the life of me work out whats going on???? any suggestions, idea's? anything?

 

PLEASE HELP

 

 

 

 

1 hour ago, bigdan1190 said:

Hi all - first time poster here, just setting up my first unRaid system but i have previously used Plex / sonarr / radarr and transmission to run a similar NAS/server on a ras pi 4. I am having download speed issues with binhex-DelugeVPN using PIA connected to the Sweden server next gen.

 

My ISP is Virgin Media here in the UK and i get 200Mb download speeds but on DelugeVPN i'm unable to download any faster than 1.2MB/s. I have had this problem previous with Virgin Media / PIA and the fix is to disable uTP however this is not an option on DelugeVPN.

I see that i should be able to install the plugin ITconfig (https://github.com/ratanakvlun/deluge-ltconfig/releases) but when i try to install this it pops up with "uploading plugin" for a split second and then disappears it never seems to get anywhere. Has anyone had any luck with this? I'm wondering if its just a compatibility issue with the binhex version of DelugeVPN. Any help much appreciated.

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 😂

11 minutes ago, DAVIDP said:

Hi All,

 

Im having trouble that i simply can't get past.

 

My container updates overnight, I'm running the latest. Now, the VPN won't connect. the logs are giving me an AUTH_FAILED error.

 

I've checked the FAQ and gone through the suggestions there. i've changed my password, i've tried other endpoints, i've moved over to the next-gen configs (copied the certs an the new ovpn files over), i've removed all special chars from the password, i've forced an update to ensure i was on the latest build (i was/am), etc. etc. It simply will not connect via deluge. I can however connect to the end point via a desktop openVPN client so i know the end point is up and my creds are fine. 

 

I've attached a screen shot from the log file - Im not picky at this point as to which server i connect to.. i just can't for the life of me work out whats going on???? any suggestions, idea's? anything?

 

PLEASE HELP

 

 

 

 

Are you using your main PIA log in credentials or the SOCKS/Proxy generated credentials?

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, 20205 yr by 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...