Hello there. I’m running the Edge browser on Windows 10 1709. When I tried to bring up the root gui via https I got the standard browser warning message for self-signed certs. I researched a few MS forums and apparently the solution was to import the signing cert into the Trusted Root Store. I therefore did so with cert.pem (having previously tried https-cert.pem). The root store recognised it as a valid question but I’m still getting the same browser warning. I’d like to get rid of this if I could. Btw, the exact message in Edge was:
“Your PC doesn’t trust this website’s security certificate.
The hostname in the website’s security certificate differs from the website you are trying to visit.
Error Code: DLG_FLAGS_INVALID_CA
Go on to the webpage (Not recommended)”
The cert.pem is used for syncing, not the https. That’s what the https-cert.pem is for.
AFAIK, there is no signing cert. I don’t know if and how you can make a valid cert for localhost.
I hear ya. A modicum of common sense should lead one to conclude that https- is https related!
I’m going to do some research re. other browsers. I guess I could run the local host GUI unencrypted. Arguably (but not definitely), it’s the least at risk.
Shown error is expected afaik. This is due to having a self signed certificate and your browser expects a CA-signed one. More information about Certificate authority and providers can be found here: https://en.wikipedia.org/wiki/Certificate_authority
Since your certificate is self signed and does work for the encryption purposes, still your browser does tell you that it cannot recognise the certificate provider. There are some bad guys out there that tries to trick you with their self signed certificates, therefore nowadays modern browsers are more strict on this and making sure that you know it is not a CA signed certificate.
So basically “like it or lump it”
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.