Certificateemitted with Invalid timestamp

[marcelao]

I´ve renewed my certificate and emitted a new one, but they don´t work
report error
Certificate Transparency:

SCT Google 'Xenon2024' log (Embedded in certificate, Invalid timestamp)

SCT Let's Encrypt 'Oak2024H2' log (Embedded in certificate, Invalid timestamp)

[MikeMcQ]

Welcome @marcelao

Can you please provide a link to the cert in https://crt.sh or provide the domain name.

We need some way to find and look at the cert

[marcelao]

Hi.
https://www.iempresarial.com.br/certs/cert.pem
Thank´s

[marcelao]

Domain name is
www.iempresarial.com.br
i´ve turn back the old certificate

[Bruce5051]

I don't see an invalid timestamp, they are base from UTC±00:00 UTC+00:00 - Wikipedia
UTC - Time.is

Using CSR Decoder and Certificate Decoder this is what I see for the certificate

[MikeMcQ]

That cert is not yet in the crt.sh logs but I found it in another CT log system. The dates on the cert look correct to me.

Is the date and time correct on the machine showing you the date error?

Where exactly do you see the error about the date?

[Bruce5051]

Has your geographic location just entered Daylight saving time or exited?
Or has when Daylight saving time happens recently changed for your geographic location?

[marcelao]

yes, it happened.

Actually i dont know...

[marcelao]

[marcelao]

Now it´s working!!!!

Thank you a lot!!!!!!

It was time ahead of expedition

[Bruce5051]

Using Windows 10 Firefox 124.0.1 (64-bit) I see this and it seems fine.

Using Windows 10 Google Chrome Version 123.0.6312.59 (Official Build) (64-bit) I see this and it seems fine also.

[marcelao]

Yes, i published it now and it is working fine!!!

[Nummer378]

Please verify that your computers time is set correctly. https://time.is.

[orangepizza]

BTW if you happen to dual boot windows save/read local time in RTC but Linux deals it as UTC time so change os make clock change as timezone difference