TLS handshake failed on launchermeta.mojang.com

Starting around May 4, users were having trouble accessing launchermeta.mojang.com and piston-meta.mojang.com. The error was a 10054 error code with a message that an SSL connection could not be established. (https://learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2#:%7E:text=WSAECONNRESET,10054)

This was happening to a very large number of users (at least in South Korea) and across multiple devices, Windows and Linux platforms.

After checking the packets with Wireshark, it appears that the server is forcibly disconnecting the socket immediately after sending the client hello packet during the ssl handshake. 

You can reproduce this issue using the openssl tool:
openssl s_client -connect launchermeta.mojang.com:443 -prexit

Most connection attempts will succeed, but about one out of ten will result in the error errno=104 (connection reset by peer). For some users, the frequency of this error is very high.

 

Whenever the connection fails, I check with wireshark and the packets have a version of TLS 1.0. I don't know why openssl is sending TLS 1.0 Client Hello packet even the server doesn't seem to support TLS 1.0. I tried with curl as well as openssl and the connection fails every time I see TLS 1.0 packets. (https://www.cdn77.com/tls-test/result?domain=launchermeta.mojang.com)