I believe I found a similar SSL issue having to do with TLSv1.2 and SNI in deluge and is also occurring in YaRSS2. Is this a fix you can also incorporate into the plugin?: http://dev.deluge-torrent.org/ticket/2765

Bummer, any way that we can have deluge force a different connection type?

Here's the traceback running from the windows 1.3.12 version (python 2.7): [DEBUG ] 11:54:50 addtorrentdialog:665 url: ******** [DEBUG ] 11:54:50 addtorrentdialog:715 Download failed: [Failure instance: Traceback: <class 'OpenSSL.SSL.Error'>: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'tlsv1 alert ...

I was using the 2.7 windows version yes.

And actually I just built out a Fedora 22 server that is using Python 2.7.10 and installed Deluge 1.3.11 (that's what's in their repository still) and still get the same behavior.

I am trying to add a torrent by URL which happens to be an https link and the site uses cloudflare (I've heard that their certificate is the problem/openssl and python). I get the following error: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'tlsv1 alert internal error')] I get this through both the ...

bump

I'm using Deluge 1.3.11 on Ubuntu 14.04. The WebUI will launch and the first time that I enter the password and connect to the local instance it works great. However, when I close the browser and then try to connect again from a new browser session, the WebUI comes up but does not have anything list...