A WordPress site half-migrated to HTTPS serves the page over TLS but loads images, scripts or the login form over http://, and the mixed content trips the warning on some pages only.
A WordPress site half-migrated to HTTPS serves the page over TLS but loads images, scripts or the login form over http://, and the mixed content trips the warning on some pages only.
Set both WordPress Address and Site Address to the https:// form, run a search-replace on http:// asset URLs in the database, then flush every cache layer.
WordPress has its own failure mode, but Your connection is not private has a wider set of causes. The most common one overall is: The certificate expired (NET::ERR_CERT_DATE_INVALID).
Renew the certificate and reload the web server.
Running the check from outside your device separates a real certificate problem from a local clock or network issue in one step.
A WordPress site half-migrated to HTTPS serves the page over TLS but loads images, scripts or the login form over http://, and the mixed content trips the warning on some pages only.
Set both WordPress Address and Site Address to the https:// form, run a search-replace on http:// asset URLs in the database, then flush every cache layer.
Chrome's full-page warning shown whenever certificate validation fails. It is not a single error — the real cause is the NET::ERR_CERT_* code printed underneath it, and that code tells you which of expiry, trust, or hostname is wrong.