03-23-2023 06:49 AM
Hi, it seems HTTPS should be enabled and activated for the EWC, but I'm still getting the no https indicator on my browser when going to the IP for the web GUI:
What other steps should be taken?
Solved! Go to Solution.
03-23-2023 07:48 AM
HTTPs is enabled as you can see from the screenshot and the URL. The not secure error you are getting is due to not having a trusted certificate to access HTTPs and thus browsers will always throw that error at you. If you wish to resolve this , you will need to install a 3rd party certificate onto the controller and set that as the HTTP trust point as shown below in your screenshot
03-23-2023 07:46 AM - edited 03-23-2023 07:47 AM
You probably don't have installed a valid certificate for the IP/hostname. Then the red message is normal. If you click on it, you should see that your browser doesn't trust the offered certificate. The connection itself should still be encrypted though.
03-23-2023 07:48 AM
HTTPs is enabled as you can see from the screenshot and the URL. The not secure error you are getting is due to not having a trusted certificate to access HTTPs and thus browsers will always throw that error at you. If you wish to resolve this , you will need to install a 3rd party certificate onto the controller and set that as the HTTP trust point as shown below in your screenshot
03-23-2023 08:44 AM
Ah right, I wasn't sure if we could just use the built-in trustpoints. So we need a third-party cert, okay. Thanks.
03-23-2023 09:16 AM
You can use them, but not without the red warning. There are possibilities to install that self-signed certificated in your computer certificate trust store and then your browser should trust it, if the URL is correct in the CN of the certificate.
But the clean way is to use a third-party cert, if you want to get rid of the red message.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide