In this case it is “tls handshake eof” so it looks like TCP connection is started, but then the network (corporate firewall or some other internet censorship middlebox) dropped the connection and this resulted in TLS library failing to read the rest of TLS handshake.
It could indeed be caused by recent changes wrt not sending SNI in some cases (Server Name Indication (SNI) extension during a TLS handshake - #2 by link2xt) and the middlebox configured to terminate connections this way when not recognized SNI is found.
Without any respones and logs we cannot debug this further, but can also recommend trying some other relays and if they work, migrate existing profiles to using a working relay: