- Your Connection Is Not Private on WordPress: What the Warning Actually Checks
- Where Your Connection Is Not Private Gets Decided
- Read the Code Under The Message Before You Touch Anything
- Find Out Whose Problem It Is
- Fix Your Connection Is Not Private When You Are the Visitor
- Fix Your Connection Is Not Private When It Is Your Own Site
- Lab Results: Five Ways to Get Your Connection Is Not Private
- Confirm the Fix Before You Declare Your Connection Is Not Private Gone
- When Your Connection Is Not Private Is the Wrong Warning
- What to Hand Off Once Your Connection Is Not Private Is Fixed
- Frequently Asked Questions: Your Connection Is Not Private on WordPress
- What does it mean when a WordPress site says your connection is not private in 2026?
- How do I fix your connection is not private when the certificate on my own site has expired?
- Why do I see your connection is not private on my laptop but not on my phone in 2026?
- Your connection is not private vs Not secure: which warning means the certificate is broken?
- Does an AHosting free certificate vs a paid certificate change your connection is not private in 2026?
- Can a WordPress plugin or theme cause your connection is not private for visitors?
- Does AHosting renew the certificate automatically, and what usually stops the renewal?
- What should I send AHosting support when my site shows your connection is not private?
- Is it safe to click Proceed anyway on your connection is not private for my own WordPress site?
- How long does your connection is not private take to clear after a certificate is renewed in 2026?
Your connection is not private on a WordPress site is decided before WordPress runs: the browser rejects the certificate and sends no request. Read the code under Advanced (date, name or authority), then ask whether the warning follows the site or the device. Site-wide, renew the certificate, add the missing name or install the full chain. One device only, check its clock and network.
Your Connection Is Not Private on WordPress: What the Warning Actually Checks
Your connection is not private is the warning Chrome shows when it refuses to trust the certificate a website presents, and on a WordPress site it is almost never a WordPress problem. The browser checks the certificate before it sends a single request, so the page, the theme and every plugin are never asked for anything. That one fact decides who has to fix the warning, and it is why deactivating plugins changes nothing.
Chromium’s own source says what a failed check can mean. Its network error list describes a certificate that is expired or not yet valid by the browser’s clock, one that does not list the name in the address bar, and one signed by an authority the browser does not trust. For each, the comments list causes that range from a misconfigured server to a wrong clock on the visitor’s device. That is why this guide starts with the code under the warning and not with a list of fixes.
We also reproduced the failures. On 2026-11-16 we built a private certificate authority and served one good and five broken certificates from nginx 1.31.6, then probed them with OpenSSL 3.6.4 and curl 8.7.1. The lab ran on one workstation, so it is not an AHosting server. We could not point Chrome at it, so the Chrome codes in this guide come from Chromium’s comments and not from watching Chrome. The OpenSSL and curl messages are real output.
Why a Plugin Cannot Cause It
In the lab, OpenSSL and curl both stopped at the handshake for all five broken certificates. We then read the nginx access log, and it held no line for any of them. The only requests that reached the site came from the good certificate and from one curl call with certificate checking switched off, which is what a visitor does when they click Proceed anyway. Because the request never arrives, nothing inside WordPress could have changed the outcome.
So a caching plugin purge, a theme switch or a plugin audit is wasted effort here. The fix lives in the certificate the server presents, or in the device and network the visitor is using.
Where Your Connection Is Not Private Gets Decided
Read the figure left to right. The certificate check sits between the visitor and every piece of software you manage inside WordPress. Everything on the failing branch happens on the visitor’s device and in the server’s certificate configuration, which on a cPanel account is the certificate installed for the domain.
Read the Code Under The Message Before You Touch Anything
Click Advanced on the warning page and Chrome prints a code that starts with NET::ERR_CERT. That code is the diagnosis. The decoder below maps the common ones to what they mean, the usual cause on a WordPress site, and who can fix it.
| Code under Advanced | What it means | Usual cause on a WordPress site | Who fixes it |
|---|---|---|---|
| NET::ERR_CERT_DATE_INVALID | The certificate has expired or is not yet valid by the browser clock | A renewal failed, or the visitor device has the wrong date | You if every device sees it; the visitor if only one does |
| NET::ERR_CERT_COMMON_NAME_INVALID | The certificate does not list the name in the address bar | The www name or the bare domain is missing, DNS points at the wrong server, or a public Wi-Fi login page intercepted the connection | You if it is consistent; the visitor if it follows one network |
| NET::ERR_CERT_AUTHORITY_INVALID | The certificate is signed by an authority the browser does not trust | A self-signed certificate, or an incomplete chain on the server | You |
| Other ERR_CERT codes | A defect in the certificate itself, such as a weak key or a validity period that is too long | A certificate issued with the wrong settings | You, by reissuing it |
Two of the three common codes have a visitor-side cause and a site-side cause. The date code can be a wrong clock or a lapsed renewal. The name code can be a wrong certificate or a public Wi-Fi login page. One code cannot assign the blame by itself, so the second question is whether the warning follows the site or follows the device.
Find Out Whose Problem It Is
The widget turns the decoder and the follow-the-site test into three questions. It runs in your browser and sends nothing anywhere.
Whose Problem Is This Warning?
Three questions. The answer says whether to fix the site or the device. Nothing you pick leaves your browser.
Fix Your Connection Is Not Private When You Are the Visitor
If the warning shows on other sites as well, or only on one device or network, the certificate is probably fine and something between you and the site is not. Two checks cover most cases.
Check the Clock First
A certificate has a start date and an end date, and the browser compares them with the clock of the device. In our lab, a certificate that starts in January 2027 produced the OpenSSL message that the certificate is not yet valid or the system clock is incorrect, so the message itself names the clock as a suspect. Chromium lists a wrong clock among the causes of the date error as well. On Windows, the Windows Time service keeps the clock in step using the Network Time Protocol, so a machine whose time sync has stopped is the first place to look.
Check the Network
Chromium’s comment on the name error lists two causes that have nothing to do with the site: a wireless network that redirects you to a login page, and an operating system DNS search suffix that turns a short name into one the certificate does not list. Open the same address on mobile data. If it loads cleanly there, your connection is not private only on that network, and the site is fine.
Fix Your Connection Is Not Private When It Is Your Own Site
If the warning follows your domain onto every device and network, the certificate your server presents is the problem. Work through the three failures below in order. Each one matches a row of the decoder.
An Expired Certificate: Your Connection Is Not Private After a Failed Renewal
First read the dates the server actually presents; the command is in the checking section below. On a cPanel account, AutoSSL runs for all users during the nightly update and again when an account is created, and before it orders a certificate it writes a CAA record into the zone. The SSL/TLS Status page filters domains by Expired, Expiring Soon and Has AutoSSL Problems, and its own example of a problem is a domain that does not resolve to an IPv4 address on the internet. It also says that conflicting CAA records must be removed, or one added for the authority you want.
Our own record agrees with that order of suspects. The free SSL and domain management guide records four failed automated renewals on AHosting shared accounts, and all four traced to authoritative DNS pointing somewhere other than the hosting account. So check the nameservers before you touch the certificate.
A Name the Certificate Does Not List: Your Connection Is Not Private on www or the Bare Domain
In the lab we served a certificate that lists www.example.test and asked for example.test. OpenSSL answered with a hostname mismatch, and curl said that no alternative certificate subject name matches the target host name. That is the name error in plain words. Print the subject alternative names, as the checking section shows, and confirm that every address people type is on the list.
The cPanel SSL/TLS Status page lists main, addon, parked, subdomain and www domains as separate types, so a missing www name shows up as its own row. If the names are right and the warning remains, DNS may point at a different server from the one holding the certificate.
An Incomplete or Self-Signed Certificate: Your Connection Is Not Private Although One Is Installed
We served a leaf certificate without its intermediate, and OpenSSL stopped with unable to get local issuer certificate. A self-signed certificate stopped at self-signed certificate. The same leaf served with the intermediate after it, leaf first, passed with verify code 0. So the repair for an incomplete chain is to install the full chain in order, not a new certificate. Chromium lists a self-signed certificate among the causes of the authority error, and cPanel states that no certificate authority secures a self-signed certificate, so the repair there is a certificate from a public authority.
Lab Results: Five Ways to Get Your Connection Is Not Private
Each row is one certificate served by nginx 1.31.6 on 127.0.0.1 and probed on 2026-11-16 with the private certificate authority trusted. The last column is the access log after all probes ran.
| Certificate served | OpenSSL verify result | curl exit and message | Line in the access log |
|---|---|---|---|
| Good, full chain | Verify return code 0 (ok) | Exit 0 | Yes, 200 |
| Expired (ended 2025-11-01) | Code 10, certificate has expired | Exit 60, certificate has expired | None |
| Not yet valid (starts 2027-01-01) | Code 9, not yet valid or the system clock is incorrect | Exit 60, certificate is not yet valid | None |
| Wrong name (lists www only) | Code 62, hostname mismatch | Exit 60, no alternative certificate subject name matches | None |
| Self-signed | Code 18, self-signed certificate | Exit 60, self signed certificate | None |
| Leaf without intermediate | Code 20, unable to get local issuer certificate | Exit 60, unable to get local issuer certificate | None |
The pattern is the finding. Every broken certificate failed at the handshake with a different message, and none of them produced a request. When we repeated the expired case with certificate checking off, the site answered and the log gained a line. The site was never the broken part.
Confirm the Fix Before You Declare Your Connection Is Not Private Gone
Do not trust the padlock on your own machine. Ask the server what it presents. The command is openssl s_client -connect www.ahosting.net:443 -servername www.ahosting.net, piped into openssl x509 -noout -subject -issuer -dates -ext subjectAltName. The -servername flag sends the hostname the way a browser does.
We ran it against our own site on 2026-11-16. It returned a Let’s Encrypt certificate that started on September 23 and ends on December 22, 2026, which is 90 days, and it lists ahosting.net and *.ahosting.net. That is what a healthy answer looks like: a start date in the past, an end date in the future and the name you typed on the list.
For a second opinion, the SSL Server Test from Qualys SSL Labs is a free online service that analyzes the configuration of any SSL web server on the public internet. Run it, then open the site from a second network before you tell anyone your connection is not private is gone.
When Your Connection Is Not Private Is the Wrong Warning
Three neighbors look similar and have different fixes. If the page loads but the browser says Not secure, the certificate is fine and something on the page is not: read the mixed content guide. If the fix is in and the browser now says the page redirected you too many times, see the redirect loop guide.
A message inside the WordPress dashboard saying the site could not establish a secure connection to wordpress.org is the server making an outbound connection, not a visitor, and a separate guide covers it.
What to Hand Off Once Your Connection Is Not Private Is Fixed
The repair above is yours to do on any host. What does not need to be yours is the watching: the end date, the DNS check and the list of names are all things automation can do. Our free SSL guide repeats the renewal chain in full, so this section stays short.
If you want a verified company name in the certificate, read OV vs DV certificates first, since a paid certificate changes what is said about you and not whether the browser accepts it, and then see the Premium SSL certificate options. For a site that should not need this checklist, our WordPress hosting plans and web hosting plans cover renewal as part of the account. On a VPS you own the certificate configuration the lab broke, so the checklist above is the job.
Frequently Asked Questions: Your Connection Is Not Private on WordPress
What does it mean when a WordPress site says your connection is not private in 2026?
Specifically, it means the browser refused to trust the certificate the site presented, so it stopped before sending any request. The code under Advanced, such as NET::ERR_CERT_DATE_INVALID, says why. The cause is the certificate, the visitor clock or network, or the server configuration, and almost never WordPress itself.
How do I fix your connection is not private when the certificate on my own site has expired?
Typically the fix is to renew and install the certificate, then confirm the new end date. On a cPanel account, open SSL/TLS Status, filter for Expired or Has AutoSSL Problems, read the error and run AutoSSL again. If the domain does not resolve to the hosting account, renewal cannot validate, so fix the DNS first.
Why do I see your connection is not private on my laptop but not on my phone in 2026?
In practice, a warning that appears on one device only is about that device or its network, not the site. The usual causes are a wrong clock, a public Wi-Fi login page that intercepts the connection, or something else on the network path. Test the same address on mobile data. If it loads cleanly there, the certificate is fine.
Your connection is not private vs Not secure: which warning means the certificate is broken?
In contrast to the other warning, your connection is not private means the certificate check failed before the page loaded. Not secure means a page loaded but something about it is unsafe, such as plain HTTP or an insecure image on a secure page. The first is fixed on the server, the second inside WordPress.
Does an AHosting free certificate vs a paid certificate change your connection is not private in 2026?
Notably, the browser applies the same checks to both: dates, names and chain. As of August 2026 our free SSL guide lists a domain-validated certificate with automatic renewal on every AHosting shared plan, with wildcard, multi-domain, OV and EV certificates as paid options. Paid options change what the certificate says about the company, not whether the browser accepts it.
Can a WordPress plugin or theme cause your connection is not private for visitors?
Indeed, no. The browser rejects the certificate before it sends a request, so a plugin or theme never runs. In our lab, five failing certificates left no line in the nginx access log. A plugin can cause other warnings, such as mixed content after a URL change, but not this one.
Does AHosting renew the certificate automatically, and what usually stops the renewal?
Fortunately, automatic renewal is included on AHosting shared plans as of August 2026. What stops it is almost always DNS: our free SSL guide records four failed renewals on AHosting shared accounts, and all four traced to nameservers pointing somewhere other than the hosting account.
What should I send AHosting support when my site shows your connection is not private?
As such, send the code under Advanced, the exact address, the time, and whether another device or network shows the same warning. Add the output of the openssl command that prints the certificate dates and names. Those facts separate a lapsed renewal from a name mismatch in one reply.
Is it safe to click Proceed anyway on your connection is not private for my own WordPress site?
Ultimately, clicking through only proves the site responds. In our lab it was the same as sending the request with certificate checking off, and the site answered normally. That is useful for diagnosis, but nothing verified who answered, so never ask visitors to do it.
How long does your connection is not private take to clear after a certificate is renewed in 2026?
Typically the next fresh visit, because the browser checks the certificate the server presents each time it connects. If DNS still points at an old server, that server certificate is what visitors see, so DNS timing sets the delay rather than the browser. Test from a second network to be sure.





