Guide SSL & Security

How to fix "Your connection is not private"

The warning always means one of three specific things: no certificate, an expired one, or a mismatch. Here is how to tell which and fix it.

iFastHosting Support Team Updated 26 August 2026 7 min read Beginner

"Your connection is not private" is the browser refusing to complete a secure connection because something about the certificate it received does not check out. It is a deliberately blunt warning, and it always comes down to one of a small number of specific, checkable causes — never a vague, unfixable problem.

Start with the exact reason, not the generic message

Every major browser shows an "Advanced" or "Details" option on this warning that reveals the actual error code underneath the generic headline. That code tells you which of the following you are dealing with, and guessing without it wastes time chasing the wrong fix.

Underlying error	What it means
Certificate expired / NET::ERR_CERT_DATE_INVALID	The certificate's validity period has ended, or the visitor's own device clock is wrong.
Certificate name mismatch / NET::ERR_CERT_COMMON_NAME_INVALID	The address requested does not match any name the certificate actually covers — commonly a www vs non-www mismatch.
Untrusted issuer / NET::ERR_CERT_AUTHORITY_INVALID	The certificate was not issued by an authority the browser recognises, often a self-signed or default placeholder certificate.
No certificate presented at all	The domain has not had a certificate issued for it yet, usually because DNS has not finished pointing at the hosting account.

Certificate expired

Free certificates on your hosting renew automatically, so an expired one usually points to something interrupting that process rather than a certificate that simply ran out. Check the SSL section of your control panel for the domain's current expiry date. If the domain has recently changed DNS or moved between accounts, that interruption is the likely cause — how to renew an SSL certificate covers what to check next. If you are using a certificate you purchased separately, it may simply be due for its manual renewal.

Check the visitor's own clock too

A device with the wrong date or time will report a perfectly valid certificate as expired or not yet valid, because the check compares the certificate's dates against the device's own clock. This is worth ruling out before assuming the server is at fault, especially if only one person is reporting the problem.

Name mismatch

A certificate is issued for specific hostnames. If it covers yourdomain.com but a visitor requests www.yourdomain.com, or the other way round, and that second name was not included on the certificate, the browser correctly refuses to treat it as a match. Check exactly which address is showing the warning, and confirm the certificate in your control panel lists that specific hostname among the names it covers. Most automatically issued certificates cover both the bare domain and its www version together, so this usually surfaces only when one version was set up after the other, or when a redirect sends visitors to a hostname the certificate does not include.

Untrusted issuer

This means the certificate was not issued by an authority browsers recognise as trustworthy — most commonly a self-signed certificate, or a default placeholder certificate that a server presents before a real one has been issued for a domain. If you have just added a domain and are seeing this immediately, it is often the default certificate showing while the real one is still being issued, and resolves itself once DNS finishes pointing at the hosting account and the automatic certificate is generated.

No certificate at all

If the browser reports it cannot establish a secure connection rather than complaining about a specific certificate, no certificate has been issued for that exact address yet. This is almost always a DNS timing issue: the domain has been added but has not finished resolving to your hosting account, so the automatic issuance check has nothing to validate against. Confirm the domain is correctly added in your control panel and give it time to finish pointing there — see how long DNS propagation takes for a realistic window.

When it is only happening to you

Before assuming the server is misconfigured, test from a different device and a different network — mobile data rather than your home Wi-Fi is the quickest check. A warning that only one person sees, on one device, is more likely to be a wrong system clock, an old cached certificate, or a corporate or ISP network doing something unusual to encrypted traffic, than an actual fault with the site's certificate.

Do not disable certificate checking to work around it

Some browsers and tools offer a setting to ignore certificate errors. That removes the protection the warning exists to provide and should never be used as a fix for a live, public-facing website — it hides the symptom for you while leaving every other visitor exposed to the same unresolved warning.

If you have worked through the specific error code shown and it still is not resolving, contact support with the exact error text and the address that is showing it, and it can be checked directly against the certificate currently active on the account.

Frequently asked questions

Is it safe to click through the warning anyway?

As a visitor, no — treat the warning as accurate and leave the site rather than proceeding. As the site owner testing your own site, clicking through tells you the page loads, but it does not fix the underlying problem your other visitors will still see.