{"id":47694,"date":"2022-03-15T12:21:17","date_gmt":"2022-03-15T12:21:17","guid":{"rendered":"\/tutorials\/?p=47694"},"modified":"2026-03-10T09:29:12","modified_gmt":"2026-03-10T09:29:12","slug":"neterr_cert_common_name_invalid","status":"publish","type":"post","link":"\/ca\/tutorials\/neterr_cert_common_name_invalid","title":{"rendered":"How to fix “NET::ERR_CERT_COMMON_NAME_INVALID” Error"},"content":{"rendered":"

When accessing a website, the browser usually has to verify the website’s SSL certificate to establish a secure connection. A website with a valid certificate will redirect the request via the HTTPS protocol, the secure version of HTTP.<\/p>

However, if the “NET::ERR_CERT_COMMON_NAME_INVALID” error occurs, it means the browser has failed to verify the SSL. Most of the time, this happens because the common name in the SSL certificate doesn’t match the actual domain name.<\/p>

For example, if you want to install an SSL certificate on your website example.com<\/strong>, the common name should also be example.com<\/strong>.<\/p>

\"NET::ERR_CERT_COMMON_NAME_INVALID<\/a><\/figure><\/div>

Domain mismatch is not the only reason the “NET::ERR_CERT_COMMON_NAME_INVALID” error occurs. In some instances, the issue may be caused by the site’s address itself and antivirus configuration settings, browser extensions, cache, and more.<\/p>

Although this error can be tricky to troubleshoot since it has many possible causes, rest assured that there are ways to fix it quickly.<\/p>

Error code<\/strong><\/td>NET::ERR_CERT_COMMON_NAME_INVALID<\/td><\/tr>
Error type<\/strong><\/td>SSL Connection Error<\/td><\/tr>
Error variations<\/strong><\/td>Your connection is not private
Your connection isn’t private
Warning: Potential Security Risk Ahead
This site is not secure<\/td><\/tr>
Error causes<\/strong><\/td>Invalid SSL certificate
Misconfigured redirects
Browser extensions conflict
Antivirus issues
Operating system issues<\/td><\/tr><\/tbody><\/table><\/figure>
\"Hostinger<\/a><\/figure>

\n\n<\/p>

10 methods to fix “NET::ERR_CERT_COMMON_NAME_INVALID”<\/h2>

Before you proceed with the methods below, check whether your site is inaccessible<\/a> only for you or everyone else, as that will give you a better idea of the cause<\/span>.<\/p>

1. Make sure that the SSL is set correctly<\/h3>

A common cause of this error is a mismatch between the common name on your SSL certificate and the correct domain name. To solve the issue, make sure you have installed the correct certificate and configured the SSL properly.<\/p>

Here’s how to troubleshoot the error using Google Chrome. If you use a different browser, the process will be similar:<\/p>

    \n
  1. Go to your website and click on the padlock<\/strong> icon<\/strong> on the address bar.<\/li>\n\n\n\n
  2. From the dropdown menu, select Connection is secure.<\/strong><\/li>\n<\/ol>
    The padlock icon at the top right of the browser bar showing the \"Connection is secure\" notification on Google Chrome<\/a><\/figure><\/div>
      \n
    1. Select Certificate is valid.<\/strong><\/li>\n<\/ol>
      The padlock icon bar at the top right of the browser bar, showing how to check \"Certificate is valid\" on Google Chrome<\/a><\/figure><\/div>
        \n
      1. A window will open containing the site’s SSL certificate details.<\/li>\n<\/ol>
        \"SSL<\/a><\/figure><\/div>

        The actual domain name should match the common name listed in the SSL certificate’s Issued to<\/strong> domain information. If that isn’t the case, there is an SSL mismatch<\/a> error between the two. The only solution is to delete and install a new SSL certificate.<\/p>

        Check wildcard SSL configuration<\/strong><\/p>

        Wildcard SSL certificates can encrypt data on multiple subdomains. Therefore in some cases, the common name inside an SSL certificate is listed as a subdomain like domain.example.com<\/strong>.<\/p>

        If you use a wildcard certificate on your subdomain and encounter the “NET::ERR_CERT_COMMON_NAME_INVALID” error, it means that your SSL certificate doesn’t cover the subdomain you are trying to access.<\/p>

        Check Subject Alternative Names (SAN) configuration<\/strong><\/p>

        A Subject Alternative Names (SAN) certificate allows data encryption on multiple domains pointing to one site address. It covers www and non-www<\/a> versions of a website, subdomains, and top-level domain (TLD)<\/a> variations.<\/p>

        If the website you’re trying to access uses a SAN certificate, examine the list of domains it protects by checking the certificate details. If a web address is not there, the certificate doesn’t cover it.<\/p>

        2. Check WWW vs. Non-WWW versions and if your site is redirecting to another URL<\/h3>

        It is important to know whether your browser is forcing your visitors to another version of your website since not all SSL certificates cover both www and non-www site versions.<\/p>

        For example, if your domain is mydomain.com<\/strong>, and the server redirects your website visitors to www.mydomain.com<\/strong>, the error may appear if there is only one SSL installed for the “www” version.<\/p>

        There are two ways to solve this problem. The first one is to change the common name on the certificate your domain defaults to. The second is to purchase another SSL certificate to cover the domain you’re redirecting from.<\/p>

        3. Ensure WordPress URL is directing to the site URL<\/strong><\/h3>

        In some cases, the web protocol HTTP may have been manually changed to HTTPS without installing an SSL. As a result, the website may encounter a common name mismatch error.<\/p>

        If that’s the case, you should change your WordPress URL:<\/p>

          \n
        1. On the WordPress dashboard, click Settings <\/strong>and choose General<\/strong>.<\/li>\n<\/ol>
          \"The<\/a><\/figure><\/div>
            \n
          1. Check whether the WordPress Address (URL)<\/strong> and Site Address (URL)<\/strong> match.<\/li>\n<\/ol>
            \"WordPress<\/a><\/figure><\/div>
              \n
            1. If they don’t match, make the appropriate changes.<\/li>\n<\/ol>

              4. Check for any browser extension conflicts<\/h3>

              Having too many browser extensions can cause issues as they may conflict with one another. This may be a possible cause of the common name mismatch error.<\/p>

              Access the website in an incognito window and see if it is reachable. If it is, the problem might be caused by a browser extension. To solve this, disable the extensions one by one while checking your site to determine the cause of the issue. Once you’ve isolated the conflicting extension, delete it.<\/p>

              Here is how to remove extensions from Google Chrome:<\/p>

                \n
              1. Click the three dots<\/strong> at the top-right corner.<\/li>\n\n\n\n
              2. Hover over More tools<\/strong> and select Extensions<\/strong>.<\/li>\n<\/ol>
                \"The<\/a><\/figure><\/div>
                  \n
                1. Once the new window opens, select the extension you want to uninstall and click Remove<\/strong>.<\/li>\n<\/ol>

                  To prevent this issue from happening in the future, make sure to audit and update your extensions regularly.<\/p>

                  5. Clear the Browser Cache<\/h3>

                  Browser caching is a great feature that stores records of websites you’ve visited so the browser cloud load them faster next time.<\/p>

                  Unfortunately, outdated cache may cause problems by loading an old website version. To prevent this, clear the browser cache<\/a> regularly. This way, your browser will load the most recent version of the website and prevent the “NET::ERR_CERT_COMMON_NAME_INVALID” error from reoccurring.<\/p>

                  6. Disable antivirus software and firewall<\/h3>

                  Some antivirus software has an HTTPS scanning feature to add more protection. That said, it may block you from visiting HTTPS sites. If you trust the website, try disabling HTTPS scanning on your antivirus.<\/p>

                  If this option is unavailable, you may have to entirely turn off the antivirus software.<\/p>

                  Here’s how to disable Windows antivirus software:<\/p>

                    \n
                  1. Click on the Start<\/strong> button and look for Settings<\/strong>.<\/li>\n\n\n\n
                  2. Find Update & Security<\/strong> and choose Windows Security<\/strong>.<\/li>\n\n\n\n
                  3. Open Virus & threat protection<\/strong> and click Manage settings<\/strong>. Finally, switch Real-time protection<\/strong> to Off<\/strong>.<\/li>\n<\/ol>
                    \"The<\/a><\/figure><\/div>

                    Here’s how to do it on macOS using ESET Endpoint Security:<\/p>

                      \n
                    1. Open Finder <\/strong>and look for the ESET Endpoint Security<\/strong> application.<\/li>\n\n\n\n
                    2. Open the application and click Setup<\/strong>. Switch Real-time file system protection<\/strong> to Disabled<\/strong>.<\/li>\n<\/ol>
                      \"ESET<\/a><\/figure><\/div>

                      7. Configure URL settings in phpMyAdmin<\/h3>

                      The “NET::ERR_CERT_COMMON_NAME_INVALID” may be caused by the URL difference between option_value<\/strong> in siteurl <\/strong>and home <\/strong>rows of your website’s database. You can change your WordPress URL settings<\/a> via phpMyAdmin<\/strong>.<\/p>

                      Here’s how to do it via hPanel:<\/p>

                        \n
                      1. Go to your hosting account and open the phpMyAdmin <\/strong>application.<\/li>\n\n\n\n
                      2. Choose your site’s database and find the wp_options <\/strong>table. Inside wp_options<\/strong>, look for siteurl <\/strong>and home <\/strong>rows. Make sure both redirect toward the same URL.<\/li>\n<\/ol>
                        \"wp_options<\/a><\/figure><\/div>

                        8. Clear the SSL state<\/h3>

                        When you access a website, the browser will cache its SSL certificate to speed up the load time the next time you visit, which might cause the error later.<\/p>

                        This troubleshooting method involves clearing the SSL state in the browser and operating system. The process may differ depending on your operating system and browser.<\/p>

                        Here’s how to clear the SSL state on Windows:<\/p>

                          \n
                        1. Navigate to Control Panel<\/strong> -> Network and Internet <\/strong>-> Internet Options<\/strong>.<\/li>\n\n\n\n
                        2. The Internet Properties<\/strong> window will open. Click the Content <\/strong>tab and choose Clear SSL state<\/strong>.<\/li>\n<\/ol>
                          \"The<\/a><\/figure><\/div>

                          You can also clear the SSL state on your browser. Here’s how to do it on Google Chrome:<\/p>

                            \n
                          1. Navigate to Settings <\/strong>after opening the three dots menu<\/strong> at the top-right corner.<\/li>\n\n\n\n
                          2. Select Security and Privacy<\/strong> and click the Security <\/strong>option.<\/li>\n\n\n\n
                          3. Scroll down and choose Manage certificates<\/strong> to see the list of SSL certificates cached by Google Chrome. Lastly, click Remove <\/strong>to clear the SSL state.<\/li>\n<\/ol>
                            \"The<\/a><\/figure><\/div>

                            9. Change your LAN settings<\/h3>

                            Proxy settings route web traffic to protect users from malicious third parties. Any misconfiguration may restrict you from accessing websites or even cause SSL errors.<\/p>

                            Here’s how to change the LAN settings on Windows:<\/p>

                              \n
                            1. Navigate to Control Panel<\/strong> -> Network and Internet <\/strong>-> Internet Options<\/strong>.<\/li>\n\n\n\n
                            2. Choose the Connections <\/strong>tab and select LAN Settings<\/strong>.<\/li>\n<\/ol>
                              \"The<\/a><\/figure><\/div>
                                \n
                              1. Tick the Automatically detect settings<\/strong> option. Save the changes by clicking OK.<\/strong><\/li>\n<\/ol>
                                The tick button to activate \"Automatically detect settings\" through the LAN Settings menu on Windows<\/a><\/figure><\/div>

                                Here’s how to do it on macOS:<\/p>

                                  \n
                                1. Open Apple menu<\/strong>, click System Preferences<\/strong>, and choose Network<\/strong>. Select a network service from the list and click Advanced<\/strong>. Finally, switch to the Proxies<\/strong> tab.<\/li>\n\n\n\n
                                2. Tick Automatic proxy configuration<\/strong> and save the changes by clicking OK.<\/strong><\/li>\n<\/ol>
                                  \"The<\/a><\/figure><\/div>

                                  10. Update your operating system and browser<\/h3>

                                  It is crucial to update your applications and operating system regularly. Failure to do so can result in software instability, potentially leading to many website errors.<\/p>

                                  Here’s how to check for Google Chrome updates:<\/p>

                                    \n
                                  1. Click the three dots<\/strong> at the top-right corner and hover over Help<\/strong>. Select About Google Chrome<\/strong>.<\/li>\n\n\n\n
                                  2. The Settings <\/strong>will open, letting you know whether an update is available. If it is, click Update Google Chrome. <\/strong>If you can’t see this button, it means you’re on the latest version.<\/li>\n<\/ol>
                                    \"<\/a><\/figure><\/div>

                                    Follow these steps to update Windows:<\/p>

                                      \n
                                    1. Go to Settings<\/strong>, then click Update & Security.<\/strong><\/li>\n\n\n\n
                                    2. Choose Windows Update<\/strong>. The system will let you know whether an update is available. You can also manually Check for updates<\/strong>.<\/li>\n<\/ol>
                                      \"The<\/a><\/figure><\/div>

                                      Here’s how to check for updates on macOS:<\/p>

                                        \n
                                      1. Open the Apple<\/strong> menu and select System Preferences<\/strong>.<\/li>\n\n\n\n
                                      2. Choose Software Update<\/strong>. Click Update Now<\/strong> if a new version of macOs is available.<\/li>\n<\/ol>
                                        \"The<\/a><\/figure>

                                        How the “NET::ERR_CERT_COMMON_NAME_INVALID” error looks on different browsers<\/h2>

                                        Depending on your browser, the common name mismatch error warning message may differ. In this section, we’ll take a look at what it looks like on several popular browsers.<\/p>

                                        Google Chrome<\/h3>

                                        If you visit a website with an SSL error using Google Chrome, the browser will display the “Your connection is not private”<\/strong> message with “NET::ERR_CERT_COMMON_NAME_INVALID” under it. Google Chrome also warns visitors that attackers might steal their information through the website.<\/p>

                                        \"NET::ERR_CERT_COMMON_NAME_INVALI<\/a><\/figure><\/div>

                                        Google Chrome will recommend users to get Back to safety<\/strong>. That said, it’s still possible to visit the website by clicking on Advanced <\/strong>and choosing to Proceed to the website<\/strong>.<\/p>

                                        Microsoft Edge<\/h3>

                                        If you encounter the “NET::ERR_CERT_COMMON_NAME_INVALID” error on Microsoft Edge, you’ll see the “Your connection isn’t private”<\/strong> message along with a warning that accessing the website might invite attackers to steal your personal information.<\/p>

                                        \"NET::ERR_CERT_COMMON_NAME_INVALI<\/a><\/figure><\/div>

                                        You will be able to choose whether to Go Back<\/strong> or visit the website by choosing Advanced<\/strong>.<\/p>

                                        Mozilla Firefox<\/h3>

                                        Mozilla Firefox displays a unique version of this error message. It says “Warning: Potential Security Risk Ahead”<\/strong> and warns the visitor that the browser has detected a potential security threat and did not continue to the website.<\/p>

                                        \"NET::ERR_CERT_COMMON_NAME_INVALI<\/a><\/figure><\/div>

                                        Firefox doesn’t indicate the code for the common name mismatch error. Instead, it informs visitors what happened in detail, mentions that the issue is most likely with the website, and provides solutions to the problem.<\/p>

                                        Opera<\/h3>

                                        When you encounter the common name mismatch error using Opera, the browser displays a similar warning message to Google Chrome and warns you that attackers may be trying to steal your personal information.<\/p>

                                        \"NET::ERR_CERT_COMMON_NAME_INVALI<\/a><\/figure><\/div>

                                        The Help me understand<\/strong> button describes why Opera doesn’t let visitors access the website. It says the browser doesn’t trust the SSL certificate used on the website.<\/p>

                                        Internet Explorer<\/h3>

                                        Internet Explorer keeps its “NET::ERR_CERT_COMMON_NAME_INVALID” error message simple by stating, “This site is not secure.”<\/strong> I<\/span>t then explains that someone might be trying to fool the visitor or steal their information. It then warns the user to close the site immediately.<\/p>

                                        \"NET::ERR_CERT_COMMON_NAME_INVALI<\/a><\/figure><\/div>

                                        Internet Explorer users can choose to Close this tab<\/strong> or see More information<\/strong>. If you select More information<\/strong>, the browser explains that it doesn’t trust this website’s SSL certificate and displays the error code “DLG_FLAGS_INVALID_CADLG_FLAGS_SEC_CERT_CN_INVALID”.<\/p>

                                        Conclusion<\/h2>

                                        SSL is an essential part of a website that is dedicated to protecting users’ data via encryption methods. However, if you’ve misconfigured the SSL settings, you may encounter an error such as “NET::ERR_CERT_COMMON_NAME_INVALID”.<\/p>

                                        Dealing with the common name mismatch error can be tricky, but many methods exist to solve it quickly. The solutions involve changing the SSL configuration, URL redirection, advanced browser settings, and proxy settings.<\/p>

                                        We hope this article has helped you troubleshoot the common name mismatch issues. If you have questions or tips, feel free to leave a comment below.<\/p>

                                        NETT::ERR_CERT_COMMON_NAME_INVALID FAQs<\/h2>

                                        What causes “NET::ERR_CERT_COMMON_NAME_INVALID”?<\/h3>

                                        “NET:ERR_CERT_COMMON_NAME_INVALID” is a certificate error that occurs when the SSL\/TLS certificate presented by a website is not issued for the specific domain or subdomain that the user is attempting to access. This can be caused by a misconfigured certificate or a mismatch between the certificate and the website’s hostname.<\/p> <\/div>

                                        How do I prevent “NET::ERR_CERT_COMMON_NAME_INVALID”?<\/h3>

                                        To prevent this error, ensure that the SSL\/TLS certificate presented by the website is valid, issued for the correct hostname, and issued by a trusted Certificate Authority. Ensure that the website’s hostname matches the name on the certificate. Avoid accessing websites that trigger SSL warnings or errors.<\/p> <\/div>

                                        What are the consequences of “NET::ERR_CERT_COMMON_NAME_INVALID”?<\/h3>

                                        The consequences of “NET:ERR_CERT_COMMON_NAME_INVALID” can include an inability to access the website, loss of sensitive data, and exposure to security risks. Users may also experience degraded website performance, slow page load times, and increased vulnerability to phishing attacks and malware infections.<\/p> <\/div> <\/div>\n","protected":false},"excerpt":{"rendered":"

                                        When accessing a website, the browser usually has to verify the website’s SSL certificate to establish a secure connection. A website with a valid certificate will redirect the request via the HTTPS protocol, the secure version of HTTP. However, if the “NET::ERR_CERT_COMMON_NAME_INVALID” error occurs, it means the browser has failed to verify the SSL. Most […]<\/p>\n

                                        Read More…<\/a><\/p>\n","protected":false},"author":298,"featured_media":139568,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"NET::ERR_CERT_COMMON_NAME_INVALID: 10 Solutions to the Error","rank_math_description":"Encountering a NET::ERR_CERT_COMMON_NAME_INVALID error when accessing a website is common. Check out these 10 solutions to fix it.","rank_math_focus_keyword":"net::err_cert_common_name_invalid","footnotes":""},"categories":[1],"tags":[],"class_list":["post-47694","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"hreflangs":[{"locale":"en-US","link":"https:\/\/www.hostinger.com\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-CA","link":"https:\/\/www.hostinger.com\/ca\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-UK","link":"https:\/\/www.hostinger.com\/uk\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-PH","link":"https:\/\/www.hostinger.com\/ph\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-MY","link":"https:\/\/www.hostinger.com\/my\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-IN","link":"https:\/\/www.hostinger.com\/in\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-AU","link":"https:\/\/www.hostinger.com\/au\/tutorials\/neterr_cert_common_name_invalid","default":0},{"locale":"en-NG","link":"https:\/\/www.hostinger.com\/ng\/tutorials\/neterr_cert_common_name_invalid","default":0}],"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/posts\/47694","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/users\/298"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/comments?post=47694"}],"version-history":[{"count":30,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/posts\/47694\/revisions"}],"predecessor-version":[{"id":138298,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/posts\/47694\/revisions\/138298"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/media\/139568"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/media?parent=47694"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/categories?post=47694"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/ca\/tutorials\/wp-json\/wp\/v2\/tags?post=47694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}