Aad Slingerland 1 Posted September 7, 2019 Posted September 7, 2019 Greetings, Just did a fresh install of ESMC on a Windows Server 2019 Essentials machine (again). All the installation tasks complete okay as far as I can see. As part of the installation a digital certificate for supporting HTTPS (I think) was generated. I filled in the form describing the certificate details. When connecting with Google Chrome (or another browser BTW) the site https://10.0.0.6/era is not trusted. I am able to go through this by clicking Advanced and proceed but would like to fix this issue. When I inspect the certificate bij clicking on the red 'Not secure' text left of the URL in the address bar and have a look at the certificate details the most of it is rubbish. See also attached images. Could use some insight in this matter and help here, Aad
ESET Staff MichalJ 434 Posted September 9, 2019 ESET Staff Posted September 9, 2019 Certificate is self-signed, meaning it´s signed by a certification authority created by ESMC installer, during installation. Which means, it is of course not trusted. You can achieve trust, by importing the CA into the trusted root certification authorities on your system, or alternatively changing the certificate with a trusted one. Instructions are provided here: https://support.eset.com/kb6721/ In the upcoming release, we will allow choosing a custom HTTPS certificate during the installation using all in one installer.
Aad Slingerland 1 Posted September 9, 2019 Author Posted September 9, 2019 Hello Michalj, Thanks for the info. I'll have a look at the knowledge base article Regards, Aad
Aad Slingerland 1 Posted September 9, 2019 Author Posted September 9, 2019 Just installed this certificate (with the aid of internet explorer) in the collection 'trusted root certificates' and the annoying error when launching IE or Chrome is gone. This will do for me for now. Thanks again. MichalJ 1
Recommended Posts