Sorry to hear, maybe enable debug-logging for both deluged and webUI.
For the deluge-console error, then that happens whenever things not setup correct for authentication, meaning that for webUI atleast worked for me without doing anything, but for deluge-console and deluge-GTK there is steps involved, which I just state again just in case:
Code: Select all
sudo cp /srv/deluge/.config/deluge/{hostlist.conf,auth} ~/.config/deluge
sudo chown xion: ~/.config/deluge/{hostlist.conf,auth}
In last line you edit 'xion to your real personal user-name, but keep the colon afterwards it, which just means default group for said user. Also, if not having a local deluge config folder, then firstly with deluged/deluge-web from systemd stopped, you run 'deluged' and 'pkill deluged', and start deluged/deluge-web again from systemd and do above steps.
Anyway, to enable logging when using systemd is the following instructions:
Stop deluged/deluge-web from systemd.
Then generate override files that enable logging, which easiest way is run 'sudo systemctl edit deluged' which opens an editor and you need copy/paste into first empty line and save it:
Code: Select all
[Service]
ExecStart=
ExecStart=/usr/bin/deluged -d -L debug -l /srv/deluge/.config/deluge/deluged.log
Run 'sudo systemctl edit deluge-web' and again copy/paste following into first empty line and save it:
Code: Select all
[Service]
ExecStart=
ExecStart=/usr/bin/deluge-web -d -L debug -l /srv/deluge/.config/deluge/deluge-web.log
Start from systemd deluged/deluge-web and test untill hitting the issue, stop again deluged/deluge-web from systemd, and check /post the logs under '/srv/deluge/.config/deluge' i.e. 'deluged.log' and 'deluge-web.log'.
When wanting remove the logging again, then with deluged/deluge-web stopped from systemd, then run:
Code: Select all
sudo systemctl revert deluged deluge-web
Good luck.
Edit: I edited the two lines in first instructions posted, to also include and copy over the 'auth' file in addition to the 'hostlist.conf' file, because found that although only hostlist.conf was needed to run deluge-console and login there, then when running non-interactively e.g. 'deluge-console info', then it would fail and say password not match, so you needed additionally 'auth' copied over into your local user-dir for this to work correct in all situations.