Managed WordPress hosts renew certificates on their own schedule, and a domain moved between hosts often keeps DNS pointing at the old host whose certificate has since lapsed.
Managed WordPress hosts renew certificates on their own schedule, and a domain moved between hosts often keeps DNS pointing at the old host whose certificate has since lapsed.
Confirm the A record points at the current host, then trigger a certificate reissue in the host's dashboard. Do not install a certificate manually on managed hosting — it will be overwritten.
WordPress has its own failure mode, but ERR_CERT_DATE_INVALID has a wider set of causes. The most common one overall is: The certificate expired and auto-renewal silently stopped.
Renew immediately. For Let's Encrypt, run the renewal manually and read the output — the usual cause is a failing HTTP-01 challenge after a redirect or firewall change.
The SSL checker returns the exact notAfter date and days remaining for the hostname, which immediately separates 'genuinely expired' from 'your clock is wrong'.
Managed WordPress hosts renew certificates on their own schedule, and a domain moved between hosts often keeps DNS pointing at the old host whose certificate has since lapsed.
Confirm the A record points at the current host, then trigger a certificate reissue in the host's dashboard. Do not install a certificate manually on managed hosting — it will be overwritten.
The certificate the server presented is outside its validity window — almost always expired. Either the certificate genuinely lapsed, or the device's clock is wrong so a valid certificate looks expired.