Yeah, but our cert is valid ! Restart your computer if it still don’t work to empty any cached ssl cert
Your Certificate is not the Problem.
The Problem is, that transmission is needing an CA BUNDLE file for that verification.
And to build this, some prerequisites are needed (e.g Curl) and if they are not available on the system, that file can not be build.
see the first link i have posted.
So a reboot will not help as long as the prerequisites are not present.
The Problem with SSL on transmission 3.0 is caused by the verification of SSL Certificates that is enabled by default on transmission 3.0
https://github.com/transmission/transmission/pull/334
https://github.com/openwrt/packages/issues/5665
In your case, I see that you are using Transmission 3.0… This may be where your problem lies. For some reason version 3.0 is very temperamental with our tracker for some reason. If you roll back to the previous version (2.94), you should have no issue with our tracker anymore.
Somebody mentioned earlier, transmission 3.0 is working again. the only reason it doesnt work before was the outdated certificate. 3.0 is just more strict with that than earlier versions.
could you please try this url: https://tracker.gaytorrent.ru/stmdd
if you reach a black page showing backend stats, you can reach our backend and so your client should be able too. But if you cannot reach this page, then Hyperfilter is blocking you for some reasons…
I can reach https://tracker.gaytorrent.ru/stmdd
I have tried with Transmission 2.94 and SSL is working, with Transmission 3.0 SSL is not working 
Still the SSL Tracker isn't working for me.
Hallo,
hat jemand Erfahrungen mit dem im Qnap NAS eingebauten BitTorrent Client
oder kann mir sagen ob ich diesen zum downloaden nutzen kann?
Also ob der Tracker da unterstützt wird ?