I’m running my renewal cronjob at 7am CET (2018-12-27T07:00:00+0100), yet the issued certificates have a not_before of 5am UTC (2018-12-27T05:00:00+0000), and the not_after is also offset by one hour. Shouldn’t the certificates have a not_before 6am UTC, since that’s when they are issued?

Thanks, but no, this is not my issue. When I renew the certs (on a server located in UTC+1 = CET, which is irrelevant) and then check them at https://crt.sh/?q=example.com , then the Validity Not Before and Not After shows UTC minus 1 hour on that page. It should show UTC. I generate it at 7 am CET…

[image] qwerto: Thanks, but no, this is not my issue. Yes, this is exactly your issue. [image] qwerto: I generate it at 7 am CST and the certificate (which I download with a Python script to get the timestamp in order to check if the server is effectively using the new certificate) shows…

@tdelmas Ah, ok, I had not seen your answer. Thank you, that makes sense. @danb35 You’re right, I’m sorry, because I only had seen JuergenAuer’s response.

[image] qwerto: Ah, ok, I had not seen your answer. Thank you, that makes sense. My fault, I have delete it then edited it, to add explanations...

Wrong validity timestamps in certificate?

Issuance Policy

JuergenAuer December 27, 2018, 11:12am 3

Hi @qwerto

there

is a thread with that problem. A computer with the wrong time settings (perhaps wrong time zone), so the new created certificate isn't valide.

Topic		Replies	Views
Time zone problem with issue date? Issuance Tech	13	8967	November 8, 2015
Certificate not yet valid after renewal? Help	3	2056	June 12, 2017
Certificate Not Valid Before dated 1 hour prior to generation Help	2	1893	November 28, 2017
Certificateemitted with Invalid timestamp Issuance Tech	13	1120	March 25, 2024
Wrong timestamps logged for new certificate Help	13	667	August 21, 2023

Wrong validity timestamps in certificate?

Related topics