deluge-web: won't autoconnect to the daemon

[sarum4n]

Sorry to raise this thread from the tomb, but the described problem still exists in the latest version of deluge-web and the solution is exactly the same proposed by the fellow OP, that is to modify the source code of the aforementioned python file to force deluge-web to read correctly the "defaultdemon" argument in web.conf, especially where it points to a port different from the default 58846. So, I'd suggest you to give a glance to latest source code, because undoubtdebly it still doesn't work as intended. Kudos and thanks to OP for giving solution, though.

[Cas]

No posting in that thread is not helpful. Please detail the problem you actually have because this was fixed in latest code and you either are not configuring correctly or it is a new bug.

http://dev.deluge-torrent.org/wiki/Faq# ... ificdaemon

[sarum4n]

First of all, sorry for posting in that thread and thanks for moving.

That said, about the issue, I followed exactly the instructions in the FAQ you linked to, but deluge-web always wanted to connect to 58846 port (the default one) and insisted doing so until I edited the python source code as addressed by the OP in the aforementioned thread.

Anyway, after reading your answer, I started to collect all the debug infos to post them here and, while doing so, I noticed that the latest version of Deluge is 1.3.12 and realised that I was running 1.3.10 though (that's what Debian testing offers by default). Therefore, after modifying my apt preferences, I upgraded only Deluge to unstable branch of Debian, obtaining the latest 1.3.12, and the issue I had disappeared by magic! Now all works great as intended.

Thanks for helping and sorry again for the misplacement of my previous post