How to fix “ERR_CERT_COMMON_NAME_INVALID”. Step-by-Step Guide

/ troubleshooting / By




How to fix “ERR_CERT_COMMON_NAME_INVALID”. Step-by-Step Guide






How to Fix the "ERR_CERT_COMMON_NAME_INVALID" Error

Learn how to resolve the "ERR_CERT_COMMON_NAME_INVALID" error step by step. This guide covers fixing SSL installation issues, adjusting date/time settings, clearing browser caches, troubleshooting extensions, and verifying proxy or antivirus settings. It also explains how to address mismatched domain configurations and update your system to prevent SSL conflicts.

Use our free chatbot to easily troubleshoot and solve technical issues like this.

Key Takeaways

  • The “ERR_CERT_COMMON_NAME_INVALID” error is related to SSL certificates and can be resolved by ensuring proper SSL certificate installation, date/time accuracy, and proper URL configurations.
  • Checking your browser, clearing caches, and troubleshooting extensions can also help eliminate the issue. Tools like EaseUS DupFiles Cleaner can optimize your system by removing unnecessary files that may interfere with SSL validation.
  • Issues with redirects, mismatched domains, proxy settings, or antivirus software can lead to the error.

Step-by-Step Guide to Fixing the “ERR_CERT_COMMON_NAME_INVALID” Error

1. Check Date and Time Accuracy

  • Reason: SSL certificates rely on accurate date and time settings to be validated.
  • Solution:
    • Ensure that your system’s date and time settings are correct.
    • On Windows, you can synchronize the time by going to Settings > Time & Language > Date & Time, and enabling Set Time Automatically.
    • On macOS, go to System Preferences > Date & Time, and click on “Set date and time automatically.”

This is essential because the certificate relies on the timestamp to evaluate its validity.

2. Verify SSL Certificate Installation

  • Reason: An improperly installed SSL certificate or using a self-signed certificate could trigger the error.
  • Solution:
    • Check your SSL installation by using an external tool like SSL Labs SSL Test to verify if the certificate is correctly configured. For enhanced security, consider encrypting your diagnostic activities with NordVPN, which protects your network from potential eavesdropping.
    • If you’re using a self-signed certificate, consider replacing it with a verified certificate from a trusted CA (Certificate Authority) like Let’s Encrypt.

3. Check for Misconfigured Redirects

  • Reason: Redirecting users from HTTP to HTTPS without a valid SSL certificate can cause this error.
  • Solution:
    • Ensure your server redirects HTTP to HTTPS after ensuring the SSL certificate is properly installed.
    • Check your .htaccess (for Apache) or nginx.conf (for NGINX) configuration to ensure redirects are correctly managed.

4. Check Browser Extensions

  • Reason: Some browser extensions might block SSL connections or interfere with the page load.

Solution:

  • Access in Incognito Mode: Right-click on your browser icon and open a new Incognito or Private window. If the page loads without errors, an extension might be the culprit.
  • Disable Suspicious Extensions:
    • Go to chrome://extensions/ or about:addons in Firefox.
    • Disable extensions one by one until you find the conflicting one.

Some ad-blockers, for example, can sometimes cause SSL-related issues—be sure to disable or whitelist the website.

5. Clear Browser Cache and Data

  • Reason: Corrupted browser cache or cookies can trigger this error.

Solution: Clear Cache

  1. Press CTRL+SHIFT+Del (or Cmd+Shift+Del on macOS).
  2. Select Cached Images and Files and Cookies.
  3. Click Clear Data.

Solution: Clear SSL State in Windows

  1. Open Internet Properties.
  2. Go to the Content tab.
  3. Click Clear SSL State.

Clearing the SSL cache can resolve issues where outdated or invalid certificates are stored locally.

6. Check Proxy Settings

  • Reason: Incorrect proxy settings, such as those configured manually, may prevent SSL validation.

Solution:

  1. Go to Internet Options > Connections tab.
  2. Click LAN Settings.
  3. Ensure Automatically detect settings is selected.

7. Check Antivirus and Firewall Settings

  • Reason: Some antivirus programs have HTTPS or web protection features that might interfere with SSL validations.

Solution:

  1. Open your antivirus software settings.
  2. Look for a setting such as HTTP/HTTPS scanning or Web Shield and try disabling it temporarily.
  3. Test the website again to see if the error persists.

If this resolves the issue, you may need to adjust your antivirus settings permanently or whitelist the website.

8. Verify Site Address and URL Settings

  • Reason: Differences between the domain name in the SSL certificate and the site’s URL can cause SSL validation errors.

Solution:

  1. For WordPress Users: Go to Settings > General and ensure that both WordPress Address (URL) and Site Address (URL) match the domain covered by your SSL certificate.
  2. For Manual Check:
    • Access phpMyAdmin and select your website’s database.
    • Navigate to the wp_options table.
    • Ensure that both siteurl and home rows match your domain (e.g., https://example.com).

9. Check for Mismatched WWW and Non-WWW Domains

  • Reason: An SSL certificate might only cover one version of your website (www or non-www).

Solution:

  • You need to ensure that your SSL certificate is valid for both www.example.com and example.com.
  • If your certificate only covers one domain, redirect traffic from the non-covered version to the covered version using 301 redirects in your .htaccess file or web server configuration.

10. Update Operating System and Browser

  • Reason: Outdated browsers or operating systems can result in compatibility issues with SSL certificates.

Solution:

  1. For Google Chrome: Go to Settings > Help > About Chrome, and it will check for and install any available updates.
  2. For Windows: Navigate to Settings > Update & Security and check for updates.
  3. For macOS: Open System Preferences > Software Update.

Keeping your software up-to-date ensures you are using the latest trusted certificate authorities. For seamless updates and secure backups of your critical system files, use MiniTool ShadowMaker.

Frequently Asked Questions (FAQs)

1. Why am I seeing the “ERR_CERT_COMMON_NAME_INVALID” error on my site?

  • The error usually occurs when there is a mismatch between the domain name listed on the SSL certificate and the website’s actual domain. It can also be caused by improper SSL certificate installation or date/time issues.

2. Is this error browser-specific?

  • No, this SSL error can happen on all browsers. However, some security settings or extensions on different browsers may affect how the error manifests.

3. How do I check if my SSL certificate is properly installed?

  • You can use tools like SSL Labs SSL Test to confirm that your SSL certificate is fully operational and correctly installed.

4. Can this error be caused by antivirus software?

  • Yes, antivirus software that scans HTTPS traffic can interfere with SSL connections, causing the “ERR_CERT_COMMON_NAME_INVALID” error.

5. Should I use self-signed certificates in production?

  • No, self-signed SSL certificates are not trusted by most browsers. In production environments, always use SSL certificates issued by a trusted Certificate Authority (CA).

6. I’ve updated my certificate, but the error persists. Why?

  • This could be due to caching. Try clearing your browser’s cache and the SSL state on your system (for Windows). The error could also be caused by old DNS records; flushing your DNS could help.

7. What’s the difference between www and non-www domains in terms of SSL certificates?

  • Both are considered different domains. Your SSL certificate must explicitly cover both unless you are using a wildcard certificate, which will cover all subdomains.
Post Views: 82

Related Posts

Subscribe
Subscribe