[Support] binhex - DelugeVPN


8722 posts in this topic Last Reply

Recommended Posts

  • 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

 

I think the problem is with your tun5.  When starting openvpn, it does indeed VPN_DEVICE_TYPE+0, take a look:

OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/IPredator-NetworkManager-Password.ovpn --daemon --dev tun50 --remote pw.openvpn.ipredator.se 1194 --proto udp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --auth-user-pass credentials.conf'

The --dev tun50 is probably what breaks it.

 

Try using just "tun" as device type and see how that goes.  I admit I don't know what is the difference between tun0 and tun5.  A quick google seems to say that the number is sometimes assigned randomly so this will probably work but YMMV

 

If you absolutely need to use tun5, you'll need a code update.

 

 

 

 

Link to post

how do i update code?

is it this COMMAND?

/plugins/dynamix.docker.manager/scripts/docker create --name="activ-transmissionvpn" --net="bridge" --privileged="true" -e TZ="Europe/Budapest" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="XXX" -e "VPN_PASS"="XXX" -e "VPN_REMOTE"="pw.openvpn.ipredator.se" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="udp" -e "VPN_PROV"="custom" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.1.0/24" -e "WHITELIST"="192.168.*.*" -e "DEBUG"="true" -e "PUID"="99" -e "PGID"="100" -e "VPN_DEVICE_TYPE"="tun" -e "STRONG_CERTS"="cipher AES-256-CBC" -p 9091:9091/tcp -p 8118:8118/tcp -v "/mnt/disk2/Downloads/":"/data":rw -v "/mnt/user/appdata/activ-transmissionvpn/config":"/config":rw activ/arch-transmissionvpn

As if i go to /plugins there is no dynamix.docker.manager 

So no clue where or what to update...

 

Ive tried to run separate OpenVPN client on unRaid with "tun" (instead of tun5) setting, but soon as it connect it changes it to "tun5" and update the *.ovpn file

 

thx

Link to post

ive tried - same result...

 

Can i edit the OpenVPN command line somewhere?

Because as you can see even i defined:

2017-04-25 21:36:12.088105 [info] VPN_DEVICE_TYPE defined as 'tun5'

 

from some reason it takes both values - probably with other VPN providers doesnt matter, but seems like "ipredator" is bit different.

 

2017-04-25 21:36:14,230 DEBG 'start-script' stdout output:
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT


OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/IPredator-NetworkManager-Password.ovpn --daemon --dev tun50

 

Thanks!

Link to post
15 hours ago, Gog said:

The --dev tun50 is probably what breaks it.

i would agree with this, just to add a bit more to this, from the googling ive done on this the numeric value after "tun" is simply to allow you have multiple tunnel device drivers, in this case we only need one as this is created inside the docker container, thus "tun0". I can see now real reason why it would have to be called "tun5" and can't see how or why your VPN provider would insist on it being called that, can you please set it to simply "tun", and then do the following:-

 

1. Set the env var key "DEBUG" to a value of "yes"

2. Delete any existing log file /config/supervisord.log

3. Restart the container and wait 5 mins for it to completely finish initialising.

4. Post the ENTIRE /config/supervisord.log file here, making sure to remove your username and password from the log.

 

This is your other problem, STRONG_CERTS is purely for PIA users only, valid values are true or false.

13 hours ago, killeriq said:

-e "STRONG_CERTS"="cipher AES-256-CBC"

Link to post

tried one more *.ovpn file which is for windows and has the Certs inside the file - It connect right away with TUN0

Other *.ovpn file which is ment for linux and Certs are separate files (added the path) - is not working in Docker,but It work in OpenVPN Client

It also created some folder structure inside the Docker Transmission folder

But im not able to connect to the Web UI

1. 

IP:8118

IP:9091

Shows:

This site can’t be reached 192.168.10.101 took too long to respond.

 

2. tried from other PC different location

VPN IP:9091

403: Forbidden

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.

If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

-------

checked the settings.json 

    "rpc-whitelist": "192.168.*.*",
    "rpc-whitelist-enabled": true,

 

settings.json

IPredator-Windows-Password.ovpn

supervisord.log

Link to post
On 23-4-2017 at 8:00 PM, Rourke said:

Hey there. Love this docker container. 

 

However I'm having an issue which causes Deluge to not start. The startup process is giving me some errors. Here are my logs: https://pastebin.com/NK2kJSUV

I posted this issue on Github at first. I didn't see the support forum link at the bottom of the readme until just now.

 

Shameless bumping my post but Deluge still isn't running for me. :(

Link to post

I just (<30 minutes ago) updated this Docker (binhex-delugevpn) and suddenly I'm unable to connect to the web-interface; it simply states the "192.168.1.251 heeft de verbinding geweigerd." (meaning: IP has refused the connection).

 

I noticed in the logs something about running /sbin/modprobe iptable_mangle on the host, which I did to add iptable_mangle kernel-module. That did not resolve the issue either.

 


2017-04-27 16:27:09.657900 [info] Starting Supervisor...
2017-04-27 16:27:09,854 CRIT Set uid to user 0
2017-04-27 16:27:09,854 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-04-27 16:27:09,856 INFO supervisord started with pid 6
2017-04-27 16:27:10,858 INFO spawned: 'start-script' with pid 111
2017-04-27 16:27:10,859 INFO spawned: 'deluge-script' with pid 112
2017-04-27 16:27:10,860 INFO spawned: 'deluge-web-script' with pid 113
2017-04-27 16:27:10,861 INFO spawned: 'privoxy-script' with pid 114
2017-04-27 16:27:10,867 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-04-27 16:27:10,868 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,873 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-04-27 16:27:10,873 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 47549797512544 for <Subprocess at 47549798290208 with name privoxy-script in state RUNNING> (stderr)>
2017-04-27 16:27:10,873 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 47549797513552 for <Subprocess at 47549798290208 with name privoxy-script in state RUNNING> (stdout)>
2017-04-27 16:27:10,873 INFO exited: privoxy-script (exit status 0; expected)
2017-04-27 16:27:10,874 DEBG received SIGCLD indicating a child quit
2017-04-27 16:27:10,875 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-04-27 16:27:10,877 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2017-04-27 16:27:10,878 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-04-27 16:27:10,880 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-04-27 16:27:10,888 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-04-27 16:27:10,921 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-04-27 16:27:10,923 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-04-27 16:27:10,926 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2017-04-27 16:27:10,928 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-04-27 16:27:10,931 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2017-04-27 16:27:10,936 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-04-27 16:27:10,937 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-04-27 16:27:10,937 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.6
192.168.1.0/24 via 172.17.0.1 dev eth0

2017-04-27 16:27:10,938 DEBG 'start-script' stdout output:
--------------------

2017-04-27 16:27:10,945 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-04-27 16:27:10,961 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2017-04-27 16:27:11,008 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-04-27 16:27:11,010 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.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -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.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2017-04-27 16:27:11,010 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2017-04-27 16:27:11,016 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-04-27 16:27:11,008 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-04-27 16:27:11,010 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.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -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.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2017-04-27 16:27:11,010 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2017-04-27 16:27:11,016 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-04-27 16:27:12,430 DEBG 'deluge-script' stdout output:
[info] Deluge not running

2017-04-27 16:27:12,431 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.16.10.6 different, marking for reconfigure

2017-04-27 16:27:18,480 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2017-04-27 16:27:18,705 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.7.10.6
[info] Deluge listening interface will be changed to 10.16.10.6
[info] Saving changes to Deluge config file /config/core.conf...

2017-04-27 16:27:18,480 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2017-04-27 16:27:18,705 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.7.10.6
[info] Deluge listening interface will be changed to 10.16.10.6
[info] Saving changes to Deluge config file /config/core.conf...
Link to post
49 minutes ago, jelzinga said:

I just (<30 minutes ago) updated this Docker (binhex-delugevpn) and suddenly I'm unable to connect to the web-interface; it simply states the "192.168.1.251 heeft de verbinding geweigerd." (meaning: IP has refused the connection).

 

I noticed in the logs something about running /sbin/modprobe iptable_mangle on the host, which I did to add iptable_mangle kernel-module. That did not resolve the issue either.

 

 


2017-04-27 16:27:09.657900 [info] Starting Supervisor...
2017-04-27 16:27:09,854 CRIT Set uid to user 0
2017-04-27 16:27:09,854 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-04-27 16:27:09,856 INFO supervisord started with pid 6
2017-04-27 16:27:10,858 INFO spawned: 'start-script' with pid 111
2017-04-27 16:27:10,859 INFO spawned: 'deluge-script' with pid 112
2017-04-27 16:27:10,860 INFO spawned: 'deluge-web-script' with pid 113
2017-04-27 16:27:10,861 INFO spawned: 'privoxy-script' with pid 114
2017-04-27 16:27:10,867 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-04-27 16:27:10,868 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,868 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-27 16:27:10,873 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-04-27 16:27:10,873 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 47549797512544 for <Subprocess at 47549798290208 with name privoxy-script in state RUNNING> (stderr)>
2017-04-27 16:27:10,873 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 47549797513552 for <Subprocess at 47549798290208 with name privoxy-script in state RUNNING> (stdout)>
2017-04-27 16:27:10,873 INFO exited: privoxy-script (exit status 0; expected)
2017-04-27 16:27:10,874 DEBG received SIGCLD indicating a child quit
2017-04-27 16:27:10,875 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-04-27 16:27:10,877 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2017-04-27 16:27:10,878 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-04-27 16:27:10,880 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-04-27 16:27:10,888 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-04-27 16:27:10,921 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-04-27 16:27:10,923 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-04-27 16:27:10,926 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2017-04-27 16:27:10,928 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-04-27 16:27:10,931 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2017-04-27 16:27:10,936 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-04-27 16:27:10,937 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-04-27 16:27:10,937 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.6
192.168.1.0/24 via 172.17.0.1 dev eth0

2017-04-27 16:27:10,938 DEBG 'start-script' stdout output:
--------------------

2017-04-27 16:27:10,945 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-04-27 16:27:10,961 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2017-04-27 16:27:11,008 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-04-27 16:27:11,010 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.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -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.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2017-04-27 16:27:11,010 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2017-04-27 16:27:11,016 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-04-27 16:27:11,008 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-04-27 16:27:11,010 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.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -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.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2017-04-27 16:27:11,010 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2017-04-27 16:27:11,016 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-04-27 16:27:12,430 DEBG 'deluge-script' stdout output:
[info] Deluge not running

2017-04-27 16:27:12,431 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.16.10.6 different, marking for reconfigure

2017-04-27 16:27:18,480 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2017-04-27 16:27:18,705 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.7.10.6
[info] Deluge listening interface will be changed to 10.16.10.6
[info] Saving changes to Deluge config file /config/core.conf...

2017-04-27 16:27:18,480 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2017-04-27 16:27:18,705 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.7.10.6
[info] Deluge listening interface will be changed to 10.16.10.6
[info] Saving changes to Deluge config file /config/core.conf...

I am having this exact issue as well, since this mornings update.

Link to post

I did a small dive into the Docker container, it seems deluged (its daemon process) is not starting properly causing the start-up scripts to hang in a sleep..

 

deluged generates a LOG-file with the following content:


[INFO    ] 17:51:17 configmanager:70 Setting config directory to: /config
[INFO    ] 17:51:17 daemon:127 Deluge daemon 1.3.14
[INFO    ] 17:51:17 configmanager:70 Setting config directory to: /config
[ERROR   ] 17:51:17 main:248 libssl.so.1.0.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/deluge/main.py", line 241, in start_daemon
    Daemon(options, args)
  File "/usr/lib/python2.7/site-packages/deluge/core/daemon.py", line 144, in __init__
    from deluge.core.core import Core
  File "/usr/lib/python2.7/site-packages/deluge/core/core.py", line 38, in <module>
    from deluge._libtorrent import lt
  File "/usr/lib/python2.7/site-packages/deluge/_libtorrent.py", line 59, in <module>
    import libtorrent as lt
ImportError: libssl.so.1.0.0: cannot open shared object file: No such file or directory

 

It seems that Deluge is looking for library libssl.so.1.0.0 and it seems 1.1 is installed.  Unfortunately that is not something I can fix inside - we need to wait for the author to fix it :)

Link to post
25 minutes ago, jelzinga said:

I did a small dive into the Docker container, it seems deluged (its daemon process) is not starting properly causing the start-up scripts to hang in a sleep..

 

deluged generates a LOG-file with the following content:

 


[INFO    ] 17:51:17 configmanager:70 Setting config directory to: /config
[INFO    ] 17:51:17 daemon:127 Deluge daemon 1.3.14
[INFO    ] 17:51:17 configmanager:70 Setting config directory to: /config
[ERROR   ] 17:51:17 main:248 libssl.so.1.0.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/deluge/main.py", line 241, in start_daemon
    Daemon(options, args)
  File "/usr/lib/python2.7/site-packages/deluge/core/daemon.py", line 144, in __init__
    from deluge.core.core import Core
  File "/usr/lib/python2.7/site-packages/deluge/core/core.py", line 38, in <module>
    from deluge._libtorrent import lt
  File "/usr/lib/python2.7/site-packages/deluge/_libtorrent.py", line 59, in <module>
    import libtorrent as lt
ImportError: libssl.so.1.0.0: cannot open shared object file: No such file or directory

 

 

It seems that Deluge is looking for library libssl.so.1.0.0 and it seems 1.1 is installed.  Unfortunately that is not something I can fix inside - we need to wait for the author to fix it :)

 

thanks for this, it does back up my suspicion that deluge doesnt seem to support openssl 1.1.x, hmmmmm right im going roll this back, hang tight guys...

 

edit - figured it out, openssl is now split into two packages, it looks like for deluge you need to explicitly say you want to install openssl 1.0.x otherwise it tries to use openssl 1.1.x and fails, for now i am still rolling back to the previous base image for now, i need to double check this works. 

 

 

Edited by binhex
Link to post
29 minutes ago, binhex said:

em to support openssl 1.1.x, hmmmmm right im going roll this back, hang tight guys...

 

edit - figured it out, openssl is now split into two packages, it looks like for deluge you need to explicitly say you want to install openssl 1.0.x otherwise it tries to use openssl 1.1.x and fails, for now i am still rolling back to the previous base image for now, i need to double check this works. 

 

The rollback worked for me - Deluge is once again starting properly -:)

 

 

Link to post

I'm still trying to figure out why deluge is not running for me. Some errors I can't seem to solve:

2017-04-30 12:45:25,073 DEBG 'start-script' stdout output:
[warn] 'tun' kernel module not available, you will not be able to establish a VPN tunnel
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe tun'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe tun'
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/tun.ko'

I'm on a Ubuntu server 16.04. Running /sbin/modprobe tun doesn't return anything.

 

And I'm also getting this:

 

2017-04-30 12:45:32,556 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2017-04-30 12:45:33,259 DEBG 'deluge-script' stdout output:
[warn] Deluge config file /config/core.conf does not contain valid data, exiting Python script config_deluge.py...

2017-04-30 12:45:34,362 DEBG 'deluge-script' stderr output:
Traceback (most recent call last):
  File "/usr/bin/deluged", line 11, in <module>
    load_entry_point('deluge==1.3.14', 'console_scripts', 'deluged')()
  File "/usr/lib/python2.7/site-packages/deluge/main.py", line 194, in start_daemon

2017-04-30 12:45:34,363 DEBG 'deluge-script' stderr output:
    deluge.log.setupLogger(level=options.loglevel, filename=options.logfile)
  File "/usr/lib/python2.7/site-packages/deluge/log.py", line 65, in setupLogger
    filemode=filemode
  File "/usr/lib/python2.7/logging/__init__.py", line 1547, in basicConfig
    hdlr = FileHandler(filename, mode)
  File "/usr/lib/python2.7/logging/__init__.py", line 913, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python2.7/logging/__init__.py", line 943, in _open
    stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/config/deluged.log'

See the attachment for logs: supervisord.log

 

Edit: I did a clean install and the permission problems are gone. I also tried installing a tunnel in my server environment through openvpn with openvpn --mktun --dev tun0 followed by ifconfig tun0 up but I still can't access the WebGUI.

Edited by Rourke
Link to post

@rourke until you sort out the missing tunnel module on your os you won't be able to use this docker image, I suggest you read up on Ubuntu and tun module

Sent from my SM-G900F using Tapatalk

Link to post
4 hours ago, binhex said:

@rourke until you sort out the missing tunnel module on your os you won't be able to use this docker image, I suggest you read up on Ubuntu and tun module

Sent from my SM-G900F using Tapatalk
 

The tun module is there inside the container, and also outside the container, both up and running. I don't see what else needs to change.

 

I made a temporary workaround with a nginx proxy in a seperate container:

events {
  worker_connections 1024;
}

http {

  server {
    listen 8112;

    location / {
      proxy_pass http://deluge:8112;
      proxy_set_header Host $http_host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      
      # HTTP 1.1 support
      proxy_http_version 1.1;
      proxy_set_header Connection "";
    }
  }
}

 

Edited by Rourke
Link to post
7 hours ago, Rourke said:

The tun module is there inside the container, and also outside the container, both up and running. I don't see what else needs to change.

how are you confirming this?, can you issue the following, firstly on your host:-

 

lsmod

post the output of the above here, then issue this command to list modules inside the container:-

 

docker exec -it <container name> lsmod

again post the output here please.

Link to post
27 minutes ago, binhex said:

how are you confirming this?, can you issue the following, firstly on your host:-

By running ifconfig tun0 and seeing it return tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>

 

lsmod:

root@dedi-par-79211:/# lsmod
Module                  Size  Used by
xt_mark                16384  4
iptable_mangle         16384  2
veth                   16384  0
xt_nat                 16384  67
xt_tcpudp              16384  129
ipt_MASQUERADE         16384  21
nf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADE
xfrm_user              32768  1
xfrm_algo              16384  1 xfrm_user
iptable_nat            16384  13
nf_conntrack_ipv4      16384  3
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  1 iptable_nat
xt_addrtype            16384  2
iptable_filter         16384  3
ip_tables              24576  3 iptable_filter,iptable_mangle,iptable_nat
xt_conntrack           16384  2
x_tables               36864  9 xt_mark,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,xt_nat,iptable_filter,iptable_mangle,xt_addrtype
nf_nat                 24576  3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4
nf_conntrack          106496  5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4
br_netfilter           24576  0
bridge                126976  1 br_netfilter
stp                    16384  1 bridge
llc                    16384  2 stp,bridge
aufs                  217088  1336
ipmi_ssif              24576  0
gpio_ich               16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             172032  0
kvm                   544768  1 kvm_intel
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
aesni_intel           167936  0
aes_x86_64             20480  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
glue_helper            16384  1 aesni_intel
ablk_helper            16384  1 aesni_intel
cryptd                 20480  3 ghash_clmulni_intel,aesni_intel,ablk_helper
joydev                 20480  0
input_leds             16384  0
serio_raw              16384  0
lpc_ich                24576  0
i2c_ismt               20480  0
shpchp                 36864  0
ipmi_si                57344  0
8250_fintek            16384  0
ipmi_msghandler        49152  2 ipmi_ssif,ipmi_si
mac_hid                16384  0
autofs4                40960  2
hid_generic            16384  0
usbhid                 49152  0
hid                   118784  2 hid_generic,usbhid
ast                    61440  1
ttm                    94208  1 ast
drm_kms_helper        155648  1 ast
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
igb                   196608  0
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
dca                    16384  1 igb
drm                   364544  4 ast,ttm,drm_kms_helper
ptp                    20480  1 igb
pps_core               20480  1 ptp
pata_acpi              16384  0
i2c_algo_bit           16384  2 ast,igb
fjes                   28672  0

lsmod in the container:

root@dedi-par-79211:/# docker exec -it deluge lsmod
Module                  Size  Used by
xt_mark                16384  4
iptable_mangle         16384  2
veth                   16384  0
xt_nat                 16384  67
xt_tcpudp              16384  129
ipt_MASQUERADE         16384  21
nf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADE
xfrm_user              32768  1
xfrm_algo              16384  1 xfrm_user
iptable_nat            16384  13
nf_conntrack_ipv4      16384  3
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  1 iptable_nat
xt_addrtype            16384  2
iptable_filter         16384  3
ip_tables              24576  3 iptable_filter,iptable_mangle,iptable_nat
xt_conntrack           16384  2
x_tables               36864  9 xt_mark,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,xt_nat,iptable_filter,iptable_mangle,xt_addrtype
nf_nat                 24576  3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4
nf_conntrack          106496  5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4
br_netfilter           24576  0
bridge                126976  1 br_netfilter
stp                    16384  1 bridge
llc                    16384  2 stp,bridge
aufs                  217088  1342
ipmi_ssif              24576  0
gpio_ich               16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             172032  0
kvm                   544768  1 kvm_intel
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
aesni_intel           167936  0
aes_x86_64             20480  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
glue_helper            16384  1 aesni_intel
ablk_helper            16384  1 aesni_intel
cryptd                 20480  3 ghash_clmulni_intel,aesni_intel,ablk_helper
joydev                 20480  0
input_leds             16384  0
serio_raw              16384  0
lpc_ich                24576  0
i2c_ismt               20480  0
shpchp                 36864  0
ipmi_si                57344  0
8250_fintek            16384  0
ipmi_msghandler        49152  2 ipmi_ssif,ipmi_si
mac_hid                16384  0
autofs4                40960  2
hid_generic            16384  0
usbhid                 49152  0
hid                   118784  2 hid_generic,usbhid
ast                    61440  1
ttm                    94208  1 ast
drm_kms_helper        155648  1 ast
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
igb                   196608  0
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
dca                    16384  1 igb
drm                   364544  4 ast,ttm,drm_kms_helper
ptp                    20480  1 igb
pps_core               20480  1 ptp
pata_acpi              16384  0
i2c_algo_bit           16384  2 ast,igb
fjes                   28672  0

I might be stating the obvious, but I'm in no way an expert on linux networking. I've been trying to figure this out for a week, also by looking into tun/tap modules. But not getting anywhere so far. If it's not something related to your docker images (which I know is likely) I just hope anyone can point me in the right direction.

Edited by Rourke
Link to post

OK so the output shows you are missing the module "tun" however you can manually create the device (which i do for you inside the container) so it shouldnt matter, so now the permissions issue is solved i would like to take another look at your log, can you please do the following:-

 

1. Delete any existing log file /config/supervisord.log

2. Stop the container and delete it (or if you're an unraid user skip this step)

3. Redefine the container parameters and additionally set the env var key "DEBUG" to a value of "yes"

4. Start the container and wait 5 mins for it to completely finish initialising.

5. Post the ENTIRE /config/supervisord.log file here, making sure to remove your username and passwords from the log.

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.