starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

HTTPS tracker doesn't work when it requires Server Name Indication #3567

New issue

Closed

opened 2026-02-21 16:50:46 -05:00 by deekerman · 10 comments

deekerman commented

2026-02-21 16:50:46 -05:00

Owner

Originally created by @Sorvigolova on GitHub (Dec 14, 2015).

Handshake failed with all trackers that used CloudFlare servers with certificates like this one: sniXXXXX.cloudflaressl.com
Please enable Server Name Indication extension to fix this issue.

https://en.wikipedia.org/wiki/Server_Name_Indication

Originally created by @Sorvigolova on GitHub (Dec 14, 2015). Handshake failed with all trackers that used CloudFlare servers with certificates like this one: sniXXXXX.cloudflaressl.com Please enable Server Name Indication extension to fix this issue. https://en.wikipedia.org/wiki/Server_Name_Indication

deekerman closed this issue

2026-02-21 16:50:48 -05:00

deekerman commented

2026-02-21 16:50:51 -05:00

Author

Owner

@dysangelist-1 commented on GitHub (Jan 17, 2016):

Cloudflare seems to be making changes lately which are making this a more common problem with HTTPS trackers that use them; TLSv1.2 requests sent in the Client Hello without the SNI extension specifying server name are suddenly being met with instant Alert/'Internal error' responses.

There's a QT bug for not sending SNI with TLSv1.1+ - https://bugreports.qt.io/browse/QTBUG-47528 - which was apparently fixed and merged in release 5.5.1 - but qBittorrent v3.3.1 is built with 5.5.1 (or so my client says) and still isn't sending SNI server name on a TLSv1.2 hello. Maybe I've misunderstood the scope or applicability of the QT bug?

Deluge had the same basic issue and sorted it by doing the incantations that make Twisted send SNI server name: http://dev.deluge-torrent.org/ticket/2765

@dysangelist-1 commented on GitHub (Jan 17, 2016): Cloudflare seems to be making changes lately which are making this a more common problem with HTTPS trackers that use them; TLSv1.2 requests sent in the Client Hello without the SNI extension specifying server name are suddenly being met with instant Alert/'Internal error' responses. There's a QT bug for not sending SNI with TLSv1.1+ - https://bugreports.qt.io/browse/QTBUG-47528 - which was apparently fixed and merged in release 5.5.1 - but qBittorrent v3.3.1 is built with 5.5.1 (or so my client says) and still isn't sending SNI server name on a TLSv1.2 hello. Maybe I've misunderstood the scope or applicability of the QT bug? Deluge had the same basic issue and sorted it by doing the incantations that make Twisted send SNI server name: http://dev.deluge-torrent.org/ticket/2765

deekerman commented

2026-02-21 16:50:51 -05:00

Author

Owner

@ghost commented on GitHub (Jan 19, 2016):

Also having the same issue. Thanks for taking the time to look at it.

@ghost commented on GitHub (Jan 19, 2016): Also having the same issue. Thanks for taking the time to look at it.

deekerman commented

2026-02-21 16:50:51 -05:00

Author

Owner

@Sorvigolova commented on GitHub (Jan 21, 2016):

May be problem with openssl. qBittorrent do not show info about openssl version.

@Sorvigolova commented on GitHub (Jan 21, 2016): May be problem with openssl. qBittorrent do not show info about openssl version.

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jan 22, 2016):

@Sorvigolova

Tracker related functions is handled by libtorrent, you might want to forward this issue to them: https://github.com/arvidn/libtorrent/issues

Unless you're talking about qBittorrent embedded tracker...

@Chocobo1 commented on GitHub (Jan 22, 2016): @Sorvigolova Tracker related functions is handled by libtorrent, you might want to forward this issue to them: https://github.com/arvidn/libtorrent/issues Unless you're talking about qBittorrent embedded tracker...

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Sorvigolova commented on GitHub (Jan 22, 2016):

Thanks @Chocobo1. Issue added: https://github.com/arvidn/libtorrent/issues/429

@Sorvigolova commented on GitHub (Jan 22, 2016): Thanks @Chocobo1. Issue added: https://github.com/arvidn/libtorrent/issues/429

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jan 25, 2016):

@sledgehammer999 @Sorvigolova

This issue can be closed, it's already fixed upstream.

@Chocobo1 commented on GitHub (Jan 25, 2016): @sledgehammer999 @Sorvigolova This issue can be closed, it's already fixed upstream.

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Sorvigolova commented on GitHub (Jan 25, 2016):

Thanks to You all, who was envolved.

@Sorvigolova commented on GitHub (Jan 25, 2016): Thanks to You all, who was envolved.

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Sorvigolova commented on GitHub (Feb 29, 2016):

libtorrent-1.0.9 Released with SNI support for https trackers and webseeds. :)
It remains to wait the next qBittorrent release. Cool!

@Sorvigolova commented on GitHub (Feb 29, 2016): libtorrent-1.0.9 Released with SNI support for https trackers and webseeds. :) It remains to wait the next qBittorrent release. Cool!

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@chrishirst commented on GitHub (Feb 29, 2016):

https://qbforums.shiki.hu/index.php/topic,4113.0.html

@chrishirst commented on GitHub (Feb 29, 2016): https://qbforums.shiki.hu/index.php/topic,4113.0.html

deekerman commented

2026-02-21 16:50:52 -05:00

Author

Owner

@Sorvigolova commented on GitHub (Mar 1, 2016):