On 11/29/2024 at 9:51 PM, SliMat said:

Hi Guys

 

I am unable to log in to deluge - I know the password, but everytime I try to log in I get an error message saying "Login Failed - You entered an incorrect password". I am not sure if the password has somehow become corrupt or someone has managed to get in and change it - but sonarr and radarr are also saying they cant connect - so I am not sure what has gone wrong.

 

I am searching for a way of resetting the password, or removing it to allow me to reconfigure the system... can anyone advise?

 

Many thanks

The Webui?

Turn off the container and go to your appdata for the container and open the web.conf.

Delete the "pwd_salt" and "pwd_sha1" variables so theyre empty like this

 

    "pwd_salt": "",
    "pwd_sha1": "",

Then start the container and you enter the webui without any password and you can set a new one


Edit: it seems like i fell trap to cookies. Damn it

The actual solution is to delete the whole "pwd_salt" & "pwd_sha1" line and then its the default password, aka deluge
 

Edited November 30, 20241 yr by Mainfrezzer

14 hours ago, Mainfrezzer said:

The actual solution is to delete the whole "pwd_salt" & "pwd_sha1" line and then its the default password, aka deluge
 

Worked perfectly - many thanks

Trying to troubleshoot why an existing install can no longer download, has been like this for around 2 days.

Startup script shows as successful on all counts... I see peers connect, then dropoff.
Changing PIA wireguard endpoints doesn't help, but I suspect its a PIA issue.

Any ideas on resolving?

Found the problem, unrelated cause

Edited December 3, 20241 yr by tjb_altf4

Trying to spin up a 2nd deluge instance. When I change the default ports and run it, no matter how I do it private / bridge / etc, it still tries to use the default deluge daemon no matter what. I cannot get it to change that.

Edited December 9, 20241 yr by Keating

On 11/29/2024 at 2:43 AM, Basgev said:

Hi all,

 

I have a strange problem with my delugevpn container for the webui and getting a IP  address. If I connect the container with the Bridge network (192.168.50.0/24) everything works fine. But if I use a costume network like custom: br2 -- Name  (192.168.70.0/24), The container will not get an IP address and there  is no port mapping. The vlan are configured the exact same way and het the same firewall rules. And other containers in the same vlan work fine.

 

Is there and config that I missed to configure?

 

using:

unraid 6.12.14

wiregaurd config

 

 

 

 

I'm having a similar issue, just updated all dockers and now binhex-delugevpn, binhex-lidarr and binhex-jacket which all run on a custom network fail to get an IP address or webui. all other containers on the custom network continue to work just fine. But switching from custom network (VPN) to host does nothing.

 

 

Nowhere in the logs does it mention a 192.168.50.xxx ip address (custom br0.50 network)

 

2024-12-08 21:44:34,379 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-12-08 21:44:35,141 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address **MY VPN EXIT IPV4**

2024-12-08 21:44:35,142 DEBG 'start-script' stdout output:
[info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment

2024-12-08 21:44:35,178 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP **MY VPN IPV4** different, marking for reconfigure

2024-12-08 21:44:35,180 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2024-12-08 21:44:35,182 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2024-12-08 21:44:35,184 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2024-12-08 21:44:35,185 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2024-12-08 21:44:35,293 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '**MY VPN IPV4**'
[info] Deluge key 'listen_interface' will have a new value '**MY VPN IPV4**'
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-12-08 21:44:35,408 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'...

2024-12-08 21:44:35,533 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'xxxxxxxxxxxxxxxxx'
[info] Deluge key 'default_daemon' will have a new value 'xxxxxxxxxxxxxxx'
[info] Writing changes to Deluge config file '/config/web.conf'...

2024-12-08 21:44:35,555 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2024-12-08 21:44:35,772 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2024-12-08 21:44:36,978 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1471d99422d0 current result: None>

2024-12-08 21:44:37,011 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2024-12-08 21:44:37,011 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2024-12-08 21:44:37,012 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2024-12-08 21:44:37,012 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2024-12-08 21:44:38,015 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2024-12-08 21:44:38,018 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Edited December 9, 20241 yr by jevan223

On 5/5/2024 at 8:03 PM, THF13 said:

The 2.1.1-5-01 update broke my YaRSS2 plugin.  I tried a few different versions of the egg and ways to name it, since it can be a bit fussy, but was unable to get it to enable.  Rolled back to 2.1.1-4-09 and it's working there.  

Yes! Thankyou, have been pulling my hair out with this for months, did not think to rollback docker version. Hopefully the plugin will get updated to work with newer builds.

On 12/9/2024 at 12:16 PM, jevan223 said:

 

I'm having a similar issue, just updated all dockers and now binhex-delugevpn, binhex-lidarr and binhex-jacket which all run on a custom network fail to get an IP address or webui. all other containers on the custom network continue to work just fine. But switching from custom network (VPN) to host does nothing.

 

 

Nowhere in the logs does it mention a 192.168.50.xxx ip address (custom br0.50 network)

Unraid bug that's been around for years, it was fixed in 7.0.0-beta4.
Note that its only cosmetic, IPs are assigned and can be confirmed in container shell using ifconfig

bug info here

 

Hello, I'm unable to get  deluge started. I select it to start and then it still doesnt run.

log post somethen about needing root access. how can i fix?

 

2024-12-29 09:57:03.630478 [info] Host is running unRAID
2024-12-29 09:57:03.665275 [info] System information: Linux f0e1f52cdfa8 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
2024-12-29 09:57:03.704186 [info] Image tags: BASE_RELEASE_TAG=2024122301,INT_RELEASE_TAG=2024122301,IMAGE_RELEASE_TAG=2.1.1-8-03
2024-12-29 09:57:03.748600 [info] PUID defined as '99'
2024-12-29 09:57:03.851624 [info] PGID defined as '100'
2024-12-29 09:57:03.979097 [info] UMASK defined as '000'
2024-12-29 09:57:04.019746 [info] Permissions already set for '/config'
2024-12-29 09:57:04.072243 [info] Deleting files in /tmp (non recursive)...
2024-12-29 09:57:04.132440 [info] VPN_ENABLED defined as 'yes'
2024-12-29 09:57:04.177262 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn'
2024-12-29 09:57:04.223295 [info] VPN_PROV defined as 'custom'
2024-12-29 09:57:04.283710 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca1465.nordvpn.com.udp.ovpn
2024-12-29 09:57:04.399649 [info] VPN remote server(s) defined as '37.19.213.142,'
2024-12-29 09:57:04.438394 [info] VPN remote port(s) defined as '1194,'
2024-12-29 09:57:04.478018 [info] VPN remote protcol(s) defined as 'udp,'
2024-12-29 09:57:04.521848 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-12-29 09:57:04.566743 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-12-29 09:57:04.608373 [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'
iptables v1.8.10 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
2024-12-29 09:57:04.656396 [crit] iptables default policies not available, exiting script...

23 hours ago, diehard2k9 said:

Hello, I'm unable to get  deluge started. I select it to start and then it still doesnt run.

log post somethen about needing root access. how can i fix?

 

2024-12-29 09:57:03.630478 [info] Host is running unRAID
2024-12-29 09:57:03.665275 [info] System information: Linux f0e1f52cdfa8 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
2024-12-29 09:57:03.704186 [info] Image tags: BASE_RELEASE_TAG=2024122301,INT_RELEASE_TAG=2024122301,IMAGE_RELEASE_TAG=2.1.1-8-03
2024-12-29 09:57:03.748600 [info] PUID defined as '99'
2024-12-29 09:57:03.851624 [info] PGID defined as '100'
2024-12-29 09:57:03.979097 [info] UMASK defined as '000'
2024-12-29 09:57:04.019746 [info] Permissions already set for '/config'
2024-12-29 09:57:04.072243 [info] Deleting files in /tmp (non recursive)...
2024-12-29 09:57:04.132440 [info] VPN_ENABLED defined as 'yes'
2024-12-29 09:57:04.177262 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn'
2024-12-29 09:57:04.223295 [info] VPN_PROV defined as 'custom'
2024-12-29 09:57:04.283710 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca1465.nordvpn.com.udp.ovpn
2024-12-29 09:57:04.399649 [info] VPN remote server(s) defined as '37.19.213.142,'
2024-12-29 09:57:04.438394 [info] VPN remote port(s) defined as '1194,'
2024-12-29 09:57:04.478018 [info] VPN remote protcol(s) defined as 'udp,'
2024-12-29 09:57:04.521848 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-12-29 09:57:04.566743 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-12-29 09:57:04.608373 [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'
iptables v1.8.10 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
2024-12-29 09:57:04.656396 [crit] iptables default policies not available, exiting script...

post screenshots of your container config - unraid webui/docker/left click container and select edit then screenshot all settings and post here, ensure you  remove the username and password for your vpn provider.

On 12/30/2024 at 9:54 AM, binhex said:

post screenshots of your container config - unraid webui/docker/left click container and select edit then screenshot all settings and post here, ensure you  remove the username and password for your vpn provider.

ok, last line key 13 is 100

not sure why it wont start.

Thank for the help in advance.

3 hours ago, diehard2k9 said:

ok, last line key 13 is 100

not sure why it wont start.

Thank for the help in advance.

you have set privileged mode toggle to off, the default is on.

1 hour ago, binhex said:

you have set privileged mode toggle to off, the default is on.

I didnt make any changes but I have urned it on and it runs but I cant connect to it.

8 hours ago, diehard2k9 said:

I didnt make any changes but I have urned it on and it runs but I cant connect to it.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Can anyone help with this error that randomly appeared today : 

 

'watchdog-script' stderr output:
/usr/lib/python3.13/site-packages/pkg_resources/__init__.py:1490: UserWarning: Extraction path is writable by group/others and vulnerable to attack when used with get_resource_filename (/config/python-eggs). Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
  warnings.warn(msg, UserWarning)

 

If anyone is having the same issue the following worked under docker command line:

chmod g-wx,o-wx /config/python-eggs

Edited January 5, 20251 yr by Random Mike

Hey guys, is there a way to show a Date Added and Date Completed on Deluge? 

I'm seeding torrents for x amount of days and i'd like to see the info on the client. I'm seeding a couple of torrents so it would be too hard to determine which is old and recent. 

 

Thanks! 

41 minutes ago, bloom_server said:

Hey guys, is there a way to show a Date Added and Date Completed on Deluge? 

I'm seeding torrents for x amount of days and i'd like to see the info on the client. I'm seeding a couple of torrents so it would be too hard to determine which is old and recent. 

 

Thanks! 

Sure, just click the "arrow" on one of the columns,select columns and add whatever you like. You may need to adjust the size of the columns by dragging them to get the new ones to appear.

32 minutes ago, strike said:

Sure, just click the "arrow" on one of the columns,select columns and add whatever you like. You may need to adjust the size of the columns by dragging them to get the new ones to appear.

You're awesome, thank you kindly good sir.

after updating to unraid 7 i've noticed deluge crashing constantly.

it could also have to do with changes in the *arrs since i keep them up to date but i'm not sure since i am unable to reproduce the crashes consistently.

 

After these "crashes" (the thinclient disconnects and i am unable to instantly reconnect, and a bunch of torrents get paused) it doesn't seem like the docker container itself is what is restarting but deluge within the container is whats restarting.

 

this is also causing all the *arrs to be unable to connect to the client and i have to manually restart the delugevpn docker container for the *arrs to be able to access it again.

 

here are some errors that i can see in the docker log for delugevpn

 

2025-01-21 10:54:07,833 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/deluge/decorators.py", line 200, in addCallbacks
    self.activate()
  File "/usr/lib/python3.13/site-packages/deluge/decorators.py", line 192, in activate
    d = defer.Deferred.fromCoroutine(self.coro)
  File "/usr/lib/python3.13/site-packages/twisted/internet/defer.py", line 1326, in fromCoroutine
    return _cancellableInlineCallbacks(coro)
  File "/usr/lib/python3.13/site-packages/twisted/internet/defer.py", line 2172, in _cancellableInlineCallbacks
    _inlineCallbacks(None, gen, status, _copy_context())
--- <exception caught here> ---
  File "/usr/lib/python3.13/site-packages/twisted/internet/defer.py", line 2003, in _inlineCallbacks
    result = context.run(gen.send, result)
  File "/usr/lib/python3.13/site-packages/deluge/core/core.py", line 772, in get_torrents_status
    torrent_ids = self.filtermanager.filter_torrent_ids(filter_dict)
  File "/usr/lib/python3.13/site-packages/deluge/core/filtermanager.py", line 179, in filter_torrent_ids
    status = self.core.create_torrent_status(
  File "/usr/lib/python3.13/site-packages/deluge/core/core.py", line 734, in create_torrent_status
    status = self.torrentmanager[torrent_id].get_status(
  File "/usr/lib/python3.13/site-packages/deluge/core/torrent.py", line 1036, in get_status
    for key in keys:
builtins.TypeError: 'Core' object is not iterable


2025-01-21 11:02:41,138 DEBG 'start-script' stdout output:

 

2025-01-21 11:39:34,291 DEBG 'watchdog-script' stderr output:
Fatal Python error: _PyEval_EvalFrameDefault: Executing a cache.
Python runtime state: initialized

Thread 0x000014683a6ff6c0 (most recent call first):
  File "/usr/lib/python3.13/threading.py", line 359 in wait
  File "/usr/lib/python3.13/queue.py", line 202 in get
  File "/usr/lib/python3.13/site-packages/twisted/_threads/_threadworker.py", line 48 in work
  File "/usr/lib/python3.13/threading.py", line 992 in run
  File "/usr/lib/python3.13/threading.py", line 1041 in _bootstrap_inner
  File "/usr/lib/python3.13/threading.py", line 1012 in _bootstrap

Current thread 0x00001468a1de1b80 (most recent call first):
  File "/usr/lib/python3.13/site-packages/deluge/core/filtermanager.py", line 200 in get_filter_tree
  File "/usr/lib/python3.13/site-packages/deluge/core/core.py", line 789 in get_filter_tree
  File "/usr/lib/python3.13/site-packages/deluge/core/rpcserver.py", line 334 in dispatch
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 1090 in runUntilCurrent
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 705 in mainLoop
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 695 in run
  File "/usr/lib/python3.13/site-packages/deluge/core/daemon.py", line 161 in start
  File "/usr/lib/python3.13/site-packages/deluge/core/daemon_entry.py", line 119 in run_daemon
  File "/usr/lib/python3.13/site-packages/deluge/common.py", line 1355 in run_profiled
  File "/usr/lib/python3.13/site-packages/deluge/core/daemon_entry.py", line 138 in start_daemon
  File "/usr/bin/deluged", line 8 in <module>

Extension modules: zope.interface._zope_interface_coptimizations
2025-01-21 11:39:34,291 DEBG 'watchdog-script' stderr output:
, _dbus_bindings, libtorrent, _cffi_backend, GeoIP, rencode._rencode (total: 6)

2025-01-21 11:40:02,744 DEBG 'watchdog-script' stderr output:
/home/nobody/watchdog.sh: line 281:   714 Aborted                 nohup /usr/bin/deluged -d -c /config -L "${DELUGE_DAEMON_LOG_LEVEL}" -l /config/deluged.log

2025-01-21 11:40:02,771 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

 

2025-01-20 06:12:27,023 DEBG 'watchdog-script' stderr output:
Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/deluge/common.py", line 1355, in run_profiled
    return func(*args)
  File "/usr/lib/python3.13/site-packages/deluge/core/daemon_entry.py", line 119, in run_daemon
    daemon.start()
  File "/usr/lib/python3.13/site-packages/deluge/core/daemon.py", line 161, in start
    reactor.run()
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 695, in run
    self.mainLoop()
--- <exception caught here> ---
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 705, in mainLoop
    self.runUntilCurrent()
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 1074, in runUntilCurrent
    self._insertNewDelayedCalls()
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 1020, in _insertNewDelayedCalls
    heappush(self._pendingTimedCalls, call)
  File "/usr/lib/python3.13/site-packages/twisted/internet/base.py", line 225, in __lt__
    if isinstance(other, DelayedCall):
builtins.TypeError: 'async for' requires an object with __aiter__ method, got bool

 

Even with all the *arrs offline i'm getting this error in the logs every now and then which crashes deluge

2025-01-22 21:09:28 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA256, peer temporary key: 253 bits X25519

2025-01-22 21:17:46,101 DEBG 'watchdog-script' stderr output:
/home/nobody/watchdog.sh: line 281:  1818 Segmentation fault      nohup /usr/bin/deluged -d -c /config -L "${DELUGE_DAEMON_LOG_LEVEL}" -l /config/deluged.log

2025-01-22 21:17:46,127 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2025-01-22 21:17:46,134 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

 

Edited January 22, 20251 yr by MammothJerk

I'm using PIA and I've recently acquired a static IP address from PIA. First, does Deluge support using my static IP address, and if so, where would I put my PIA static IP token? TIA!

3 hours ago, Jake89 said:

I'm using PIA and I've recently acquired a static IP address from PIA. First, does Deluge support using my static IP address, and if so, where would I put my PIA static IP token? TIA!

Nope there is no support for PIA static IP addresses.

So for some unknown reason my downloads have started crawling or just stalling. There are lots of peers so I don't think that's it. Also I tried downloading something again from a week or so ago and it's crawling. Any ideas? Let me know if I can add logs or something.

Hi,

For the life of me, i can't get wireguard to work with PIA either with Deluge or Qbitorrent. Everything should be correct and it works perfect with openvpn but the speeds are slow. It works with VPN off also.

 

The problem is the UI goes to 'This Site Can't Be Reached', even though in the logs it looks like the UI should be started. 

 

Any chance someone could point me in the right direction with this? I've configured the wg0 to the closet region but still no luck.

 

[info] france.privacy.network
[info] slovenia.privacy.network
[info] mexico.privacy.network
[info] ro.privacy.network
[info] au-australia-so.privacy.network
[info] nl-netherlands-so.privacy.network
[info] bo-bolivia-pf.privacy.network
[info] nigeria.privacy.network
[info] fi-2.privacy.network
[info] liechtenstein.privacy.network
[info] ae.privacy.network

2025-01-23 12:47:15,627 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31894'

2025-01-23 12:47:15,925 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.39.250.204 different, marking for reconfigure

2025-01-23 12:47:15,930 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2025-01-23 12:47:15,935 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2025-01-23 12:47:15,939 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2025-01-23 12:47:15,940 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 31894 different, marking for reconfigure

2025-01-23 12:47:15,942 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2025-01-23 12:47:16,397 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.20.254.102'
[info] Deluge key 'listen_interface' will have a new value '10.39.250.204'
[info] Writing changes to Deluge config file '/config/core.conf'...

2025-01-23 12:47:16,699 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'...

2025-01-23 12:47:16,992 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '2648ae8965e349d6ae20ad931f3fddff'
[info] Deluge key 'default_daemon' will have a new value '2648ae8965e349d6ae20ad931f3fddff'
[info] Writing changes to Deluge config file '/config/web.conf'...

2025-01-23 12:47:17,049 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2025-01-23 12:47:17,588 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2025-01-23 12:47:20,249 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2025-01-23 12:47:20,249 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14a58a2c4190 current result: None>

2025-01-23 12:47:22,948 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (31894, 31894)
Configuration value successfully updated.

2025-01-23 12:47:22,948 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14bf8b9bc190 current result: None>

2025-01-23 12:47:25,648 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1501e48ac190 current result: None>

2025-01-23 12:47:25,737 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2025-01-23 12:47:25,738 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2025-01-23 12:47:25,740 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2025-01-23 12:47:26,751 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2025-01-23 12:47:26,757 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

On 1/22/2025 at 7:47 PM, downloadedskill said:

So for some unknown reason my downloads have started crawling or just stalling. There are lots of peers so I don't think that's it. Also I tried downloading something again from a week or so ago and it's crawling. Any ideas? Let me know if I can add logs or something.

Anyone have thoughts on this? I even changed the location to another that supports port forwarding. 

4 hours ago, downloadedskill said:

Anyone have thoughts on this? I even changed the location to another that supports port forwarding. 

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

No *arrs running, no webuis connected, no thinclients connect, still crashes.

this time "aborted" instead of "segmentation fault" though.

 

also not sure if this is the cause of the crash or the reaction to the crash...

 

Extension modules: zope.interface._zope_interface_coptimizations, _dbus_bindings, libtorrent, _cffi_backend, GeoIP, rencode._rencode (total: 6)

2025-01-24 22:37:10,910 DEBG 'watchdog-script' stderr output:
/home/nobody/watchdog.sh: line 281:  6605 Aborted                 nohup /usr/bin/deluged -d -c /config -L "${DELUGE_DAEMON_LOG_LEVEL}" -l /config/deluged.log

2025-01-24 22:37:10,942 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2025-01-24 22:37:10,949 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...