Certificate expired (Certificate not yet due for renewal)

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. https://crt.sh/?q=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:
certbot renew and sudo certbot renew

It produced this output:

My web server is (include version):
nginx 1.10.3-1+deb9u2

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

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

From my perspective, https://phone.teomanga.org.nz/ is using a certificate for remote.teomanga.org.nz issued by GoDaddy that expires in 2020. Plus it’s a Microsoft IIS server, not Nginx.

It doesn’t match, but it’s also not expired.

What software is saying what URL is expired?

Has Nginx been reloaded or restarted since the certificate was renewed in February? (If the certificate was created with certbot --nginx, Certbot would do this automatically.)

What certificate and key files are Nginx configured to use?

1 Like

That’s on port 443, sorry I should have added that this cert is running on port 5001

Oh. That makes sense. :smile: Yes, I see the expired certificate on the Nginx server on https://phone.teomanga.org.nz:5001/.

As you can see in the screenshot I originally attached certbot acknowledges that the certificate expires 05/03/2019
The server time and my local time is 05/03/2019

But it also says it’s not due for renewal today…

The certificate expires May 3. That’s what Certbot is saying.


What certificate-related files is your nginx configuration pointed at? Did you set up that configuration manually after you got your certificate?

Do you remember – or still have a record of – the command used to create the certificate originally?

-sigh- thanks everyone for your help but I can confirm that this was a Layer 8 issue.

I was reading 5/3 as 5th of march (today)
Not 3rd of May, which it is…

Nginx was configured to the wrong certificates

1 Like

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