Ignore : Cert with future not valid before date

This looks to be an issue with the testing site I used and not with the cert itself.
This can all be ignored now. Thanks!

– original below –

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:thninc.com

I ran this command: sudo sh ./certbot-auto certonly

It produced this output:- Congratulations! Your certificate and chain have been saved at:

My web server is (include version): na

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

My hosting provider, if applicable, is: na

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

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

Cert bot just issued me a new cert (thanks!) but the not valid before date is set in the future.

I went to : https://www.checktls.com/perl/live/TestReceiver.pl#TestService
to make sure the cert was good, it gave me the warning:


EXPIRED: Certificate 1 of 3 in chain:
Version: 3 (0x2)
Serial Number: 03:35:a1:24:76:06:35:b5:82:da:d5:5e:06:0b:f8:29:57:f4
Signature Algorithm: sha256WithRSAEncryption
commonName = Let’s Encrypt Authority X3
organizationUnitName =
organizationName = Let’s Encrypt
countryName = US
localityName =
StateOrProvinceName =
Not Before: Feb 6 20:54:19 2018 GMT <---- THIS IS THE ISSUE
Not After : May 7 21:54:19 2018 GMT
commonName = thninc.com

Which is a couple hours in the future still.

I don’t need any support, I just wanted to report the issue.
Thanks for a great service!

Hi @gzader,

I think there's something fishy going on with your clock, or the TestReceiver.pl script.

You can see in the copy of this certificate logged to certificate transparency that the NotBefore is Feb 6 15:54:19 2018 GMT. The current time in GMT is 17:37 at the time of this post so this seems OK to me and not any kind of an error (or a certificate valid only in the future).

I did check the clock on my system. And yes, the cert does show a proper time issued.

I suspect it is with the service I used to check the cert.


1 Like

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