Your Connection Is Not Private”: Fix It in Chrome

If Chrome shows your connection is not private, it cannot verify the website’s HTTPS certificate for the address you opened. The cause may be your device, a Wi-Fi login page, Chrome or security software, or the website’s SSL setup.

What you need before troubleshooting

Keep the exact website address and the small error code visible on the warning page. You will also need to know whether the warning appears on one website or on every website you open.

If you own the website, keep access to your domain registrar and hosting panel ready. Do not enter a password, card number or other personal information on a page that Chrome marks as unsafe, and do not install a certificate file suggested by a random website.

What the warning means

HTTPS uses a digital certificate to prove that the server is presenting the correct website identity and to create an encrypted connection. Chrome checks the certificate’s name, validity dates, issuing authority and certificate chain before it lets the page load normally.

The warning does not automatically mean that someone is attacking you. It means Chrome cannot complete one of those checks. A wrong clock can make a valid certificate look expired; a captive Wi-Fi portal can replace the page temporarily; or the website owner may have forgotten to renew the certificate.

The safest first decision is to identify the scope:

What you see	Most likely area to check
The warning appears on one website	That website’s certificate, domain or DNS
It appears on many unrelated websites	Your clock, network, device or security software
It appears only on public Wi-Fi	The network’s sign-in portal
It appears only in normal Chrome, not Incognito	An extension, cached data or browser setting

Chrome’s official certificate-error guidance also recommends checking the network portal, trying Incognito, updating the operating system and checking HTTPS-scanning software.

Read the error code

The large warning is general; the code underneath usually points to the next action.

NET::ERR_CERT_DATE_INVALID

Chrome believes the certificate is not valid for the current date. First check your device’s date, time and time zone. If they are correct and only one website fails, the certificate may be expired or not yet valid on that website.

NET::ERR_CERT_AUTHORITY_INVALID

Chrome cannot trust the certificate issuer or the certificate chain. This can happen with a website using a wrongly installed certificate, an old device trust store, antivirus HTTPS scanning or a work/school proxy that inspects secure traffic.

Do not manually install a certificate from an unknown source. On a managed computer, ask the administrator whether the proxy’s required certificate is installed; on a website you own, renew or reinstall the certificate from the hosting panel.

NET::ERR_CERT_COMMON_NAME_INVALID

The certificate does not cover the hostname in the address bar. A common example is a certificate issued for example.com while you opened www.example.com, or a certificate for the old domain after a domain change.

HSTS or an invalid-name warning

When HSTS is involved, Chrome may refuse to offer a bypass because the site has instructed browsers to use HTTPS. Treat that as a reason to correct the certificate or domain configuration, not as a reason to search for a bypass trick.

Step 1: Check whether the problem is local

This step separates a device or network problem from a website problem.

1. Open two or three unrelated, well-known websites in new tabs.
2. Try the same website on mobile data if you are currently using Wi-Fi, or on another trusted network.
3. Check whether the address is spelled correctly and whether you accidentally opened an old bookmark or an unfamiliar look-alike domain.
4. Note the exact error code on the warning page.

Success looks like: the website opens on another network or device. That points to your original network or device, so continue with the visitor fixes below. If the same domain fails everywhere while other sites work, send the error code and hostname to the website owner.

Step 2: Correct your clock and complete Wi-Fi sign-in

An incorrect clock changes Chrome’s idea of whether a certificate is valid. Public Wi-Fi can also show a certificate warning until you complete its sign-in page.

1. Open your device’s date and time settings.
2. Turn on automatic date and time and automatic time zone, if those options are available.
3. Save the change, close and reopen Chrome, then try the website again.
4. On café, airport, hotel or other public Wi-Fi, open a plain HTTP address such as http://example.com to trigger the network’s sign-in page. Complete the portal login, then reopen the HTTPS website.
5. If the clock keeps losing time after a restart, ask a technician to check the device rather than repeatedly bypassing certificate warnings.

Success looks like: the warning disappears after the correct time is applied, or the Wi-Fi portal appears and the site opens after you sign in. If the warning remains on one site only, the site owner needs to check its certificate.

Step 3: Test Chrome without extensions or cached data

An extension or security tool can interfere with the connection even when the website’s certificate is correct.

1. Open Chrome’s menu and choose New Incognito window.
2. Enter the website address manually in the Incognito window.
3. If it works there, return to normal Chrome and open the extensions page. Disable extensions, then enable them one at a time until you identify the one affecting the connection.
4. If Incognito does not help, update Chrome and your operating system, restart the device and try again.
5. Check antivirus or firewall settings for a feature named HTTPS scanning, encrypted traffic scanning or similar. Temporarily pause that feature only for a controlled test, then turn protection back on.
6. On a company, school or managed computer, contact the administrator instead of changing certificate settings yourself.

Success looks like: the page loads after an extension or HTTPS-scanning feature is disabled. If every website still shows a certificate warning, the network, device trust store or managed proxy needs attention. Google’s Chrome connection troubleshooting steps cover updating, Incognito, extensions, browsing data and security software.

Step 4: Check the website’s SSL certificate

Website owners need to confirm that a valid certificate is installed for every hostname visitors use.

1. List the exact hostnames that should work, such as example.com, www.example.com and any required subdomain.
2. Check that the domain’s DNS records point to the current hosting account. An old A or AAAA record can send some visitors to a different server with the wrong certificate.
3. In DirectAdmin, open SSL Certificates at user level and review the certificate status. Menu names can vary slightly with the panel skin.
4. Use the ACME or Let’s Encrypt option to request or renew the certificate. Include the root domain and www version when both are used by the website.
5. If issuance fails, check that DNS resolves correctly and that no CAA record blocks the certificate authority. Correct the DNS issue first, then request the certificate again.
6. Open both https://example.com and https://www.example.com in a private window. Select the site-information icon in Chrome and inspect the certificate details if one hostname still shows an error.

Success looks like: each intended hostname opens over HTTPS, the certificate name covers the hostname in the address bar, and the certificate is not expired. DirectAdmin documents automatic ACME issuance and renewal for user domains in its official SSL and Let’s Encrypt guide.

Step 5: Fix a missing, expired or mismatched certificate

The browser cannot repair a certificate that is wrong on the server. The website owner must replace it or correct the domain configuration.

If the certificate is expired

Request a renewal in the hosting panel and wait for it to finish. Do not merely change the computer’s date; that hides the symptom and creates a different security problem.

If the certificate is missing the www name

Decide whether the canonical address should use www or the non-www version. Request a certificate containing both names if both receive traffic, then redirect one version to the other after HTTPS works.

If the domain recently moved

Confirm that DNS has finished pointing to the new hosting account and that the new server has a certificate for the domain. Test the domain directly over HTTPS before changing every WordPress URL or adding redirect rules.

If the certificate issuer is blocked

Review CAA records and DNSSEC at the DNS provider. A CAA record can limit which certificate authorities may issue certificates for a domain. Remove an incorrect restriction or allow the certificate authority you actually use, then retry issuance.

Step 6: Force HTTPS after the certificate works

Redirecting HTTP to HTTPS improves consistency, but it cannot make an invalid HTTPS certificate valid. Complete the certificate test first.

1. In DirectAdmin, open the domain’s setup or SSL settings.
2. Enable the panel’s Force SSL with HTTPS redirect option, or the equivalent HTTPS redirect setting in your skin.
3. Save the change and test a page using http:// in a fresh browser window.
4. Confirm that it redirects to the intended HTTPS hostname without a redirect loop.
5. Update WordPress Address and Site Address only after the HTTPS version loads correctly. Replace old HTTP image, stylesheet and script URLs if the page later reports mixed content.

For a site using a custom .htaccess rule, follow the existing HTTP-to-HTTPS redirect guide carefully and keep one redirect method active. DirectAdmin’s documentation also describes its built-in force-SSL and hostname redirect controls.

Avoid it for good: use auto-renewing free SSL

Let’s Encrypt provides free, automated domain-validation certificates for HTTPS. Its default certificates are valid for 90 days, so automation matters more than remembering a renewal date; the project recommends renewing them every 60 days. See the Let’s Encrypt FAQ for the current certificate lifetime and renewal guidance.

For a small business, portfolio, tuition centre or first WordPress site, choose hosting that includes all of the following:

1. A certificate for the actual domain and its required subdomains.
2. Automatic renewal rather than a calendar reminder alone.
3. A panel where you can see certificate status and retry a failed request.
4. Self-service backup and restore tools, so certificate or redirect changes can be reversed safely.
5. A clear way to force HTTPS after the certificate has been issued.

HostKarle’s DirectAdmin shared hosting includes a free auto-renewing Let’s Encrypt SSL, one-click WordPress installation and self-service backup tools. The Basic plan supports one website with 70 GB pure SSD storage, 10 business email accounts and 2 MySQL databases at ₹99/mo, billed as ₹1,188 yearly; it renews at the price you sign up at.

If you already have hosting, you do not need to move just because Chrome displays this warning. Identify the error code, correct the device or domain issue, renew the certificate, then test every hostname your visitors use.

FAQ

Is it safe to click Advanced and continue?

Avoid continuing on a warning page when you are entering passwords, payment details or personal information. A bypass does not fix the certificate and may send data through a connection Chrome could not verify. If it is your site, repair the certificate; if it is someone else’s site, contact the owner.

Why does Chrome say the error on every website?

Check your device clock, Wi-Fi sign-in, antivirus HTTPS scanning, VPN or proxy first. If the same problem appears on multiple networks and devices, ask your network administrator or internet provider to investigate the connection.

Why does the error happen only on www?

The certificate may cover the root domain but not www, or DNS for www may point to a different server. Add the required hostname to the certificate, correct its DNS record and then choose one canonical hostname for the redirect.

Does clearing Chrome’s cache renew an SSL certificate?

No. Clearing browsing data can remove stale browser state, but it cannot change a certificate installed on the website. Use it only after checking the clock, network, error code and certificate itself.

How often should a website’s SSL certificate renew?

It depends on the certificate authority and automation setup. Let’s Encrypt’s standard certificates are valid for 90 days and should be renewed automatically well before expiry; monitor renewal status rather than waiting for Chrome to report an error.

DONE your-connection-is-not-private words=2075

{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “Is it safe to click Advanced and continue?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Avoid continuing on a warning page when you are entering passwords, payment details or personal information. A bypass does not fix the certificate and may send data through a connection Chrome could not verify. If it is your site, repair the certificate; if it is someone else’s site, contact the owner.”}}, {“@type”: “Question”, “name”: “Why does Chrome say the error on every website?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Check your device clock, Wi-Fi sign-in, antivirus HTTPS scanning, VPN or proxy first. If the same problem appears on multiple networks and devices, ask your network administrator or internet provider to investigate the connection.”}}, {“@type”: “Question”, “name”: “Why does the error happen only on `www`?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “The certificate may cover the root domain but not www, or DNS for www may point to a different server. Add the required hostname to the certificate, correct its DNS record and then choose one canonical hostname for the redirect.”}}, {“@type”: “Question”, “name”: “Does clearing Chrome’s cache renew an SSL certificate?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “No. Clearing browsing data can remove stale browser state, but it cannot change a certificate installed on the website. Use it only after checking the clock, network, error code and certificate itself.”}}, {“@type”: “Question”, “name”: “How often should a website’s SSL certificate renew?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “It depends on the certificate authority and automation setup. Let’s Encrypt’s standard certificates are valid for 90 days and should be renewed automatically well before expiry; monitor renewal status rather than waiting for Chrome to report an error. DONE your-connection-is-not-private words=2075”}}]}