Fix a certificate that is not valid yet on Cloudflare
Why it matters
Browsers reject a certificate before its start date and show a full-page security warning. This is usually a certificate created on a machine whose clock was ahead (self-signed or internal CA), or a certificate for a later switch that was installed early.
The fix
- For a proxied record the certificate comes from Cloudflare's edge. A not-yet-valid edge certificate is a Cloudflare-side problem, so check the Cloudflare status page and contact Cloudflare support.
- If you uploaded a custom certificate, its start date is in the future. Open SSL/TLS then Edge Certificates, then delete it or replace it with a currently valid one.
Related
- Reported by the certificate chain and expiry check
- Renew the expired TLS certificate
- Renew the certificate before it expires
- Install a certificate that covers this hostname
- Replace the self-signed certificate with a trusted one
- Use a certificate from a publicly trusted authority
- Serve the full certificate chain
- Replace the expired intermediate certificate
- Re-issue the certificate with a stronger key
- Replace the certificate that uses a broken hash
- Fix the certificate that browsers reject
Scan your domain to see whether this applies to you.