How to fix NET::ERR_CERT_DATE_INVALID

Check the device clock and scope

Chrome compares its current time with the certificate’s validity period. A clock set too far ahead can make a valid certificate appear expired. If several trusted sites fail, check automatic date and time, then retry. If it happens only on hotel or office Wi-Fi, try mobile data. A sign-in portal or managed network can affect the result. Avoid entering sensitive information while the warning is shown.

Inspect the live certificate

The browser validates an HTTPS certificate before it can read that address’s redirect. A working root site therefore does not rule out an expired www certificate. Check the exact name, validity dates and covered hostnames. A new Certificate Transparency entry shows issuance. The server can still be presenting an old certificate.

Find the failed renewal or deployment step

1. Verify DNS, including A and AAAA, to rule out an old endpoint.
2. Check the CDN’s edge certificate and the origin certificate separately.
3. Read the renewal log. Validation may have failed, or the server may not have loaded the renewed certificate.
4. Retest the failing address on two networks.

Follow the actual error code

ERR_CERT_COMMON_NAME_INVALID typically points to a hostname mismatch. ERR_CERT_AUTHORITY_INVALID points to trust. A clock correction does not fix either on the server. If you do not manage the site, send the owner the exact URL, error code and time.