https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #18 from m.eik michalke <bugs.kde....@ad.gelduntergang.biz> --- (In reply to m.eik michalke from comment #17) > turns out: using a custom port > an the server behind a NAT router might be the real issue in my case. at > first 'openssl' kept waiting for a response until i aborted the call. i then > tried the '-4' switch to force using an IPv4 address, and that resulted in a > successful connection. TLS connection war ok for both TLS v1.2 and v1.3. > this led me to assume that, while web browsers, the seafile client and > vdirsyncer seem to fall back to IPv4 (because of the explicitly set port?), > akonadi might only be trying IPv6 and doesn't get a response because there's > not NAT. yes, that's really it. i called 'ping -4' on the server and temporarily added it's current IPv4 address to /etc/hosts to resolve the domain locally, after that kontact was *instantly* able to fetch contacts and calendars. so all i'm missing is a way to tell kontact/akonadi to try IPv4 first. -- You are receiving this mail because: You are watching all bug changes.