Certificate seems updated on server but still listed as expired during site access

3 months ago I transitioned to letsencrypt. I got letsencrypt working using "acme.sh/acme.sh --issue -d mysite.com -d www.mysite.com -w /home/myname/public_html/ --server letsencrypt" and then in cPanel providing the generated certificate and key.

Since it has been 3 months it expired, so I repeated the process above. In cPanel it says it's updated and now expires on July 14, 2023. However, when I go to the site it still says it's expired with the date of April 12, 2023. Is there something extra I need to do?

Restart the web service?

3 Likes

Unfortunately I've already done that and it didn't solve the issue.

Restart the machine the web server is running on?

1 Like

Maybe clear your browser's cache? What does this SSL Checker site say about the cert?

3 Likes

The SSL checker says it's still expired.

Is cPanel truly connected to and with your web server?

2 Likes

I'm quite certain it is.

With the limited info you gave us it's hard to be specific. You could try asking on a cPanel forum. Or, fill out more of the info from the form you were shown

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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

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):

4 Likes

I reached out to my hosting provider and it's been resolved. The only feedback they gave was, "The issue was server related". A bit frustrating I spent several hours trying to resolve it, but I guess the lesson is to reach out sooner than later. Thanks for all the replies here!.

4 Likes

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