Most likely, you did not generate or apply for your renewal certificate. Think of SSL like a passport – when the old one expires you must toss it out and apply for a new one. You should be able to see in your account or via an email how to generate or apply for your new order. If you have generated, make sure that the new certificate was approved and installed in place of the old expiring certificate. If the new certificate is installed, then the issue is with the configuration. Common solutions to this problem are to restart your webserver (http server), also to uninstall/delete the incorrect/old certificate(s).

Most likely, you did not generate or apply for your renewal certificate. Think of SSL like a passport – when the old one expires you must toss it out and apply for a new one. You should be able to see in your account or via an email how to generate or apply for your new order. If you have generated, make sure that the new certificate was approved and installed in place of the old expiring certificate.

Depending on the certificate details submitted with your renewal, the Certificate Authority (CA) may be able to use some previously validated information/documents. If this is an EV order, certificates validated more than 13 months are required to complete full business validation again, including providing new documentation. For OV orders, the CA can reuse previous validated information up to 39 months from the original order. Please note that if any details of your organization change, you may be required to provide additional documents.

We recommend that you generate a new CSR to renew your certificate; however, if generating a new CSR proves to be challenging, you can use the original CSR and it will work. The drawback of using the original CSR is that it will be the exact same private key, so it’s a little less secure.

A renewal is basically the same as buying a brand new certificate, “renewal” is simply an industry term that is used by all providers. So, you can go through the exact same purchasing process to renew your certificate. However, if you have access to a “renewal” option when purchasing your SSL certificate, be sure and use that so you get the remaining time rolled over from your expiring certificate to your new renewal certificate.

You can use the SSL checker tool from Cert Logik to test whether or not your SSL certificate has been installed properly. The link is: https://certlogik.com/ssl-checker/.

This is more than likely because the intermediate certificates were never installed. Installing them should resolve this error. Below you will find links on where to locate and install your intermediate certificate, depending on the Certificate Authority that issued the cert. Or you can always contact your SSL provider.

• https://knowledge.digicert.com/generalinformation/INFO4331.html
• https://knowledge.geotrust.com/support/knowledge-base/index?page=content&id=AR1421
• https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=AR1384
• https://knowledge.rapidssl.com/support/ssl-certificate-support/index?page=content&id=AR1548
• https://support.comodo.com/index.php?/Default/Knowledgebase/List/Index/108/sha-2

This means that URL in the browser and the common name in the certificate are not an EXACT match (for instance, the www. is missing). Another common reason for this is the web host’s certificate is incorrectly assigned to your domain name. Or, you purchased a certificate that does not cover the specific subdomain you are looking at.

There are actually many reasons why this could be happening, some of which could be entirely unrelated to your certificate. So, unfortunately, we can’t give specific advice. But, we would recommend clicking on the “Details” button to get more specific information about this error from the browser.

There are several reasons why this could be occurring or a combination of several. The four most common reasons are:

1. Insecure content, which means there are HTML elements on your site being explicitly linked by http. This would need to be updated via your system administrator.
2. Missing or invalid intermediate chain. Your certificate is issued from an intermediate file. Make sure that you install this alongside your certificate on your server. If you do not have this file please contact your SSL provider.
3. Your certificate is issued with the SHA-1 hashing algorithm. Browsers no longer trust this algorithm. You will need to reissue with SHA-2.
4. It is the incorrect certificate. Sometimes your old expired certificate or a certificate provided by your hosting company or a self-signed certificate is installed on your site. You will need to identify the source of the incorrect certificate and contact that party to resolve the issue.