Troubleshooting · Troubleshooting
How to Fix "Your Connection Is Not Private" in WordPress
Short answer
Open the page in another browser and read the error code under Advanced. If the code says the certificate expired, only the site owner can fix it by renewing the certificate. If many sites show the warning, check your device clock first, since a wrong date makes valid certificates look expired.
Key takeaways
- The warning means the browser could not verify the site's certificate, not that the site is down.
- The error code under Advanced names the failed check, such as an expired certificate or a name mismatch.
- A wrong device clock makes good certificates look expired, and it affects many sites at once.
- Let's Encrypt certificates last 90 days and renew automatically, so an expiry usually means renewal stopped.
- Visitors cannot fix an expired certificate, but site owners can renew it in minutes through their host.
What does “Your connection is not private” mean?
The warning means your browser could not verify the site's certificate, so it stopped instead of loading the page.
A certificate is a small file that ties a site's keys to its domain name. MDN's TLS guide says the certificate binds the site's keys to its domain name, so the browser knows it is really connecting to that site.
When the check fails, the browser shows a full-page warning instead of the site, and it does not load any of the page content.
The warning does not prove the site is run by criminals. Google's Chrome help says a connection problem can come from the site, the network, or your device. The error code under the message tells you which of the three to check first.
How do you read the error code on the warning page?
Click Advanced on the warning page to see the error code, which names the exact check that failed.
Google's Chrome help lists several codes under this warning, including NET::ERR_CERT_AUTHORITY_INVALID and ERR_CERT_COMMON_NAME_INVALID.
A separate entry covers NET::ERR_CERT_DATE_INVALID, which Chrome shows as Your clock is behind or Your clock is ahead. Write the code down before you change anything, since it decides the fix.
| Error code | What failed | Who can fix it |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | Certificate dates, or your clock | You, or the site owner |
| ERR_CERT_COMMON_NAME_INVALID | Certificate name does not match the address | Site owner |
| NET::ERR_CERT_AUTHORITY_INVALID | Issuer is not trusted by the browser | Site owner, or your IT admin |
| ERR_CERTIFICATE_TRANSPARENCY_REQUIRED | Certificate missing from transparency logs | Site owner |
If the warning shows no code at all, try the same address in a different browser. Firefox and Safari word the same problem differently, and the extra detail can point to the cause. The code is the fastest way to tell a device problem from a site problem.
What if your device clock is wrong?
A wrong device clock is the most common cause, and it makes good certificates look expired.
Every certificate carries two dates, and the browser compares them with your device clock. If your clock is days or months off, a valid certificate looks expired or not yet valid.
Google's Chrome help says you get the Your clock is behind, Your clock is ahead, or NET::ERR_CERT_DATE_INVALID message when the device date and time are inaccurate.
- Open your device settings and turn on automatic date and time.
- Check that the time zone is set to automatic too.
- Reload the page and see if the warning is gone.
A clock problem affects many sites at once, not just one. If every HTTPS site shows the warning, the clock is the first thing to check. If only one site shows it, the problem is almost certainly on that site.
What if the certificate has expired?
An expired certificate is a site-side problem, and only the site owner can fix it by renewing the certificate.
Let's Encrypt's FAQ says its default certificates are valid for 90 days, and it recommends renewing every 60 days. Most hosts renew them automatically, so an expiry usually means the renewal stopped. A failed renewal can follow a host move, a DNS change, or a billing lapse.
As a visitor, you cannot fix an expired certificate from your side. Do not enter passwords or payment details on the page, since the browser cannot confirm who runs the site. Contact the site owner and tell them the exact error code and the date the warning started.
If you own the site, renew the certificate from your host panel and then reload the page in a private window. If the warning stays after renewal, the server may still be serving the old certificate, so restart the web server or ask your host to reload it.
What if the certificate name does not match the domain?
A name mismatch means the certificate was issued for a different address than the one you typed.
This is common when a certificate covers example.com but not www.example.com, or the other way around.
Let's Encrypt's FAQ says one certificate can list several names using the Subject Alternative Name mechanism, so the fix is to reissue the certificate with both names on it.
The site owner must request the new certificate; a visitor cannot fix it.
A mismatch can also mean the server is handing out the wrong certificate, such as a host default certificate for a different customer. Check both the bare domain and the www version of the address.
If one works and the other shows the warning, the certificate is missing one of the two names.
What if the warning only appears on public Wi-Fi?
On public Wi-Fi, the warning often means you have not signed in to the network yet, not that the site is broken.
Cafes, airports, and hotels run a sign-in page, called a portal, that you must complete before normal browsing works.
Google's Chrome help says to open any address that starts with http://, such as http://example.com, so the network shows its sign-in page. Sign in there, then try your site again.
Google's connection help also notes that Chrome can detect these portals and prompt you to sign in.
If the warning appears on every site only on one network, the network is the cause. If it follows you home, the cause is on your device or the site.
How do you fix it when you own the WordPress site?
Site owners fix the warning by renewing, reissuing, or reinstalling the certificate, then checking the result in a private window.
- Open your host panel and check the certificate status for your domain.
- Renew the certificate, or run AutoSSL if your host offers it.
- Confirm the certificate lists both the bare domain and www.
- Reload the site in a private window and check the warning is gone.
Let's Encrypt's FAQ says its certificates are free Domain Validation certificates, so most hosts can issue one without a purchase. MDN's TLS guide notes that modern hosting services manage HTTPS for you, either by default or through a setting.
If your site sits behind Cloudflare, check the SSL mode in your Cloudflare dashboard as well. A mismatch between Cloudflare and your origin certificate can keep the warning alive even after a renewal. Our guide to Cloudflare SSL settings for WordPress walks through the modes.
A plugin that forces HTTPS can also cause trouble if it runs before the certificate is valid. If the warning started right after you installed a security or redirect plugin, deactivate it and reload the page. WordPress.org's common errors guide recommends deactivating plugins one by one to find a conflict.
If you need a paid certificate instead, our guide to SSL certificate costs explains the options.
When should you ask your host for help?
Ask your host when the certificate will not renew, when the warning affects every visitor, or when you cannot reach your host panel.
Your host can see the renewal logs, the certificate chain, and the server configuration, which you cannot see from the dashboard. Tell them the exact error code and the date the warning started.
Say whether the warning affects the bare domain, www, or both, and ask whether the certificate covers both names. Ask whether the server is still sending an old certificate after a renewal.
If your site uses an older TLS version, the browser may refuse the connection even with a valid certificate. MDN's TLS guide says TLS 1.3 is the current version, and TLS 1.1 and 1.0 should no longer be used.
Google's Chrome help tells site owners to set the server to use TLS 1.3, while still offering TLS 1.2 for older clients.
For a related SSL error in Chrome, see our guide to fixing ERR_SSL_PROTOCOL_ERROR.
What mistakes should you avoid?
The biggest mistake is clicking through the warning and entering passwords anyway, since the browser cannot confirm who runs the site.
- Do not enter passwords or payment details on a page that shows the warning.
- Do not install a certificate yourself on a work computer, since Google warns that this is usually a security risk.
- Do not buy a new certificate before checking whether your host renews the free one automatically.
- Do not ignore the warning when it affects every visitor, since an expired certificate blocks the whole site.
Frequently asked questions
Is "Your connection is not private" a virus on my computer?
No. The warning means the browser could not verify the site's certificate, and it can come from the site, the network, or your device. A wrong clock, an expired certificate, or a Wi-Fi sign-in page are far more common causes than malware. Run your normal antivirus scan if you are worried, then work through the checks in this guide.
Why does the warning appear in Chrome but not in Firefox?
Browsers check certificates in slightly different ways and show different messages for the same problem. One browser may accept a certificate chain that another rejects, or it may show a softer warning. Open the site in a second browser and compare the messages, but treat the warning seriously in both cases.
Can I just click Advanced and proceed to the site?
You can, but you should not enter passwords, payment details, or personal information after doing so. Clicking through tells the browser to ignore a check it could not pass, and the connection is no longer verified. Use it only to read public information on a site you trust, and fix the certificate problem instead.
How long does it take to fix an expired certificate?
A renewal through your host usually takes a few minutes once you start it, and the warning clears as soon as the new certificate is live. If the renewal fails, the delay comes from finding why it failed, such as a DNS change or a billing lapse. Ask your host for the renewal log if the first attempt does not work.
Why does my WordPress site show the warning only on the checkout page?
A single page can show the warning when it loads content from a different domain, or when the certificate does not cover a subdomain used by that page. Check whether the checkout page calls an address that the certificate does not list. If it does, reissue the certificate with that name included, or move the content to a covered address.
Sources
- Get help with common error messages in Chrome Google Chrome Help
- Fix connection and loading errors in Chrome Google Chrome Help
- Transport Layer Security (TLS) MDN Web Docs
- FAQ Let's Encrypt
- Common WordPress errors WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
