2

I have set up my own Root CA and Intermediate CAs for my local sites (virtual sites). I also have installed them to trusted certificates in my computer and also the intermediate CAs on their own folder in the cert market of my computer.

However, when I open my website in a browser it finds my certificate invalid. What could be the fix to this? Please consider pictures below.

I use Yandex Browser (almost the same as Chrome Browser)

enter image description here

  • What does a current version of vanilla Chrome report? (Press F12 and then choose the Security tab.) – StackzOfZtuff Jan 26 '18 at 12:43
1

I ran into the same situation today: self-signed CA (registered as trustworthy CA) and server certificate signed by that CA.

  • Firefox and Edge accepted the certificate
  • Java accepted it as well (JAX-RS request with CA in truststore)
  • but Chrome rejected it with ERR_CERT_INVALID.

The CA and server certificate both used EC-256 key material.

When I recreated the CA and server certificate, using RSA-2048 keys instead of Elliptic Curves, the certificate chain was accepted by Chrome.

Seems to be an ECC issue with Chrome and other Chrome based user agents (such as Postman, which also wouldn't connect when using ECC keys).

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.