SMTP TLS Handshake Error & Login Stuck on nine.testrun.org (Desktop Windows)

Hello Delta Chat Support,

Since 3 days ago, my Delta Chat Desktop (Windows) client has been constantly disconnecting and reconnecting.
Incoming messages works, but outgoing messages fail with the following error:

Error: SMTP connection failure: SMTP failed to connect: tls handshake eof

When I open Advanced → Password and Account and try to recheck or verify settings, the progress bar stays halfway and never finishes.
I have already tried the following steps, but the issue persists:

My account is hosted on: nine.testrun.org.
Other users on the same domain seem to have experienced similar SMTP/TLS connection issues since 3 day ago.

Could you please check if there is a known problem with the SMTP or TLS configuration on nine.testrun.org, or advise me if I should change any client settings?

Thank you for your help!
Best regards,

1 Like

Which Delta Chat Desktop version do you run? Is it a recent version?

Does creating a new profile work? Could you try creating a new profile, then waiting until it finishes or fails? It should eventually fail, but it may take a long time, so start it and leave it for 10 minutes or so until it reports an error and offers to save the log. If you send the log to delta@merlinux.eu, we can look into it.

If this happens only on some network, e.g. your company network, then it may be that the network is blocking the connection.

Are you by any chance from Russia?

In general it looks like DeltaChat stoped or never did sending SNI during request to server, so server replies with default certificate, which creates error during TLS handshkae.

When a client does not send the Server Name Indication (SNI) extension during a TLS handshake, the server cannot determine which hostname the client is trying to reach if it hosts multiple secure websites on a single IP address. This leads to a certificate mismatch error and a failed connection.

The most effective solution is to upgrade the DeltaChat or application library to a modern version that supports SNI.

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:

I also caught the same error today, now I tried again the page was loading for a long time, but then the qr code appeared and everything went well, I don’t think this is due to censorship(I have no restrictions). I also connected all other servers to version 2.33.1 and I didn’t have any other difficulties

For me https://mehl.cloud page opens instantly, if it is slow to load for you then there is likely some network issue. And it is not even something that can be fixed in Delta Chat, it’s just a web page opened in a browser.

I was talking about https://nine.testrun.org/

as I see it, this is what we’re talking about

For nine.testrun.org it’s also instant for me, the page opens in way less than a second: