Deluge web not connectiong to deluged

[cybergatto]

Hello,
i've just setup deluged and deluge-web on linux ubuntu.

Code: Select all

root@box:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 19.04
Release:        19.04
Codename:       disco
root@box:~#
deluge@box:~/.config/deluge$ deluged -v
deluged: 1.3.15
libtorrent: 1.1.11.0
deluge@box:~/.config/deluge$ deluge-web -v
deluge-web: 1.3.15
libtorrent: 1.1.11.0

deluged is running and i'm able to connect to it with deluge-console
anyway deluge-web is not connecting to deluge. the web interface is up but it shows tha daemon down.
in deluge-web.log i see the following:

Code: Select all

[INFO    ] 13:59:43 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:43 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:43 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":4076}
[INFO    ] 13:59:43 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:43 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:43 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:45 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":5241}
[INFO    ] 13:59:45 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:45 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:45 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:45 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":4077}
[INFO    ] 13:59:45 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:45 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:45 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:47 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":5242}
[INFO    ] 13:59:47 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:47 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:47 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:47 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":4078}
[INFO    ] 13:59:47 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:47 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:47 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:49 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":5243}
[INFO    ] 13:59:49 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:49 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:49 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[DEBUG   ] 13:59:49 json_api:270 json-request: {"method":"web.get_host_status","params":["4e016e7322ba084d1c21384ea62803cffdbb9302"],"id":4079}
[INFO    ] 13:59:49 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:49 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:59:49 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.

and in deluged.log

Code: Select all

[INFO    ] 14:03:41 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48156
[INFO    ] 14:03:41 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:43 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48158
[INFO    ] 14:03:43 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:43 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48160
[INFO    ] 14:03:43 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:45 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48162
[INFO    ] 14:03:45 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:45 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48164
[INFO    ] 14:03:45 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:47 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48166
[INFO    ] 14:03:47 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:47 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48168
[INFO    ] 14:03:47 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:49 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48170
[INFO    ] 14:03:49 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 14:03:49 rpcserver:206 Deluge Client connection made from: 127.0.0.1:48172
[INFO    ] 14:03:49 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.

i dont know where to look now, any idea?

[thornside]

Did you ever get an answer on this? I'm having the same issue and haven't been able to find a solution.

[rickmacd]

Have a look at the topic I just created with the Subject: "Thin client mode makes me manually connect WebUI to running daemon"

You have the same repeating messages every 2 seconds that I have. That is, until I actually connect with the browser interface localhost:8112. That could well be your work-around.

Note, you might need to specify your LAN IP address, such as 192.168.0.37:8112 instead of localhost (127.0.0.1). This depends on the setting in web.conf. I found that "interface": "0.0.0.0" allows both to work.