Hacker News new | ask | show | jobs
by andyco01 1505 days ago
I was on chat with godaddy and they said that any certs that were issued before June 2020 will not be on any of Google's SCTs and that they will need to be re-keyed. I did that with a new cert as ours was expiring in July and that has fixed it for us. So give re-keying a try.
3 comments

This is going to be a very annoying thing for us, if true. Our April 2020 issued Cert expires in July and was on track to roll out a new cert in two weeks. This means we get to push up the timetable and do an out-of-sequence patch roll to address this in over 100 environments.

Fun night ahead.

The weird part is, if you click on the error in chrome, it displays the Cert Details, including this wonderful gem:

    Certificate Transparency:
    SCT Google 'Pilot' log (Embedded in certificate, Verified)
    SCT Google 'Rocketeer' log (Embedded in certificate, Verified)
    SCT DigiCert Log Server (Embedded in certificate, Verified)
https://groups.google.com/a/chromium.org/g/ct-policy/c/abPZR...

Pilot and Rocketeer were just shut down, however, I'm surprised this had any impact because the above post says:

> If you are delivering SCTs embedded in the certificate, this should require no action on your part. All previously-issued certificates containing SCTs from these logs that complied with the Chrome CT Policy will continue to do so.

Edit: Ah but if /all/ the logs are retired, it's no longer valid. So if you have two retired google logs + a digicert log that's presumably also retired, the SCTs are no longer acceptable.

My problem is solved for both of my sites. I renewed both certs and uploaded them and each site now loads fine in chrome. Thank you to everyone who posted in this thread. I can now go get a beer!
thx for the info. My 2 sites' certs are valid from (before June 2020) Set to auto renew in July. 5/9/2020 to 7/7/2022 5/10/2020 to 7/9/2022

I'll try re-keying one of them and see if that solves the problem... based on your info seems that it would. Thank you!