[Support] binhex - DelugeVPN


Recommended Posts

I have just set up delugevpn and am attempting to test the speed and make sure everything is in working order, and I can't get the web UI for speedtest working through deluge to save my life. I'm trying to put adolfintel's speedtest docker through delugevpn. I followed the following steps:

  1. Set network type in speedtest to none
  2. Set extra parameters in speedtest to --net=container:binhex-delugevpn
  3. Add port variable in delugevpn docker that matches the port variable of speedtest

Both start up. curl ifconfig.io shows the correct ip address in the country of my VPN config file. However, when I attempt to get to the speedtest webui by typing in my server IP and port, the connection times out. Attached are images of the relevant settings. Am I doing anything wrong?

Edit: this is happening with all dockers I've tested.

 

Speedtest settings:

speedtest_settings.png

 

delugevpn settings:

delugevpn_settings.pngdelugevpn_portsettings.png

 

port mappings:

speedtest_portmappings.png

delugevpn_portmappings.png

Edited by kwatz
  • Thanks 1
Link to comment
9 hours ago, kwatz said:

I have just set up delugevpn and am attempting to test the speed and make sure everything is in working order, and I can't get the web UI for speedtest working through deluge to save my life. I'm trying to put adolfintel's speedtest docker through delugevpn. I followed the following steps:

  1. Set network type in speedtest to none
  2. Set extra parameters in speedtest to --net=container:binhex-delugevpn
  3. Add port variable in delugevpn docker that matches the port variable of speedtest

Both start up. curl ifconfig.io shows the correct ip address in the country of my VPN config file. However, when I attempt to get to the speedtest webui by typing in my server IP and port, the connection times out. Attached are images of the relevant settings. Am I doing anything wrong?

 

Speedtest settings:

speedtest_settings.png

 

delugevpn settings:

delugevpn_settings.pngdelugevpn_portsettings.png

 

port mappings:

speedtest_portmappings.png

delugevpn_portmappings.png

 

I am having the exact same issue, I'm running all of my dockers through Binhex-privoxyvpn and everything is great. However, whenever I try to run ANY torrent docker (Binhex's Deluge or anything else) through Binhex-privoxyvpn, I run into the exact same issue as yourself.

 

I look forward to seeing if you are able to fix this issue. Please let me know if you resolve it away from this post. 👍🏻

 

***EDIT***

The solution is here (Q24 & Q25);

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

You need to update you VPN_INPUT_PORTS variable in Privoxyvpn with the port of the container you wish to access. This was implemented as part of Binhex tightening security.

Edited by BeardedNoir
Link to comment

Hello,

 

I'm having trouble with my deluge container (binhex-delugevpn) since this morning.


Up until yesterday, everything was working fine. I'm using Heimdall, Sonarr and Radarr. All 3 of them could reach deluge's API, and deluge's web gui was working fine.

 

Now, since this morning, the web gui just wont work anymore, it keeps loading until I have a timeout


It seems deluge is still properly running though. Sonarr and Radarr can still reach the API and Heimdall is showing my up and down speed. Apparently a few torrents are still being seeded.

If I connect to my server using SSH and try a wget of deluge's URL with the local IP of the container (which is 172.17.0.3:8112 right now) it works, as soon as I use the IP from my local network it won't work and gives a timeout

 

If I disable the VPN in the container's setting it works (setting VPN_ENABLED to no)

 

The container logs are attached.

 

Anyone might have an idea ?

 

Thanks !

 

EDIT : Nevermind, the error was in the logs and right in my face all along, I feel dumb lol

[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

I simply started the module manually as suggested and it's working !

deluge-container.log

Edited by shinigota
Link to comment

Hello all!

 

This is now the second time this has happened to me. What I ended up doing the last time is removing the container entirely and reinstalling it. I cannot access the webui again nor does sonarr/radarr can access delugevpn. Everything was working well for the past 2 weeks and now the same issue. Started a few days ago. I am using PIA, I have tried multiple servers that support port forwarding, checked to make sure the server's port forwarding was up, (Canada, Netherlands, ect.) and still can't access. Checked username/pass all correct. Running curl ifconfig.io resolves the VPN address. I am now at a loss LOL. Because of this now sonarr and raddarr cannot see deulugevpn. Also turned off port forwarding and still the same issue. Any ideas would be much appreciated. Logs attached. Thanks all!supervisord.log

 

Link to comment

I'm having the same issue as a lot of other people where it's been working no issues for a year and for the last two weeks I haven't been able to access the WebUI. I haven't changed anything and I do not have the VPN enabled. Below are my logs. I have no idea what the issue could be. Any help is appreciated.

 

Quote

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

2021-08-25 11:02:25.586103 [info] Host is running unRAID
2021-08-25 11:02:25.603819 [info] System information Linux 46626e98853e 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2021-08-25 11:02:25.624657 [info] OS_ARCH defined as 'x86-64'
2021-08-25 11:02:25.645568 [info] PUID defined as '99'
2021-08-25 11:02:25.685419 [info] PGID defined as '100'
2021-08-25 11:02:25.744337 [info] UMASK defined as '000'
2021-08-25 11:02:25.764333 [info] Permissions already set for volume mappings
2021-08-25 11:02:25.790782 [info] Deleting files in /tmp (non recursive)...
2021-08-25 11:02:25.816336 [info] VPN_ENABLED defined as 'no'
2021-08-25 11:02:25.831958 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2021-08-25 11:02:25.854406 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-08-25 11:02:25.875257 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-08-25 11:02:25.898932 [info] Starting Supervisor...
2021-08-25 11:02:26,088 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-08-25 11:02:26,088 INFO Set uid to user 0 succeeded
2021-08-25 11:02:26,090 INFO supervisord started with pid 7
2021-08-25 11:02:27,092 INFO spawned: 'shutdown-script' with pid 84
2021-08-25 11:02:27,094 INFO spawned: 'start-script' with pid 85
2021-08-25 11:02:27,095 INFO spawned: 'watchdog-script' with pid 86
2021-08-25 11:02:27,095 INFO reaped unknown pid 8 (exit status 0)
2021-08-25 11:02:27,103 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2021-08-25 11:02:27,103 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-25 11:02:27,103 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-25 11:02:27,104 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-25 11:02:27,104 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22773084371456 for <Subprocess at 22773084370784 with name start-script in state RUNNING> (stdout)>
2021-08-25 11:02:27,104 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22773084496320 for <Subprocess at 22773084370784 with name start-script in state RUNNING> (stderr)>
2021-08-25 11:02:27,104 INFO exited: start-script (exit status 0; expected)
2021-08-25 11:02:27,104 DEBG received SIGCHLD indicating a child quit
2021-08-25 11:02:27,126 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2021-08-25 11:02:27,129 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2021-08-25 11:02:27,130 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2021-08-25 11:02:27,251 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has an undefined value
[info] Deluge key 'listen_interface' will have a new value ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2021-08-25 11:02:27,358 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has an undefined value
[info] Deluge key 'outgoing_interface' will have a new value ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2021-08-25 11:02:27,501 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '22fa08cc64cf41f0adcbd5cd4febc427'
[info] Deluge key 'default_daemon' will have a new value '22fa08cc64cf41f0adcbd5cd4febc427'
[info] Writing changes to Deluge config file '/config/web.conf'...

2021-08-25 11:02:27,772 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

 

Link to comment

Hi all, first time poster - long time lurker :)

I'm having a few issues - primarily when trying to use Wireguard as a protocol.

Everything is nice and dandy, right up until a few minutes into maxing out the bandwith (i have 1gbit fiber, but it seems to max out at 550mbit on Wireguard).
Anyhow - the internet connection simply stops working in the container and then the container restarts since it fails to resolve DNS and etc.. but Wireguard is still dead despite restarting the container and i then run into a restart loop until it work again after maybe 15 minutes or so.

 

I do suspect that this is a fault in PIA's side though.. am i correct in this assumption?

OpenVPN ẃorks as intended btw, but speeds are maxed at 220mbit :/ 

Link to comment
14 minutes ago, HakimEG said:

Everything is nice and dandy, right up until a few minutes into maxing out the bandwith (i have 1gbit fiber, but it seems to max out at 550mbit on Wireguard).

its possible you are flooding your router and getting into a situation where Deluge is consuming all available bandwidth and thus stopping name resolution from happening, try throttling deluge back to say 450 Mb/s and see if that helps.

Link to comment
17 minutes ago, Level1 said:

Something was updated upstream and now all of his VPN apps are broken. DelugeVPN, PrivoxyVPN, rtorrentVPN all of them broke at the same time

not for me they're not im running privoxyvpn and qbittorrentvpn right now, just restarted qbittorrentvpn and it came right up (vpn provider pia), no issues, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Link to comment
On 8/25/2021 at 5:49 PM, AtomZ said:

Hello all!

 

This is now the second time this has happened to me. What I ended up doing the last time is removing the container entirely and reinstalling it. I cannot access the webui again nor does sonarr/radarr can access delugevpn. Everything was working well for the past 2 weeks and now the same issue. Started a few days ago. I am using PIA, I have tried multiple servers that support port forwarding, checked to make sure the server's port forwarding was up, (Canada, Netherlands, ect.) and still can't access. Checked username/pass all correct. Running curl ifconfig.io resolves the VPN address. I am now at a loss LOL. Because of this now sonarr and raddarr cannot see deulugevpn. Also turned off port forwarding and still the same issue. Any ideas would be much appreciated. Logs attached. Thanks all!supervisord.log

 

nothing obviously wrong in that log, it shows a successful start, is your LAN_NETWORK defined correctly?, from your log:-

2021-08-24 20:08:41.048311 [info] LAN_NETWORK defined as '192.168.1.0/24'

se Q4 if you are unsure:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment
1 hour ago, binhex said:

its possible you are flooding your router and getting into a situation where Deluge is consuming all available bandwidth and thus stopping name resolution from happening, try throttling deluge back to say 450 Mb/s and see if that helps.

I'll try it out and report back.
But when you say router - what do you exactly mean? the routing inside the container?

Link to comment
5 minutes ago, binhex said:

no, your physical router.

Ah well i'm pretty sure that's not the case - i have a full 1gbit ISP line, and am only consuming half of that for Deluge.
Spec wise, i'm using a Unifi Dream Machine, and the rest of my home never has any downtime coinciding with what's happening in the delugevpn container.

I tried limiting bandwith to 350mbit, but the same thing is still happening :/
Also enabled debug output for logging, but nothing of interest really shows up i feel.


 

2021-08-27 12:52:35,597 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-08-27 12:52:35,704 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.176.196'

2021-08-27 12:52:35,707 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2021-08-27 12:52:35,740 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2021-08-27 12:52:35,764 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 45387
[debug] Deluge incoming port is 45387
[debug] VPN IP is 10.24.153.129
[debug] Deluge IP is 10.24.153.129

2021-08-27 12:53:05,770 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-08-27 12:54:48,884 WARN received SIGTERM indicating exit request
2021-08-27 12:54:48,885 DEBG killing watchdog-script (pid 169) with signal SIGTERM
2021-08-27 12:54:48,886 INFO waiting for shutdown-script, start-script, watchdog-script to die
2021-08-27 12:54:49,887 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22905190581680 for <Subprocess at 22905190580672 with name watchdog-script in state STOPPING> (stdout)>
2021-08-27 12:54:49,888 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22905190581728 for <Subprocess at 22905190580672 with name watchdog-script in state STOPPING> (stderr)>
2021-08-27 12:54:49,888 INFO stopped: watchdog-script (terminated by SIGTERM)
2021-08-27 12:54:49,889 DEBG received SIGCHLD indicating a child quit
2021-08-27 12:54:49,889 DEBG killing start-script (pid 168) with signal SIGTERM
2021-08-27 12:54:50,891 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22905190407136 for <Subprocess at 22905190406464 with name start-script in state STOPPING> (stdout)>
2021-08-27 12:54:50,892 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22905190581152 for <Subprocess at 22905190406464 with name start-script in state STOPPING> (stderr)>
2021-08-27 12:54:50,892 INFO stopped: start-script (terminated by SIGTERM)
2021-08-27 12:54:50,893 DEBG received SIGCHLD indicating a child quit
2021-08-27 12:54:50,893 DEBG killing shutdown-script (pid 167) with signal SIGTERM
2021-08-27 12:54:50,894 DEBG 'shutdown-script' stdout output:

 

Link to comment
29 minutes ago, HakimEG said:

i have a full 1gbit ISP line

yeah i appreciate you have a high speed line, but what is connected to the end of the line?, a cheap ISP router i would suffice, your Unifi Dream Machine does not come into this, as this is simply a AP, try reducing the number of connections in deluge as well, also reduce the upload rate, if its set to unlimited this will def cause issues.

Link to comment
2 hours ago, binhex said:

nothing obviously wrong in that log, it shows a successful start, is your LAN_NETWORK defined correctly?, from your log:-

2021-08-24 20:08:41.048311 [info] LAN_NETWORK defined as '192.168.1.0/24'

se Q4 if you are unsure:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Hey Binhex thanks for the reply. I did confirm my lan network is defined correctly and should be 192.168.1.0/24. It still will not let me connect to the container unfortunately. image.thumb.png.f5e4ae4bd5e7b30342d90b004ec403f7.png

Link to comment
6 hours ago, AtomZ said:

Hey Binhex thanks for the reply. I did confirm my lan network is defined correctly and should be 192.168.1.0/24. It still will not let me connect to the container unfortunately. 

 

ok try another browser, also try another host, you could also confirm deluge is running by going to the 'Terminal' via unraid web ui (the host not the container) and running the following:-

 

curl 192.168.1.120:8112

if you see output then you know the issue is connectivity from unraid to the machine running the browser.

Link to comment
On 8/27/2021 at 3:33 PM, binhex said:

 

ok try another browser, also try another host, you could also confirm deluge is running by going to the 'Terminal' via unraid web ui (the host not the container) and running the following:-

 

curl 192.168.1.120:8112

if you see output then you know the issue is connectivity from unraid to the machine running the browser.

 

Ok so I ran that command and it returned the following:

curl: (52) Empty reply from server

 

Also what's interesting now in the logs this is what is populating:

2021-08-28 20:48:08,110 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


2021-08-28 20:48:08,113 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 1433, in mainLoop
reactorBaseSelf.runUntilCurrent()
File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 972, in runUntilCurrent
f(*a, **kw)
File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 477, in callback
self._startRunCallbacks(result)
File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 580, in _startRunCallbacks
self._runCallbacks()
--- <exception caught here> ---
File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 662, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 444, in import_list

File "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 544, in auto_detect

deluge_blocklist.detect.UnknownFormatError:


2021-08-28 20:49:39,057 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '49452'

2021-08-28 21:04:39,228 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '49452'

2021-08-28 21:19:39,413 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '49452'

 

I am not sure what's going on now LOL. Any ideas? Still cannot access the webui but running curl ifconfig.io still resolves the VPN address. Other containers are still able to to open that I have passing through delugevpn such as radarr/sonarr/sabnzb which is interesting all are also resolving the correct VPN address. 

Link to comment
 
Ok so I ran that command and it returned the following:
curl: (52) Empty reply from server

 
Also what's interesting now in the logs this is what is populating:

2021-08-28 20:48:08,110 DEBG 'watchdog-script' stderr output:Unhandled error in Deferred:2021-08-28 20:48:08,113 DEBG 'watchdog-script' stderr output:Traceback (most recent call last):File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 1433, in mainLoopreactorBaseSelf.runUntilCurrent()File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 972, in runUntilCurrentf(*a, **kw)File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 477, in callbackself._startRunCallbacks(result)File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 580, in _startRunCallbacksself._runCallbacks()---  ---File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 662, in _runCallbackscurrent.result = callback(current.result, *args, **kw)File "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 444, in import_listFile "/usr/lib/python3.9/site-packages/deluge/plugins/Blocklist-1.4-py3.9.egg/deluge_blocklist/core.py", line 544, in auto_detectdeluge_blocklist.detect.UnknownFormatError:2021-08-28 20:49:39,057 DEBG 'start-script' stdout output:[info] Successfully assigned and bound incoming port '49452'2021-08-28 21:04:39,228 DEBG 'start-script' stdout output:[info] Successfully assigned and bound incoming port '49452'2021-08-28 21:19:39,413 DEBG 'start-script' stdout output:[info] Successfully assigned and bound incoming port '49452'

 
I am not sure what's going on now LOL. Any ideas? Still cannot access the webui but running curl ifconfig.io still resolves the VPN address. Other containers are still able to to open that I have passing through delugevpn such as radarr/sonarr/sabnzb which is interesting all are also resolving the correct VPN address. 

Ok that looks like deluge is crashing, try renaming the core.conf file then restart the container, this should then regenerate that file

Sent from my CLT-L09 using Tapatalk

Link to comment
On 8/27/2021 at 1:31 PM, binhex said:

yeah i appreciate you have a high speed line, but what is connected to the end of the line?, a cheap ISP router i would suffice, your Unifi Dream Machine does not come into this, as this is simply a AP, try reducing the number of connections in deluge as well, also reduce the upload rate, if its set to unlimited this will def cause issues.

 

On 8/27/2021 at 1:05 PM, binhex said:

i dont see any dns failure in the log you posted above, can you please do the following and attempt to replicate the issue https://github.com/binhex/documentation/blob/master/docker/faq/help.md

So i went through the steps in the help.md, and everything looks to work as it should now.

 

Just to note, i didnt change anything except deleting and install the container again - every container setting and Deluge setting is the same.

  • I already did have a upload limit (25mb/s)
  • 40 mb/s download limit
  • Had 100 connection limit per torrent (250 global)

Regarding the Unifi Dream Machine, i think you are mistaken - It's just not an AP, it is a full fledged router, but with a built-in and more than capable of running full 1gbit, so the issues wasn't there.

But! it works now, so that's great :) (for now at the very least)

I wonder though why just plain a old delete/install worked?

Thanks the the help @binhex

Link to comment

I've had my binhex-delugevpn container running for about a year or so now.. suddenly in the past few days I get 192.168.111.61 refused to connect (access via local LAN).  I'm a bit of a docker newb, so please let me know what info you might need to assist.

 

TIA

 

Here's my Log File: 

 

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

2021-08-31 01:44:31.524777 [info] System information Linux 53c7e0c8be09 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2021-08-31 01:44:31.580052 [info] OS_ARCH defined as 'x86-64'
2021-08-31 01:44:31.634676 [info] PUID defined as '99'
2021-08-31 01:44:31.752444 [info] PGID defined as '100'
2021-08-31 01:44:31.916102 [info] UMASK defined as '000'
2021-08-31 01:44:31.968548 [info] Permissions already set for volume mappings
2021-08-31 01:44:32.030580 [info] Deleting files in /tmp (non recursive)...
2021-08-31 01:44:32.091722 [info] VPN_ENABLED defined as 'yes'
2021-08-31 01:44:32.146326 [info] VPN_CLIENT defined as 'openvpn'
2021-08-31 01:44:32.198384 [info] VPN_PROV defined as 'custom'
2021-08-31 01:44:32.261029 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
2021-08-31 01:44:32.361116 [info] VPN remote server(s) defined as '94-1-ca.cg-dialup.net,'
2021-08-31 01:44:32.406572 [info] VPN remote port(s) defined as '443,'
2021-08-31 01:44:32.452242 [info] VPN remote protcol(s) defined as 'udp,'
2021-08-31 01:44:32.504500 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-08-31 01:44:32.556325 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-08-31 01:44:32.608175 [info] LAN_NETWORK defined as '192.168.111.0/24'
2021-08-31 01:44:32.660165 [info] NAME_SERVERS defined as '208.67.222.222,208.67.220.220,209.222.18.222,84.200.69.80,37.235.1.174,209.222.18.218,37.235.1.177,84.200.70.40'
2021-08-31 01:44:32.712107 [info] VPN_USER defined as '****'
2021-08-31 01:44:32.764029 [info] VPN_PASS defined as '****'
2021-08-31 01:44:32.816342 [info] ENABLE_PRIVOXY defined as 'yes'
2021-08-31 01:44:32.869161 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2021-08-31 01:44:32.921484 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-08-31 01:44:32.973998 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-08-31 01:44:33.036572 [info] Starting Supervisor...
2021-08-31 01:44:33,436 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-08-31 01:44:33,436 INFO Set uid to user 0 succeeded
2021-08-31 01:44:33,440 INFO supervisord started with pid 6
2021-08-31 01:44:34,443 INFO spawned: 'start-script' with pid 172
2021-08-31 01:44:34,446 INFO spawned: 'watchdog-script' with pid 173
2021-08-31 01:44:34,446 INFO reaped unknown pid 7 (exit status 0)
2021-08-31 01:44:34,456 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-08-31 01:44:34,456 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-31 01:44:34,456 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-31 01:44:34,565 DEBG 'start-script' stdout output:
[info] Adding 208.67.222.222 to /etc/resolv.conf

2021-08-31 01:44:34,572 DEBG 'start-script' stdout output:
[info] Adding 208.67.220.220 to /etc/resolv.conf

2021-08-31 01:44:34,578 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-08-31 01:44:34,584 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-08-31 01:44:34,590 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-08-31 01:44:34,596 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-08-31 01:44:34,603 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-08-31 01:44:34,609 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-08-31 01:46:24,989 DEBG 'start-script' stdout output:
[crit] '94-1-ca.cg-dialup.net' cannot be resolved, possible DNS issues, exiting...

2021-08-31 01:46:24,989 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23233414805920 for <Subprocess at 23233414807168 with name start-script in state RUNNING> (stdout)>
2021-08-31 01:46:24,989 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23233411213344 for <Subprocess at 23233414807168 with name start-script in state RUNNING> (stderr)>
2021-08-31 01:46:24,989 INFO exited: start-script (exit status 1; not expected)
2021-08-31 01:46:24,990 DEBG received SIGCHLD indicating a child quit

Link to comment
2 hours ago, JimmyOdcu said:

[crit] '94-1-ca.cg-dialup.net' cannot be resolved, possible DNS issues, exiting...

out of date vpn configuration file, re-download wireguard/openvpn config file from your vpn provider.

  • Thanks 1
Link to comment

First, thank you for the image.  I've been running it flawlessly for years.

 

I've noticed that deluge can get itself into a state where it looks like it's running:  it downloads, unarchives, webUI is up and running, and torrents show Announce OK.  But I get hit-and-run warnings from my sites.  I've tried investigating a couple of times, but the answer always seems to be "kill deluge pid".  The watchdog starts it back up again and all the warnings go away.

I know the "right" thing to do is figure out why it's hanging, but the reality is that a simple feature to restart the process every month would basically solve the problem for me.  

So, feature request:  Accept a docker param that specifies a cron string that restarts the process at a certain interval.

 

Thanks for considering it and thanks again for the image!

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.