deluged is causing a system error in Ubuntu 18.04 (and 16.04) when started as a systemd service at startup. I know this is the cause of the system error because my Ubuntu 16.04 system started giving the system error shortly after I installed deluged as a service, then after formatting the drive and ...

In my case, I was getting the error because I was trying to start deluged twice. The error went away once I realised this.

I also recently installed 18.04 and have been presented with the same error message.

Problem fixed by correcting the file ownership/permissions.

I've been fiddling around, and I think the problem is related to file and directory ownership permissions. Right now, the deluged service is running as deluge user. However, I told it to download the files to my login user's directory at /home/myuser/Downloads. I think this is what is causing the pr...

I have deluged set up to run as a systemd service in Ubuntu. I have a user/password set up in the auth file with admin level access (10). I have full allocation selected. Yet when I connect to the deluged from a client running the deluge gui, or through the deluge-web interface, it is impossible to ...

Never mind. After I rebooted the server, I was able to successfully connect from the client using the GUI.

I need help with my set up. I tried to follow the deluge wiki guides for setting up systemd service which autostarts each time the computer startes, and thinclient on my two Ubuntu 16.04 machines. From the server machine I can verify that deluged and deluge-web are both running as systemctl status s...

Just tried this and it seems to be working so far....

sudo chown -R deluge:myuser ~/Downloads/Torrents/

Now deluged appears to be writing to the folder and I am also able to access the folder with my regular user.

Hopefully now I finally fixed this.

Damn :( I thought my issues were solved, but apparently they aren't. Please be patient with me... I am by no means an expert in setting permissions/groups/ownerships, and this has been causing me trouble for last few days... I've tried several permutations of folder/file permissions and I can either...