-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS initialization failed - Appimage on Debian 11 #65
Comments
Same error here with the same version. |
You got this error only with 0.7.1 and not with 0.7.0 or 0.6 ? |
I receive the same using 0.7.0. With this specific domain I'm using Let's Encrypt: browsers correctly shows the encrypted connection. Thank you, |
It's not a certificate problem. The connection isn't opened at all.
is quite clear about it. This seems like a rather common problem on Debian. This happened a long time ago in Calibre, too, so looking there for a patch might help. |
A continuous build is ready. Can be fetched at https://github.com/AlexandrePTJ/kemai/releases/tag/Continuous |
working. Would you mind summarizing the trick? This seems to be happening in a lot of AppImages that have not been compiled on Debian. |
I still have the same problem using Kemai-0.8.0-x86_64.AppImage from continuous on Debian bookworm/sid... |
Qt6 split several things in plugins, TLS is part of it. So in the appimage creation process, it is now necessary to add a requirement on tls plugin. |
Is it fixed on stable ? |
Sorry I didn't understand, is there a stable after 0.7.1? ...or do you mean Debian stable? I can't try this on the fly. Thank you, |
I meant Debian stable. |
Bonjour ! |
I confirm the same problem still exist using Appimage in Debian 12 bookworm (testing) and in Ubuntu 22.04. Thank you, |
Last release looks to works with ubuntu 22, but not on debian 11... |
Hi,
the Kemai-0.7.1-x86_64.AppImage on Debian 11 shows me, for multiple instances of Kimai, on different servers:
Error on request [version]: TLS initialization failed
when testing the connection.
The server ssl certificate is valid and is not self signed.
Thank you,
Riccardo
The text was updated successfully, but these errors were encountered: