[SOLVED] thinclient not connecting to daemon BadLoginError

[caravaggio971]

I'm posting this in case someone is facing the same problem.
Case scenario:
You installed deluged and deluge-web (v.13.12). on your Ubuntu 16.04 Server and it works. Deluge client (thin client mode (v.13.12)) instead returns an error when trying to connect to the daemon (BadLoginError: Username does not exist).

After helplessly googling for a couple of days I was finally able to find a solution to what I guess is a Deluge bug that occurs when you create the config files (running the command

Code: Select all

deluged

and the auth file typing

Code: Select all

echo "user:password:10" >> ~/.config/deluge/auth

.
Apparently deluged creates 2 different config folders and 2 auth files in /home/user/.config/deluge and another one in /var/lib/deluge/.config/deluge and also 2 different core.conf files in the same directories.
The thinclient points to the auth file in the /var directory whereas the user details are stored in your home directory with the result that the client cant connect cause it cant find the user.
How I solved it:
Stop the deamon

Code: Select all

sudo systemctl stop deluged
sudo systemctl stop deluge-web

move your auth file in your home directory to the var directory

Code: Select all

sudo mv /home/user/.config/deluge/auth /var/lib/deluge/.config/deluge/auth

Remove the deluge directory and all its files in your home folder.

Code: Select all

sudo rm -r /home/user/.config/deluge

Edit the core.conf file

Code: Select all

sudo nano /var/lib/deluge/.config/deluge/core.conf

find

Code: Select all

"allow_remote": false,

and change it to

Code: Select all

"allow_remote": true,

Save it and exit;
Make sure that the auth file has been moved to the var directory and that contains the user and pwd you previously created.
start the deamon

Code: Select all

sudo systemctl start deluged
sudo systemctl start deluge-web

Open deluge client create a new connection pointing to your web server IP address, port 58846, your user and passwrd. Restart (Ctrl + Q) deluge client and at that point it should finally connect.

Cheers

[Cas]

This is all covered in http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

[caravaggio971]

Well the wiki is not so straight forward as you point out. Following the wiki I got to a dead end and I'm pretty sure many others did too and gave up installing deluge. The wiki is cryptic in certain parts and it takes for granted that you already know the deluge architecture and how it works.
You should consider that people installing this nice piece of software are not all tech savvy (this is my case) and that the command line is something mysterious and unknown. I used to have transmission installed but compared to deluge is too basic. Nevertheless Installing transmission was very easy, on the contrary deluge thin client a nightmare and it still needs to be tuned.

Thanks for your help anyway.

[shamael]

I guess you followed the guide http://dev.deluge-torrent.org/wiki/User ... ce/systemd ? If not below info may not be relevant

The new profile comes from the "deluge" user creation running the daemon and having its home folder in /var/lib/deluge deluge

Code: Select all

sudo adduser --system  --gecos "Deluge Service" --disabled-password --group --home /var/lib/deluge deluge

Anyway copying the auth file to the correct location as you did will help accessing the deluge-console on your server, the first line key is needed to avoid connection error. Starting then you can access it with

Code: Select all

sudo -u deluge deluge-console

if your restricted the access to deluge user only.

I faced an issue with the web UI in 1.3.13 too (same thing as above in fact), details here http://forum.deluge-torrent.org/viewtop ... =7&t=49127 for the records.

Enjoy the SW