[Support] binhex - DelugeVPN

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images (25th Feb 2021) i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image. You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on

Recommended by binhex

Ryanoc3ros

June 28, 20233 yr

Found the solution on reddit. Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab.

NordVPN authentication issues - Solution

Recommended by binhex

April 11, 20215 yr

Hello there! I've used the image for quite some time and it worked like a charm. But after Docker Desktop (Mac OS) update to 3.3.0 (62916) the logs are like this:

2021-04-11 21:34:34,395 DEBG 'start-script' stdout output:
--------------------
2021-04-11 21:34:34,399 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
2021-04-11 21:34:34,411 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible
2021-04-11 21:34:34,418 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard
2021-04-11 21:34:34,420 DEBG 'start-script' stderr output:
Error: Unknown device type.
2021-04-11 21:34:34,423 DEBG 'start-script' stderr output:
Unable to access interface: Protocol not supported
2021-04-11 21:34:34,423 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2021-04-11 21:34:34,427 DEBG 'start-script' stderr output:
Cannot find device "wg0"
2021-04-11 21:34:34,428 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

The "config/wireguard/wg0.conf" is like that:

[Interface]
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'
Address = ???.???.???.???/24
DNS = ???.???.???.???, ???.???.???.???
PrivateKey = ???

[Peer]
PublicKey = ???
PresharedKey = ???
AllowedIPs = 0.0.0.0/0
Endpoint = ???.???.???.???:???
PersistentKeepalive = 25

(of course there are real values instead of ???)

Any ideas on how to fix that or what to look for in the logs?

Quote

Replies 10.8k
Views 2.4m
Created 10 yr10 yr
Last Reply Jun 18Jun 18

Popular Days

Posted Images

April 12, 20215 yr

7 hours ago, booppy said:

Hello there! I've used the image for quite some time and it worked like a charm. But after Docker Desktop (Mac OS) update to 3.3.0 (62916) the logs are like this:



2021-04-11 21:34:34,395 DEBG 'start-script' stdout output:
--------------------
2021-04-11 21:34:34,399 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
2021-04-11 21:34:34,411 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible
2021-04-11 21:34:34,418 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard
2021-04-11 21:34:34,420 DEBG 'start-script' stderr output:
Error: Unknown device type.
2021-04-11 21:34:34,423 DEBG 'start-script' stderr output:
Unable to access interface: Protocol not supported
2021-04-11 21:34:34,423 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2021-04-11 21:34:34,427 DEBG 'start-script' stderr output:
Cannot find device "wg0"
2021-04-11 21:34:34,428 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

The "config/wireguard/wg0.conf" is like that:



[Interface]
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'
Address = ???.???.???.???/24
DNS = ???.???.???.???, ???.???.???.???
PrivateKey = ???

[Peer]
PublicKey = ???
PresharedKey = ???
AllowedIPs = 0.0.0.0/0
Endpoint = ???.???.???.???:???
PersistentKeepalive = 25

(of course there are real values instead of ???)

Any ideas on how to fix that or what to look for in the logs?

Exact same thing happened to me.

Quote

April 12, 20215 yr

Author

17 hours ago, TBoneStaek said:

I just upgraded Unraid from 6.8.3 to 6.9.1.

That's the only change I've made and now delugevpn gui won't load and the log is showing a few errors which I've searched through here but can't seem to find a solution that applies to me.

2021-04-11 11:15:37,734 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0

2021-04-11 11:15:37,931 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 1, column 7

2021-04-11 11:15:37,932 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://199.36.223.130/authv3/generateToken'
[info] Retrying in 10 secs...

attached is my salted debug log

supervisord (salted).txt 60 kB · 1 download

try a different endpoint, looks like a pia outage for ca-montreal.

Quote

April 12, 20215 yr

Hello since the last Unraid update.

I have an password error on webUI.

How is possible ?? My password is correct.

I use Bitwarden for this.

How change admin password without web UI?

(sorry for my english)

image.png.35115d8f888e28420aa5a25c39950fad.png

Quote

April 12, 20215 yr

30 minutes ago, thymon said:

Hello since the last Unraid update.

I have an password error on webUI.

How is possible ?? My password is correct.

I use Bitwarden for this.

How change admin password without web UI?

(sorry for my english)

Have you tried the default password incase it reset in the update? deluge is the default

Quote

April 12, 20215 yr

For those with the startup script errors:

I just redownloaded a configuration file from PIA website, deleted the old one, and restarted Deluge and it seems to have fixed it. It looks to me that they renamed it to exclude the "nextgen-" from the file name. I don't know if that matters.

Quote

April 12, 20215 yr

8 minutes ago, LTM said:

For those with the startup script errors:

I just redownloaded a configuration file from PIA website, deleted the old one, and restarted Deluge and it seems to have fixed it. It looks to me that they renamed it to exclude the "nextgen-" from the file name. I don't know if that matters.

Do you have a link to the download? I am assuming this is only if you are using the ovpn files and not using Wireguard?

Quote

April 12, 20215 yr

Quote

Updated Unraid to 6.9.2 this morning and this container will no longer work correctly.




2021-04-12 09:33:16,216 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0


2021-04-12 09:33:16,450 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 1, column 7


2021-04-12 09:33:16,451 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://154.3.40.3/authv3/generateToken'
[info] Retrying in 10 secs...

I am using Wireguard+PIA.

Any ideas?

EDIT: Looks to be an issue with Canadian endpoints? Tried ca-montreal.privacy.network and ca-toronto.privacy.network with the same error, but Bahamas (bahamas.privacy.network) seems to work fine.

Oddly, I can connect to both of the above Canadian endpoints just fine using my Windows client.

Edited April 12, 20215 yr by dcarpenter85

Quote

April 12, 20215 yr

33 minutes ago, dcarpenter85 said:

EDIT: Looks to be an issue with Canadian endpoints? Tried ca-montreal.privacy.network and ca-toronto.privacy.network with the same error, but Bahamas (bahamas.privacy.network) seems to work fine.

Oddly, I can connect to both of the above Canadian endpoints just fine using my Windows client.

I've been okay with Toronto. Strange...

Quote

April 12, 20215 yr

1 hour ago, TBoneStaek said:

I've been okay with Toronto. Strange...

Interesting. Out of curiousity, are you on Unraid 6.9.2 and using Wireguard?

Quote

April 12, 20215 yr

2 minutes ago, dcarpenter85 said:

Interesting. Out of curiousity, are you on Unraid 6.9.2 and using Wireguard?

I just upgraded to 6.9.1 from 6.8.3 a few days ago. And yes, wireguard.

Quote

April 12, 20215 yr

7 minutes ago, TBoneStaek said:

I just upgraded to 6.9.1 from 6.8.3 a few days ago. And yes, wireguard.

But not 6.9.2 yet? My problems didn't start until I went from 6.9.1 to 6.9.2

Quote

April 12, 20215 yr

1 minute ago, dcarpenter85 said:

But not 6.9.2 yet? My problems didn't start until I went from 6.9.1 to 6.9.2

Nope, not 6.9.2. I contemplated doing that today to see if that fixed it but... I imagine not. Must have been a coincidence though, again, I have Toronto working for me. Very strange.

Quote

April 12, 20215 yr

I seem to have an issue where my container is using the wrong IP to generate a PIA token?

2021-04-12 19:37:51,550 DEBG 'start-script' stdout output:
parse error: Invalid numeric literal at line 1, column 7


2021-04-12 19:37:51,551 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'

2021-04-12 19:37:51,551 DEBG 'start-script' stdout output:
[info] 12 retries left
[info] Retrying in 10 secs...

Quote

April 12, 20215 yr

On 4/10/2021 at 6:43 PM, Keek Uras said:

Hello. I can't seem to make Deluge check my files. The files are there, the paths are correct but instead of using the existing files, it starts downloading them again. Any suggestions on how I might remedy this? Thank you in advance.

Deluge doesn't really keep track of files, it just downloads what is sent to it. You may want to look at whatever you have sending downloads to Deluge. It sounds like it is losing track of the file once it is complete and it is thinking it failed and reinitiates the download again.

Quote

April 13, 20215 yr

On 4/12/2021 at 9:34 AM, dcarpenter85 said:

EDIT: Looks to be an issue with Canadian endpoints? Tried ca-montreal.privacy.network and ca-toronto.privacy.network with the same error, but Bahamas (bahamas.privacy.network) seems to work fine.

Oddly, I can connect to both of the above Canadian endpoints just fine using my Windows client.

I was having issues connecting to Canadian endpoints as well, same error in the logs. Was able to connect to the Bahamas just fine. Not sure which version I was running before (should have checked) but I added :lastest to the containers Repository field and after pulling down the image I'm able to connect to Toronto again.

Quote

April 13, 20215 yr

Also having the same issue with this container used with wireguard/pia after upgrade to 6.9.2

For those that managed to fix it which file did you download and where did you put it ?

Quote

April 13, 20215 yr

2 hours ago, WishmastR said:

Also having the same issue with this container used with wireguard/pia after upgrade to 6.9.2

For those that managed to fix it which file did you download and where did you put it ?

For me it was simply adding " :latest " to the end of the repository line. I'm also using wireguard/pia connecting to Toronto.

Quote

April 14, 20215 yr

I switched to Toronto just fine but was originally using Montreal. Anybody using PIA wireguard Montreal successfully now?

Quote

April 14, 20215 yr

Hi,

I'm having trouble access the webui. I've not long updated to 6.9.2 and I WAS using Pia with OPENVPN but for some reason France stopped working so I thought now is a good time as any to change over to wireguard

So i removed the old template and thought i'd start again. Think I have everything setup correctly (assume i don't need to add the new VPN_CLIENT variable as its already on the new template.

I've added :latest to the repository as suggested above. and the only errors i'm getting on the logs are:

2021-04-14 11:04:21,597 DEBG 'start-script' stderr output:
parse error: Invalid literal at line 4, column 0

Warning: `/config/wireguard/wg0.conf' is world accessible

2021-04-14 11:04:32,861 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

Any ideas what i'm doing wrong?

Quote

April 14, 20215 yr

I just tryied to access my delugeVPN and I am getting ' This site can’t be reached '

I am still on very 6.9.1 for Unraid but deluge is update on version.

I haven't done anything to it, but this morning when I log on. I discovered that I was not able to WebGui onit it, but when go into the console I see that I am getting the right VPN IP address

I have tried agin running the following command to see if this is the issue

Quote

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go

echo "/sbin/modprobe iptable_mangle" >> /boot/config/go

which it is not,

I also turn off the VPN within deluge and then I was able to access the WEBGUI

but once I turn it back on, it fails

I have check my username and password and this are all OK.

as I have a VPN on my pfsense I also turned this off - and this made no differant.

I have posted my log file to see if anything can see the issue, as this is becoming very frustrating as it looks like that after a few weeks deluge fails over and then I have to re-troubleshoot it

I look forward to your reply.

Quote

ErrorWarningSystemArrayLogin

2021-04-14 11:26:36.972070 [info] VPN remote port(s) defined as '1198,'
2021-04-14 11:26:36.991906 [info] VPN remote protcol(s) defined as 'udp,'
2021-04-14 11:26:37.017213 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-04-14 11:26:37.041326 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-04-14 11:26:37.069501 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-04-14 11:26:37.098090 [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'
2021-04-14 11:26:37.124051 [info] VPN_USER defined as '**********'
2021-04-14 11:26:37.148817 [info] VPN_PASS defined as '**********'
2021-04-14 11:26:37.175055 [info] STRICT_PORT_FORWARD defined as 'yes'
2021-04-14 11:26:37.201882 [info] ENABLE_PRIVOXY defined as 'yes'
2021-04-14 11:26:37.232949 [warn] ADDITIONAL_PORTS DEPRECATED, please rename env var to 'VPN_INPUT_PORTS'
2021-04-14 11:26:37.256049 [info] ADDITIONAL_PORTS defined as '8989,9117,7878,8118,8112'
2021-04-14 11:26:37.279141 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-04-14 11:26:37.306411 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-04-14 11:26:37.334214 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-04-14 11:26:37.357955 [info] Starting Supervisor...
2021-04-14 11:27:00,766 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-04-14 11:27:00,766 INFO Set uid to user 0 succeeded
2021-04-14 11:27:00,828 INFO supervisord started with pid 6
2021-04-14 11:27:01,830 INFO spawned: 'shutdown-script' with pid 181
2021-04-14 11:27:01,832 INFO spawned: 'start-script' with pid 182
2021-04-14 11:27:01,987 INFO spawned: 'watchdog-script' with pid 192
2021-04-14 11:27:01,988 INFO reaped unknown pid 7 (exit status 0)
2021-04-14 11:27:01,988 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2021-04-14 11:27:01,988 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-14 11:27:01,988 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-14 11:27:01,988 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-14 11:27:02,043 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-04-14 11:27:02,048 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-04-14 11:27:02,054 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-04-14 11:27:02,058 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-04-14 11:27:02,063 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-04-14 11:27:02,067 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-04-14 11:27:02,074 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-04-14 11:27:02,079 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-04-14 11:27:07,870 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2021-04-14 11:27:07,871 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/5.10.21-Unraid

2021-04-14 11:27:07,871 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2021-04-14 11:27:07,888 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2021-04-14 11:27:07,888 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2021-04-14 11:27:08,281 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2021-04-14 11:27:08,336 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2021-04-14 11:27:08,343 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-04-14 11:27:08,343 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-04-14 11:27:08,345 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.5
192.168.1.0/24 via 172.17.0.1 dev eth0

2021-04-14 11:27:08,345 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.5
local 172.17.0.5 dev eth0 table local proto kernel scope host src 172.17.0.5
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.5

2021-04-14 11:27:08,345 DEBG 'start-script' stdout output:
--------------------

2021-04-14 11:27:08,350 DEBG 'start-script' stdout output:
iptable_mangle 16384 0
ip_tables 28672 3 iptable_filter,iptable_nat,iptable_mangle

2021-04-14 11:27:08,350 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2021-04-14 11:27:08,363 DEBG 'start-script' stderr output:
RTNETLINK answers: File exists

2021-04-14 11:27:10,902 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-04-14 11:27:10,905 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 -s 143.244.57.142/32 -i eth0 -j ACCEPT
-A INPUT -s 143.244.57.141/32 -i eth0 -j ACCEPT
-A INPUT -s 143.244.57.132/32 -i eth0 -j ACCEPT
-A INPUT -s 143.244.57.131/32 -i eth0 -j ACCEPT
-A INPUT -s 143.244.57.151/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8989 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8989 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9117 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9117 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 7878 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 7878 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8118 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -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 -m tcp --dport 8118 -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 -d 143.244.57.142/32 -o eth0 -j ACCEPT
-A OUTPUT -d 143.244.57.141/32 -o eth0 -j ACCEPT
-A OUTPUT -d 143.244.57.132/32 -o eth0 -j ACCEPT
-A OUTPUT -d 143.244.57.131/32 -o eth0 -j ACCEPT
-A OUTPUT -d 143.244.57.151/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8989 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8989 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9117 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9117 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 7878 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 7878 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8118 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -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 -m tcp --sport 8118 -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

2021-04-14 11:27:10,906 DEBG 'start-script' stdout output:
--------------------

2021-04-14 11:27:10,907 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2021-04-14 11:27:13,096 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

2021-04-14 11:27:13,097 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 WARNING: file 'credentials.conf' is group or others accessible

2021-04-14 11:27:13 OpenVPN 2.5.1 [git:makepkg/f186691b32e68362+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 24 2021
2021-04-14 11:27:13 library versions: OpenSSL 1.1.1j 16 Feb 2021, LZO 2.10

2021-04-14 11:27:13,097 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-04-14 11:27:13,097 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----

2021-04-14 11:27:13,097 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 TCP/UDP: Preserving recently used remote address: [AF_INET]143.244.57.142:1198
2021-04-14 11:27:13 UDP link local: (not bound)
2021-04-14 11:27:13 UDP link remote: [AF_INET]143.244.57.142:1198

2021-04-14 11:27:13,292 DEBG 'start-script' stdout output:
2021-04-14 11:27:13 [paris406] Peer Connection Initiated with [AF_INET]143.244.57.142:1198

2021-04-14 11:27:14,390 DEBG 'start-script' stdout output:
2021-04-14 11:27:14 TUN/TAP device tun0 opened
2021-04-14 11:27:14 net_iface_mtu_set: mtu 1500 for tun0
2021-04-14 11:27:14 net_iface_up: set tun0 up

2021-04-14 11:27:14,390 DEBG 'start-script' stdout output:
2021-04-14 11:27:14 net_addr_v4_add: 10.13.112.239/24 dev tun0
2021-04-14 11:27:14 /root/openvpnup.sh tun0 1500 1553 10.13.112.239 255.255.255.0 init

2021-04-14 11:27:14,393 DEBG 'start-script' stdout output:
2021-04-14 11:27:14 Initialization Sequence Completed

2021-04-14 11:27:16,606 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2021-04-14 11:27:16,948 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 143.244.57.142

2021-04-14 11:27:16,966 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2021-04-14 11:27:16,966 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'france.privacy.network' is port forward enabled...

2021-04-14 11:27:21,692 DEBG 'start-script' stdout output:
[info] PIA endpoint 'france.privacy.network' is in the list of endpoints that support port forwarding

2021-04-14 11:27:21,692 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2021-04-14 11:27:21,692 DEBG 'start-script' stdout output:
[info] al.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] ad.privacy.network
[info] austria.privacy.network
[info] brussels.privacy.network
[info] ba.privacy.network
[info] sofia.privacy.network
[info] czech.privacy.network
[info] denmark.privacy.network
[info] ee.privacy.network
[info] fi.privacy.network
[info] france.privacy.network
[info] de-berlin.privacy.network
[info] de-frankfurt.privacy.network
[info] gr.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] hungary.privacy.network
[info] is.privacy.network
[info] ireland.privacy.network
[info] man.privacy.network
[info] italy.privacy.network
[info] lv.privacy.network
[info] liechtenstein.privacy.network
[info] lt.privacy.network
[info] lu.privacy.network
[info] mk.privacy.network
[info] malta.privacy.network
[info] md.privacy.network
[info] monaco.privacy.network
[info] montenegro.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] nl-amsterdam.privacy.network
[info] no.privacy.network
[info] poland.privacy.network
[info] pt.privacy.network
[info] ro.privacy.network
[info] rs.privacy.network
[info] sk.privacy.network
[info] spain.privacy.network
[info] sweden.privacy.network
[info] swiss.privacy.network
[info] ua.privacy.network
[info] uk-manchester.privacy.network
[info] uk-southampton.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] uk-2.privacy.network
[info] uk-london.privacy.network
[info] bahamas.privacy.network
[info] ca-ontario.privacy.network
[info] ca-toronto.privacy.network
[info] ca-montreal.privacy.network
[info] ca-vancouver.privacy.network
[info] greenland.privacy.network
[info] mexico.privacy.network
[info] panama.privacy.network
[info] ar.privacy.network
[info] br.privacy.network
[info] venezuela.privacy.network
[info] yerevan.privacy.network
[info] bangladesh.privacy.network
[info] cambodia.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] china.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] israel.privacy.network
[info] japan-2.privacy.network
[info] japan.privacy.network
[info] kazakhstan.privacy.network
[info] macau.privacy.network
[info] mongolia.privacy.network
[info] philippines.privacy.network
[info] qatar.privacy.network
[info] saudiarabia.privacy.network
[info] sg.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] srilanka.privacy.network
[info] taiwan.privacy.network
[info] tr.privacy.network
[info] ae.privacy.network
[info] vietnam.privacy.network
[info] aus-melbourne.privacy.network
[info] au-sydney.privacy.network
[info] aus-perth.privacy.network
[info] nz.privacy.network
[info] dz.privacy.network
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network

2021-04-14 11:27:21,693 DEBG 'start-script' stdout output:
[info] za.privacy.network

2021-04-14 11:29:26,134 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'
[info] 12 retries left
[info] Retrying in 10 secs...

2021-04-14 11:32:38,645 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'
[info] 11 retries left
[info] Retrying in 10 secs...

Quote

April 14, 20215 yr

Author

52 minutes ago, zapp8rannigan said:

I've not long updated to 6.9.2 and I WAS using Pia with OPENVPN but for some reason France stopped working

13 minutes ago, chris_netsmart said:

I am still on very 6.9.1 for Unraid but deluge is update on version.

firstly can i just mention that issues with this docker are NOT related to the version of unraid, there are no known compatibility issues with 6.9.2 or any other version for that matter., the issues people are seeing here are 100% related to the VPN provider.

ao both of you guys quoted above are using france endpoint i would suspect its down, you need to switch to another endpoint, the list of available endpoints that support port forwarding is shown in the log '/config/supervisord.log'

Quote

April 14, 20215 yr

56 minutes ago, binhex said:

firstly can i just mention that issues with this docker are NOT related to the version of unraid, there are no known compatibility issues with 6.9.2 or any other version for that matter., the issues people are seeing here are 100% related to the VPN provider.

ao both of you guys quoted above are using france endpoint i would suspect its down, you need to switch to another endpoint, the list of available endpoints that support port forwarding is shown in the log '/config/supervisord.log'

I'm not using OpenVPN anymore, i've switched to wireguard so no longer using france, according to the wg0.conf I'm using nl-amsterdam.privacy.network

Quote

April 14, 20215 yr

1 hour ago, binhex said:

firstly can i just mention that issues with this docker are NOT related to the version of unraid, there are no known compatibility issues with 6.9.2 or any other version for that matter., the issues people are seeing here are 100% related to the VPN provider.

ao both of you guys quoted above are using france endpoint i would suspect its down, you need to switch to another endpoint, the list of available endpoints that support port forwarding is shown in the log '/config/supervisord.log'

Hi @binhex I didn't want to employ it was your fault, but or your dockers - as I feel that you are doing a fantastic job, as I mentioned I looked around and I was not able to find anything and yes I will be changing my VPN France to something else and re-testing.

and also ' I didn't realise ' that the docker is complete independent from unraid so I will no long post my unraid version.

UPDATE: I just tried England and Israel and both are doing the same thing. I will leave it for a few days to see if it sorts itself out.

Edited April 14, 20215 yr by chris_netsmart

Quote

April 14, 20215 yr

Author

15 minutes ago, zapp8rannigan said:

I'm not using OpenVPN anymore, i've switched to wireguard so no longer using france, according to the wg0.conf I'm using nl-amsterdam.privacy.network

netherlands also had issues a while ago and its possible they still have intermittent issues, try changing to sweden.

Quote

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.

Followers

Go to topic listing

Replies 10.8k
Views 2.4m
Created 10 yr10 yr
Last Reply Jun 18Jun 18

[Support] binhex - DelugeVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

Ryanoc3ros

shaunsund

Dad_Rage

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

Ryanoc3ros

shaunsund

Dad_Rage

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)