Skip to main content

"NET::ERR_CERT_COMMON_NAME_INVALID" error in Google Chrome browser while configuring HTTPS on TIBCO Spotfire Server

Rich Talbot
  • Created
Date Posted:
Product: TIBCO Spotfire®

Problem:

"NET::ERR_CERT_COMMON_NAME_INVALID" error in Google Chrome browser while configuring HTTPS on TIBCO Spotfire Server


Solution:

While configuring HTTPS on the TIBCO Spotfire Server, you may find that the HTTPS URL of the TIBCO Spotfire Server is working fine in Internet Explorer, but it is displaying a "NET::ERR_CERT_COMMON_NAME_INVALID" error in the Google Chrome browser. During Transport Layer Security (TLS) connections, Chrome browser checks to make sure the connection to the site is using a valid, trusted server certificate.

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.

Doc: Configuring HTTPS External:

Comments

0 comments

Article is closed for comments.