Post #1411508
2026-04-16 02:40 UTC
Replies (1)
-
@simon@procrastodon.net 2026-04-16 02:45
@johann It starts fine, but clients can't connect to encrypted servers anymore on 5.22.1. The TeamTalk client doesn't seem to produce a useful error either. It just tries for a while, gives up, and tries again a few seconds later in an infinite loop. I know it's not just me, because I made the mistake of updating the binaries on a few locations and almost immediately started getting messages from other people who couldn't connect. I've confirmed that the latest QT client and the old classic client are both experiencing this problem. When I go back to 5.21.1, with the exact same configuration and certificates, it starts working again. So it's a 5.22 problem, and also a problem that doesn't affect everyone, since you said it's fine. It definitely affects all of my servers, and I'm wondering if there's some commonality in the way I set them up. But they really are the most boring unmodified install of Debian you can imagine, plus a few packages like unattended-upgrades. I don't even use the tt utility. So it's quite strange. All I got from Bjorn was basically "It works on my end🤷." Since the client isn't giving me useful errors, I tried connecting with the actual OpenSSL command, and that worked fine. So there's something funny going on in the client itself, and the only way I think I'll figure out the problem is by actually getting useful debug messages from the client. I just can't be bothered right now, so i'm going to migrate everyone to 5.21.1 and tackle it later.