How long till the cert is recognozed by browsers

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My cert expired and the renewal was not working. I deleted the cert and generated a new one. However, my old expired cert is still showing up on browsers. How long till the new cert is recognized by browsers going to my site?

My domain

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Hello @azook, welcome to the Let's Encrypt community. :slightly_smiling_face:

Here is a list of issued certificates for |, the newest being 2022-10-14.

I cannot find the domain name, is the name correct?
I do not find any DNS Records for it.


Once the new cert is being sent to a browser and received by said browser the new cert is recognized.

1 Like seems to be sending this issued certificate | 7115804396,
which Expired Oct 10 20:46:09 2022 GMT

1 Like

It seems that is running on Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.4.16

OpenSSL 1.0.2 is old and no longer supported. From here: /source/index.html
Note: The latest stable version is the 3.0 series supported until 7th September 2026. This is also a Long Term Support (LTS) version. The previous LTS version (the 1.1.1 series) is also available and is supported until 11th September 2023. All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used. Users of these older versions are encouraged to upgrade to 3.0 as soon as possible. Extended support for 1.0.2 to gain access to security fixes for that version is [available](

1 Like is not the correct URL. I deleted the cert and created a new one. This time I made sure it was

And here is a list of issued certificates |

However your server is still serving up an Expired Certificate.

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).

And to assist with debugging there is a great place to start is Let's Debug.


I just got it fixed. I did not tell my server to install the new cert. Thanks for your assistance.


You are welcome @azook! Have a good day. :slightly_smiling_face:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.