[Support] binhex - DelugeVPN


8725 posts in this topic Last Reply

Recommended Posts

So in the past week I've been experiencing intermittent connection issues (as in; no internet access at all) locally everything kept working fine.

Eventually after a bit of mucking about, it turns out to be this container. Stopping the binhex-delugevpn container and everything suddenly started working as intended, I did not have this issue with the normal deluge container.

 

So it's mostly dns server related (though I'm no professional so my diagnosis might be wrong) But using the default NAME_SERVERS causes major latency issues, pinging the dns server would show a delay of on average 200-300ms with about 50% of the pings simply timing out. stopping the container immediatly resolves that. Regardless of which vpn server (I'm using PIA) or name server I use the issue persist.

 

Now I've changed the Name server to an opendns one that I know for sure isn't being used by anything in the house and as a workaround this is okay-ish, however it appears download speeds are still suffering heavily because of this, it also occasionaly breaks tracking torrents (until I restart the container).

 

Any clues as to why this might happen or how to resolve this? First week I had this running there were no issues at all, and I had the normal deluge container running fine for months so besides the vpn all settings are identical. 

 

edit nvm, my workaround did not work, running the container completely wrecks my internet connection to  the point it's unusable

Edited by Capronicus
additional info
Link to post
  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

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 n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

4 hours ago, binhex said:

I know you didn't speak directly to my post, but I looked at that and saw similar errors in my logs... turns out it was the VPN provider (PIA)... Not sure what's going on, but the CA locations don't appear to support port forwarding anymore, and their france location must be having locations. Resorted to de-berlin, and everything is back online now.

Link to post
15 hours ago, NVS1 said:

I know you didn't speak directly to my post, but I looked at that and saw similar errors in my logs... turns out it was the VPN provider (PIA)... Not sure what's going on, but the CA locations don't appear to support port forwarding anymore, and their france location must be having locations. Resorted to de-berlin, and everything is back online now.

I'm using CA Vancouver just now & don't have any issues with port forwarding. I think with PIA doing their 'next gen' changes, as a few people here have mentioned, it's causing some instability over a bunch of locations.

Link to post

I'm very new to Deluge and this may be better on a Deluge support board, but I'll ask here first before I go create an account somewhere else.

 

I've attempted to install the YaRSS2 plugin by changing the version number in the file name as was indicated could be done here. I click the "Install Plugin" button, click "Browse" then select the YaRSS2-2.1.4-py3.8.egg file and it shows me this:

image.png.5a2bf421000b48045bbba6f6ddfed8d8.png

I click the Install button, the dialog box goes away, but I don't see any sign that the plugin has been installed. i.e., it's not in the list of plugin in the plugin page of Preferences. I even restarted the container and it's still not there.

 

Am I doing this wrong, or is something not working correctly?

Link to post
46 minutes ago, FreeMan said:

I'm very new to Deluge and this may be better on a Deluge support board, but I'll ask here first before I go create an account somewhere else.

 

I've attempted to install the YaRSS2 plugin by changing the version number in the file name as was indicated could be done here. I click the "Install Plugin" button, click "Browse" then select the YaRSS2-2.1.4-py3.8.egg file and it shows me this:

image.png.5a2bf421000b48045bbba6f6ddfed8d8.png

I click the Install button, the dialog box goes away, but I don't see any sign that the plugin has been installed. i.e., it's not in the list of plugin in the plugin page of Preferences. I even restarted the container and it's still not there.

 

Am I doing this wrong, or is something not working correctly?

You could try placing the egg file directly into the plugin folder and restarting the container. Sometimes works.

Link to post
2 hours ago, wgstarks said:

You could try placing the egg file directly into the plugin folder and restarting the container. Sometimes works.

Winner, winner, chicken dinner!

 

Thanks!

 

There's a file of some sort called [object FileList] located in the plugins directory, which isn't surprising, that's exactly what was shown in the "install plugin" dialog box. Must be a bug somewhere in the install routine.

Link to post

So I've been having issues with torrents entirely stalling out in Deluge, and I finally went digging in the logs to find this initial issue:

2020-09-06 14:00:49,695 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

 

So I went and added the other PIA servers that support port-forwarding and reloaded the container. The attached log file is the result, and the WebUI won't even load at this point. I'm a bit stumped as to what a fix for it would be. 

 

 

 

delugevpn_log_9_6_2020.txt

Link to post
9 hours ago, untraceablez said:

So I've been having issues with torrents entirely stalling out in Deluge, and I finally went digging in the logs to find this initial issue:


2020-09-06 14:00:49,695 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

 

So I went and added the other PIA servers that support port-forwarding and reloaded the container. The attached log file is the result, and the WebUI won't even load at this point. I'm a bit stumped as to what a fix for it would be. 

 

 

 

delugevpn_log_9_6_2020.txt 10.2 kB · 1 download

'swiss.privacy.network' is from pia next-gen network, this does not support port forwarding at present, if you want to use next-gen and dont mind the lower speeds due to no port forwarding then set 'STRICT_PORT_FORWARD' to 'no'.

Link to post

Another user with PIA issues here, I suspect. I haven't been able to log into the webui for a while and it would appear the VPN is the issue since turning off VPN solves the problem. Is there anything else I have to do to change the PIA server loacation than changing the openVPN file in the appdata folder? I have tried several different locations now that supposedly supports port-forwarding, but my webUI remains dead while the VPN is turned on.

Link to post
1 minute ago, WellThen said:

Another user with PIA issues here, I suspect. I haven't been able to log into the webui for a while and it would appear the VPN is the issue since turning off VPN solves the problem. Is there anything else I have to do to change the PIA server loacation than changing the openVPN file in the appdata folder? I have tried several different locations now that supposedly supports port-forwarding, but my webUI remains dead while the VPN is turned on.

CA Vancouver is working for me.

Link to post
2 hours ago, iLaurens said:

Having the same issues with port forwarding. Any western-european servers that have kept their port-forwarding abilities? I tried Swiss, french and german servers with no luck...

I don't think anything except Canada works now. We should all complain to PIA.

Link to post
On 9/5/2020 at 7:14 AM, xxDeadbolt said:

I'm using CA Vancouver just now & don't have any issues with port forwarding. I think with PIA doing their 'next gen' changes, as a few people here have mentioned, it's causing some instability over a bunch of locations.

I had to switch to CA Vancouver as well. CA Toronto and CA Montreal weren't allowing the strict port forwarding to be enabled and work properly. I think you're correct that the upgrades are causing issues at the moment. But hopefully they'll figure it out soon.

Link to post
52 minutes ago, govperm said:

I had to switch to CA Vancouver as well. CA Toronto and CA Montreal weren't allowing the strict port forwarding to be enabled and work properly. I think you're correct that the upgrades are causing issues at the moment. But hopefully they'll figure it out soon.

I spoke with customer support at PIA, they are now aware that port forwarding on CA Montreal and CA Toronto does not work with their open vpn files. They said it does work with their PIA clients, but they need to figure something out with the open vpn config or something. For now CA Vancouver works, but who knows for how long. Hopefully they fix Toronto and Montreal before they switch to Nextgen for Vancouver and mess it up.

Link to post
4 minutes ago, chris_netsmart said:

is there any update on the openVPN files

you can switch to next-gen but there is no port forwarding available for native openvpn clients, your best bet for now is sadly to set STRICT_PORT_FORWARDING to no and connect to any endpoint you want, obviously speeds will be slow.

Link to post

Running binhex-delugevpn docker

I am trying to use pia for vpn and it will not connect to webUI

In the logs i see, [warn] Exit code '52' from curl != 0 or no response body received

I have tried multiple vpn sites all on the approved port forwarding list and get the same response every time.

Any help would be appreciated.

 

ErrorWarningSystemArrayLogin



2020-09-08 15:11:33,378 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-09-08 15:11:33,390 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-09-08 15:11:33,393 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-09-08 15:11:33,394 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-09-08 15:11:33,394 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.4
192.168.1.0/24 via 172.17.0.1 dev eth0

2020-09-08 15:11:33,394 DEBG 'start-script' stdout output:
--------------------

2020-09-08 15:11:33,423 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-09-08 15:11:33,424 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2020-09-08 15:11:33,424 DEBG 'start-script' stdout output:
--------------------

2020-09-08 15:11:33,425 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-09-08 15:11:33,439 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:33 2020 WARNING: file 'credentials.conf' is group or others accessible
Tue Sep 8 15:11:33 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
Tue Sep 8 15:11:33 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-09-08 15:11:33,439 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:33 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
[info] OpenVPN started

2020-09-08 15:11:33,441 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:33 2020 CRL: loaded 1 CRLs from file [[INLINE]]

2020-09-08 15:11:33,441 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:33 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]89.36.76.120:1198
Tue Sep 8 15:11:33 2020 UDP link local: (not bound)
Tue Sep 8 15:11:33 2020 UDP link remote: [AF_INET]89.36.76.120:1198

2020-09-08 15:11:34,141 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:34 2020 [berlin408] Peer Connection Initiated with [AF_INET]89.36.76.120:1198

2020-09-08 15:11:35,371 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:35 2020 TUN/TAP device tun0 opened
Tue Sep 8 15:11:35 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-09-08 15:11:35,372 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:35 2020 /usr/bin/ip addr add dev tun0 10.7.112.2/24 broadcast 10.7.112.255

2020-09-08 15:11:35,373 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:35 2020 /root/openvpnup.sh tun0 1500 1558 10.7.112.2 255.255.255.0 init

2020-09-08 15:11:35,376 DEBG 'start-script' stdout output:
Tue Sep 8 15:11:35 2020 Initialization Sequence Completed

2020-09-08 15:11:35,488 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'de-berlin.privacy.network' is port forward enabled...

2020-09-08 15:11:47,551 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'de-berlin.privacy.network' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
[info] Please consider switching to one of the endpoints shown below

2020-09-08 15:11:47,551 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-08 15:12:58,260 DEBG 'start-script' stdout output:
[warn] Exit code '7' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

2020-09-08 15:13:08,496 DEBG 'start-script' stdout output:
[warn] Exit code '7' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

2020-09-08 15:13:18,733 DEBG 'start-script' stdout output:
[warn] Exit code '7' from curl != 0 or no response body received
[info] 10 retries left
[info] Retrying in 10 secs...

2020-09-08 15:13:53,769 WARN received SIGTERM indicating exit request
2020-09-08 15:13:53,769 DEBG killing watchdog-script (pid 180) with signal SIGTERM
2020-09-08 15:13:53,769 INFO waiting for start-script, watchdog-script to die
2020-09-08 15:13:54,653 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22676490288432 for <Subprocess at 22676490287760 with name watchdog-script in state STOPPING> (stdout)>
2020-09-08 15:13:54,653 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22676490450016 for <Subprocess at 22676490287760 with name watchdog-script in state STOPPING> (stderr)>
2020-09-08 15:13:54,653 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-09-08 15:13:54,653 DEBG received SIGCHLD indicating a child quit
2020-09-08 15:13:54,653 DEBG killing start-script (pid 179) with signal SIGTERM
2020-09-08 15:13:55,654 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22676490674624 for <Subprocess at 22676490677264 with name start-script in state STOPPING> (stdout)>
2020-09-08 15:13:55,654 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22676490287664 for <Subprocess at 22676490677264 with name start-script in state STOPPING> (stderr)>
2020-09-08 15:13:55,654 INFO stopped: start-script (terminated by SIGTERM)
2020-09-08 15:13:55,655 DEBG received SIGCHLD indicating a child quit
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-09-08 15:13:56.403633 [info] System information Linux 3489c0a725ec 4.19.107-Unraid #1 SMP Sun Mar 8 14:34:03 CDT 2020 x86_64 GNU/Linux
2020-09-08 15:13:56.425512 [info] OS_ARCH defined as 'x86-64'
2020-09-08 15:13:56.448695 [info] PUID defined as '99'
2020-09-08 15:13:56.472561 [info] PGID defined as '100'
2020-09-08 15:13:56.525943 [info] UMASK defined as '000'
2020-09-08 15:13:56.548963 [info] Permissions already set for volume mappings
2020-09-08 15:13:56.573922 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-09-08 15:13:56.596418 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-09-08 15:13:56.619128 [info] VPN_ENABLED defined as 'yes'
2020-09-08 15:13:56.644610 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Vancouver.ovpn
2020-09-08 15:13:56.683316 [info] VPN remote line defined as 'remote ca-vancouver.privateinternetaccess.com 1198'
2020-09-08 15:13:56.705066 [info] VPN_REMOTE defined as 'ca-vancouver.privateinternetaccess.com'
2020-09-08 15:13:56.726913 [info] VPN_PORT defined as '1198'
2020-09-08 15:13:56.753977 [info] VPN_PROTOCOL defined as 'udp'
2020-09-08 15:13:56.777606 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-09-08 15:13:56.798482 [info] VPN_PROV defined as 'pia'
2020-09-08 15:13:56.820757 [info] LAN_NETWORK defined as '192.168.1.0/24'
2020-09-08 15:13:56.842698 [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-09-08 15:13:56.862946 [info] VPN_USER defined as 'p2309891'
2020-09-08 15:13:56.884132 [info] VPN_PASS defined as 'Steve123!'
2020-09-08 15:13:56.907635 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-09-08 15:13:56.934658 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-09-08 15:13:56.958738 [info] ENABLE_PRIVOXY defined as 'no'
2020-09-08 15:13:56.982486 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-09-08 15:13:57.006267 [info] Deleting files in /tmp (non recursive)...
2020-09-08 15:13:57.032735 [info] Starting Supervisor...
2020-09-08 15:13:57,184 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-09-08 15:13:57,184 INFO Set uid to user 0 succeeded
2020-09-08 15:13:57,185 INFO supervisord started with pid 6
2020-09-08 15:13:58,187 INFO spawned: 'start-script' with pid 172
2020-09-08 15:13:58,188 INFO spawned: 'watchdog-script' with pid 173
2020-09-08 15:13:58,188 INFO reaped unknown pid 7 (exit status 0)
2020-09-08 15:13:58,193 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-09-08 15:13:58,193 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-09-08 15:13:58,193 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-09-08 15:13:58,203 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2020-09-08 15:13:58,238 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-09-08 15:13:58,240 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-09-08 15:13:58,242 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-09-08 15:13:58,245 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-09-08 15:13:58,247 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-09-08 15:13:58,249 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-09-08 15:13:58,252 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-09-08 15:13:58,254 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-09-08 15:13:58,256 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-09-08 15:13:58,420 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2020-09-08 15:13:58,421 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.107-Unraid

2020-09-08 15:13:58,421 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2020-09-08 15:13:58,422 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2020-09-08 15:13:58,422 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-09-08 15:13:58,435 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-09-08 15:13:58,437 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-09-08 15:13:58,438 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-09-08 15:13:58,439 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.4
192.168.1.0/24 via 172.17.0.1 dev eth0

2020-09-08 15:13:58,439 DEBG 'start-script' stdout output:
--------------------

2020-09-08 15:13:58,466 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-09-08 15:13:58,467 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2020-09-08 15:13:58,468 DEBG 'start-script' stdout output:
--------------------

2020-09-08 15:13:58,468 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-09-08 15:13:58,473 DEBG 'start-script' stdout output:
Tue Sep 8 15:13:58 2020 WARNING: file 'credentials.conf' is group or others accessible
Tue Sep 8 15:13:58 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
Tue Sep 8 15:13:58 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-09-08 15:13:58,473 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-09-08 15:13:58,473 DEBG 'start-script' stdout output:
Tue Sep 8 15:13:58 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-09-08 15:13:58,474 DEBG 'start-script' stdout output:
Tue Sep 8 15:13:58 2020 CRL: loaded 1 CRLs from file [[INLINE]]

2020-09-08 15:13:58,475 DEBG 'start-script' stdout output:
Tue Sep 8 15:13:58 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]172.83.40.111:1198
Tue Sep 8 15:13:58 2020 UDP link local: (not bound)
Tue Sep 8 15:13:58 2020 UDP link remote: [AF_INET]172.83.40.111:1198

2020-09-08 15:13:58,631 DEBG 'start-script' stdout output:
Tue Sep 8 15:13:58 2020 [592ca2b34a8b9c9ff3a0fbc7fb729cae] Peer Connection Initiated with [AF_INET]172.83.40.111:1198

2020-09-08 15:14:05,071 DEBG 'start-script' stdout output:
Tue Sep 8 15:14:05 2020 TUN/TAP device tun0 opened
Tue Sep 8 15:14:05 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-09-08 15:14:05,072 DEBG 'start-script' stdout output:
Tue Sep 8 15:14:05 2020 /usr/bin/ip addr add dev tun0 local 10.20.11.6 peer 10.20.11.5

2020-09-08 15:14:05,073 DEBG 'start-script' stdout output:
Tue Sep 8 15:14:05 2020 /root/openvpnup.sh tun0 1500 1558 10.20.11.6 10.20.11.5 init

2020-09-08 15:14:05,077 DEBG 'start-script' stdout output:
Tue Sep 8 15:14:05 2020 Initialization Sequence Completed

2020-09-08 15:14:05,186 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-vancouver.privateinternetaccess.com' is port forward enabled...

2020-09-08 15:14:06,104 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-09-08 15:14:06,104 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-08 15:14:06,639 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

2020-09-08 15:14:16,901 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

2020-09-08 15:14:27,165 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 10 retries left
[info] Retrying in 10 secs...

2020-09-08 15:14:47,243 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 9 retries left
[info] Retrying in 10 secs...

2020-09-08 15:15:07,320 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 8 retries left
[info] Retrying in 10 secs...

2020-09-08 15:15:27,397 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 7 retries left
[info] Retrying in 10 secs...

2020-09-08 15:15:38,085 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 54511

2020-09-08 15:15:38,123 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-09-08 15:15:38,474 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.83.40.111

2020-09-08 15:15:38,572 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.20.11.6 different, marking for reconfigure

2020-09-08 15:15:38,574 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-09-08 15:15:38,577 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-09-08 15:15:38,577 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 54511 different, marking for reconfigure

2020-09-08 15:15:38,577 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-09-08 15:15:38,847 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has an undefined value
[info] Deluge key 'listen_interface' will have a new value '10.20.11.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-09-08 15:15:39,119 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has an undefined value
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-09-08 15:15:39,283 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '184de89885694ff7bdfe449db324f560'
[info] Deluge key 'default_daemon' will have a new value '184de89885694ff7bdfe449db324f560'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-09-08 15:15:39,559 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-09-08 15:15:39,770 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-09-08 15:15:42,695 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-09-08 15:15:45,395 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (54511, 54511)
Configuration value successfully updated.

2020-09-08 15:15:45,395 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (54511, 54511)
Configuration value successfully updated.

2020-09-08 15:15:48,135 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-09-08 15:15:48,135 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

Logs attached.

Log for_ binhex-delugevpn.html

Edited by whitewraith
Link to post

Please assist, how can I determine if this is a port forwarding issue or a DelugeVPN issue. Unable to download files using DelugeVPN with PIA and server, remote ca-toronto.privateinternetaccess.com port 1198. Torrents stuck in state downloading. See attached deluge logs for more info. deluge-web.logdeluged.log

 

Attempts to resolve this issue

 

Changed from CA Toronto to DE Berlin. Issue(s) remains.

 

Attempt to enable port forwarding - tldr; Issue remains:

 

Enabled port forwarding on archlinux docker container running OpenVPN as directed by PIA support portal. OS details are as follows, note all commands are ran from within the DelugeVPN docker container.

 

sh-5.0# cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux
sh-5.0# uname -r
4.19.107-Unraid

 

Results of running `port_forwarding.sh` are as follows.

 

sh-5.0# chmod +x port_forwarding.sh
sh-5.0# ./port_forwarding.sh
Loading port forward assignment information...
Port forwarding is already activated on this connection, has expired, or you are not connected to a PIA region that supports port forwarding

 

After running the above command the docker container was restarted, none of the downloads became active. I am attempting to download ubuntu and torguard's check my torrent ipaddress.

 

Edited by kingJahfy
clarification
Link to post
2 minutes ago, kingJahfy said:

Please assist, how can I determine if this is a port forwarding issue or a DelugeVPN issue

If you read just a few post above yours on this same page you will see that there are lots of reports of OpenVPN endpoints no longer working with port forwarding via PIA.

 

The last reported endpoint that did work is CA Vancouver.  That may or may not still work.  FYI - Just switched to to CA Vancouver and did a couple of downloads and it worked for me.

Link to post
Quote

The last reported endpoint that did work is CA Vancouver.  That may or may not still work.  FYI - Just switched to to CA Vancouver and did a couple of downloads and it worked for me.

 

Unfortunately for me, now the UI doesn't work.... with CA Vancover 😦

 

2020-09-08 15:51:26,782 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-09-08 15:51:26,782 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-09-08 15:51:47,137 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

 

Stating the obvious --- This frustrating, PIA is very popular and i've had little issue with the service until now

Edited by kingJahfy
add quote
Link to post
1 hour ago, kingJahfy said:

Changed from CA Toronto to DE Berlin. Issue(s) remains.

 

5 minutes ago, kingJahfy said:

Unfortunately for me - no luck with CA Vancover....😦

......

Stating the obvious --- This frustrating, PIA is very popular and i've had little issue with the service until now

 

I am not denying you are having issues as seen in your log, but I mentioned previously, and it still remains, CA Toronto works for me.  Also not denying there are issues with PIA for others in this forum.  I just wanted to confirm that some endpoints people have issues with work for other people.  Not sure why.

Edited by Burizado
Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.