What it means
A certificate is valid from a start date to an end date. The certificate your server sends has a start date that hasn't arrived yet, so browsers treat it as not valid. The detail shows the date it becomes valid.
Why it matters
Until that date, visitors get a security warning and apps refuse to connect, exactly as with an expired certificate. This usually happens right after a certificate was issued with a start date set ahead, after a time zone mix-up, or when a server's clock was wrong when the certificate was made on it.
How to fix it
- Look at the start date in the result. If it's days away rather than minutes, something went wrong when the certificate was made.
- If the certificate was made on your own server (a self-made or internal certificate), check that server's clock and time zone, correct them, and issue the certificate again.
- If a certificate authority issued it, ask them to reissue it with today's date, or put the previous certificate back until the new one becomes valid.
- Install the certificate with its full chain and reload the web server.
Linux servers
Check the clock with timedatectl. If it is off, turn on time synchronisation with
sudo timedatectl set-ntp true and issue the certificate again.
Check it worked
Run the SSL check again. Each card should say "Trusted" and show a start date in the past. If the start date is still ahead, the server is still sending the new certificate; restore the old one until then.