How to Fix Your Connection to This Site is Not Secure Error

We’ve all experienced it. That sinking feeling when you try to visit a website and are instead met with a “your connection to this site is not secure” message. It’s both confusing and a little scary. This common error, which often pops up as “your connection is not private,” is a stark reminder that there are risks lurking on the internet. Any information you send could be intercepted by people you don’t want to have it.

Knowing what this message means and how to deal with it is a good skill for anyone to learn, not just for protecting your personal information but also for making sure your browsing experience stays smooth.

In the sections below, we’re going to get to the bottom of why this warning appears and, more importantly, give you a step-by-step “connection not secure” fix and other strategies to solve the problem and lock down your digital footprint.

“Your connection to this site is not secure.” What does it mean?

So, what is your browser really trying to tell you with this message? At its core, the message that your connection is not private means your browser simply cannot confirm the identity of the website you’re trying to reach.

The verification process happens through a security protocol called an SSL/TLS handshake. Think of it as a quick, secret conversation between your computer and the website’s server. Your browser says, “Hello,” and the server answers with its digital ID, an SSL certificate, to prove it’s the real deal. They then agree on an encryption method to keep your data safe. If there’s any problem during this handshake, like an SSL certificate error, your browser stops the connection and throws up the warning.

Basically, it’s your browser’s way of saying, “Hold on, we can’t confirm this site is who it claims to be. Proceed with extreme caution.”

Here are the most common reasons this security check fails:

• Website-side problems: The most frequent culprit is an issue with the site’s SSL certificate. It might be expired, invalid, misconfigured, or issued by an organization your browser doesn’t trust, resulting in an SSL certificate error. Another issue is “mixed content,” where the main page is secure (HTTPS), but some elements like images or scripts are not (HTTP).
• Client-side problems: Sometimes, the issue is actually on your end. One primary cause is an incorrect date and time on your computer, which makes it impossible to validate a certificate’s time-sensitive validity. An outdated browser, corrupted data in your browser’s cache, a misbehaving browser extension, or even an outdated DNS entry that requires you to flush a DNS connection that’s not secure can also trigger the error.
• Network interference: Sometimes, a third party is interfering with the connection. This could be antivirus software that intercepts traffic for scanning, a VPN, a proxy, or even a public Wi-Fi network that requires you to log in.

How do you fix “Your connection is not secure” errors?

Before you start messing around in browser-specific settings, there are a handful of universal fixes that solve the majority of these connection errors. We recommend running through these simple steps first, as they are often the quickest solution when you see that your connection is not private:

1. Check your device’s date and time: This is the most common and easiest problem to fix. It’s a simple “connection not secure” fix. SSL certificates have an expiration date, and if your system’s clock is wrong, your browser can’t verify it correctly. Go to your computer’s Date and Time settings and ensure that it’s set to update automatically.
2. Use an Incognito or Private Window: Open an incognito or private window in your browser and try to access the site. This mode loads without your cache, cookies, or extensions. If the site works here, but you still see an incognito mode “connection not private” error in a normal window, the problem is likely with your browser’s stored data or an extension.
3. Clear your browser’s cache and cookies: If the incognito window worked, your next step should be to clear your browser’s cache and cookies. Old, corrupted data can interfere with new connections.
4. Try a different network: To rule out a network-specific issue, just try connecting with a different Wi-Fi network or use your phone’s mobile data hotspot. If the site loads, the problem is with your original network.
5. Flush your DNS cache: Your computer stores a cache of recent DNS lookups. If this data is out of date, it can stop you from reaching a site that has recently changed its server. A command to flush “DNS connection not secure” data can resolve this.

“Your connection to this site is not secure” how to fix on Chrome

To tackle the “your connection to this site is not secure” issue in Chrome, you can walk through these steps. Here’s how to fix “connection not secure” in Chrome for the most common scenarios:

1. Open Chrome and click the 3 vertical dots in the upper right corner to access the menu.

2. Select “Settings” from the dropdown menu.

3. Click on “Privacy and security,” then select “Security.”

4. Make sure the setting for “Safe browsing” is set to either “Standard protection” or “Enhanced protection.” This is a key part of how to fix “connection not secure” in Chrome. 

5. Also, ensure that “Use secure DNS” is enabled to help prevent navigation to dangerous sites.

6. If the error persists, clear your browsing data, which includes cookies, cached files, and other site data. To do this, go back to the “Privacy and security” section and select “Clear browsing data.”

7. Update Chrome: An out-of-date browser can have old security protocols. Go to Help > About Google Chrome. The browser will automatically check for and install any available updates, which is often the easiest solution for how to fix a connection that’s not secure in Chrome.

8. Check Chrome error codes: Chrome often provides a specific code that can help diagnose the problem. Look for a code under the “your connection is not private” message. Common connection not secure error codes include:
   • NET::ERR_CERT_AUTHORITY_INVALID: The website’s certificate issuer isn’t trusted.
   • NET::ERR_CERT_DATE_INVALID: The certificate is expired, or your computer’s clock is wrong.
   • NET::ERR_CERT_COMMON_NAME_INVALID: The name on the certificate doesn’t match the website you’re trying to visit. This can indicate a misconfiguration or a malicious redirect.
   • ERR_SSL_PROTOCOL_ERROR: A generic error indicating a problem during the SSL handshake.

How to fix Firefox “connection is not secure” error

Firefox is another popular web browser, and the steps to fix the Firefox connection not secure error are fairly similar to Chrome. Here’s what you need to do to address how to fix “connection not secure” in Firefox:

• Open Firefox and click on the 3 horizontal lines in the upper-right corner.
• Select “Settings” from the dropdown menu.
• Head over to the “Privacy & Security” section.
• Under “Connection and Software Security,” make sure the checkbox for “Block dangerous and deceptive content” is checked. This is a fundamental step for how to fix “connection not secure” in Firefox.

• Scroll down to “Certificates” and click on ” Manage Certificates.”

• In the window that appears, click on the “Authorities” tab, then scroll down to locate the certificate of the website you’re trying to access.

• When you find it, select it and click on the “Delete or Distrust” button.
• After that, try accessing the website again. If it still shows an error, clear your browsing data by clicking on the “Clear Data” button under the “Browsing Data” section. 

• Disable add-ons: Faulty or overly aggressive security add-ons can interfere with connections. Trying to disable your add-ons one by one to see if one of them is the culprit is a great troubleshooting method for how to fix a connection that’s not secure in Firefox.
• Check Firefox error codes: Like Chrome, Firefox provides specific connection not secure error codes that offer clues, and sometimes, a persistent SSL certificate error is the root cause:

“Your connection is not secure”: How to fix it in Edge

Microsoft Edge is built on the same foundation as Chrome, so the troubleshooting steps are similar, but the menus are slightly different. Here’s how to tackle the “connection not secure” error in Edge:

• Check Security settings: Click the 3 horizontal dots in the top-right corner and go to Settings > Privacy, search, and services. Under the “Security” section, ensure that “Microsoft Defender SmartScreen” is turned on.

• Clear browsing data: In the same Privacy, search, and services menu, find the “Clear browsing data” section. Click “Choose what to clear,” select “Cached images and files” and “Cookies and other site data,” and then click “Clear now.”

• Update Edge: An outdated browser is a common cause of this problem. Go to Settings > About Microsoft Edge. Edge will automatically check for and install updates.
• Check Edge error codes: Edge often uses the same “connection not secure” error codes as Chrome, but they present them differently. Check for the following messages, which are part of how to fix a connection that’s not secure in Edge:
  • DLG_FLAGS_INVALID_CA or Error Code: 0: This indicates a problem with the certificate’s issuing authority.
  • NET::ERR_CERT_COMMON_NAME_INVALID: The certificate name doesn’t match the site’s address.

“This connection is not private.” How to fix it in Safari on Mac.

Safari uses slightly different wording for the same error, often displaying, “This Connection Is Not Private.” Unlike other browsers, Safari doesn’t typically show short error codes, instead providing a more descriptive message. 

Here’s how to fix “connection not secure” in Safari:

1. Check Date & Time: Go to System Settings > General > Date & Time and make sure “Set time and date automatically” is enabled.
2. Clear website data: In Safari, go to Safari > Settings > Privacy. Click “Manage Website Data,” wait for the list to load, and then click “Remove All.” This is a common solution for how to fix “connection not secure” in Safari, because the cache and cookies might be causing the problem.
3. Check Keychain for problematic certificates: This is a more advanced step. Open the “Keychain Access” app on your Mac. In the sidebar, select “Certificates.” Look for any certificates related to the website you’re having trouble with. If you find one that looks suspicious or is marked as untrusted (often with a red ‘X’), you can delete it. Proceed with caution here; deleting the wrong certificate can cause other issues.
4. Update macOS and Safari: Browser updates for Safari are tied to macOS updates. Go to System Settings > General > Software Update to ensure that your system is fully up to date, which is the most reliable way for how to fix a connection that’s not secure in Safari.

Other possible reasons why your connection is not secure

If you’ve tried the browser-specific fixes and are still blocked by a “your connection is not private” warning, the issue might be caused by other software or your network environment. Here are 3 common culprits.

Antivirus HTTPS Scanning

Many internet security suites, including products from Avast, Bitdefender, and ESET, have a feature that scans encrypted HTTPS traffic. To do this, the antivirus program intercepts the SSL connection, acting as a middleman. This process can sometimes break the certificate chain, causing your browser to flag a perfectly safe site as untrusted. 

To test this, temporarily disable the “SSL Scan,” “HTTPS Protection,” or similarly named features in your antivirus settings, and try accessing the site again for a potential “connection not secure” fix.

VPN Interference

A VPN can sometimes cause this error if its server routing conflicts with the SSL validation process or if the website actively blocks traffic from known VPN IP addresses. You can diagnose this by temporarily disabling your VPN. If the site loads correctly, the VPN is the cause. You can try switching to a different server location within your VPN app.

If you’re on an untrusted network like public Wi-Fi, you absolutely need a VPN for security. If your current VPN is causing issues, you need a better tool. This is a perfect scenario to test ClearVPN. It’s designed to work smoothly and can be a great diagnostic tool to see if a properly configured VPN solves the problem. You can learn more about what a VPN is and how it works on our blog.

Public Wi-Fi and captive portals

When you connect to public Wi-Fi at a café, airport, or hotel, you often have to go through a “captive portal” page to log in or accept terms of service. Before you complete this step, the network may block or redirect all traffic, leading to SSL errors on any site you try to visit. The fix is simple: Open your browser and try to navigate to a non-HTTPS site, like http://example.com. This should force the portal’s login page to appear. 

Once you’ve signed in, your connection should work normally, but if not, you may need to flush the DNS connection for non-secure data as a final step.

FAQs

Why is Chrome saying my site is not secure?

Chrome may display a “not secure” warning if the site you’re visiting doesn’t use HTTPS encryption, which would mean that any exchanged data is not protected. This often happens if the website’s SSL certificate is missing, expired, or not set up correctly.

Why do some websites say “not secure connection”?

Websites may show a “not secure connection” warning if they lack a valid SSL certificate. SSL certificates encrypt data between the user and the site, enhancing security. Unsecured websites can leave personal information vulnerable to cyber threats, and therefore, browsers often caution users when SSL certification is absent or incorrect.

How do I bypass “your connection is not private”?

Most browsers will show a button or link, often labeled “Advanced” or “Details,” that allows you to proceed to the website anyway. While this is technically possible, it’s highly discouraged. Bypassing the warning means you accept the risk that your connection is not secure, and any information you share (like passwords or credit card numbers) could be stolen. Only do this if you are 100% certain the site is safe, and the error is a known, temporary issue.

Why is every website showing “connection not secure”?

If this error pops up on every website you visit, the problem is almost certainly on your device or network. The most common causes are an incorrect system clock (date and time), an overly aggressive antivirus program scanning all your traffic, or a misconfigured network/firewall that is interfering with all SSL connections.

Does this error mean the site was hacked?

Not necessarily. In most cases, the error is due to a simple configuration mistake by the website’s administrator, such as forgetting to renew an SSL certificate. It’s an indicator of poor security hygiene, but it doesn’t automatically mean the site has been breached. However, it does mean the connection is vulnerable, so you should treat the site as untrustworthy until the error is fixed.

How do I fix “connection not secure” on my phone?

The fixes are very similar to those on a desktop. First, check that your phone’s date and time are set to update automatically. Second, try clearing the browser data in your mobile browser’s settings (e.g., Chrome or Safari). Third, try switching from Wi-Fi to your mobile data network (or vice versa) to see if the network is the problem. Finally, make sure your phone’s operating system and browser app are fully updated.