---
title: "Your connection is not private on WordPress: cause and fix"
description: "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…"
canonical: "https://lemwatch.com/errors/your-connection-is-not-private/in-wordpress"
source: "https://lemwatch.com"
---

# Your connection is not private on WordPress

> 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.

## Why it happens on WordPress

 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.

## The fix on WordPress

 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.

## If that didn't fix it

 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.

## Check your own domain

 Running the check from outside your device separates a real certificate problem from a local clock or network issue in one step.

## Frequently asked questions

### Why does Your connection is not private happen on WordPress?

 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.

### How do I fix Your connection is not private on WordPress?

 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.

### What does Your connection is not private mean?

 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.


## Related

- [All causes of Your connection is not private](https://lemwatch.com/errors/your-connection-is-not-private)
- [All website error codes](https://lemwatch.com/errors)
- [Your connection is not private on iPhone](https://lemwatch.com/errors/your-connection-is-not-private/on-iphone)
- [Your connection is not private on Chrome](https://lemwatch.com/errors/your-connection-is-not-private/on-chrome)
- [Your connection is not private on Windows](https://lemwatch.com/errors/your-connection-is-not-private/on-windows)
- [Free SSL certificate check](https://lemwatch.com/tools/ssl-checker)
- [Your connection is not private on Android](https://lemwatch.com/errors/your-connection-is-not-private/on-android)
- [All monitoring checks](https://lemwatch.com/features)