"Your connection is not private" means the browser couldn't confirm the SSL certificate for the site, so it stopped before loading the page. On our hosting, every domain gets a free certificate from AutoSSL, so this error almost always points to DNS, a missing www or subdomain record, an expired certificate that couldn't renew, or a problem on the visitor's own device. This guide explains the common SSL certificate errors and how to fix them.
What the error looks like
| Browser | Message |
|---|---|
| Chrome and Edge | "Your connection is not private" (Edge: "Your connection isn't private"), with a code such as NET::ERR_CERT_COMMON_NAME_INVALID or NET::ERR_CERT_DATE_INVALID |
| Firefox | "Warning: Potential Security Risk Ahead", with a code such as SSL_ERROR_BAD_CERT_DOMAIN or SEC_ERROR_EXPIRED_CERTIFICATE |
| Safari | "This Connection Is Not Private" |
The code tells you what's wrong. Click Advanced (or Show Details) on the error page to see it.
First: is it just your device?
Try the site on another device, ideally a phone on mobile data. If it works there, the problem is on the first device:
- Wrong date or time. Chrome may say "Your clock is behind" or "Your clock is ahead" (
NET::ERR_CERT_DATE_INVALID). Set your device's date and time to update automatically. - Public Wi-Fi. Hotel, airport and cafe networks often need you to sign in first. Open any http site or the network's login page, then try again.
- Antivirus or a work network that inspects HTTPS traffic can cause certificate errors on every site. Try with it paused, or ask your IT department.
- Outdated device. Very old operating systems and browsers don't trust current certificates. Install updates.
NET::ERR_CERT_COMMON_NAME_INVALID (wrong name)
The certificate the server sent doesn't cover the exact name you typed. Common causes on Instant Access Internet Services hosting:
- www isn't covered.
example.comworks butwww.example.comdoesn't, usually because the www DNS record is missing or points somewhere else. - A new domain or subdomain. AutoSSL hasn't issued the certificate yet. Until it does, the server shows a certificate for a different name.
- The domain was excluded from AutoSSL on the SSL/TLS Status page.
- DNS points somewhere else. If the domain's A record points to another server, that server's certificate is shown.
NET::ERR_CERT_DATE_INVALID (expired certificate)
If the visitor's clock is correct, the certificate has expired. AutoSSL renews certificates automatically, so an expired certificate usually means renewal failed: the domain no longer points to our nameservers, a Cloudflare setting blocked validation, a CAA record doesn't allow AutoSSL's certificate authority, or the site uses a certificate you bought that wasn't renewed.
How to fix it on your website
- Log in to cPanel and go to Security > SSL/TLS Status.
- Find the name that shows the error (for example
www.example.com). Check its status and read any message in the Certificate Status column. - If it's marked as excluded, tick it and click Include during AutoSSL.
- If the message mentions DNS or says the name doesn't resolve to the server, check your DNS. Make sure your domain uses our nameservers, or if you manage DNS elsewhere, that the domain and the
wwwrecord point to your hosting. See the nameserver and Zone Editor guides below. - If you use Cloudflare, set SSL/TLS to Full (strict). If AutoSSL still fails, turn the proxy off (grey cloud) until the certificate is issued, then turn it back on.
- AutoSSL runs by itself several times a day, so there's no button to start it. After fixing DNS, wait a few hours (longer if you just changed nameservers) and check SSL/TLS Status again.
- If you use a certificate you bought, renew it with the company that sold it and install the new one in Security > SSL/TLS. Or remove it and let AutoSSL cover the domain for free.
Common questions
Is it safe to click "Proceed anyway"?
Not on a site where you enter passwords or payment details. For your own site while you're fixing it, the risk is low, but don't make a habit of it and don't ask your visitors to do it.
My site shows a padlock but some visitors still see the error
Ask them to check their date and time and try another network. If only some visitors see it right after a DNS change, it can be propagation: some still reach the old server. See the propagation guide below.
What about the "Not secure" warning with no error page?
That's usually mixed content: the page loads over HTTPS but includes images or scripts over http. See the mixed content guide below.
When to open a ticket
If SSL/TLS Status still shows the name as unsecured a day after DNS is correct, open a ticket. Include the exact address, the error code from the browser, and the message from the Certificate Status column.
Related guides
- Free SSL Certificates: How AutoSSL and SSL/TLS Status Work
- How to Use the cPanel Zone Editor (A, CNAME, MX and TXT Records)
- Our Nameservers: How to Point Your Domain to Your Hosting
- DNS Propagation: Why Domain Changes Take Time and How to Check
- How to Fix "Not Secure" Warnings and Mixed Content Errors
Still stuck? Open a support ticket and the Instant Access Internet Services team will help.
