Deluge Forum

Has anyone gotten deluge daemon to work in 16.04?

I've followed your (Deluge's) guide and tried to piece together numerous guides, forum posts, etc. to get it to work. Still nada.

I end up with directories owned by "debian-deluge", config files in obscure places, and I can't seem to sort it out. I'm not extremely well versed in the art of Linux, but I can get around. But I can't seem to get it working at all.

I know there's been alot of issues with the switch from upstart to systemd. I'm pretty sure thats where the problems come from.

To start: Running Ubuntu Server 16.04 (headless)

- Follow Deluge's guide to setting up Deluged (Daemon only for thin client access)
- I can get the Daemon running with systemd, status is green and running.
- Can't connect with thin client.
- Can't connect deluge-console locally, error's bounce between "connection refused" to "invalid user"
- I've found all my conf files in /var/lib/deluge/.config/deluge/ (core.conf, auth.conf etc.)
- but not in the normal directories, I.E. ~/.config/deluge (those are normal for me, as I've been running Deluge on headless servers for several years), the really strange part is the phantom user, "debian-deluge" that owns all those directories.

Theres nothing in any logs I can show, as no logs are generated, that I can find anyways.

I guess, what I need, is a solid guide, or a guide to fix the above issues. I've spent many hours trying to sort it. 3 fresh OS installs (I consider it part of the learning process:)), lots of reading, changing ownership/permissions. Undoing what I changed, etc.

Or, if I'm being ignorant to the problem, please let me know. Although reading through forums and comment sections of existing guides, I'm not the only one:)

Thanks for any and all input.

Did you read this post: http://forum.deluge-torrent.org/viewtop ... 12#p224285

Make sure any init installed by ubuntu deluge package is removed or disabled.

Yeah, thats not really my problem though...just something I noticed while trying to figure it out.

I have no problems starting the deamon:

nihil@nihilist:~$ systemctl status deluged
● deluged.service - Deluge Bittorrent Client Daemon
Loaded: loaded (/etc/systemd/system/deluged.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2016-05-31 18:27:08 MDT; 18s ago
Main PID: 12889 (deluged)
Tasks: 4
Memory: 23.4M
CPU: 943ms
CGroup: /system.slice/deluged.service
└─12889 /usr/bin/python /usr/bin/deluged -d

May 31 18:27:08 nihilist systemd[1]: Started Deluge Bittorrent Client Daemon.

It starts when booted like it's supposed to.

My main issue is not being able to connect, and deluge-console not allowing me to modify the core.conf (I did manually modify the /var/lib/deluge/.config/deluge/core.conf, to no avail though). Console throws this error: Failed to connect to 127.0.0.1:58846 with reason: Username does not exist

I've ran this same setup on multiple other "servers", but never before in 16.04. So it seems to me anyways, that systemd is the cuplrit. I'm just stumped I guess.

On a side note, I've been using Deluge for a longtime, thanks for a great piece of free software:)

Thanks for any input.

Edit: Would you recommend going back to 14.04? Only reason I went 16.04 was my OCD's need to have everything updated as much as possible:P

I started watching the core.conf and auth files while starting and stopping the daemon. Seems there was a core.conf and auth file in ~/.config/deluge that were over writing the same in var/lib/deluge/.config/deluge. Deleted those, and everything runs perfect! Most likely this <-- Noob's fault, so sorry to bug ya.

Thanks again for replying and Deluge:)

Edit: Ok I have a new issue:D I searched forums and google the best I could...

I downloaded my first torrent, after finally getting it working. Went great. About 20 minutes after it downloaded and was seeding, a new torrent popped up unprovoked...

It has no name, says it's seeding, says I added it 12/31/1969 05:00:00 PM. There is nothing in my "watching", "downloading", or "downloaded" folders to represent it (meaning those represent my "download to", "move downloaded to", and "auto add" folders).

Is this a common bug? Or a common mistake, for that matter...