[Support] binhex - DelugeVPN


Recommended Posts

any idea on this one @binhex? 😁

On 1/21/2020 at 8:58 PM, MammothJerk said:

I'm getting a lot of spam in my deluged.log with "Session status key not valid:" thanks to the stats plugin, it starts off during the plugin load as such:


20:19:41.892 [INFO    ][deluge_label.core             :78  ] *** Start Label plugin ***
20:19:41.907 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Label enabled...
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:41.914 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:41.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:42.214 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Stats enabled...
20:19:42.218 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Scheduler enabled...

then it starts repeating constantly after all my torrents have loaded


20:19:49.616 [INFO    ][deluge.core.torrentmanager    :885 ] Finished loading 2032 torrents in 0:00:03.984063
20:19:49.831 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:49.831 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.046 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:50.046 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:50.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:50.936 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
20:19:51.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:51.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:52.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:52.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:53.138 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.x.x.x:xxxxx
20:19:53.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:53.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:54.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:54.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:55.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:55.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:56.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:56.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:57.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:57.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:58.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:58.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:19:59.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:19:59.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:00.656 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx
20:20:00.749 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
20:20:00.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:00.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:01.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:01.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:02.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:02.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:03.484 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: xxx.xxx.x.xxx:xxxxx
20:20:03.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:03.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:04.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:04.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:05.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:05.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:06.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:06.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:07.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:07.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:08.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:08.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:09.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:09.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:10.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:10.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:11.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:11.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:12.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:12.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:13.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:13.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:14.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:14.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:15.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:15.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:16.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:16.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:17.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:17.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:18.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:18.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:19.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:19.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:20.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:20.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:21.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:21.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:22.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:22.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:23.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:23.916 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:24.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:20:24.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:20:25.915 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:55:09.531 [INFO    ][deluge.pluginmanagerbase      :250 ] Plugin Stats disabled...

-no errors for 5 minutes til i start it up again

20:59:43.245 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:43.245 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:43.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:43.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:43.510 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Stats enabled...
20:59:44.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:44.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:45.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:45.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:46.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:46.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:47.246 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:47.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections
20:59:48.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: dht_cache_nodes
20:59:48.247 [WARNING ][deluge.core.core              :656 ] Session status key not valid: num_connections

Disabling the stats plugin prevents this spam from occurring, and according to this topic on the deluge bug tracker i have to do something to the stats egg. the problem is i'm not sure where this egg is located in the unraid/docker/delugevpn installation. any pointers on what to do to fix this?

 

Edited by MammothJerk
Link to comment

Hi, I'm another QNAP user trying to get this package to work... I was able to tackle the daemon_conf issues raised earlier - and I can connect to PIA and it looks to be stable.  However, whenever I try to download a torrent I see peers connect, but then they drop after 5 seconds or so.  The only traffic I see is network overhead.  I feel like it is probably something in my setup somewhere, but I can't see where.

 

I'm using CA-Montreal, which I think supports port forwarding.  I'd really appreciate any help.

 

I have gone through this link and made sure I did everything there:

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

 

Supervisor.log:

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

2020-02-11 19:29:40.786334 [info] System information Linux 40ddf0579d56 4.14.24-qnap #1 SMP Fri Dec 6 11:32:47 CST 2019 x86_64 GNU/Linux
2020-02-11 19:29:40.892961 [info] PUID defined as '0'
2020-02-11 19:29:41.009574 [info] PGID defined as '0'
2020-02-11 19:29:41.378818 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2020-02-11 19:29:41.508641 [info] Permissions already set for volume mappings
2020-02-11 19:29:41.648921 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2020-02-11 19:29:41.741220 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2020-02-11 19:29:41.834308 [info] VPN_ENABLED defined as 'yes'
2020-02-11 19:29:41.938699 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Montreal.ovpn
2020-02-11 19:29:42.153039 [info] VPN remote line defined as 'remote ca-montreal.privateinternetaccess.com 1198'
2020-02-11 19:29:42.254781 [info] VPN_REMOTE defined as 'ca-montreal.privateinternetaccess.com'
2020-02-11 19:29:42.363284 [info] VPN_PORT defined as '1198'
2020-02-11 19:29:42.479173 [info] VPN_PROTOCOL defined as 'udp'
2020-02-11 19:29:42.593731 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-02-11 19:29:42.686322 [info] VPN_PROV defined as 'pia'
2020-02-11 19:29:42.777204 [info] LAN_NETWORK defined as '192.168.0.0/24'
2020-02-11 19:29:42.869337 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to name servers defined in readme.md
2020-02-11 19:29:42.960482 [info] VPN_USER defined as ''
2020-02-11 19:29:43.053043 [info] VPN_PASS defined as ''
2020-02-11 19:29:43.144605 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-02-11 19:29:43.235445 [info] STRICT_PORT_FORWARD defined as 'YES'
2020-02-11 19:29:43.327747 [warn] ENABLE_PRIVOXY not defined (via -e ENABLE_PRIVOXY), defaulting to 'no'
2020-02-11 19:29:43.472356 [info] Deleting files in /tmp (non recursive)...
2020-02-11 19:29:43.567638 [info] Starting Supervisor...
2020-02-11 19:29:44,210 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-02-11 19:29:44,211 INFO Set uid to user 0 succeeded
2020-02-11 19:29:44,220 INFO supervisord started with pid 8
2020-02-11 19:29:45,224 INFO spawned: 'start-script' with pid 163
2020-02-11 19:29:45,228 INFO spawned: 'watchdog-script' with pid 164
2020-02-11 19:29:45,229 INFO reaped unknown pid 9
2020-02-11 19:29:45,247 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-02-11 19:29:45,247 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-11 19:29:45,247 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-11 19:29:45,419 DEBG 'start-script' stdout output:
[info] Default route for container is 10.0.3.1

2020-02-11 19:29:45,431 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-02-11 19:29:45,442 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-02-11 19:29:45,454 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-02-11 19:29:45,468 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-02-11 19:29:45,478 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-02-11 19:29:45,489 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-02-11 19:29:45,500 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-02-11 19:29:45,509 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-02-11 19:29:45,629 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2020-02-11 19:29:45,633 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.24-qnap

2020-02-11 19:29:45,636 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2020-02-11 19:29:45,639 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2020-02-11 19:29:45,641 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-02-11 19:29:45,720 DEBG 'start-script' stdout output:
[info] Docker network defined as    10.0.3.0/24

2020-02-11 19:29:45,731 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2020-02-11 19:29:45,735 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-02-11 19:29:45,738 DEBG 'start-script' stdout output:
default via 10.0.3.1 dev eth0 
10.0.3.0/24 dev eth0 proto kernel scope link src 10.0.3.2 
192.168.0.0/24 via 10.0.3.1 dev eth0 

2020-02-11 19:29:45,739 DEBG 'start-script' stdout output:
--------------------

2020-02-11 19:29:45,882 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-02-11 19:29:45,885 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.0.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.0.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-02-11 19:29:45,889 DEBG 'start-script' stdout output:
--------------------

2020-02-11 19:29:45,893 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-02-11 19:29:45,907 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:45 2020 WARNING: file 'credentials.conf' is group or others accessible
Tue Feb 11 19:29:45 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan  3 2020
Tue Feb 11 19:29:45 2020 library versions: OpenSSL 1.1.1d  10 Sep 2019, LZO 2.10

2020-02-11 19:29:45,909 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-02-11 19:29:45,924 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:45 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-02-11 19:29:45,928 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:45 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.152:1198
Tue Feb 11 19:29:45 2020 UDP link local: (not bound)
Tue Feb 11 19:29:45 2020 UDP link remote: [AF_INET]199.229.249.152:1198

2020-02-11 19:29:46,301 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:46 2020 [06c7d7a2a99775b068106fd6379327f7] Peer Connection Initiated with [AF_INET]199.229.249.152:1198

2020-02-11 19:29:47,622 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:47 2020 TUN/TAP device tun0 opened
Tue Feb 11 19:29:47 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-02-11 19:29:47,625 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:47 2020 /usr/bin/ip addr add dev tun0 local 10.30.11.6 peer 10.30.11.5

2020-02-11 19:29:47,629 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:47 2020 /root/openvpnup.sh tun0 1500 1558 10.30.11.6 10.30.11.5 init

2020-02-11 19:29:47,649 DEBG 'start-script' stdout output:
Tue Feb 11 19:29:47 2020 Initialization Sequence Completed

2020-02-11 19:29:47,787 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled...

2020-02-11 19:29:47,799 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2020-02-11 19:29:48,655 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2020-02-11 19:29:48,871 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-02-11 19:29:48,871 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2020-02-11 19:29:48,872 DEBG 'start-script' stdout output:
[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] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com

2020-02-11 19:29:48,872 DEBG 'start-script' stdout output:
[info] Attempting to get dynamically assigned port...

2020-02-11 19:29:48,890 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=1c3a9cb50585793078223832ad2c4a3440f36c46f0b3f4e69cf109170d37dcf9...

2020-02-11 19:29:49,514 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=1c3a9cb50585793078223832ad2c4a3440f36c46f0b3f4e69cf109170d37dcf9, response code 200

2020-02-11 19:29:49,634 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 39838

2020-02-11 19:29:49,637 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-02-11 19:29:49,827 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '216.58.206.4'

2020-02-11 19:29:49,832 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-02-11 19:29:50,284 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 199.229.249.152

2020-02-11 19:29:50,326 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.30.11.6 different, marking for reconfigure

2020-02-11 19:29:50,336 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-02-11 19:29:50,353 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-02-11 19:29:50,355 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 39838 different, marking for reconfigure

2020-02-11 19:29:50,357 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-02-11 19:29:51,605 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.3.10.6'
[info] Deluge key 'listen_interface' will have a new value '10.30.11.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-02-11 19:29:52,309 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-02-11 19:29:53,012 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'e1bd94b2a5e84de7b6d6b6cae0ca4f2b'
[info] Deluge key 'default_daemon' will have a new value 'e1bd94b2a5e84de7b6d6b6cae0ca4f2b'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-02-11 19:29:54,172 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-02-11 19:29:54,755 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-02-11 19:29:55,755 DEBG 'watchdog-script' stderr output:
Unable to initialize gettext/locale!

2020-02-11 19:29:55,756 DEBG 'watchdog-script' stderr output:
'ngettext'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation
    builtins.__dict__['_n'] = builtins.__dict__['ngettext']
KeyError: 'ngettext'

2020-02-11 19:30:05,825 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-02-11 19:30:07,067 DEBG 'watchdog-script' stderr output:
Unable to initialize gettext/locale!

2020-02-11 19:30:07,068 DEBG 'watchdog-script' stderr output:
'ngettext'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation
    builtins.__dict__['_n'] = builtins.__dict__['ngettext']
KeyError: 'ngettext'

2020-02-11 19:30:16,023 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (39838, 39838)
Configuration value successfully updated.

2020-02-11 19:30:17,280 DEBG 'watchdog-script' stderr output:
Unable to initialize gettext/locale!

2020-02-11 19:30:17,323 DEBG 'watchdog-script' stderr output:
'ngettext'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation
    builtins.__dict__['_n'] = builtins.__dict__['ngettext']
KeyError: 'ngettext'

2020-02-11 19:30:26,776 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-02-11 19:30:26,777 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-02-11 19:30:26,777 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2020-02-11 19:30:27,756 DEBG 'watchdog-script' stderr output:
Unable to initialize gettext/locale!

2020-02-11 19:30:27,757 DEBG 'watchdog-script' stderr output:
'ngettext'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation
    builtins.__dict__['_n'] = builtins.__dict__['ngettext']
KeyError: 'ngettext'

2020-02-11 19:32:40,894 WARN received SIGTERM indicating exit request
2020-02-11 19:32:40,895 DEBG killing watchdog-script (pid 164) with signal SIGTERM
2020-02-11 19:32:40,895 INFO waiting for start-script, watchdog-script to die
2020-02-11 19:32:41,897 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140310345230224 for <Subprocess at 140310345229552 with name watchdog-script in state STOPPING> (stdout)>
2020-02-11 19:32:41,897 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 140310344568448 for <Subprocess at 140310345229552 with name watchdog-script in state STOPPING> (stderr)>
2020-02-11 19:32:41,898 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-02-11 19:32:41,898 DEBG received SIGCHLD indicating a child quit
2020-02-11 19:32:41,898 DEBG killing start-script (pid 163) with signal SIGTERM
2020-02-11 19:32:42,900 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140310345475312 for <Subprocess at 140310345475360 with name start-script in state STOPPING> (stdout)>
2020-02-11 19:32:42,901 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140310345229456 for <Subprocess at 140310345475360 with name start-script in state STOPPING> (stderr)>
2020-02-11 19:32:42,901 INFO stopped: start-script (terminated by SIGTERM)
2020-02-11 19:32:42,901 DEBG received SIGCHLD indicating a child quit

 

and then the deluged.log

19:44:40.089 [INFO    ][deluge.configmanager:52  ] Setting config directory to: /config
19:44:40.571 [INFO    ][deluge.core.daemon            :94  ] Deluge daemon 2.0.4.dev23
19:44:40.573 [WARNING ][deluge.core.core              :337 ] Unable to load /config/session.state: [Errno 2] No such file or directory: '/config/session.state'
19:44:40.574 [WARNING ][deluge.core.core              :337 ] Unable to load /config/session.state.bak: [Errno 2] No such file or directory: '/config/session.state.bak'
19:44:40.577 [INFO    ][deluge.core.alertmanager      :148 ] Alert Queue Size set to 10000
19:44:40.622 [INFO    ][deluge.core.rpcserver         :402 ] Starting DelugeRPC server :58846
19:44:40.630 [INFO    ][twisted                       :154 ] Factory (TLS) starting on 58846
19:44:40.630 [INFO    ][twisted                       :154 ] Starting factory <twisted.internet.protocol.Factory object at 0x7f79766e2280>
19:44:40.634 [INFO    ][deluge.core.daemon            :154 ] Deluge daemon starting...
19:44:40.666 [INFO    ][deluge_label.core             :78  ] *** Start Label plugin ***
19:44:40.667 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Label enabled...
19:44:40.703 [WARNING ][deluge.config                 :410 ] Unable to open config file /config/blocklist.conf: [Errno 2] No such file or directory: '/config/blocklist.conf'
19:44:40.704 [INFO    ][deluge.pluginmanagerbase      :189 ] Plugin Blocklist enabled...
19:44:40.705 [INFO    ][deluge.core.authmanager       :228 ] Opening auth for load: /config/auth
19:44:40.706 [INFO    ][deluge.core.authmanager       :236 ] Successfully loaded auth: /config/auth
19:44:40.707 [WARNING ][deluge.core.torrentmanager    :1165] Bad shutdown detected so archiving state files
19:44:40.708 [WARNING ][deluge.common                 :195 ] Too many existing archives for state. Deleting oldest archive.
19:44:40.743 [INFO    ][deluge.core.torrentmanager    :806 ] Loading torrent state: /config/state/torrents.state
19:44:40.743 [INFO    ][deluge.core.torrentmanager    :822 ] Successfully loaded /config/state/torrents.state
19:44:40.744 [INFO    ][deluge.core.torrentmanager    :1069] Opening torrents.fastresume for load: /config/state/torrents.fastresume
19:44:40.744 [INFO    ][deluge.core.torrentmanager    :1080] Successfully loaded torrents.fastresume: /config/state/torrents.fastresume
19:44:40.947 [INFO    ][deluge.core.torrentmanager    :668 ] Torrent slackware64-14.2-iso from user "localclient" loaded
19:44:40.947 [INFO    ][deluge.core.torrentmanager    :885 ] Finished loading 1 torrents in 0:00:00.205042
19:44:41.546 [INFO    ][deluge.core.torrentmanager    :1612] on_alert_external_ip: 199.229.249.180
19:44:50.304 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:37718
19:44:50.558 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:45:00.413 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:37726
19:45:00.453 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:45:10.223 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:37732
19:45:10.355 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:45:12.406 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:37734
19:45:31.945 [INFO    ][deluge.core.torrentmanager    :1612] on_alert_external_ip: 199.229.249.180

 

Edited by randyy
a line
Link to comment
1 hour ago, Pducharme said:

Deleted my reply.  Lol didn't think about the Quote copy ahha

I debated editing out both copies when I saw it earlier, but at that point the damage had already been done, those credentials were burnt anyway.

1 hour ago, randyy said:

So I can't take that out....guess who is getting a new VPN password.

That's the only acceptable answer.

 

As far as your original problem, how many different endpoints have you tried with the exact same behaviour?

Link to comment
3 minutes ago, randyy said:

I can try others if you feel that could be the issue?

Dunno, but it couldn't hurt to walk down the list of port forwarding servers and see if they all act identical.

 

This specific forum is for Unraid users, so most of the troubleshooting here is probably not going to be relevant.

Link to comment
2 hours ago, jonathanm said:

Dunno, but it couldn't hurt to walk down the list of port forwarding servers and see if they all act identical.

 

This specific forum is for Unraid users, so most of the troubleshooting here is probably not going to be relevant.

Yeah.  I have Deluge running in a container by itself with no issues.  It the connections run as expected if I turn the VPN_ENABLE switch off - so I figure it's got to be something to do with the ports.  Any reason I should be defining the ports (as opposed to letting the container select them automatically)?

 

----

I ended up recreating everything from scratch and it worked..... same settings.  sigh.

 

Edited by randyy
Link to comment
24 minutes ago, anylettuce said:

question, since some sites have magnetic links only, is there an easy way to pass that info to the docker via windows 10 or linux?

I run the deluge thin client on the Linux Mint desktop - that will intercept magnet links and direct them to the deluge server.

Link to comment

Hey guys, I'm sorry for the noob question... but..

I'm not using the vpn side of this docker, I'm running binhex's sabnzbdvpn (so sabnzbd can use the vpn).

And in deluge I set the proxy to the privoxy settings in sabnzbdvpn. 

My downloads will not work. The proxy works for everything else i throw at it, just not deluge.

I turn the proxy off, and it works fine. Turn it on, no downloads, no seed connections, no nothing.

Any ideas...? Tired using both binhex's deluge dockers, and the linixserver one as well. all do the same thing... 

 

Link to comment

DelugeVPN has been amazing so far. Scratching my head on this one.

I have tried both the native Extractor and the SimpleExtractor-1.3 plugins with the intent of having torrents needing automatic extraction (rar, zip etc) to unpack into the torrent's download folder.  However I'm finding that the extracted file not matter what I do ends up in the /config directory </mnt/user/appdata/binhex-delugevpn>

 

For the Extractor Plugin Configuration: I have left it blank as per the instructions.  This is supposed to unpack to the torrent's own directory.

For the SimpleExtractor Plugin Configuration: I set it to "In-Place" for the same behavior as above.

 

For example torrent downloaded in data/complete/EXAMPLETORR/Example.zip should unpack to data/complete/EXAMPLETORR/example.unpackedfile but ends up in /config/example.unpackedfile

 

It seems the plugins are not aware of anything outside of the /config mount and ignore the /data mount.

 

Hopefully I'm doing something wrong 🙂 . Keep up the great work!

 

 

 

Edited by tompapajr
Link to comment
On 2/7/2020 at 11:46 AM, Level1 said:

Hey guys, I'm new to the forums but am absolutely loving the OS so far. I recommend it to every techie I know constantly. As easy as it is to use though, sometimes I run into issues I can't google my way out of which brings me here. I am trying to use the Binhex DelugeVPN with privoxy docker container that Spaceinvader One has the tutorial for. In his tutorial, though, he only sets it up with the PIA provider who is already included in the package. I am trying to use the docker with another service, specifically PureVPN. I have put in my credentials and imported the appropriate crt, key, and ovpn file pointing to the proper credential file. However, I can never actually access the WebUI because the VPN never fully connects. I have tried multiple servers and replaced the URLs in the ovpn file with the ipv4 to circumvent any DNS issues. Nothing works. The log gives me the following error:

 

2020-02-07 02:51:27,870 DEBG 'start-script' stdout output:
Fri Feb 7 02:51:27 2020 OpenSSL: error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md too weak
Fri Feb 7 02:51:27 2020 Cannot load inline certificate file
Fri Feb 7 02:51:27 2020 Exiting due to fatal error

 

I am out of potential solutions. Any suggestions?

I had the same after trying lots of different PureVPN settings ... I ended up forcing the docker to update (docker - advanced - force update), I then replaced all the OpenVPN files ... it kept all the settings and started working again.

Link to comment
8 minutes ago, Andy Test said:

I ended up forcing the docker to update (docker - advanced - force update),

fyi that wont of done anything.

 

8 minutes ago, Andy Test said:

I then replaced all the OpenVPN files

this will of been the fix, looks like purevpn have improved their ovpn config and certs so that it now passes openvpn strict checks.

Link to comment
3 hours ago, casperse said:

The python version of the last deluge is:

sh-5.0# python --version
Python 3.8.1
sh-5.0# 

 

So Far all the plugin I have found doesn't support this new version?

I need a RSS plugin does anyone have one working?

As always your support and knowledge sharing is highly appreciated Thanks!

Questions like this should really be posted in the Deluge forums. Your much more likely to get some sort of answer there since they have threads dedicated to these plugins.

Link to comment
3 hours ago, casperse said:

The python version of the last deluge is:

sh-5.0# python --version
Python 3.8.1
sh-5.0# 

 

So Far all the plugin I have found doesn't support this new version?

I need a RSS plugin does anyone have one working?

As always your support and knowledge sharing is highly appreciated Thanks!

To help others you can rename the plugin to match the 3.8 python and it will then show up in the deluge UI

BUT IT WILL NOT WORK... so I guess we have to wait for a new version to come out here:

https://bitbucket.org/bendikro/deluge-yarss-plugin/downloads/

 

I can see that others are using the other docker just to get the RSS feed :-)

 

 

Link to comment

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.