repentharlequin

August 16, 2018

Updated to the latest docker image today.
It looks like the image is failing to startup and gets stuck in some retry loop.
Attached the log as a text file.

log.txt

February 10, 2018

Well, that did the trick thanks.

Not sure why it chose now to act up, it's been wrong for months

February 10, 2018

Tried switching to 192.168.0.0 had no effect.
Also tried 192.168.1.1 (my router's IP) and no luck there either

February 10, 2018

After upgrading to unraid 6.4.1 (from 6.4.0) my deluge webgui is no longer accessible, and it appears inactive on my tracker.
The docker log is below, but nothing in there seemed to stand out.
Are there any known issues with this docker image on the latest unraid?

Thanks

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

2018-02-09 18:20:26.070858 [info] Host is running unRAID
2018-02-09 18:20:26.095977 [info] System information Linux 43313008e7f4 4.14.16-unRAID #1 SMP PREEMPT Wed Jan 31 08:51:39 PST 2018 x86_64 GNU/Linux
2018-02-09 18:20:26.133134 [info] PUID defined as '99'
2018-02-09 18:20:26.178612 [info] PGID defined as '100'
2018-02-09 18:20:26.260002 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2018-02-09 18:20:26.288966 [info] Permissions already set for volume mappings
2018-02-09 18:20:26.320803 [info] VPN_ENABLED defined as 'yes'
2018-02-09 18:20:26.371032 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...
2018-02-09 18:20:26.402966 [info] VPN remote line defined as 'nl.privateinternetaccess.com 1198'
2018-02-09 18:20:26.434083 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
2018-02-09 18:20:26.462048 [info] VPN_PORT defined as '1198'
2018-02-09 18:20:26.492825 [info] VPN_PROTOCOL defined as 'udp'
2018-02-09 18:20:26.521557 [info] VPN_DEVICE_TYPE defined as 'tun'
2018-02-09 18:20:26.549207 [info] VPN_PROV defined as 'pia'
2018-02-09 18:20:26.579061 [info] LAN_NETWORK defined as '192.168.0.1/24'
2018-02-09 18:20:26.609072 [info] NAME_SERVERS defined as '8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177'
2018-02-09 18:20:26.637627 [info] VPN_USER defined as ''
2018-02-09 18:20:26.668203 [info] VPN_PASS defined as ''
2018-02-09 18:20:26.697073 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-02-09 18:20:26.723637 [warn] STRICT_PORT_FORWARD not defined (via -e STRICT_PORT_FORWARD), defaulting to 'yes'
2018-02-09 18:20:26.752911 [info] ENABLE_PRIVOXY defined as 'no'
2018-02-09 18:20:26.777259 [info] Setting permissions on files/folders inside container...
2018-02-09 18:20:26.811452 [info] Starting Supervisor...
2018-02-09 18:20:27,128 CRIT Set uid to user 0
2018-02-09 18:20:27,128 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2018-02-09 18:20:27,131 INFO supervisord started with pid 7
2018-02-09 18:20:28,133 INFO spawned: 'start-script' with pid 131
2018-02-09 18:20:28,135 INFO spawned: 'deluge-script' with pid 132
2018-02-09 18:20:28,136 INFO spawned: 'deluge-web-script' with pid 133
2018-02-09 18:20:28,137 INFO spawned: 'privoxy-script' with pid 134
2018-02-09 18:20:28,137 INFO reaped unknown pid 8
2018-02-09 18:20:28,142 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2018-02-09 18:20:28,142 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-02-09 18:20:28,143 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2018-02-09 18:20:28,144 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2018-02-09 18:20:28,144 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23255617743904 for <Subprocess at 23255617741528 with name privoxy-script in state RUNNING> (stderr)>
2018-02-09 18:20:28,144 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 23255617743472 for <Subprocess at 23255617741528 with name privoxy-script in state RUNNING> (stdout)>
2018-02-09 18:20:28,144 INFO exited: privoxy-script (exit status 0; expected)
2018-02-09 18:20:28,144 DEBG received SIGCLD indicating a child quit
2018-02-09 18:20:28,144 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2018-02-09 18:20:28,201 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2018-02-09 18:20:28,205 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2018-02-09 18:20:28,209 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2018-02-09 18:20:28,214 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2018-02-09 18:20:28,217 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2018-02-09 18:20:28,339 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2018-02-09 18:20:28,340 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2018-02-09 18:20:28,340 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2018-02-09 18:20:28,341 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.2

2018-02-09 18:20:28,341 DEBG 'start-script' stdout output:
--------------------

2018-02-09 18:20:28,346 DEBG 'start-script' stdout output:
[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

2018-02-09 18:20:28,346 DEBG 'start-script' stdout output:
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'

2018-02-09 18:20:28,367 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2018-02-09 18:20:28,474 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2018-02-09 18:20:28,477 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-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.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 OUTPUT -o 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.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

2018-02-09 18:20:28,477 DEBG 'start-script' stdout output:
--------------------

2018-02-09 18:20:28,478 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 WARNING: file 'credentials.conf' is group or others accessible
Fri Feb 9 18:20:28 2018 OpenVPN 2.4.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017
Fri Feb 9 18:20:28 2018 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
[info] OpenVPN started

2018-02-09 18:20:28,518 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2018-02-09 18:20:28,520 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:28 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]46.166.188.207:1198
Fri Feb 9 18:20:28 2018 UDP link local: (not bound)
Fri Feb 9 18:20:28 2018 UDP link remote: [AF_INET]46.166.188.207:1198

2018-02-09 18:20:29,081 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:29 2018 [ea20ec2051d1996fc127af8a0a13b9] Peer Connection Initiated with [AF_INET]46.166.188.207:1198

2018-02-09 18:20:30,384 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 auth-token received, disabling auth-nocache for the authentication token

2018-02-09 18:20:30,385 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 TUN/TAP device tun0 opened

2018-02-09 18:20:30,385 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Feb 9 18:20:30 2018 /usr/bin/ip link set dev tun0 up mtu 1500

2018-02-09 18:20:30,386 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 /usr/bin/ip addr add dev tun0 local 10.48.10.6 peer 10.48.10.5

2018-02-09 18:20:30,388 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 /root/openvpnup.sh tun0 1500 1558 10.48.10.6 10.48.10.5 init

2018-02-09 18:20:30,396 DEBG 'start-script' stdout output:
Fri Feb 9 18:20:30 2018 Initialization Sequence Completed

2018-02-09 18:20:30,424 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.48.10.6 different, marking for reconfigure

2018-02-09 18:20:30,519 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=aede12a2ecf7f4e5f761bb8ec3828ff9d54a0ce85ef053341415569bb59480a6...

2018-02-09 18:20:30,810 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 56 from curl != 0
[info] 12 retries left
[info] Retrying in 10 secs...

2018-02-09 18:20:30,811 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 212.92.115.177

2018-02-09 18:20:42,735 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=aede12a2ecf7f4e5f761bb8ec3828ff9d54a0ce85ef053341415569bb59480a6, response code 200

2018-02-09 18:20:43,440 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2018-02-09 18:20:43,941 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.14.10.6
[info] Deluge listening interface will be changed to 10.48.10.6
[info] Saving changes to Deluge config file /config/core.conf...

2018-02-09 18:20:44,392 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui...

2018-02-09 18:20:48,338 DEBG 'deluge-script' stdout output:
Setting random_port to False..
Configuration value successfully updated.

2018-02-09 18:20:48,927 DEBG 'deluge-script' stdout output:
Setting listen_ports to (38935, 38935)..
Configuration value successfully updated.

2018-02-09 18:20:48,955 DEBG 'deluge-script' stdout output:
[info] Deluge started

January 2, 2017

I decided to turn enabling VM and then starting the docker, and now the webui works fine (still can't connect the remote Deluge client though).

I'm wondering if my setup is somehow detecting my station as on a different network than my UNRAID box.

A little confused as to how this could happen, my network has the two systems plugged into the same router.

December 30, 2016

And just to be clear, when I say cannot connect, chrome has the following message:

This site can’t be reached

192.168.0.101 took too long to respond.

Try:

Checking the connection

Checking the proxy and the firewall

ERR_CONNECTION_TIMED_OUT

Are you attempting to connect to 192.168.0.101:8112 ?

Yes

December 29, 2016

And just to be clear, when I say cannot connect, chrome has the following message:

This site can’t be reached

192.168.0.101 took too long to respond.

Try:

Checking the connection

Checking the proxy and the firewall

ERR_CONNECTION_TIMED_OUT

December 29, 2016

For the sake of my sanity, I redownloaded the linuxserver deluge docker and that works just fine still (with binhex's stopped)

December 29, 2016

I'm on the same LAN, and enabling and disabling VM did nothing

December 29, 2016

Nope, I had removed the previous image when I saw that as a suggestion earlier in the thread.

Also rebooted the system again just for grins, but that did not help.

Sickrage can still communicate with the deluge

December 29, 2016

Attached the last entry from the supervisord log as .txt

supervisord_last_entry.txt

December 28, 2016

I apparently suck at this.

I switched from linuxserver's generic deluge to this one to take advantage of the VPN features.

I got everything working (checked using the fake torrent file), and it all worked happily for two months (with the exception that I've never been able to get a remote deluge client to connect from a different system on the LAN).

Today I rebooted my system, and when the docker came back up I can no longer access the web UI.

Any thoughts as to why I can't get on the webui (or connect a remote deluge) would be appreciated.

My server is running on 192.168.0.101, and my configuration looks like:

Network Type: Bridge

Privileged: ON

Host Port 1: 8112

Container Port: 8112

Host Port 2: 58846

Container Port: 58846

Host Port 3: 8118

Container Port: 8118

Host Path 2: /mnt/user/Download/

Container Path: /data

Key 1: yes

Container Variable: VPN_ENABLED

Key 2: XXXXXXXXX

Container Variable: VPN_USER

Key 3: XXXXXXXX

Container Variable: VPN_PASS

Key 4: nl.privateinternetaccess.com

Container Variable: VPN_REMOTE

Key 5: 1198

Container Variable: VPN_PORT

Key 6: udp

Container Variable: VPN_PROTOCOL

Key 7: tun

Container Variable: VPN_DEVICE_TYPE

Key 8: pia

Container Variable: VPN_PROV

Key 9: no

Container Variable: STRONG_CERTS

Key 10: no

Container Variable: ENABLE_PRIVOXY

Key 11: 192.168.0.1/24

Container Variable: LAN_NETWORK

Key 12: 8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177

Container Variable: NAME_SERVERS

Key 13: false

Container Variable: DEBUG

Key 14: 99

Container Variable: PUID

Key 15: 100

Container Variable: PGID

repentharlequin

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by repentharlequin

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN

[Support] binhex - DelugeVPN