For Chrome 58 and later, only the subjectAlternativeName extension, not commonName, is used to match the domain name and site certificate. The certificate subject alternative name can be a domain name or IP address. If the certificate doesn’t have the correct subjectAlternativeName extension, users get a "NET::ERR_CERT_COMMON_NAME_INVALID" error letting them know that the connection isn’t private. If the certificate is missing a subjectAlternativeName extension, users see a warning in the Security panel in Chrome DevTools that lets them know the subject alternative name is missing.

To resolve the issue, you can generate a new certificate with correct subjectAlternativeName extension.

In other scenarios, there are several other solutions for this issue like clearing your internet browser cookies and cache, making sure that the browser is up-to-date, clearing the SSL state on your Windows PC, flushing the DNS on your Windows PC, changing your internet DNS address settings, checking and correcting the Date & Time settings on your Windows PC, checking your antivirus software or firewall, turn off extensions in Chrome, etc. Please refer to the below listed online articles for more details on the error and it's resolution techniques.

• https://docs.tibco.com/pub/spotfire_server/7.11.1/doc/html/TIB_sfire_server_tsas_admin_help/GUID-58E436B3-A057-431C-B65C-92FCE34AB224.html

• https://support.google.com/chrome/a/answer/7391219?hl=en
• https://medium.com/@sslsecurity/fix-net-err-cert-invalid-error-on-chrome-3a1d9067ac57
• https://www.xtremerain.com/fix-err-cert-common-name-invalid
• https://www.drivereasy.com/knowledge/fix-err-cert-common-name-invalid-chrome-solved/
• https://aboutssl.org/quick-steps-fix-google-chrome-ssl-certificate-errors/
• https://www.youtube.com/watch?v=4FmzpOGNxAE