I see, thank you.
I'll file an appropriate ticket.

Apparently I was forgetting to kill deluge-web. My bad.

As a side note, I requested 1.3.10 to be made available on the repo and then did a rollback to that version. Everything works fine, including the WebUI. Ergo, something in the update was changed and caused WebUI to stop working properly.

Thin client on my own PC is able to connect fine.

WebUI is relentlessly attempting (and failing) to use SSL3 to connect, as seen in the logs. It also keeps overwriting the config I'm giving it with its own, discarding my changes to change HTTPS or cert settings.

I went and talked to some CentOS folks, and there's nothing wrong with the OS itself. The problem is in deluge trying to use SSL3. Apparently CouchPotato had the same issue, but it got fixed in their version.

I tend to not update things selectively, so OpenSSL was updated as soon as it was out. And I also verified that it's up to date as per the Wiki page linked. Would it be possible to simply disable SSL/TLS in my Deluge setup to begin with? I'm not interested in making connections to itself secure, and...

Just set up some logging and found out that the WebUI keeps trying (and failing) to connect to the Daemons using SSL, for whatever reason. As another fun fact, deluge-web keeps tossing aside my config and inserting a default one instead, rendering me unable to turn on HTTPS or change paths to cert/k...

Hello! I'm running two Deluge (1.3.11, libtorrent 0.15.10.0, installed from package manager) daemons (as two different users) on a CentOS 6.6 (kernel 2.6.32) server and a WebUI (no plugins) as one of the two users. I've updated everything recently and now the WebUI refuses to acknowledge/notice eith...