search

binhex / arch-delugevpn

Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
GNU General Public License v3.0
696 stars 112 forks source link

Unable to successfully download PIA json to generate token from URL #203

Closed ihatecomputerswithapassion closed 3 years ago

ihatecomputerswithapassion commented 4 years ago

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

Got the latest image pulled and the following config:

docker run -d \
    --cap-add=NET_ADMIN \
    -p 8112:8112 \
    -p 8118:8118 \
    -p 58846:58846 \
    -p 58946:58946 \
    --name=delugevpn \
    -v /zfspool/containers/deluge/data:/data \
    -v /zfspool/containers/deluge/config:/config \
    -v /zfspool/containers/deluge/temp:/downloads \
    -v /zfspool/media/tv:/tv \
    -v /zfspool/media/movies:/movies \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_PROV=pia \
    -e STRICT_PORT_FORWARD=yes \
    -e ENABLE_PRIVOXY=no \
    -e LAN_NETWORK=192.168.0.0/16 \
    -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 DEBUG=false \
    -e PUID=1000 \
    -e PGID=1000 \
    binhex/arch-delugevpn

I only have one .ovpn file in /config/openvpn as well as the next-gen .crt and .pem file. Ovpn file has the following endpoints in it:

And they are all failing with the same error:

2020-09-29 18:04:00,636 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...,

Have I missed anything obvious?

ihatecomputerswithapassion commented 4 years ago

Actually, out of those endpoints, only de-berlin.privateinternetaccess.com worked, had it for some reason last in my list so I originally missed the attempt towards this endpoint.

The rest however throws that error.

mdewyer commented 4 years ago

Getting the same when I try A19.

But good find @ihatecomputerswithapassion, that's the only endpoint that works for me as well.

tom472 commented 4 years ago

I believe this is because de-berlin.privateinternetaccess.com is the only endpoint you have listed that supports port forwarding. Which from my understanding is necessary for arch-delugevpn to work as expected.

Take a look the the "list" provided in the answer to Q20 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Those are all of the PIA endpoints that support port forwarding, so you would want your .ovpn file to look like that and/or only contain endpoints from that list.

mdewyer commented 4 years ago

@tom472 Indeed, I had been working off of the wrong list. A20's list does work, thanks 👍

tom472 commented 4 years ago

@ihatecomputerswithapassion -- Does altering your list help/work for you?

ihatecomputerswithapassion commented 4 years ago

I thought all new endpoints in PIA next-gen supported port forward? Logs seems to tell me that as well:

[info] List of PIA endpoints that support port forwarding:-
2020-10-01 20:28:43,707 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
[info] is.privacy.network
[info] ireland.privacy.network
fo] man.privacy.network
[info] italy.privacy.network
[info] lv.privacy.network
2020-10-01 20:28:43,707 DEBG 'start-script' stdout output:
[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
2020-10-01 20:28:43,707 DEBG 'start-script' stdout output:
[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
2020-10-01 20:28:43,707 DEBG 'start-script' stdout output:
[info] ar.privacy.network
[info] br.privacy.network
[info] venezuela.privacy.network
[info] yerevan.privacy.network
[info] cambodia.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] iran.privacy.network
[info] israel.privacy.network
[info] japan.privacy.network
[info] kazakhstan.privacy.network
2020-10-01 20:28:43,707 DEBG 'start-script' stdout output:
[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
2020-10-01 20:28:43,707 DEBG 'start-script' stdout output:
[info] dz.privacy.network
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network

Anyhow, I change config to STRICT_PORT_FORWARD=no which allows me to connect to any of those endpoints.

Has anyone else noticed that Sonarr stops working with delugevpn after a few hours? It still adds downloads as scheduled but after a while, it stops importing completed downloads. A restart of delugevpn container resolves it. I'm starting to wonder if it's related to having the downloads from delugevpn going to a zfs pool which has cache.

wchan-ranelagh commented 4 years ago

I have this same issue where it cannot download the PIA json to generate token when I have STRICT_PORT_FORWARD=yes.

My .ovpn file looks like this (used the openvpn generator thing in PIA to get it, and i'm skipping the cert part here):

client
dev tun
proto udp
remote ca-vancouver.privacy.network 1198
remote ca-montreal.privacy.network 1198
resolv-retry infinite
nobind
persist-key
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server

auth-user-pass credentials.conf
compress
verb 1

The log looks like this:

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

2020-10-14 23:17:01.608890 [info] System information Linux delugevpn 4.14.24-qnap #1 SMP Fri Sep 25 05:17:36 CST 2020 x86_64 GNU/Linux
2020-10-14 23:17:01.740501 [info] OS_ARCH defined as 'x86-64'
2020-10-14 23:17:01.828722 [warn] PUID not defined (via -e PUID), defaulting to '99'
2020-10-14 23:17:01.925517 [warn] PGID not defined (via -e PGID), defaulting to '100'
2020-10-14 23:17:02.043450 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2020-10-14 23:17:02.097223 [info] Permissions already set for volume mappings
2020-10-14 23:17:02.202747 [info] Deleting files in /tmp (non recursive)...
2020-10-14 23:17:02.254365 [info] VPN_ENABLED defined as 'yes'
2020-10-14 23:17:02.301127 [info] VPN_CLIENT defined as 'openvpn'
2020-10-14 23:17:02.344378 [info] VPN_PROV defined as 'pia'
2020-10-14 23:17:02.850045 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/nextgen-ca_vancouver-aes-128-cbc-udp-dns.ovpn
2020-10-14 23:17:02.977973 [info] VPN remote server(s) defined as 'ca-vancouver.privacy.network,'
2020-10-14 23:17:03.017132 [info] VPN remote port(s) defined as '1198,'
2020-10-14 23:17:03.056118 [info] VPN remote protcol(s) defined as 'udp,'
2020-10-14 23:17:03.102705 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-10-14 23:17:03.148159 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-10-14 23:17:03.192236 [info] LAN_NETWORK defined as '192.168.2.0/24,192.168.100.0/24,192.168.200.0/24'
2020-10-14 23:17:03.235839 [info] NAME_SERVERS defined as '209.222.18.222,209.222.18.218'
2020-10-14 23:17:03.283552 [warn] VPN_USER not defined (via -e VPN_USER), assuming authentication via other method
2020-10-14 23:17:03.336775 [warn] VPN_PASS not defined (via -e VPN_PASS), assuming authentication via other method
2020-10-14 23:17:03.378815 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-10-14 23:17:03.421231 [warn] ENABLE_PRIVOXY not defined (via -e ENABLE_PRIVOXY), defaulting to 'no'
2020-10-14 23:17:03.463135 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-10-14 23:17:03.505624 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-10-14 23:17:03.547518 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-10-14 23:17:03.751275 [info] Starting Supervisor...
2020-10-14 23:17:04,263 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-10-14 23:17:04,266 INFO Set uid to user 0 succeeded
2020-10-14 23:17:04,271 INFO supervisord started with pid 8
2020-10-14 23:17:05,274 INFO spawned: 'start-script' with pid 181
2020-10-14 23:17:05,276 INFO spawned: 'watchdog-script' with pid 182
2020-10-14 23:17:05,276 INFO reaped unknown pid 9 (exit status 0)
2020-10-14 23:17:05,288 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

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

2020-10-14 23:17:05,393 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-10-14 23:17:25,541 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2020-10-14 23:17:25,555 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.24-qnap

2020-10-14 23:17:25,556 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2020-10-14 23:17:25,559 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2020-10-14 23:17:25,560 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2020-10-14 23:17:25,613 DEBG 'start-script' stdout output:
[info] Default route for container is 10.0.3.1

2020-10-14 23:17:25,636 DEBG 'start-script' stdout output:
[info] Docker network defined as    10.0.3.0/24

2020-10-14 23:17:25,642 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2020-10-14 23:17:25,650 DEBG 'start-script' stdout output:
[info] Adding 192.168.100.0/24 as route via docker eth0

2020-10-14 23:17:25,659 DEBG 'start-script' stdout output:
[info] Adding 192.168.200.0/24 as route via docker eth0

2020-10-14 23:17:25,661 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-10-14 23:17:25,664 DEBG 'start-script' stdout output:
default via 10.0.3.1 dev eth0 

2020-10-14 23:17:25,664 DEBG 'start-script' stdout output:
10.0.3.0/24 dev eth0 proto kernel scope link src 10.0.3.2 

2020-10-14 23:17:25,664 DEBG 'start-script' stdout output:
192.168.2.0/24 via 10.0.3.1 dev eth0 

2020-10-14 23:17:25,665 DEBG 'start-script' stdout output:
192.168.100.0/24 via 10.0.3.1 dev eth0 

2020-10-14 23:17:25,665 DEBG 'start-script' stdout output:
192.168.200.0/24 via 10.0.3.1 dev eth0 

2020-10-14 23:17:25,667 DEBG 'start-script' stdout output:
--------------------

2020-10-14 23:17:25,823 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-10-14 23:17:25,827 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 10.0.3.0/24 -d 10.0.3.0/24 -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.2.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.100.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.200.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 tun0 -j ACCEPT
-A OUTPUT -s 10.0.3.0/24 -d 10.0.3.0/24 -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.2.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -d 192.168.100.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -d 192.168.200.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 tun0 -j ACCEPT

2020-10-14 23:17:25,830 DEBG 'start-script' stdout output:
--------------------

2020-10-14 23:17:25,832 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2020-10-14 23:17:26,009 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:26 2020 WARNING: file 'credentials.conf' is group or others accessible
Wed Oct 14 23:17:26 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
Wed Oct 14 23:17:26 2020 library versions: OpenSSL 1.1.1h  22 Sep 2020, LZO 2.10

2020-10-14 23:17:26,010 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:26 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-10-14 23:17:26,011 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:26 2020 CRL: loaded 1 CRLs from file [[INLINE]]

2020-10-14 23:17:26,012 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:26 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]71.19.251.194:1198
Wed Oct 14 23:17:26 2020 UDP link local: (not bound)
Wed Oct 14 23:17:26 2020 UDP link remote: [AF_INET]71.19.251.194:1198

2020-10-14 23:17:26,200 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:26 2020 [vancouver402] Peer Connection Initiated with [AF_INET]71.19.251.194:1198

2020-10-14 23:17:27,254 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:27 2020 TUN/TAP device tun0 opened
Wed Oct 14 23:17:27 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-10-14 23:17:27,257 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:27 2020 /usr/bin/ip addr add dev tun0 10.14.112.2/24 broadcast 10.14.112.255

2020-10-14 23:17:27,258 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:27 2020 /root/openvpnup.sh tun0 1500 1558 10.14.112.2 255.255.255.0 init

2020-10-14 23:17:27,266 DEBG 'start-script' stdout output:
Wed Oct 14 23:17:27 2020 Initialization Sequence Completed

2020-10-14 23:17:29,444 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-10-14 23:17:34,720 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 71.19.251.194

2020-10-14 23:17:34,722 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2020-10-14 23:17:34,723 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-vancouver.privacy.network' is port forward enabled...

2020-10-14 23:17:35,853 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privacy.network' is in the list of endpoints that support port forwarding

2020-10-14 23:17:35,854 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[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
[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

2020-10-14 23:17:35,857 DEBG 'start-script' stdout output:
[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
[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-14 23:17:37,187 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...

2020-10-14 23:17:47,574 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...

If I set STRICT_PORT_FORWARD=no then it works fine but I do want to port forward if possible.

Any idea how it can be fixed?

Thanks!

TechplexEngineer commented 3 years ago

I just ran into this same problem, I was using the username/password combination from the SOCKS section on the PIA website. I found using my PIA website credentials I was able to get past the wireguard setup.

josjaf commented 3 years ago

I'm having a similiar issue on the rtorrent version of this. I haven't changed the endpoint in years....

kumy commented 3 years ago

Also getting this issue since yesterday

Edit: changing from ro.privacy.network to another server fixed my issue

Birdheezy commented 3 years ago

Also getting this issue since yesterday

Edit: changing from ro.privacy.network to another server fixed my issue

Could you elaborate? Thanks.

guipace commented 3 years ago

I just started having this issue as well. Has anyone been able to find a solution? Where can I go for instructions on how to re-configure PIA for delugevpn?

kumy commented 3 years ago

Also getting this issue since yesterday Edit: changing from ro.privacy.network to another server fixed my issue

Could you elaborate? Thanks.

I have edited my .ovpnfile and replaced the server by another one on the remote line

remote poland.privacy.network 1198
that1guy commented 3 years ago

I'm using Unraid + wireguard + PIA w/ the binhex-deluge container. I just solved my issue:

Modified appData/binhex-delugevpn/wireguard/wg0.conf

Changed from Endpoint = nl-amsterdam.privacy.network:1337 to Endpoint = poland.privacy.network:1198

Please let me know if there is another better endpoint.

vk2mpj commented 3 years ago

I'm using Unraid + wireguard + PIA w/ the binhex-deluge container. I just solved my issue:

Modified appData/binhex-delugevpn/wireguard/wg0.conf

Changed from Endpoint = nl-amsterdam.privacy.network:1337 to Endpoint = poland.privacy.network:1198

Please let me know if there is another better endpoint.

Same issue here started happening yesterday. It came good, but then fell over again. I have done the same workaround and all is working. Is this an issue with the container, or more likely to be an endpoint problem?

binhex commented 3 years ago

Try pulling down latest guys