I think I might have everything working now with Mullvad/Wireguard although I don't seem to be seeding in Deluge but I can't tell if it's a problem or not. Might need to double check my Mullvad port setup. No obvious errors at least. IPleak.net tests look good, just no IPv6.

 

My extra parameters are: --privileged=true --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl="net.ipv4.conf.all.src_valid_mark=1" 

 

My wg0 is completely vanilla. I just dragged and dropped the Mullvad one in and didn't edit it at all. It's got the DNS line and it looks like the docker parameters take the ",::0/0" off of the AllowedIPs line automatically, as far as I can tell.

 

But like I said, I don't really know what I'm doing.

 

EDIT: I think seeding is working fine now. It was a router issue. Forgot change the port forwarding.

Edited October 14, 20205 yr by Herman Terds
router issue

10 hours ago, Herman Terds said:

My wg0 is completely vanilla. I just dragged and dropped the Mullvad one in and didn't edit it at all. It's got the DNS line and it looks like the docker parameters take the ",::0/0" off of the AllowedIPs line automatically, as far as I can tell.

the reason you didnt need to do any edits is cos im now doing them for you :-), if you check your wg0.conf file you will see it has all ipv6 ip and port removed, it also has the up and down scripts added in.

 

10 hours ago, Herman Terds said:

My extra parameters are: --privileged=true --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl="net.ipv4.conf.all.src_valid_mark=1" 

just to nail this so i know EXACTLY which parameters are required, can you please try removing the parameter:-

--sysctl net.ipv6.conf.all.disable_ipv6=0

as i dont THINK thats required, but i dont know for sure as i cannot test (not mullvad user).

 

10 hours ago, Herman Terds said:

EDIT: I think seeding is working fine now. It was a router issue. Forgot change the port forwarding.

port forwarding should NOT be done on your router!, it is not required and is a potential cause of ip leakage, so please remove the port.

Ah. Well, like I said, no idea what I'm doing.

 

OK so my parameters are now: --privileged=true --sysctl="net.ipv4.conf.all.src_valid_mark=1" and I just removed the port forwarding rule. Everything seems to be working. IPleak looks fine. I think seeding is working, downloaded ubuntu to check and it looks like I'm uploading.

 

The reason I opened the ports before was because a tracker started throwing alerts that my ports were blocked. But it may have just been some lag from bringing Deluge up and down or I was still monkeying with Mullvad port settings. I've been up for 20 minutes or so now and although I'm not seeing any seeding with this particular tracker, I'm also not getting any blocked port messages either. Probably just zero peers to seed. 

Edited October 15, 20205 yr by Herman Terds

Anyone having issues with starting delugeVPN from inside UnRaid that is running it beside PIA?  Was working last evening, and now it's not.  Already tired turning port forwarding off within the docker properties and that does not work.  

16 minutes ago, JohnSracic said:

Anyone having issues with starting delugeVPN from inside UnRaid that is running it beside PIA?  Was working last evening, and now it's not.  Already tired turning port forwarding off within the docker properties and that does not work.  

Have you upgraded to the new servers w/ PIA?

5 minutes ago, chesh said:

Have you upgraded to the new servers w/ PIA?

 

Have not.  Are there instructions someplace to follow to do this?  

9 minutes ago, JohnSracic said:

 

Have not.  Are there instructions someplace to follow to do this?  

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

See Q19.

11 minutes ago, wgstarks said:

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

See Q19.

 

Thank you!  I grabbed the files from https://www.privateinternetaccess.com/helpdesk/kb/articles/where-can-i-find-your-ovpn-files and updated them on the server and my initial test seems to have worked.  Would be nice if they allowed port forwarding.  

 

Update:  It worked.

Edited October 15, 20205 yr by JohnSracic

31 minutes ago, JohnSracic said:

 Would be nice if they allowed port forwarding.  

They do. You just have to use the servers that support it.

I'm trying to move from OVPN to WireGuard and I'm running into a roadblock. Based on my logs I believe everything is starting properly, however, I cannot reach the webui. If I change 'wireguard' to 'openvpn' in the configuration I can reach the UI as expected. Any ideas?

docker run -d --name='binhex-delugevpn' --net='br0.10' --ip='192.168.10.15' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8112'='8112' -e 'TCP_PORT_58846'='58846' -e 'TCP_PORT_58946'='58946' -e 'UDP_PORT_58946'='58946' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxxxxxxxx' -e 'VPN_PASS'='xxxxxxxxxx' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='192.168.10.1/24' -e 'NAME_SERVERS'='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' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'ADDITIONAL_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/disks/unassigned/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

 

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

2020-10-15 23:56:08.672244 [info] System information Linux 843aa7a70558 5.7.8-Unraid #1 SMP Thu Jul 9 11:10:03 PDT 2020 x86_64 GNU/Linux
2020-10-15 23:56:08.707765 [info] OS_ARCH defined as 'x86-64'
2020-10-15 23:56:08.755273 [info] PUID defined as '99'
2020-10-15 23:56:09.103466 [info] PGID defined as '100'
2020-10-15 23:56:09.722302 [info] UMASK defined as '000'
2020-10-15 23:56:09.741216 [info] Permissions already set for volume mappings
2020-10-15 23:56:09.841045 [info] Deleting files in /tmp (non recursive)...
2020-10-15 23:56:09.884032 [info] VPN_ENABLED defined as 'yes'
2020-10-15 23:56:09.906021 [info] VPN_CLIENT defined as 'wireguard'
2020-10-15 23:56:09.925092 [info] VPN_PROV defined as 'pia'
2020-10-15 23:56:14.841527 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2020-10-15 23:56:14.875796 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network'
2020-10-15 23:56:14.934189 [info] VPN_REMOTE_PORT defined as '1337'
2020-10-15 23:56:14.953274 [info] VPN_DEVICE_TYPE defined as 'wg0'
2020-10-15 23:56:14.971720 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2020-10-15 23:56:14.995647 [info] LAN_NETWORK defined as '192.168.10.1/24'
2020-10-15 23:56:15.019885 [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'
2020-10-15 23:56:15.039629 [info] VPN_USER defined as 'xxxxxxxx'
2020-10-15 23:56:15.063950 [info] VPN_PASS defined as 'xxxxxxxx'
2020-10-15 23:56:15.088321 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-10-15 23:56:15.108386 [info] ENABLE_PRIVOXY defined as 'no'
2020-10-15 23:56:15.127681 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-10-15 23:56:15.153110 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-10-15 23:56:15.174085 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-10-15 23:56:15.199612 [info] Starting Supervisor...
2020-10-15 23:56:17,177 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-10-15 23:56:17,177 INFO Set uid to user 0 succeeded
2020-10-15 23:56:17,207 INFO supervisord started with pid 6
2020-10-15 23:56:18,209 INFO spawned: 'start-script' with pid 157
2020-10-15 23:56:18,210 INFO spawned: 'watchdog-script' with pid 158
2020-10-15 23:56:18,210 INFO reaped unknown pid 7 (exit status 0)
2020-10-15 23:56:18,226 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-10-15 23:56:18,227 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-10-15 23:56:18,227 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-10-15 23:56:18,229 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-10-15 23:56:18,231 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-10-15 23:56:18,234 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-10-15 23:56:18,237 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-10-15 23:56:18,239 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-10-15 23:56:18,242 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-10-15 23:56:18,245 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-10-15 23:56:18,247 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-10-15 23:56:19,487 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0


2020-10-15 23:56:20,125 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2020-10-15 23:56:20,642 DEBG 'start-script' stdout output:
[info] Default route for container is 192.168.10.1

2020-10-15 23:56:20,654 DEBG 'start-script' stdout output:
[info] Docker network defined as 192.168.10.0/24

2020-10-15 23:56:20,657 DEBG 'start-script' stdout output:
[info] Adding 192.168.10.1/24 as route via docker eth0

2020-10-15 23:56:20,657 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.


2020-10-15 23:56:20,658 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-10-15 23:56:20,658 DEBG 'start-script' stdout output:
default via 192.168.10.1 dev eth0
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.15

2020-10-15 23:56:20,658 DEBG 'start-script' stdout output:
--------------------

2020-10-15 23:56:20,661 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 28672 8 iptable_filter,iptable_raw,iptable_nat,iptable_mangle

2020-10-15 23:56:20,661 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-10-15 23:56:20,749 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-10-15 23:56:20,750 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 192.168.10.0/24 -d 192.168.10.0/24 -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.10.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 192.168.10.0/24 -d 192.168.10.0/24 -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.10.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-15 23:56:20,751 DEBG 'start-script' stdout output:
--------------------

2020-10-15 23:56:20,753 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2020-10-15 23:56:20,793 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2020-10-15 23:56:20,798 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2020-10-15 23:56:20,799 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2020-10-15 23:56:20,807 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.25.245.109/32 dev wg0

2020-10-15 23:56:20,812 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2020-10-15 23:56:20,838 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2020-10-15 23:56:20,838 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2020-10-15 23:56:20,839 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2020-10-15 23:56:20,840 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2020-10-15 23:56:20,842 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2020-10-15 23:56:20,851 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2020-10-15 23:56:20,871 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2020-10-15 23:56:22,128 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-10-15 23:56:37,514 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 212.102.34.182

2020-10-15 23:56:37,515 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2020-10-15 23:56:37,515 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2020-10-15 23:56:37,516 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled...

2020-10-15 23:56:39,111 DEBG 'start-script' stdout output:
[info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding

2020-10-15 23:56:39,111 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2020-10-15 23:56:39,112 DEBG 'start-script' stdout output:
[info] al.privacy.network
[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-frankfurt.privacy.network
[info] de-berlin.privacy.network
[info] gr.privacy.network
[info] hungary.privacy.network

2020-10-15 23:56:39,112 DEBG 'start-script' stdout output:
[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
[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-london.privacy.network
[info] uk-southampton.privacy.network
[info] bahamas.privacy.network
[info] ca-vancouver.privacy.network
[info] ca-ontario.privacy.network
[info] ca-montreal.privacy.network
[info] ca-toronto.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] cambodia.privacy.network
[info] china.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] iran.privacy.network

2020-10-15 23:56:39,112 DEBG 'start-script' stdout output:
[info] israel.privacy.network
[info] japan.privacy.network
[info] kazakhstan.privacy.network
[info] philippines.privacy.network
[info] qatar.privacy.network
[info] saudiarabia.privacy.network
[info] sg.privacy.network
[info] srilanka.privacy.network
[info] taiwan.privacy.network
[info] tr.privacy.network
[info] ae.privacy.network
[info] vietnam.privacy.network
[info] aus-perth.privacy.network
[info] au-sydney.privacy.network
[info] aus-melbourne.privacy.network
[info] nz.privacy.network
[info] dz.privacy.network
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network
[info] za.privacy.network

2020-10-15 23:56:41,732 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '47146'

2020-10-15 23:56:42,196 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.25.245.109 different, marking for reconfigure

2020-10-15 23:56:42,261 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-10-15 23:56:42,263 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-10-15 23:56:42,263 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 47146 different, marking for reconfigure

2020-10-15 23:56:42,270 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-10-15 23:56:44,217 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.26.129.208'
[info] Deluge key 'listen_interface' will have a new value '10.25.245.109'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-10-15 23:56:44,374 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-10-15 23:56:44,501 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '9b89b378e26b43ed89a18c7b060d30de'
[info] Deluge key 'default_daemon' will have a new value '9b89b378e26b43ed89a18c7b060d30de'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-10-15 23:56:44,950 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-10-15 23:56:45,411 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-10-15 23:56:47,515 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-10-15 23:56:49,315 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (47146, 47146)
Configuration value successfully updated.

2020-10-15 23:56:51,151 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2020-10-15 23:56:51,152 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-10-15 23:56:51,152 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

3 hours ago, BrttClne22 said:

I'm trying to move from OVPN to WireGuard and I'm running into a roadblock. Based on my logs I believe everything is starting properly, however, I cannot reach the webui. If I change 'wireguard' to 'openvpn' in the configuration I can reach the UI as expected. Any ideas?

that is a successful start, your issue is misconfiguration, taken from your log above:-

2020-10-15 23:56:14.995647 [info] LAN_NETWORK defined as '192.168.10.1/24'

this is incorrect, see Q4 for how to configure this correctly:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi there,

I have had this running successfully for some time on my QNAP NAS, but I appear to be struggling with the change over to the new PIA servers.  I have added my usual server (France - but the new one!) to the openvpn folder, along with ca.rsa.2048.crt and crl.rsa.2048.pem, renaming the old .ovpn file.

 

Here is my docker-compose setup, which is just as it was before (except I have added VPN_CLIENT): 

https://hastebin.com/vorululusi.http

Here is my supervisord.log

https://hastebin.com/qozugovewa.yaml

The web interface comes up, it even starts downloading for a short time (4 or 5 seconds?) initially, but then it stops and I appear not to be connected to any peers.

 

The error I see in the log that might be relevant is: 

 

> ERROR: Linux route add command failed: external program exited with error status: 2

 

As I say, this had been working successfully for some time previously, but now appears to have issues with the new servers.

 

Any help appreciated,

 

Thanks!

 

23 minutes ago, jamesking said:

Hi there,

I have had this running successfully for some time on my QNAP NAS, but I appear to be struggling with the change over to the new PIA servers.  I have added my usual server (France - but the new one!) to the openvpn folder, along with ca.rsa.2048.crt and crl.rsa.2048.pem, renaming the old .ovpn file.

 

Here is my docker-compose setup, which is just as it was before (except I have added VPN_CLIENT): 

https://hastebin.com/vorululusi.http

Here is my supervisord.log

https://hastebin.com/qozugovewa.yaml

The web interface comes up, it even starts downloading for a short time (4 or 5 seconds?) initially, but then it stops and I appear not to be connected to any peers.

 

The error I see in the log that might be relevant is: 

 

> ERROR: Linux route add command failed: external program exited with error status: 2

 

As I say, this had been working successfully for some time previously, but now appears to have issues with the new servers.

 

Any help appreciated,

 

Thanks!

 

qnap issue, see Q13:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

44 minutes ago, binhex said:

qnap issue, see Q13:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you, this appeats to have worked.  The daemon_mgr.conf file was in folder /etc/

 

I did read the FAQ, but I initially didn't try that as I did not think I had changed anything with respect to using openvpn.  do you know why it might have recently occured?

 

EDIT - I guess this could correspond to a firmware update a couple of weeks ago, along with a reboot yesterday (due to a power cut), but it's not obvious from the FAQ when this problem first was introduced. :-)

 

Anyway, very grateful.

Edited October 16, 20205 yr by jamesking

6 minutes ago, jamesking said:

EDIT - I guess this could correspond to a firmware update

most probably.

Last night I updated to 2.0.4.dev38_g23a48dd01-2-12.  This seems version does not work for me.  I thought maybe it needed the next gen OVPN file but it still would not work.  Rolled back to 2.0.4.dev38_g23a48dd01-2-11 and all is working fine now.  Is this an issue with the update or am I missing something?

3 hours ago, jamesking said:

Hi there,

I have had this running successfully for some time on my QNAP NAS, but I appear to be struggling with the change over to the new PIA servers.  I have added my usual server (France - but the new one!) to the openvpn folder, along with ca.rsa.2048.crt and crl.rsa.2048.pem, renaming the old .ovpn file.

 

Here is my docker-compose setup, which is just as it was before (except I have added VPN_CLIENT): 

https://hastebin.com/vorululusi.http

Here is my supervisord.log

https://hastebin.com/qozugovewa.yaml

The web interface comes up, it even starts downloading for a short time (4 or 5 seconds?) initially, but then it stops and I appear not to be connected to any peers.

 

The error I see in the log that might be relevant is: 

 

> ERROR: Linux route add command failed: external program exited with error status: 2

 

As I say, this had been working successfully for some time previously, but now appears to have issues with the new servers.

 

Any help appreciated,

 

Thanks!

 

Did you install 2.0.4.dev38_g23a48dd01-2-12 version of the docker when it broke?  I just rolled back to 2.0.4.dev38_g23a48dd01-2-11 and all is well now.

1 hour ago, Gragorg said:

Did you install 2.0.4.dev38_g23a48dd01-2-12 version of the docker when it broke?  I just rolled back to 2.0.4.dev38_g23a48dd01-2-11 and all is well now.

Possibly, I just have it set to latest.

@jamesking @Gragorg jamesking got his issue resolved, it was to do with Qnap and their strange decision to kill openvpn process, as for your issue Gragorg, its impossible to say with the amount of detail you gave, as in none!, what exactly is your issue?, what vpn provider are you using?, are you an unraid user?, can you do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Hello,

Sonarr and Radarr stopped properly connecting to binhex-delugevpn and I tried to fix it without any success. I first suspected it was caused by PIA not allowing Switzerland.ovpn so I downloaded PIA's updated openvpn files. I replaced it with France. I also tried deleting perms.txt. Would appreciate some help. Thanks.

supervisord.log

10 minutes ago, elliotiscool said:

Would appreciate some help. Thanks.

You have posted your vpn username and password. I would recommend changing them with PIA.

11 minutes ago, elliotiscool said:

Hello,

Sonarr and Radarr stopped properly connecting to binhex-delugevpn and I tried to fix it without any success. I first suspected it was caused by PIA not allowing Switzerland.ovpn so I downloaded PIA's updated openvpn files. I replaced it with France. I also tried deleting perms.txt. Would appreciate some help. Thanks.

supervisord.log 4.98 MB · 1 download

Had the same issue yesterday. Here was what worked for me. Also, be sure to check port forwarding in the docker container. Unless you are using a location that allows it, you must select no. 

 

I grabbed the files from https://www.privateinternetaccess.com/helpdesk/kb/articles/where-can-i-find-your-ovpn-files and updated them on the server and my initial test seems to have worked. 

3 minutes ago, wgstarks said:

You have posted your vpn username and password. I would recommend changing them with PIA.

Thank you so much for pointing that out. Just changed them right now.

4 minutes ago, JohnSracic said:

Had the same issue yesterday. Here was what worked for me. Also, be sure to check port forwarding in the docker container. Unless you are using a location that allows it, you must select no. 

 

I grabbed the files from https://www.privateinternetaccess.com/helpdesk/kb/articles/where-can-i-find-your-ovpn-files and updated them on the server and my initial test seems to have worked. 

Thanks for pointing all of that out. I tried updating the files but it didn't work. Also, I was originally able to access deluge when I last checked a couple weeks ago. Something happened since then.

24 minutes ago, elliotiscool said:

Thanks for pointing all of that out. I tried updating the files but it didn't work. Also, I was originally able to access deluge when I last checked a couple weeks ago. Something happened since then.

Just to be sure, you downloaded the most up to date files, right?  I think the are dated August 11th.