Re: Fedora 34 - Deluge Daemon 2.0.3 lies about port being in use by another service
Posted: Mon Nov 01, 2021 10:12 pm
Strange, yes I could connect here, without that option also. Hope you succede, good luck 
Edit: Just in case, in webui open preferences and enable remote connections.
Also you could try add e.g test:test:10 to auth of deluge profile and connect with those creds.
You can also delete profile dirs and start fresh.
Last, official guide states also:
"Accessing deluged service with local UI Client ΒΆ
When attempting to access a daemon deluged on the same machine but running as a different user e.g. your login user is user and deluged is running as deluge, you may be unable access to deluged. This is due to the client automatically authorising using the localhost line in the auth file, which is assumed to be at the same config location as deluged.
The workaround is to replace the localclient line in your user config auth file (~/.config/deluge/auth) with the localclient line from the deluged config auth file e.g. /var/lib/deluge/auth."
Source: https://dev.deluge-torrent.org/wiki/Use ... ThinClient

Edit: Just in case, in webui open preferences and enable remote connections.
Also you could try add e.g test:test:10 to auth of deluge profile and connect with those creds.
You can also delete profile dirs and start fresh.
Last, official guide states also:
"Accessing deluged service with local UI Client ΒΆ
When attempting to access a daemon deluged on the same machine but running as a different user e.g. your login user is user and deluged is running as deluge, you may be unable access to deluged. This is due to the client automatically authorising using the localhost line in the auth file, which is assumed to be at the same config location as deluged.
The workaround is to replace the localclient line in your user config auth file (~/.config/deluge/auth) with the localclient line from the deluged config auth file e.g. /var/lib/deluge/auth."
Source: https://dev.deluge-torrent.org/wiki/Use ... ThinClient