https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #17 from m.eik michalke <bugs.kde....@ad.gelduntergang.biz> --- (In reply to Benjamin from comment #15) > - Update nextcloud to the newest release > - Install openssl 3 on the server where the nc instance is running actually, i'm already running nextcloud 24 and the system also uses backports, so iguess that's not an issue. i'm usually not a friend of replacing packages without some proof that that's actually the problem. so i was examining the TLS connection to the server in question using 'openssl s_client'. 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. > > on your desktop: > check out the issue i have posted above maybe there is a different solution > to your problem. > > ...besides: I use backports ppa on my kubuntu to ensure that the newest > packages are installed and updated... > > This is all I can say sofar. > But to be honest: I don't think that the problem is within nextcloud or > serverside. It seems more a problem with akonadi/openssl/kontact (as this > work together)... -- You are receiving this mail because: You are watching all bug changes.
