https://bugs.kde.org/show_bug.cgi?id=453121
Allen Winter changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=453121
Lapineige changed:
What|Removed |Added
CC||lp@lavache.com
--- Comment #20 from Lapineige
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #19 from m.eik michalke ---
(In reply to m.eik michalke from comment #18)
> 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.
i've tried configu
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #18 from m.eik michalke ---
(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 abort
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #17 from m.eik michalke ---
(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 al
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #16 from Benjamin ---
regarding your question: no the port should not be a problem...port forwarding
and stuff is handled by apache serverside so that is almost surely not a
problem
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #15 from Benjamin ---
Not easy to say, but I would check the follwowing:
- Update nextcloud to the newest release
- Install openssl 3 on the server where the nc instance is running
on your desktop:
check out the issue i have posted above ma
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #14 from m.eik michalke ---
i checked with "akonadictl --verbose start" and don't see any errors regarding
"qt.network.ssl", it just shows the HTTP error (0) without any further warnings
or errors.
i also configured nextcloud to use log lev
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #13 from m.eik michalke ---
glad you solved the problem on your side! however, installing libssl-dev didn't
solve it for me, i'm still getting the "HTTP error (0)" response.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #12 from Benjamin ---
Okay i had success while running thourgh this issue:
https://stackoverflow.com/questions/52210603/qt-and-openssl-incompatible-version-on-ubuntu#52210604
That is definitely the problem here.
In my case the solution was
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #11 from Benjamin ---
Here is also the akonadictl start output, cause I gues it might be useful:
>org.kde.pim.akonadiserver: Subscriber
>Akonadi::Server::NotificationSubscriber(0x7fd288049150) identified as
>"AgentBaseChangeRecorder - 948
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #10 from Benjamin ---
Okay I just tried a little bit around...
In this issue it is recommended to check the different openssl versions:
https://github.com/flathub/org.kde.kontact/issues/71
I then tried to upgrade the server of the nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #9 from gjditchfi...@acm.org ---
(In reply to m.eik michalke from comment #8)
> i doubt that's the issue, at least im running with let's encrypt certs.
> rather i suspect apache's TLS configuration could be causing this. can
> anyone suggest
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #8 from m.eik michalke ---
(In reply to gjditchfield from comment #7)
> My second wild guess is that Qt and your browser use different
> configurations;
> Chrome uses a different SSL library, for instance.
that would explain why access via
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #7 from gjditchfi...@acm.org ---
(In reply to Benjamin from comment #6)
> Mhm...Actually lowering the security level to 0 seems a little bit bad for a
> workaround. Any hints how to solve this?
> ...Thanks for your replies!
My second wild gu
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #6 from Benjamin ---
Mhm...Actually lowering the security level to 0 seems a little bit bad for a
workaround. Any hints how to solve this?
...Thanks for your replies!
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #5 from m.eik michalke ---
(In reply to gjditchfield from comment #4)
> I use KOrganizer 5.20.0 successfully with two different Nextcloud servers,
> running on KDE Neon (which is basically Ubuntu 20.04). As a wild guess,
> perhaps the mini
https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #4 from gjditchfi...@acm.org ---
I use KOrganizer 5.20.0 successfully with two different Nextcloud servers,
running on KDE Neon (which is basically Ubuntu 20.04). As a wild guess,
perhaps
the minimum supported TLS version was raised in Kubu
https://bugs.kde.org/show_bug.cgi?id=453121
gjditchfi...@acm.org changed:
What|Removed |Added
Summary|Flatpak calender can't |calender can't connect to
19 matches
Mail list logo
