Deluge Forum

Hi, I am totally freshman to linux. I install deluge on debian 8.1 (after trying several times), bu the web ui can not connect daemon. The connection manager does not show the vesion of deluge and either start or stop button for the daemon does not receive any response. By running:
$sudo systemctl status deluged
deluged appears to have been started.

Some detailed imfomation is given below。
1. Status of deluged service
$ sudo systemctl stop deluged
$ sudo systemctl start deluged
$ sudo systemctl status deluged
● deluged.service - Deluge Bittorrent Client Daemon
Loaded: loaded (/etc/systemd/system/deluged.service; enabled)
Active: active (running) since Thu 2017-05-18 15:36:05 CEST; 6s ago
Main PID: 28575 (deluged)
CGroup: /system.slice/deluged.service
└─28575 /usr/bin/python /usr/bin/deluged -d

2. Status of deluge-web service
$ sudo systemctl status deluge-web
● deluge-web.service - Deluge Bittorrent Client Web Interface
Loaded: loaded (/etc/systemd/system/deluge-web.service; enabled)
Active: active (running) since Thu 2017-05-18 15:37:32 CEST; 241ms ago
Main PID: 28671 (deluge-web)
CGroup: /system.slice/deluge-web.service
└─28671 /usr/bin/python /usr/bin/deluge-web

May 18 15:37:32 sd-44534 systemd[1]: Started Deluge Bittorrent Client Web I...e.
Hint: Some lines were ellipsized, use -l to show in full.

3. After installation, configuration files are generated only for user of root (I don't know why)
$ sudo find / -name "core.conf"
/root/.config/deluge/core.conf
$ sudo find / -name "auth"
/root/.config/deluge/auth
and the owner and permission infomation is
$ sudo ls -al /root/.config/deluge
total 80
drwx------ 6 root root 4096 May 18 12:53 .
drwx------ 3 root root 4096 May 13 08:07 ..
-rw------- 1 root root 77 May 13 10:00 auth
-rw------- 1 root root 56 May 13 09:58 auth.old
-rw-r--r-- 1 root root 2442 May 13 10:00 core.conf
-rw-r--r-- 1 root root 5015 May 18 12:08 deluged.log
-rw-r--r-- 1 root root 11 May 13 10:00 deluged.pid
-rw-r--r-- 1 root root 3883 May 13 10:00 dht.state
-rw-r--r-- 1 root root 168 May 13 10:30 hostlist.conf.1.2
-rw-r--r-- 1 root root 305 May 13 10:30 hostlist.conf.1.2~
drwxr-xr-x 2 root root 4096 May 13 08:15 icons
drwxr-xr-x 2 root root 4096 May 13 08:15 plugins
-rw-r--r-- 1 root root 4253 May 13 10:00 session.state
drwxr-xr-x 2 root root 4096 May 13 08:15 ssl
drwxr-xr-x 2 root root 4096 May 18 15:47 state
-rw-r--r-- 1 root root 56 May 13 09:33 ui.conf
-rw-r--r-- 1 root root 656 May 13 08:23 web.conf
-rw-r--r-- 1 root root 656 May 13 08:16 web.conf~

4.
$ dpkg -l | grep deluged
ii deluged 1.3.10-3 all bittorrent client written in Python/PyGTK (daemon)
$ dpkg -l | grep deluge-web
ii deluge-web 1.3.10-3 all bittorrent client written in Python/PyGTK (web ui)
$ dpkg -l | grep libtorrent
ii libtorrent-rasterbar7 0.16.18-1 amd64 C++ bittorrent library by Rasterbar Software
ii python-libtorrent 0.16.18-1 amd64 Python bindings for libtorrent-rasterbar
Many thanks.

Hi,

The config file are generated in the home folder of the user starting the application. So if you configured the service with the user root this is fine.
If you created a dedicated user like "deluge" as in the wiki http://dev.deluge-torrent.org/wiki/User ... ce/systemd the service should create the config file in /var/lib/deluge/

The webui screenshot is from the same computer or you tried from another one?
Have you configured a user able to connect? http://dev.deluge-torrent.org/wiki/User ... cationfile