[Support] binhex - DelugeVPN

[shonen787]

4 hours ago, binhex said:

well you can def see the dns resolution failure in your screenshot above, to confirm left click deluge icon and select 'console' then type 'ping www.google.com' and that should failto resolve, now the question is what on your lan is blocking it.

 

Agreed. It does fail to resolve but i can't find anything in my LAN that's blocking it. Everything else can resolve to the same domain.

[gh0stkey]

1 hour ago, binhex said:

ok try accessing web ui from another machine/device, try different browser too, also just to double check the network type for the container should be set to 'bridge' is this the case?.

I have tried access it from another computer and multiple other browsers. It is running in bridged network. I haven’t tried redoing the container but it seems that, that’s what I’ll have to do. 

[gh0stkey]

2 hours ago, binhex said:

ok try accessing web ui from another machine/device, try different browser too, also just to double check the network type for the container should be set to 'bridge' is this the case?.

My apologies, this whole time I've been accessing my server through a Openvpn server I have on my router, I got home and to my surprise the Deluge Web UI works... I'm not sure why everything else but the Web UI traffic goes through the vpn...

[shonen787]

56 minutes ago, shonen787 said:

 

Agreed. It does fail to resolve but i can't find anything in my LAN that's blocking it. Everything else can resolve to the same domain.

 

So is it weird that it works with the VPN off, i can resolve hostnames, rather than with it on.

 

[wgstarks]

6 minutes ago, gh0stkey said:

My apologies, this whole time I've been accessing my server through a Openvpn server I have on my router, I got home and to my surprise the Deluge Web UI works... I'm not sure why everything else but the Web UI traffic goes through the vpn...

I've seen the same problem with accessing any docker webUI's running on my unRAID server. I can't access them through the openVPN server on my pfSense appliance anymore. My guess is that there has been a recent change to the openVPN package or maybe pfSense. I know there haven't been any recent updates to unRAID. It's strange though because I can still access any UI's not running on the unRAId server.

[shonen787]

31 minutes ago, shonen787 said:

 

So is it weird that it works with the VPN off, i can resolve hostnames, rather than with it on.

 

Welp. At this point i feel like i've tried everything. The only thing i can think of is that i'm using ExpressVPN and they're the problem

[binhex]

8 hours ago, gh0stkey said:

I've been accessing my server through a Openvpn server

the key bit of info missing :-), ok if you want to be able to access the web ui whilst out and about then you need to add your VPN network range to the LAN_NETWORK value, for instance assuming your VPN allocates a network of 192.168.2.0/24 and your LAN network is 192.168.1.0/24 your LAN_NETWORK value would be:-

 

192.168.1.0/24,192.168.2.0/24

 

[binhex]

7 hours ago, shonen787 said:

 

So is it weird that it works with the VPN off, i can resolve hostnames, rather than with it on.

 

with the vpn off the container will not use the specified name servers defined in NAME_SERVERS value, it will instead use the name servers defined on the unraid host, which are obviously permitted by your firewall, you could try setting NAME_SERVERS to the same value as the name servers defined on your unraid host, this should allow it to work.

[GingaRanga]

On 3/28/2020 at 7:30 PM, Seryth said:

I'm lost....  All of the sudden while adding a link deluge just crashed.  WebuUI stopped responding and just general funky behavior.  Try a few thins and realize that I am not updated to the latest version of anything so I update unraid and everything else.  Still having issues so I figure I will redo my deluge install.  I follow spaceinvaderones video (as always) and get it back to where I can get into the webUI.  Great.  I am going to set up my download preference to /data/incomplete and /data/complete (those are the names of my folders) and I can not apply my changes.  The word "error" is visilbe in the complete lower right corner and the message is "free space in downloads folder".  There is no visible IP address.  When I go the plugins section of the preferences it is blank.  There are no options form me to choose.  

 

  

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

2020-03-28 18:09:39.406140 [info] System information Linux c04960187034 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-03-28 18:09:39.425014 [info] PUID defined as '99'
2020-03-28 18:09:39.446853 [info] PGID defined as '100'
2020-03-28 18:09:39.801880 [info] UMASK defined as '000'
2020-03-28 18:09:39.824684 [info] Permissions already set for volume mappings
2020-03-28 18:09:39.848633 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-03-28 18:09:39.868224 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-03-28 18:09:39.890018 [info] VPN_ENABLED defined as 'yes'
2020-03-28 18:09:39.924339 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
2020-03-28 18:09:39.960297 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
2020-03-28 18:09:39.978968 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
2020-03-28 18:09:40.001227 [info] VPN_PORT defined as '1198'
2020-03-28 18:09:40.022166 [info] VPN_PROTOCOL defined as 'udp'
2020-03-28 18:09:40.039892 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-03-28 18:09:40.060326 [info] VPN_PROV defined as 'pia'
2020-03-28 18:09:40.078984 [info] LAN_NETWORK defined as '192.168.1.0/24'
2020-03-28 18:09:40.096752 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-03-28 18:09:40.117838 [info] VPN_USER defined as 'changes for privacy'
2020-03-28 18:09:40.149591 [info] VPN_PASS defined as 'also changed for privacy'
2020-03-28 18:09:40.176399 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-03-28 18:09:40.203194 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-03-28 18:09:40.221357 [info] ENABLE_PRIVOXY defined as 'yes'
2020-03-28 18:09:40.241426 [info] Deleting files in /tmp (non recursive)...
2020-03-28 18:09:40.260245 [info] Starting Supervisor...
2020-03-28 18:09:40,364 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-03-28 18:09:40,364 INFO Set uid to user 0 succeeded
2020-03-28 18:09:40,366 INFO supervisord started with pid 7
2020-03-28 18:09:41,367 INFO spawned: 'start-script' with pid 162
2020-03-28 18:09:41,369 INFO spawned: 'watchdog-script' with pid 163
2020-03-28 18:09:41,369 INFO reaped unknown pid 8
2020-03-28 18:09:41,372 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-03-28 18:09:41,372 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-03-28 18:09:41,372 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-03-28 18:09:41,408 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-03-28 18:09:41,410 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-03-28 18:09:41,413 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-03-28 18:09:41,415 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-03-28 18:09:41,416 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-03-28 18:09:41,418 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-03-28 18:09:41,420 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-03-28 18:09:41,422 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-03-28 18:09:41,424 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-03-28 18:09:41,452 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-03-28 18:09:41,454 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-03-28 18:09:41,455 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-03-28 18:09:41,456 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.3
192.168.1.0/24 via 172.17.0.1 dev eth0

2020-03-28 18:09:41,456 DEBG 'start-script' stdout output:
--------------------

2020-03-28 18:09:41,457 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 4 iptable_filter,iptable_nat,iptable_mangle

2020-03-28 18:09:41,458 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-03-28 18:09:41,481 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-03-28 18:09:41,482 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.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 INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.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
-A OUTPUT -o tun0 -j ACCEPT

2020-03-28 18:09:41,482 DEBG 'start-script' stdout output:
--------------------

2020-03-28 18:09:41,483 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-03-28 18:09:41,486 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:41 2020 WARNING: file 'credentials.conf' is group or others accessible

Sat Mar 28 18:09:41 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
Sat Mar 28 18:09:41 2020 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10

2020-03-28 18:09:41,487 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-03-28 18:09:41,487 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:41 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-03-28 18:09:41,488 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:41 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.39:1198

2020-03-28 18:09:41,489 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:41 2020 UDP link local: (not bound)
Sat Mar 28 18:09:41 2020 UDP link remote: [AF_INET]172.98.67.39:1198

2020-03-28 18:09:41,596 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:41 2020 [ba900c88cc6f18b52fd8aedf7fdd21cf] Peer Connection Initiated with [AF_INET]172.98.67.39:1198

2020-03-28 18:09:42,802 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:42 2020 TUN/TAP device tun0 opened
Sat Mar 28 18:09:42 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-03-28 18:09:42,803 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:42 2020 /usr/bin/ip addr add dev tun0 local 10.1.10.6 peer 10.1.10.5

2020-03-28 18:09:42,804 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:42 2020 /root/openvpnup.sh tun0 1500 1558 10.1.10.6 10.1.10.5 init

2020-03-28 18:09:42,808 DEBG 'start-script' stdout output:
Sat Mar 28 18:09:42 2020 Initialization Sequence Completed

2020-03-28 18:09:42,915 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privateinternetaccess.com' is port forward enabled...

2020-03-28 18:09:42,918 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2020-03-28 18:09:43,178 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2020-03-28 18:09:43,236 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-toronto.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-03-28 18:09:43,236 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com

2020-03-28 18:09:43,236 DEBG 'start-script' stdout output:
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-03-28 18:09:43,240 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=b57e53c30534aef81f23f559999abc53552abc7f7a54ac014abd2aabfaeebfa4...

2020-03-28 18:09:43,305 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...

2020-03-28 18:09:54,279 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=b57e53c30534aef81f23f559999abc53552abc7f7a54ac014abd2aabfaeebfa4, response code 200

2020-03-28 18:09:54,302 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 56807

2020-03-28 18:09:54,303 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-03-28 18:09:54,440 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.23.100'

2020-03-28 18:09:54,441 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-03-28 18:09:54,557 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.98.67.39

2020-03-28 18:09:55,009 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.1.10.6 different, marking for reconfigure

2020-03-28 18:09:55,013 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-03-28 18:09:55,015 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-03-28 18:09:55,017 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2020-03-28 18:09:55,017 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 56807 different, marking for reconfigure

2020-03-28 18:09:55,017 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-03-28 18:09:55,334 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.12.10.6'
[info] Deluge key 'listen_interface' will have a new value '10.1.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-03-28 18:09:55,502 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-03-28 18:09:55,630 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '5978a02494d949cc9f5fb371d6b734f8'
[info] Deluge key 'default_daemon' will have a new value '5978a02494d949cc9f5fb371d6b734f8'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-03-28 18:09:55,842 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-03-28 18:09:56,052 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-03-28 18:09:57,766 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-03-28 18:09:59,195 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (56807, 56807)
Configuration value successfully updated.

2020-03-28 18:10:00,813 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-03-28 18:10:00,813 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2020-03-28 18:10:00,817 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2020-03-28 18:10:01,820 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2020-03-28 18:10:01,823 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

 

Have you found a solution? I think I am running into the same problem...

[[email protected]]

On 1/17/2022 at 3:44 PM, NY152 said:

Hello All,  Can someone tell me what I'm possibly doing wrong.  I've been running binhex's delugevpn for months now and love it.  However, yesterday, i realized I could no longer log in.  The deluge password had somehow changed.

I deleted the docker completely and reset it up as per Spaceinvaders tutorial.  Near the end of the setup I noticed a message coming from the webui that my password had been saved but I did not make any changes.   Same problem.  I could not login again.   So i started over again.  This time I saw where this was happening.  See below.     My first thought was to simply remove the password but found this was not simple at all (I have no idea how do to it and it seem's complicated)    Thanks

 

[gh0stkey]

16 hours ago, binhex said:

the key bit of info missing :-), ok if you want to be able to access the web ui whilst out and about then you need to add your VPN network range to the LAN_NETWORK value, for instance assuming your VPN allocates a network of 192.168.2.0/24 and your LAN network is 192.168.1.0/24 your LAN_NETWORK value would be:-

 

192.168.1.0/24,192.168.2.0/24

 

Thank you so much man!

[takkischitt]

Is there any way to get the WebUI button back on containers routed through binhex-delugevpn? I've followed the instructions and can access by putting the containers IP and port directly into the browser, but I was wondering if there was any way to get back the WebUI button in the container menu when clicking on the logo in unRAID docker tab.

[JonathanM]

14 minutes ago, takkischitt said:

if there was any way to get back the WebUI button in the container menu when clicking on the logo in unRAID docker tab.

Not currently.

 

[takkischitt]

14 hours ago, JonathanM said:

Not currently.

 

Ah, no problem! Thanks for the confirmation. I maybe should have asked sooner as I've spent the last week on and off trying to work out what I was doing wrong! 🥴

[Tomahawk51]

On 3/2/2022 at 6:55 AM, binhex said:

please dont generalise, what might look like everybody has the same problem (cant access web ui) there are literally dozens of reasons for this, please do the following to help identify the problem:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Reporting back, to eat my hat and learn the lesson.  My issues related to...a change in my VPN Provider's certificate.  Sorry binhex, and also, thanks for this docker.  I'm going to give rTorrent a shot next, and may transition, after reading some of your past comments on "what's the best" de facto client to use on Unraid.

[crazykidguy]

I noticed that the container was outputting a lot of logs very frequently and most of the logs seem to be for debugging purposes. What could be causing these logs to be written so often? I don't remember seeing this behavior before, at least not this level of frequency.

 

Quick edit add: the container is working perfectly (WebUI, seeding, VPN, etc), just the log size is significantly bigger than other dockers and a lot of writing to cache. 

 

2022-03-08 14:52:52,702 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-03-08 14:52:52,859 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196'

2022-03-08 14:52:52,860 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-03-08 14:52:52,872 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-03-08 14:52:52,882 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 43701
[debug] Deluge incoming port is 43701
[debug] VPN IP is 10.11.112.4

2022-03-08 14:52:52,882 DEBG 'watchdog-script' stdout output:
[debug] Deluge IP is 10.11.112.4

2022-03-08 14:53:22,885 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-03-08 14:53:23,037 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196'

2022-03-08 14:53:23,038 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-03-08 14:53:23,048 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-03-08 14:53:23,061 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 43701
[debug] Deluge incoming port is 43701
[debug] VPN IP is 10.11.112.4

2022-03-08 14:53:23,061 DEBG 'watchdog-script' stdout output:
[debug] Deluge IP is 10.11.112.4

2022-03-08 14:53:53,064 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-03-08 14:53:58,219 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196'

2022-03-08 14:53:58,220 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-03-08 14:53:58,234 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-03-08 14:53:58,249 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 43701
[debug] Deluge incoming port is 43701
[debug] VPN IP is 10.11.112.4

2022-03-08 14:53:58,250 DEBG 'watchdog-script' stdout output:
[debug] Deluge IP is 10.11.112.4

2022-03-08 14:54:28,252 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-03-08 14:54:28,378 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '216.58.209.164'

2022-03-08 14:54:28,379 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-03-08 14:54:28,390 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-03-08 14:54:28,405 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 43701
[debug] Deluge incoming port is 43701
[debug] VPN IP is 10.11.112.4

2022-03-08 14:54:28,405 DEBG 'watchdog-script' stdout output:
[debug] Deluge IP is 10.11.112.4

 

Edited March 8, 2022 by crazykidguy
clarifying functionality

[Del1rium]

Hi All

 

Please I need some help, I am stumped, my DelugeVPN container suddenly stopped working - cannot access the WebUI. Here is the end of my log, the log doesn't log anything more.

2022-03-10 23:51:06,505 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50541'

2022-03-10 23:51:08,591 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-03-10 23:51:08,599 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running
[info] Deluge incoming port 6890 and VPN incoming port 50541 different, marking for reconfigure

2022-03-10 23:51:08,602 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-03-10 23:52:02,000 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.10.244.162'
[info] Deluge key 'listen_interface' will have a new value '10.31.136.27'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-03-10 23:52:02,468 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-03-10 23:52:04,893 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'fe8895acd6a04b21b5e376d3bf5fff23'
[info] Deluge key 'default_daemon' will have a new value 'fe8895acd6a04b21b5e376d3bf5fff23'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-03-10 23:52:15,480 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-03-10 23:52:25,420 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-03-10 23:54:02,438 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2022-03-10 23:54:09,920 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50541, 50541)
Configuration value successfully updated.
 

[Luneski]

Hi everybody,

 

long time user of your excelent templates Binhex. It works like a charm and I'm really happy with it.

 

However, for 4 days I was able to access the webui, add torrents (manually or by an ARR app), view my VPN (pia) adress but nothing downloads, eveything is stuck at 0%... I can see some kB/s traffic at the moment I add a torrent and then nothing.

 

I can't see anything in the container logs and for a test, I installed deluge and PIA VPN app on a windows machine to try one of my torrent that is stuck in the container and it works, so neither my vpn provider or torrent provider is blocking me.

 

Where can I have a look to be able to troubleshoot this weird issue ?

[strike]

8 minutes ago, Luneski said:

Hi everybody,

 

long time user of your excelent templates Binhex. It works like a charm and I'm really happy with it.

 

However, for 4 days I was able to access the webui, add torrents (manually or by an ARR app), view my VPN (pia) adress but nothing downloads, eveything is stuck at 0%... I can see some kB/s traffic at the moment I add a torrent and then nothing.

 

I can't see anything in the container logs and for a test, I installed deluge and PIA VPN app on a windows machine to try one of my torrent that is stuck in the container and it works, so neither my vpn provider or torrent provider is blocking me.

 

Where can I have a look to be able to troubleshoot this weird issue ?

Post your docker run command and a screenshot of your deluge downloads settings

[Luneski]

4 minutes ago, strike said:

Post your docker run command and a screenshot of your deluge downloads settings

Here you go for the docker run and deluge downloads settings.

[strike]

8 minutes ago, Luneski said:

Here you go for the docker run and deluge downloads settings.

That looks good. Wrong volume mappings usually cause the symptoms you're seeing, but your mappings looks ok. So it's not that. Do you have free space in your Downloads folder? Can you write to it from inside the delugevpn container? Try to open a terminal in the container and do: 

fallocate -l 100M /data/completed/test.img

That should write a test file in your completed folder. If it fails your have a permission issue.

[Luneski]

9 hours ago, strike said:

That looks good. Wrong volume mappings usually cause the symptoms you're seeing, but your mappings looks ok. So it's not that. Do you have free space in your Downloads folder? Can you write to it from inside the delugevpn container? Try to open a terminal in the container and do: 

fallocate -l 100M /data/completed/test.img

That should write a test file in your completed folder. If it fails your have a permission issue.

Hi, I tried and it created the file succesfully. No error. Any other idea ? concerning my free space Deluge indicate me more than 4TB free so I don't think it is causing the issue.

[Luneski]

Hi people ! I manage to solve my problem by creating a new folder and pointing it to the data folder in Deluge Docke. I''m not really sur where was the issue (probably permission related) but it is now solved. Thanks @strike for pointing me to the right direction

[MrWage]

Hello

 

After restarting my server, the web UI keeps timing out even though the log shows that the web UI has started successfully. Deluge even shows an external IP for the region expected.

However, the log does record:

Successfully assigned and bound incoming port '27062'

every 15 minutes, the port does not change.

 

I've tried force updating the container, replacing the .ovpn files, restarting the server, restarting my network, clearing a cache in the browser, trying a different browser and machine, and completely removing and reinstalling the container but still no dice.

 

I'm totally stumped, is there something obvious I've missed?

 

Solved: Changed a value in the LAN_NETWORK setting from .1.0/24 to .0.0/24

Edited March 20, 2022 by MrWage

[Simmer]

Hello there! I recently lost the ability to access my UI on deluge. I have been wanting to switch to qbit anyway so I deployed binhex' qbit-vpn container but have the same exact issue. I am not sure if it was due to recent container update or not, as I haven't accessed container in a week or so but up until this point it was fine. Browser error states timeout/busy.

Attached is my supervisord.log for deluge (did not attach qbit, since diff thread and maybe I can use solution for both)

 

Thanks!

EDIT: removed attachment, as issue solved. - LAN network definition

 

Edited March 25, 2022 by Simmer