[Support] binhex - DelugeVPN


Recommended Posts

4 minutes ago, DigitalDivide said:

Is there a place in the docker where one configures where the torrents should be picked up from or is that a deluge config parameter?  I only thought it was a docker issue as the problem occurred when I updated the docker.  

That all in the app configuration if I understand correctly what you are doing.

Link to comment
1 minute ago, DigitalDivide said:

I'm not using any other software other than the deluge vpn docker.  As I said, the torrent files which I save to my torrents folder are not being picked up, either by the docker or deluge, so the files are not being downloaded.  

check your watched (sometimes also known as blackhole) path in the deluge web ui, make sure its still set correctly, if it is then try manually adding a torrent via the deluge web ui.

Link to comment
20 minutes ago, DigitalDivide said:

I don't see a watched folder option but I noticed under plugins there's one for autadd.  It's not enabled.  I don't recall if I ever had it enabled but I just did and set it to my torrents folder and it now seems to be working...

ahh ok, been a while since ive used deluge :-), you are right watched folder is done via autoadd, which is a plugin, so you would need to enable and configure the plugin, due to the massive changes between deluge v1 and v2 i would expect any plugin configuration to be most probably invalid, so you will need to re-configure.

Link to comment
2 hours ago, DigitalDivide said:

I don't think is is a problem with Deluge bur rather the docker....in my case I think so anyhow...  If you go into the Deluge Console, then click Files, and point to a torrent file you downloaded into a folder, then click Add, does it download?  Mine does   

 

1 hour ago, binhex said:

check your watched (sometimes also known as blackhole) path in the deluge web ui, make sure its still set correctly, if it is then try manually adding a torrent via the deluge web ui.

In my instance, I don't have a watched folder. But when I manually download the .torrent file to my computer and upload it to Deluge via the web UI, the torrent still doesn't download. The icon shows green so there are no errors and ports are open, connection is clear.

Link to comment
2 minutes ago, vurt said:

 

In my instance, I don't have a watched folder. But when I manually download the .torrent file to my computer and upload it to Deluge via the web UI, the torrent still doesn't download. The icon shows green so there are no errors and ports are open, connection is clear.

have you configured the "Download to:" path in the deluge web ui?

Link to comment
Just now, vurt said:

This set up was working before 2.0.3, I haven't changed a thing.

deluge v2 and deluge v1 are very different under the hood, just cos it worked in v1 does not mean it will work in v2, this is especially true of deluge v1 plugins, none of which work with deluge v2. 

Link to comment

Hmmm ok, kinda odd that nobody else seems to have the same problem and this wasn't broken before. I'm not using any plugins either.

 

Are there any logs I can provide which can help troubleshoot? Anything I can do to help figure this out? I've asked on the Deluge forum but no replies over there.

Link to comment

Well turns out my problem was not resolved.  I tried enabling the AutoAdd plugin which is listed in the preferences in the Deluge Gui, they get added to the download screen but don't actually download.  So I disabled that.  THe only way I can get the torrents to download is from the Deluge Gui selecting Add, then manually adding each torrent.  For whatever reason, whatever was configured before I upgraded the docker, something changed as Deluge will not pick up the downloaded torrents and add them to the gui and download.

 

I'm now wondering if the AutoAdd plug in the Deluge Preferences broke due to the new version of Deluge....

Link to comment

Hello folks. my Binex Docker DelugeVPN suddenly stopped working about two days ago and I can't figure out what's up. I noticed first of all that it my torrents were no longer connecting to the internet last night, so I restarted the docker container before I went to bed. Then today, I found out that DelugeVPN isn't starting up at all, or is getting blocked somehow. I haven't made any changes to any settings and it had been running perfectly (or as perfectly as Deluge runs) for months. Any ideas? I posted the log below. I'm using AirVPN. The only thought I had was to create a new AirVPN config, which I did earlier today, but it still doesn't work and now I'm out of ideas. I set up my docker container using the instructions here: http://tomthegreat.com/2018/03/11/setting-up-deluge-with-vpn-on-synology-using-docker/ and I don't think I've changed anything, at least in a very long time.

 

Here's what's going down when I boot up:

 



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

2019-08-02 15:41:01.645088 [info] System information Linux DelugeVPN 4.4.59+ #24922 SMP PREEMPT Fri May 10 02:59:42 CST 2019 x86_64 GNU/Linux
2019-08-02 15:41:01.712834 [info] PUID defined as '1026'
2019-08-02 15:41:01.780966 [info] PGID defined as '100'
2019-08-02 15:41:01.898745 [info] UMASK defined as '000'
2019-08-02 15:41:01.960760 [info] Permissions already set for volume mappings
2019-08-02 15:41:02.029282 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2019-08-02 15:41:02.091647 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2019-08-02 15:41:02.155152 [info] VPN_ENABLED defined as 'yes'
2019-08-02 15:41:02.225755 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AirVPN_America_UDP-443.ovpn
dos2unix: converting file /config/openvpn/AirVPN_America_UDP-443.ovpn to Unix format...
2019-08-02 15:41:02.326372 [info] VPN remote line defined as 'remote america.vpn.airdns.org 443'
2019-08-02 15:41:02.389404 [info] VPN_REMOTE defined as 'america.vpn.airdns.org'
2019-08-02 15:41:02.452542 [info] VPN_PORT defined as '443'
2019-08-02 15:41:02.522156 [info] VPN_PROTOCOL defined as 'udp'
2019-08-02 15:41:02.585667 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-08-02 15:41:02.648643 [info] VPN_PROV defined as 'airvpn'
2019-08-02 15:41:02.711017 [info] LAN_NETWORK defined as '192.168.0.1/24'
2019-08-02 15:41:02.773780 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4'
2019-08-02 15:41:02.837684 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-08-02 15:41:02.900296 [info] ENABLE_PRIVOXY defined as 'yes'
2019-08-02 15:41:02.962771 [info] Starting Supervisor...
2019-08-02 15:41:03,310 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-08-02 15:41:03,311 INFO Set uid to user 0 succeeded
2019-08-02 15:41:03,317 INFO supervisord started with pid 7
2019-08-02 15:41:04,320 INFO spawned: 'start-script' with pid 132
2019-08-02 15:41:04,322 INFO spawned: 'watchdog-script' with pid 133
2019-08-02 15:41:04,324 INFO spawned: 'privoxy-script' with pid 134
2019-08-02 15:41:04,325 INFO reaped unknown pid 8
2019-08-02 15:41:04,334 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-08-02 15:41:04,335 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-08-02 15:41:04,335 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-08-02 15:41:04,335 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-08-02 15:41:04,338 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/core.conf to Unix format...

2019-08-02 15:41:04,443 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-08-02 15:41:04,450 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-08-02 15:41:04,458 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-08-02 15:41:04,465 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-08-02 15:41:04,474 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-08-02 15:41:04,481 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-08-02 15:41:04,487 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-08-02 15:41:04,583 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2019-08-02 15:41:04,591 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2019-08-02 15:41:04,593 DEBG 'start-script' stderr output:
RTNETLINK answers: Invalid argument

2019-08-02 15:41:04,594 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-08-02 15:41:04,596 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 

2019-08-02 15:41:04,597 DEBG 'start-script' stdout output:
--------------------

2019-08-02 15:41:04,606 DEBG 'start-script' stdout output:
iptable_mangle          1656  0
ip_tables              14092  3 iptable_filter,iptable_mangle,iptable_nat
x_tables               16302  21 ip6table_filter,xt_ipvs,xt_iprange,xt_mark,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_geoip,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_mac,xt_nat,xt_multiport,iptable_filter,xt_REDIRECT,iptable_mangle,ip6_tables,xt_addrtype

2019-08-02 15:41:04,607 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-08-02 15:41:04,672 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-08-02 15:41:04,674 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 443 -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 -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -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 443 -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 -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-08-02 15:41:04,676 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2019-08-02 15:41:04,688 DEBG 'start-script' stdout output:
Fri Aug  2 15:41:04 2019 WARNING: file 'credentials.conf' is group or others accessible
Fri Aug  2 15:41:04 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018

2019-08-02 15:41:04,688 DEBG 'start-script' stdout output:
Fri Aug  2 15:41:04 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-08-02 15:41:04,690 DEBG 'start-script' stdout output:
[info] OpenVPN started
Fri Aug  2 15:41:04 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-08-02 15:41:04,691 DEBG 'start-script' stdout output:
Fri Aug  2 15:41:04 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:41:04 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2019-08-02 15:41:04,692 DEBG 'start-script' stdout output:
Fri Aug  2 15:41:04 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.19:443
Fri Aug  2 15:41:04 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Aug  2 15:41:04 2019 UDP link local: (not bound)
Fri Aug  2 15:41:04 2019 UDP link remote: [AF_INET]199.19.94.19:443

2019-08-02 15:42:04,950 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:04 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting

2019-08-02 15:42:04,950 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:04 2019 SIGHUP[soft,ping-restart] received, process restarting

2019-08-02 15:42:04,950 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:04 2019 WARNING: file 'credentials.conf' is group or others accessible
Fri Aug  2 15:42:04 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Aug  2 15:42:04 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10
Fri Aug  2 15:42:04 2019 Restart pause, 5 second(s)

2019-08-02 15:42:09,951 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:09 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-08-02 15:42:09,952 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:09 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:42:09 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2019-08-02 15:42:09,953 DEBG 'start-script' stdout output:
Fri Aug  2 15:42:09 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.19:443
Fri Aug  2 15:42:09 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Aug  2 15:42:09 2019 UDP link local: (not bound)
Fri Aug  2 15:42:09 2019 UDP link remote: [AF_INET]199.19.94.19:443

2019-08-02 15:43:09,734 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:09 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting

2019-08-02 15:43:09,735 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:09 2019 SIGHUP[soft,ping-restart] received, process restarting
Fri Aug  2 15:43:09 2019 WARNING: file 'credentials.conf' is group or others accessible

2019-08-02 15:43:09,735 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:09 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Aug  2 15:43:09 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10
Fri Aug  2 15:43:09 2019 Restart pause, 5 second(s)

2019-08-02 15:43:14,735 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:14 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-08-02 15:43:14,736 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:14 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:43:14 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2019-08-02 15:43:14,736 DEBG 'start-script' stdout output:
Fri Aug  2 15:43:14 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.19:443
Fri Aug  2 15:43:14 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Aug  2 15:43:14 2019 UDP link local: (not bound)
Fri Aug  2 15:43:14 2019 UDP link remote: [AF_INET]199.19.94.19:443

2019-08-02 15:44:14,774 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:14 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting

2019-08-02 15:44:14,774 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:14 2019 SIGHUP[soft,ping-restart] received, process restarting
Fri Aug  2 15:44:14 2019 WARNING: file 'credentials.conf' is group or others accessible
Fri Aug  2 15:44:14 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Aug  2 15:44:14 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-08-02 15:44:14,775 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:14 2019 Restart pause, 5 second(s)

2019-08-02 15:44:19,775 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:19 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-08-02 15:44:19,775 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:19 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:44:19 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2019-08-02 15:44:19,776 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:19 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.19:443
Fri Aug  2 15:44:19 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Aug  2 15:44:19 2019 UDP link local: (not bound)
Fri Aug  2 15:44:19 2019 UDP link remote: [AF_INET]199.19.94.19:443

2019-08-02 15:45:19,305 DEBG 'start-script' stdout output:
Fri Aug  2 15:45:19 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting

2019-08-02 15:45:19,305 DEBG 'start-script' stdout output:
Fri Aug  2 15:45:19 2019 SIGHUP[soft,ping-restart] received, process restarting
Fri Aug  2 15:45:19 2019 WARNING: file 'credentials.conf' is group or others accessible
Fri Aug  2 15:45:19 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Aug  2 15:45:19 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-08-02 15:45:19,306 DEBG 'start-script' stdout output:
Fri Aug  2 15:45:19 2019 Restart pause, 5 second(s)

2019-08-02 15:45:24,306 DEBG 'start-script' stdout output:
Fri Aug  2 15:45:24 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-08-02 15:45:24,307 DEBG 'start-script' stdout output:
Fri Aug  2 15:45:24 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:45:24 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Aug  2 15:45:24 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.19.94.19:443
Fri Aug  2 15:45:24 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Aug  2 15:45:24 2019 UDP link local: (not bound)
Fri Aug  2 15:45:24 2019 UDP link remote: [AF_INET]199.19.94.19:443

 

The only thing that stands out to me is the  "WARNING: file 'credentials.conf' is group or others accessible."

An help would be really appreciated! This container is the heart of my entire setup and I'm SOL with it broken.

 

Link to comment
16 minutes ago, Ranzingabon Hagglesmith said:

2019-08-02 15:44:14,774 DEBG 'start-script' stdout output:
Fri Aug  2 15:44:14 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting

looks to me like openvpn is unable to connect to airvpn, check openvpn config file is up to date, think about anything you may of changed. firewall, router, modem, any network gear.

Link to comment
14 minutes ago, binhex said:

looks to me like openvpn is unable to connect to airvpn, check openvpn config file is up to date, think about anything you may of changed. firewall, router, modem, any network gear.

Hmm, crap. I tried putting in a new openvpn config file before I posted here. I can't think of anything else that I would have changed, unless they changed on their own somehow.

Link to comment
43 minutes ago, binhex said:

looks to me like openvpn is unable to connect to airvpn, check openvpn config file is up to date, think about anything you may of changed. firewall, router, modem, any network gear.

Okay, here are my port and then firewall settings. Does this look right?

 

DockerVPN port settings:

JSuG2FY.png

 

Firewall settings in Synology DSM:

W9OIjEe.png

 

edit:

 

Okay, I tried just disabling my Synology DSM firewall totally and that made no difference -- same problem. I tried replacing the AirVPN config before I posted here. I don't see how my router settings could changed, but I can't check that just this minute.  Is there anything else I can check for in the mean time?

Edited by Ranzingabon Hagglesmith
updated informaiton
Link to comment

Just noticed a similar issue that the VPN died, re did my config no help, so went to re-install the Docker now I can't even get that to occur. Fails to launch even without VPN enabled, and the appdata folder is empty.

 

Error I'm seeing when trying to re-install 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='[email protected]' -e 'VPN_PASS'='XXXXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='LAN IP/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 
74e8b2f9a0a4c501db897bb7121600d7c369369339109096fb4feb512d354823
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (45a4bc0be49c5fc449436264d169b81ab935ec76e57f2f8ca68eb9650f348182): Error starting userland proxy: listen udp 0.0.0.0:58946: bind: address already in use.

The command failed.

 

Edited by Magaman
Link to comment
On 8/2/2019 at 9:34 AM, binhex said:

ok lets make sure its nothing else, can you follow the procedure as detailed in the following link:-

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

Hi @binhex, I've attached two logs, deliged.log and supervisord.log.

 

One thing I noticed in deluged.log:

 

10:00:04 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 212.32.244.72:56873
10:00:04 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:05 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 82.123.64.112:54659
10:00:05 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:05 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 173.246.31.184:59384
10:00:06 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:09 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.120.17.95:53888
10:00:09 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:10 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 184.58.233.197:58134
10:00:10 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:11 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 83.135.154.122:56440
10:00:11 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:12 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 97.113.139.203:33786
10:00:12 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]

This is happening every second and deluged.log has ballooned to 18 MB. It looks like it's disconnecting from the swarm due to wrong SSL version?

deluged.log supervisord.log

Edited by vurt
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.