Can't connect to daemon after restart

[Protected]

Hi there. I've had a daemon-thin client setup that has been running just fine for years. Recently, someone accidentally restarted the daemon, and ever since people have been unable to connect to it. The server's uptime was just a few months. I made no manual changes to the setup.

Whenever I attempt to connect from my Windows client, I see the "Password is required" prompt dialog for entering my username and password. Upon entering the correct username and password and clicking "Connect", the same dialog appears again, and no connection is established.

Originally I had the client from three years ago installed. I upgraded to this year's release (2.2.0), but nothing has changed. I'm on Windows 10. No third party security software is running. I am not on a VPN.

In the daemon's log file, only this is logged (once per connection attempt):

(timestamp) [INFO ][deluge.core.rpcserver :1622] Deluge Client connection made from: (ip address):(port)
(timestamp) [INFO ][deluge.core.rpcserver :1622] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.

Even if I set the log level to "debug", nothing else is logged pertaining to the connection attempt. There are no errors whatsoever in the log file from the moment the daemon starts running. There are normal log messages that describe the daemon's normal start up process.

The server is running Debian 12 "bookworm" .

deluged -v
deluged 2.2.0
libtorrent: 2.0.8.0
Python: 3.11.2
OS: Linux 6.1.0-31-amd64

Could anyone please help me sort this out? Do you need any more information?

[charliebrown33]

basketball starsIt sounds like the daemon’s auth or hostlist config may have reset after restart - try re-adding your client’s IP in `~/.config/deluge/auth` and checking that `allow_remote` is set to `true` in `core.conf`.