#Sitesucker with invalid certificate how to#
#Sitesucker with invalid certificate install#
#Sitesucker with invalid certificate windows#

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.Ĭheck Subject Alternative Names (SAN) ConfigurationĪ Subject Alternative Names (SAN) certificate allows data encryption on multiple domains pointing to one site address. Therefore in some cases, the common name inside an SSL certificate is listed as a subdomain like. Wildcard SSL certificates can encrypt data on multiple subdomains.

#Sitesucker with invalid certificate install#

The only solution is to delete and install a new SSL certificate. If that isn’t the case, there is an SSL mismatch error between the two. The actual domain name should match the common name listed in the SSL certificate’s Issued to domain information. From the dropdown menu, select Connection is secure.Go to your website and click on the padlock icon on the address bar.

#Sitesucker with invalid certificate how to#

Here’s how to check the SSL certificate configuration: If you use a different browser, the process will be similar.

We will show you a step-by-step guide to troubleshoot the error using Google Chrome. To solve the issue, make sure you have installed the correct certificate and configured the SSL properly.

Make Sure That the SSL Is Set CorrectlyĪ common cause of this error is a mismatch between the common name on your SSL certificate and the correct domain name. That said, before you proceed, make sure to check whether your site is inaccessible only for you or everyone else. In this tutorial, we will explain ten methods to solve the NET::ERR_CERT_COMMON_NAME_INVALID error on your website. 10 Methods to Fix NET::ERR_CERT_COMMON_NAME_INVALID In some instances, the issue may be caused by the site’s address itself and antivirus configuration settings, browser extensions, cache, and more.Īlthough this error can be tricky to troubleshoot since it has many possible causes, rest assured that there are ways to fix it quickly. Most of the time, this happens because the common name which is written in the SSL certificate doesn’t match the actual domain name.įor example, if you want to install an SSL certificate on your website, the common name should also be .ĭomain mismatch is not the only reason why the NET::ERR_CERT_COMMON_NAME_INVALID error occurs. However, if the NET::ERR_CERT_COMMON_NAME_INVALID error occurs, it means the browser has failed to verify the SSL certificate. A website with a valid certificate will redirect the request via the HTTPS protocol, the secure version of HTTP. The web browser security warning should no longer be present and the certificates should now appear as valid and trusted.Usually when accessing a website, the browser has to verify the website’s SSL certificate to establish a secure connection.

#Sitesucker with invalid certificate windows#

After the certificates have been loaded in to your Windows Keystore, close and reopen your web browser and navigate to the URL.

Click Yes to continue importing the certificate.

After clicking on Finish, you will likely encounter a security warning indicating that Windows cannot validate the certificate.

Complete the remaining steps in the Certificate Import Wizard.

If you are importing an Intermediate Certificate, you will need to select and import the certificate in to the Intermediate Certification Authorities store. If you are importing the Root Certificate you will import in to the Trusted Root Certification Authorities store. Click the browse button, and select the appropriate certificate store.

Select Place all certificates in the following store.

Import the certificate to the Current User store, click Next.

Find the exported certificate file and double click the file to launch the Certificate Properties page.

Complete the remaining steps in the wizard to create the exported certificate file.

Name the file anything you wish, such as

The file can be saved in any location, here we are saving it to our default Downloads directory.

On the Details tab of the missing certificate, click Copy to File… to save a copy of the missing certificate.

Select the missing certificate and click View Certificate.

On the Certification Path tab we can see that at least one of our certificates is not trusted.

On the certificate properties page, verify that the certificate had been issued to the correct server and issued by a valid trusted source.

Click on the Security tab and click View Certificate. Press F12 to load the Chrome developer tools. This is because you have not yet told your computer to trust the Root Certificate Authority and Intermediate Certificate Authority used to sign the Planning Analytics certificate.

Access your URL using Chrome, for example:.

The example URL uses TM1Web, however would be applicable to any SSL secured web page. If you are using another browser, you will need to adjust the steps as required. The following steps use the Chrome web browser.