Deluge Forum

Hi,
I have set up Deluge(v2.1.1, Libtorrent v2.0.6.0) as a server-client on Windows 10. Been running like this for over 4 years without any issues but for the past few weeks the Web-GUI has been taking a long time to start up, which it never used to. It takes about 30~40 seconds to start after the daemon is started. Sometimes it takes even longer. I(Sonarr and Radarr also) can't access Deluge with the browser or thin-client at that time. I have around 70~80 torrents at seeding.
Here is the log of Deluge Daemon and Deluge Client. https://mega.nz/folder/E49yyK6Q#ZMlIagkFjvZzXRe1H0Vjcw

Also having problems connecting to Sonarr and Radarr after the Web-GUI is started. Randomly Sonarr and Radarr got disconnected saying
"Unable to retrieve queue and history items from Deluge: No connection could be made because the target machine actively refused it. (localhost:8112)"
and then auto reconnected within a minute. Sonarr and Radarr are on the same PC.
https://imgur.com/BgUWQ1C

Thanks in advance.

Sorry dunno, would self re-setup fresh(rename old profile to end in bak with all deluge components closed. Just see you have several hosts in hostlist.conf, one fails imidiatelly and other then used, and maybe just delete and make deluge generate anew hostlist.conf and auth, and add to them afterwards, from deluge or manually. I would also just to test hardcode my local IP in deluge settings for in/out - I have instructions somewhere here for obtaining guid to input instead, but easier just use own local ip for testing. If you have external firewall or vpn then try disable, for troubleshooting if related. You have lots dns and connection errors and 10049 error for malformed connection, or non-existant ip, though you use localhost I see. Also try libtorrent 1.2.x instead imho.
Sorry no propper help, but just what I would start with.