I was running into a similar issue with launchermeta servers (and probably all the other servers given the nature of the issue).
I'm now curious if I actually fixed my issue locally (because I missed some updates) or if I incidentally did all that while Mojang fixed things on their end.
This issue can be resolved permanently by Mojang by having the launcher handle TLS itself, rather than relying on the Windows SCHANNEL toolkit since Win7 and Win8 won't have continued support for newer TLS ciphers and protocols. And this is absolutely doable because browsers like Chrome do it already --you could see the launchermeta json URLs in Chrome despite the launcher failing the handshake because only the latter goes through SCHANNEL.
This is probably the preferable solution in the long term, since it means not dropping Win7/8 support, nor having to allow weaker ciphers indefinitely as the technology progresses.
ETA: probably moot to comment on a closed ticket, but I'm not sure if I should raise a new ticket for this because it's less "bug" and more "feature request".
StarSumiaki
I was running into a similar issue with launchermeta servers (and probably all the other servers given the nature of the issue).
I'm now curious if I actually fixed my issue locally (because I missed some updates) or if I incidentally did all that while Mojang fixed things on their end.
This issue can be resolved permanently by Mojang by having the launcher handle TLS itself, rather than relying on the Windows SCHANNEL toolkit since Win7 and Win8 won't have continued support for newer TLS ciphers and protocols. And this is absolutely doable because browsers like Chrome do it already --you could see the launchermeta json URLs in Chrome despite the launcher failing the handshake because only the latter goes through SCHANNEL.
This is probably the preferable solution in the long term, since it means not dropping Win7/8 support, nor having to allow weaker ciphers indefinitely as the technology progresses.
ETA: probably moot to comment on a closed ticket, but I'm not sure if I should raise a new ticket for this because it's less "bug" and more "feature request".