BillClinton

Hi Guys, Thanks for keeping an eye on this. I have had the server webgui lock up and muy deluge becomes unresponsive. I changed a couple of settings on deluge as the cache wasn't big enough. but the lock up still happened. Here is the latest Diagnostics and the syslog as well syslog-192.168.88.242.log tower-diagnostics-20240118-1750.zip

Thanks JorgeB I’ll enable that when I’m back from holiday in a couple of weeks. As a an FYI, the server webgui is inaccessible again. I update the post when I have the syslog info.

Hi Guys, I have had this issue happen a few times over the last couple of months. After a while the WebGUI becomes unresponsive and I am unable to log in and it times out. I can PING the server fine. All dockers are working in this last lock up. All accessable via their WebGUIs. My Ubuntu VM is still working as I have Twingate working in the VM and still accessible. I have trouble starting my Windows 10 VM via WOL (it is running on a Passed Through NVME) Can someone with better knowledge take a look over my diagnostics please. If you need anymore info, please let me know. tower-diagnostics-20231220-2242.zip

Only other thing I can think of is the certificate in Jacketts app data is old or balked. See if you can flush the old one.

It might be Telstra blocking that website. I know Australia has cracked down on torrent sites. Have you tried connecting to hd-torrents via your browser? Only solution is either to find another torrent site, or switch internet providers, or set up a vpn.

I use 2 dockers for historical info. Netdata for fine details. Munin for long term stats history.

I had system hangs with this as well. It was from mono running away with my ram. In the end I limited the ram to this docker to just 1GB.

A bit of a shot in the dark; Have you tried /config -> /mnt/cache/apps/radarr Instead of /config -> /mnt/user/apps/radarr

This happens to me sometimes when I stop and restart the container too quickly. Eg stopping it just after starting the container, interrupting the torrent ‘resume’ process. There is a ‘state’ folder in the appdata which you can use to get it going. You’ll just have to re-add the torrents manually. You might have to add them in a paused state and make sure they are pointing to the right folder where your completed and not completed are kept. Then you’ll have to get them all to rescan for files. Could take a while.

You need to specify a build number within the edit docker page. In the repository field, add build number after linuxserver/deluge:XXX put in a number from the docker webpage -> tags. Click link in docker containers webgui Eg: “By:Linuxserver/deluge:latest”

Assuming you have all the original files still (including but not limited to all files have exactly the original file name) you put files back into completed directory, add .torrent file back to deluge IN A PAUSED STATE. Ensure that torrent is pointing to correct directory in details window. Tell deluge to recheck torrent. Make sure it sees most if not all files are complete 100% If all good start torrent. I hope this is clear

Got some links to that please? doing some general googling I found these links of others in the deluge world with similar issues. Hope this helps https://github.com/arvidn/libtorrent/issues/2857 https://dev.deluge-torrent.org/ticket/3153 https://forum.deluge-torrent.org/viewtopic.php?p=227823 if this is unclear, please forgive my noobish research.

Same problems here. A short term solution is to specify build 113 in the Docker setup. In repository it looks like Linuxserver/deluge:113 It works for me so far.

Following the info in the first post set up a new path in the docker setup page like this:

Thanks for the clarification.