invalid server certificate in google chrome

You can simply overwrite your old certificate file with the new one. You can add as many as you like.Īfter you approve the change, you'll get a new certificate with the domain name added. To add a name to the certificate, just Log In, click 'Add/Remove domain names' and add the domain you'd like.Īll our EV certificates come with 3 domains built in, after that there's a small charge per domain name. Here's a certificate with no Common Name at all - it's fine. Again, Chrome doesn't actually use the field anymore. The important bit is, getting a certificate with a new 'common name' won't fix the problem.

The field - the only field - that stores domain names on certificates these days is called 'Server Alternate Names', or SANs - so you might hear the process referred to as 'adding a new SAN' by people who like being specific. You'll need to add an additional domain names to the domain names on the certificate. For example, if you visited and the certificate only contained and you'd see this error. The real cause of the error is simple: the name of the site you're visiting isn't included on the certificate. Chrome is definately storing some information on its own storage just. Now that your way worked I’ve deleted the server certificate using MMC certificate snap-in chrome still opens up the site in GREEN color. The 'Common Name' field was used more than a decade ago, but has been phased out by browsers since 2001. When I tried installing server certificate using MMC certificate snap-in chrome ignored it and kept on displaying certificate invalid. The error message is wrong - Chrome, like most web browsers, doesn't use Common Names. Not only Google Chrome, but all other browsers also allow you to check the SSL certificate so that you can see if the exact domain or subdomain is listed in the certificate.

Invalid server certificate in google chrome