GOT IT! Thanks!

Right so the service setup is fine. Reviewing you prior message you mentioned previously you added the user pi in auth Please copy the output of sudo cat /var/lib/deluge/.config/deluge/auth Modifying the auth file is intended for Web access, not deluge-console straight from the server on ssh (or te...

sudo systemctl status deluged results: deluged.service Loaded: loaded (/etc/systemd/system/deluged.service) Active: active (running) since Mon 2017-08-14 18:00:54 EDT; 1 day 1h ago Main PID: 1921 (deluged) CGroup: /system.slice/deluged.service └─1921 /usr/bin/python /usr/bin/deluged -d -l /var/log/...

You stopped the service with the start command? Did you restart the service before trying to connect? Ugh, I pasted wrong. Edited. I stopped it with the stop command. And yeah, restarted the service. See below. :) Regarding the relevant prior comment what about: sudo bash sudo -u deluge deluge-cons...

Alright. I stopped the service with sudo systemctl stop deluged , renamed /var/lib/deluge/.config/deluge Then I added my login to the auth file in /var/lib/deluge/.config/deluge like so: pi:(password):10 Now when I try to launch deluge-console, I get: Failed to connect to 127.0.0.1:58846 with reason...

Hi djmattb241 Do you still have copy to the problematic Deluge profile for testing purpose? did you tried to launch the deluge-console with the daemon"s user (sudo -u $user deluge-console) You can always rename the profile, start deluge so a new one is created, then stop it and copy the "...

Hi all, I've been banging my head against this for like a week now. I had deluge, with the daemon, the GTK UI, and the web console, installed and working great. Then I changed the password on my user account on the raspberry pi, and now when I try to connect to the CLI, I get: Failed to connect to 1...