Can't connect to Deluged daemon from GTK client

[naugrim]

Hey all,

I'm about at my wits end trying to figure this out. I just can't seem to connect to the Deluged daemon when i use the GTK client, i just get the username and password prompt over and over. I am running a debian 12 virtual machine in proxmox 7.4-18, and i installed deluge 2.1.1 using the instruction I found in the second post here
viewtopic.php?p=237912&hilit=bookworm#p237912.

I added the Deluge PPA and installed deluge, deluged, deluge-web, deluge-console.

deluge --version
deluge 2.1.1
libtorrent: 2.0.8.0
Python: 3.11.2
OS: Linux 6.1.0-23-amd64

I created the systemd serivices with user.conf override files as described here
https://deluge.readthedocs.io/en/latest ... rvice.html

I can connect successfully using deluge-web (using the default deluge password and changing when prompted) and deluge-console, but every time I try to connect using the gtk client (I think that's what it's called) it just keeps prompting me for the username and password but no error or anything to indicate if I'm entering something incorrectly.

I found deluge folders in the typical locations /var/lib/deluge and /var/log/deluge but I also found a .config folder in /root/deluge which I though was odd, and it contained an auth file so I entered the credentials in there too as well as in the /var/lib/deluge/.config/deluge/auth but still not accepting the credentials.

I have another instance of deluged 2.0.3 running in an older virtual machine which is going to be replaced by this new one I'm building. Knowing that it wasn't interfering I still shut it down and tested the connection and still won't accept the credentials. I have a firewall running in the vm, but even after disabling it, it still won't accept the credentials.

I don't know what else to do short of trashing the vm and starting from scratch.

Anyone out there that might be able to help.

[mhertz]

It's only /var/lib/deluge/.config/deluge/auth when starting deluged from systemd using official docs, and make sure deluged stopped when entering user:pass:10 in auth, and enable allow_remote = true in /var/lib/deluge/.config/deluge/core.conf also with deluged closed and then start deluged systemd service and try again.

Else run deluged with error logging, e.g instead of from systemd, then sudo -u deluge -L error -l /tmp/deluged.log etc.

Edit: And/or deluge -L error -l /tmp/deluge.log.

[naugrim]

Unfortunately i'm not able to execute either of those commands, as it's giving me an error sudo: invalid option "L".

I enabled logging from the systemd service file but nothing shows up in the log file when using the log level of error.

I changed it to debug to see if i could capture more info and this shows up when i try to establish a connection
06:51:44 [DEBUG ][deluge.core.rpcserver :1622] intevents: {}
06:51:44 [INFO ][deluge.core.rpcserver :1622] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
06:51:44 [INFO ][deluge.core.rpcserver :1622] Deluge Client connection made from: 192.168.2.5:59128
06:51:44 [DEBUG ][deluge.core.rpcserver :1622] RPC dispatch daemon.login

Waiting around for my message to be posted, idecided to try to build a new vm and start with deluged and nothing else that might get in my way and it works on the new vm, not sure what i did to mess things up in the other one.

Thanks for your help anyway, i appreciate it.

[asensio]

I have the same issue.

I have been using deluge for years and the only thing i needed to do was to install deluged, deluge-web, deluge-gtk, copy the deluge folder into my /.config, the services to /etc/systemd/system/ and it was up and running. Since I upgraded to ubuntu 24.04 and installed deluge 2.1.2.dev0 i can't connect to the gtk GUI, i'm constantly beeing prompted for the localclient password.

On the webUI everything seems to be working, I was even able to change the password for the webUI (although every folder config on the daemon seems to point to /var/lib/deluged/Downloads, for some reason)

Tried uninstalling everything and start from scratch, following these:
https://deluge-torrent.org/userguide/thinclient/
https://deluge.readthedocs.io/en/latest ... rvice.html
https://linuxconfig.org/set-up-a-headle ... r-on-linux
https://www.linuxbabe.com/ubuntu/instal ... untu-20-04

but I always get some errors on the commands along the way that make it impossible to continue. At this point i dont even know why the service files are located in /usr/lib/systemd/system/ or if they are installed with deluged

Is there anywhre a simple guide to follow to make deluge work again as normal?
Any pointers will be much appreciated
ASENSIO

EDIT: seems to be connectiong to different servers, the GTK doesnt connect, from the browser connects to one server, from my phoe using a 3rd party app seems to connect to another

EDIT2: only way to get it to work as before was to delete the services and make a script to start deluged and deluged-web at startup and not as a service

[mhertz]

Debian/ubuntu (annoyingly) enables a service just by mere installing it, so already is added and enabled btw.

The services are installed, and can be run manually, from /usr/lib/systemd/system - enabling such service, symlinks it into /etc/systemd/system/<target>.

Make sure deluged stopped when making changes so 'sudo systemctl stop deluged'. Sometimes needs 'sudo systemctl daemon-reload' so can do that just in case too.

Default path usually is /var/lib/deluge/.config/deluge, where you edit 'auth' file to add users, however the default Debian package atleast in older times setup by default to be ran by user called Debian-deluged and cannot remember from top of head now honestly, but probably would have that path then also as /var/lib/debian-deluged/.config/deluge.

So, atleast in older times needed decide if wanting use that setup they ship by default(Debian-deluged user and path) or change to the more standard one stated in the official docs(deluge user and regular path).

You can check which user defined for deluge to run under, through e.g systemctl cat deluged.

Sorry little confusing and hard to explain.

Btw, if wanting login to deluge as localclient in gtk-ui, when using systemd, then can copy over hostlist.conf and auth just in case, from /var lib/deluge/.config/deluge, or /var/lib/debian-deluge/.config/deluge, and into ~/.config/deluge.

Edit: I just quickly downloaded the latest deluged package for debian sid, I think ubuntu uses straight unmodded deb packages for deluge if remember right - not sure if you though use PPA. but would install repo version regardless if newer in version number. Anyway I extracted the deb package locally and peeked into it, and they indeed use debian-deluged user, though see added with the path almost like official docs, though with added 'd', so /var/lib/deluged/.config/deluge(they also did that in older times I just now recollect).