I'm running the thin client mode, with the webui plugin enabled. When I start Deluge, it starts the daemon and downloading always works fine. However, I can't connect to the webui remotely until I first connect to it using the web interface at 192.168.1.2:8812. That seems to complete or somehow initialize the connection of the webui to the daemon, thus enabling remote connections. Shouldn't deluge make that final connection between webui and the running daemon at startup time?
Here are the details:
After freshly starting Deluge and seeing that downloads are continuing, if I try to connect with Transdrone from my Android phone, I get the message "Web interface not connected to a running daemon". Yet, when I look at the daemon DEBUG log, I see this:
Code: Select all
[INFO ] 00:11:58 server:679 Serving on 192.168.1.2:8112 view at http://192.168.1.2:8112
...
[DEBUG ] 00:26:15 json_api:270 json-request: {"method":"blocklist.get_status","params":[],"id":819}
[DEBUG ] 00:26:17 json_api:270 json-request: {"method":"auth.login","params":["XxXxXxXxX"],"id":1}
[DEBUG ] 00:26:17 auth:199 Received a password via the 1.2 auth method
[INFO ] 00:26:17 auth:327 Login success (ClientIP 192.168.1.1)
[DEBUG ] 00:26:17 auth:146 Creating session for admin
Using the browser on my server running Deluge, I go to 192.168.1.2:8812 and login with my webui password. These messages appear in the daemon log (same as the Transdone attempt caused):
Code: Select all
[DEBUG ] 00:29:30 json_api:270 json-request: {"method":"blocklist.get_status","params":[],"id":916}
[DEBUG ] 00:29:31 json_api:270 json-request: {"method":"auth.login","params":["XxXxXxXxX"],"id":1}
[DEBUG ] 00:29:31 auth:199 Received a password via the 1.2 auth method
[INFO ] 00:29:31 auth:327 Login success (ClientIP 192.168.1.2)
[DEBUG ] 00:29:31 auth:146 Creating session for admin
Code: Select all
[DEBUG ] 00:32:25 json_api:270 json-request: {"method":"web.get_host_status","params":["abcdef0123456789abcdef0123456789"],"id":40}
[INFO ] 00:32:25 client:217 Connecting to daemon at localhost:58846..
[INFO ] 00:32:25 rpcserver:206 Deluge Client connection made from: 127.0.0.1:53070
[INFO ] 00:32:25 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 00:32:25 client:224 Connection lost to daemon at localhost:58846 reason: Connection was closed cleanly.
[INFO ] 00:32:25 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
When I connect to the host, I get these messages in the daemon log:
Code: Select all
[DEBUG ] 00:39:10 json_api:270 json-request: {"method":"web.connect","params":["abcdef0123456789abcdef0123456789"],"id":319}
[INFO ] 00:39:10 client:217 Connecting to daemon at localhost:58846..
[INFO ] 00:39:10 rpcserver:206 Deluge Client connection made from: 127.0.0.1:54306
[INFO ] 00:39:10 client:121 Connected to daemon at 127.0.0.1:58846..
[DEBUG ] 00:39:10 pluginbase:77 WebPlugin initialized..
[DEBUG ] 00:39:10 pluginmanagerbase:156 Adding AutoAdd to enabled_plugins list in config
[INFO ] 00:39:10 pluginmanagerbase:158 Plugin AutoAdd enabled..
[DEBUG ] 00:39:10 pluginmanager:115 adding script AutoAdd for autoadd.js
[DEBUG ] 00:39:10 pluginmanager:119 adding debug script AutoAdd for autoadd.js
...and other plugin messages...
Code: Select all
[DEBUG ] 00:43:33 json_api:270 json-request: {"method":"blocklist.get_status","params":[],"id":606}
[DEBUG ] 00:43:33 json_api:270 json-request: {"method":"auth.login","params":["XxXxXxXxX"],"id":1}
[DEBUG ] 00:43:33 auth:199 Received a password via the 1.2 auth method
[INFO ] 00:43:33 auth:327 Login success (ClientIP 192.168.1.1)
[DEBUG ] 00:43:33 auth:146 Creating session for admin
So, it seems like Deluge isn't completing some part of the webui startup. The browser interface on the server (192.168.1.2:8812) has the Connection Manager that causes the webui to connect to the host. Transdone doesn't offer to do that magic bit.
Shouldn't deluge make that final connection between webui and the running daemon at startup time?