Thank you, that was the solution.
This works best for me, better than auto.
ssl_ecdh_curve secp384r1:prime256v1;
SSL Certificate from StartCom not accepted
-
@rekisum Did you use the correct intermediate certiciate, “StartCom Class 1 DV Server CA” from https://startssl.com/root?
-
do you mean the 1_root_bundle.crt ?
It came in the zip file.
Where do I find “StartCom Class 1 DV Server CA” on the web site?
Thanks for the quick help by the way
-
@rekisum On https://startssl.com/root, “Intermediate CA Certificates”, you can download “StartCom Class 1 DV Server CA” in PEM format (
.crt). -
yeah, found already ca.server1.crt
tried to use it as certificate chain file
SSLCertificateChainFile /etc/ssl/certs/sca.server1.crt
didn’t help
did you mean that?
or is the pem file better?
? -
neither of them worked
-
@rekisum Well, according to ssllabs.com, the StartCom Class 1 DV Server CA is still not in the chain. So there’s something wrong with the configuration, maybe the
SSLCertificateChainFileis not applied or something. You will have to fix that to get the certificate accepted by all clients.Or, just click on “Always accept” in DAVdroid, it should work, too. But it won’t fix the real problem.
-
How do you see that?
It says: Chain issues incomplete
Do you mean: extra download?No, always accept doesn’t work.
Have alway to click the dialog multiple times. -
@rekisum said:
How do you see that?
It says: Chain issues incomplete
Do you mean: extra download?Yes, that means that chain is not complete and requires extra downloads to verify it.
No, always accept doesn’t work.
Have alway to click the dialog multiple times.Then there’s a bug.
-
@rekisum Try removing the account from your Android device and re-adding it. I’m having similar problems (dialog constantly popping up) after a change of the certificates and re-creating the account solves the problem consistently.
-
Ok, seem I resolved my SSL certificate problems, despite the CA-Flag.
At sometime finding the bug i disabled the StartCom certificate in the System Settings.
Enabling it and going through accept permanently dialogs seems to fixed it.
Calender gets synced again. .-)
