-
Notifications
You must be signed in to change notification settings - Fork 31
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
Generated SSL Certificate is not trusted #13
Comments
Hi @j-flat I faced the exact same issues as you and did the following things to resolve it: 1. Update the CA certificates on EdgeOS so that you don't have to use the insecure mode anymore
2. Save the intermediate certificate to
|
Hi @dmengelt ! Thanks for helping out! I have a stupid question regarding the step 2., how can I identify ISRG Root X10 on the |
You can copy the value of the certificate to an online base64 decoder and it will show you the name |
@j-flat did it work? |
I followed the advice as the problem surfaced on my edgerouter as well. I would suspect that a hard refresh of the browser is needed after completing step 2. I didn't do it and ended up doing step 1 once again before refreshing the browser. Anyway, it now works. Thanks for sharing your knowledge! |
@nahoj74 nice! glad it worked for you. |
Hi @dmengelt I've encountered the same issue and have followed your instructions as well as I could. I'm questioning if I've done step 2 as you intended. Can you please comment if it was ok? Browsers (plural - chrome, edge, IE) show me it's invalid. Thanks! |
Hi, I ran into this issue when I generated the SSL certificate for the first time on my EdgeRouterX. Everything seemed to go correctly when I ran the
renew.acme.sh
-script for the first time (DNS Authority is Cloudflare), but I needed to run it in insecure-mode since allcurl
-calls to HTTPS-endpoints are failing while SSL-certificate is invalid.However the resulting certificate is still not trusted by Google Chrome (Version 94.0.4606.61 (Official Build) (x86_64)) as shown in the screenshot:
Any ideas why is this and how to get it fixed?
The text was updated successfully, but these errors were encountered: