Additionally, when viewing the certificate via windows, the Certificate status says, "This certificate has invalid digital signature." When Google Chrome tried to connect to 10.36.0.1 this time, the website sent back unusual and incorrect credentials. With the web client, certificates play a much more important role in the overall design and untrusted certificate on your vCenter and ESXi hosts will plague you when trying to deploy new VMs, import OVF’s and other upload situations. NET::ERR_CERT_INVALID ... if you are using Windows vCenter Server, you won’t be able to download the certificate file, since there will be no link to download the archive with the certificate. Chrome tried to connect to
However Chrome provides no way to import certs into the store so you should add them via IE instead. Chrome doesn't have it's own cert store and uses Window's own.
10.36.0.1 normally uses encryption to protect your information. So, I think now you are clear on the reasons for the occurrence of SSL errors on your computer. An upgrade vSphere 6.5 means no more beloved Windows/C# vSphere Client and loads of people are being forced to the web client. Your connection is not private NET::ERR_CERT_INVALID 08-06-2018 10:11 PM. I'll award the bounty because of your effort (especially your screenshot of the green lock, which gave me hope that it was possible). incorrect credentials. Let’s check out the tutorial on “How to fix NET::ERR_CERT_AUTHORITY_INVALID chrome Error?” How to fix your connection is not private NET::ERR_CERT_AUTHORITY_INVALID Error? Here is the guide for both users and webmasters to get rid of this problem. When Google. NET::ERR_CERT_AUTHORITY_INVALID [Hide advanced] [Reload]