-
Notifications
You must be signed in to change notification settings - Fork 0
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
Certificate too long #4
Comments
If you add it to your OS's certificate store and restart your browser, this shouldn't be an issue. I have tested it on Windows with Chrome browser. What is your OS and browser ? |
I have tested on iOS, Windows and MacOS. All them, even importing to root ca trusted, the issue persists. Apparently it's a limitation from new browsers. |
Just to confirm, while trusting the root ca, did you follow the steps from the wiki ? |
Yes. But I think that is related to devices. Take a look at: https://www.ssls.com/blog/apples-new-ssl-lifetime-limitation-and-what-it-means-for-you/. |
I got a hold of Macbook and tried adding the root CA to the Keychain. After adding, chrome accepted it just fine, no errors. For, Safari I had to take a few additional steps for the first time, henceforth it gave no issues.
That is for certificates issued by Public CA not for self signed certificates.. |
I am not able to replicate this. Anyways, these are self-signed certificates and they will not work as regular SSL certificates. |
Even after add root ca as a trusted certificate, browsers are not allowing saying about invalid certificate. Searching for a solution I have found that any browser is rejecting SSL certificates with validity above to 397 days. I think a fixing this issue will also need an auto renew script.
https://stackoverflow.com/questions/64597721/neterr-cert-validity-too-long-the-server-certificate-has-a-validity-period-t
The text was updated successfully, but these errors were encountered: