Fix the “Your connection is not private” error on Chrome, Safari, and other browsers

What does “Your connection is not private” mean?

The “Your connection is not private” error means the browser can’t validate the website’s SSL certificate. Without that certificate, the browser can’t establish a secure, encrypted connection between you and the website. Simply speaking, your browser can’t confirm that a site you’re trying to visit is safe.

When you visit an HTTPS (HyperText Transfer Protocol) site, your browser and the website must verify each other through a quick digital exchange. That exchange is called an SSL/TLS handshake. It’s how your browser and a website’s server agree to communicate safely. During this process, the website sends the browser its SSL certificate to prove that it’s secure, and they both agree on the encryption protocol they’ll use to communicate. If any step in this process fails (for example, the certificate has expired), your browser blocks access and shows a privacy error.

Where the DNS (Domain Name System) provides the Internet's phonebook, SSL/TLS handshakes provide the security needed. Running an SSL server test is a good way to check the security status of a server or site.

Why does the “Your connection is not private” error appear?

Seeing the “Your connection is not private” error on your computer screen doesn’t yet mean that your data has been stolen. It’s a preventive warning saying that your browser can’t confirm the site’s identity and stops the page from loading until you confirm it’s safe to continue. Most popular browsers work this way to protect you.

You might get the “Your connection is not private” error because of:

• Expired, missing, or invalid SSL certificates. The website’s SSL certificate may have expired or be incorrectly set up.
• Untrusted certificate authority. The browser can’t check who issued the website’s security certificate.
• Server configuration problems. The server uses the wrong HTTPS settings or outdated TLS versions and ciphers.
• Incorrect date or time. If your device clock is set incorrectly and doesn’t match certificate validity dates, certificates may appear expired.
• Browser or cache issues. Corrupted data or old cookies can block secure access.
• Public Wi-Fi networks. Using open networks may interrupt SSL connections.
• Security software interference. Antivirus software, firewalls, VPNs, or browser extensions can disrupt the SSL/TLS handshake.
• Malware or hacking attempts. While it's rare, malicious software or an unsafe network may try to intercept your traffic, which can trigger this warning.

How to fix the “Your connection is not private” error

The “Your connection is not private” message can stem from several causes, and each requires a separate solution to resolve it. These are the most popular ways to get rid of the “Your connection is not private” issue:

1. 1.Reload the page
2. 2.Try incognito mode
3. 3.Check the time and date on your device
4. 4.Check Wi-Fi connection
5. 5.Clear the browsers’ cookies and cache
6. 6.Update your OS
7. 7.Check your antivirus or firewall
8. 8.Clear the SSL state on your device’s browser
9. 9.Restart your devices
10. 10.Troubleshoot your VPN
11. 11.Update your browser
12. 12.Try another browser
13. 13.Flush the DNS cache
14. 14.Disable browser extensions
15. 15.Try another network
16. 16.Check the URL
17. 17.Check the SSL certificate
18. 18.Contact website admin
19. 19.Bypass the “Your connection is not private” error

These steps are compatible with Chrome, Firefox, Edge, Opera, and Safari. Start from the first one and work down until the page loads securely again. Let’s walk through each one.

1. Reload the page

Sometimes the easiest fix is the right one, and all you need to do is refresh the page. It's possible that when you were trying to connect, the website owner was reissuing the security certificate, or a glitch occurred. Reload the page to restart the connection and fetch a fresh certificate: 

• On Windows, press “Ctrl” + “R” or “F5” on your keyboard. Hard reload (force the webpage to reload without using cached files) with “Ctrl” + “Shift” + “R.”
• On Mac, press “Command” + “R” on the keyboard. Hard refresh with “Command” + “Shift” + “R.”

If that doesn’t work, close and reopen your browser, then try again.

2. Try incognito mode

Try visiting the site in incognito mode. Cached data or your extensions might be preventing the SSL connection. To open a new incognito window:

• On Chrome. Click on the Menu icon (three vertical dots) > “New incognito window” or press “Ctrl”/”Command” + “Shift” + “N” on your keyboard.
• On Firefox. Open the Menu by clicking on the three vertical lines (the hamburger menu icon) > “New private window” or press “Ctrl”/”Command” + “Shift” + “P.”
• On Edge. Click on the Menu icon (three horizontal dots) > “New InPrivate window” or click the “Ctrl”/”Command” + “Shift” + “N” combination on your keyboard.
• On Opera. Click on the Opera menu icon > “New private window” or press “Ctrl”/”Command” + “Shift” + “N.”
• On Safari. Click “File” > “New private window” or press ”Command” + “Shift” + “N.”

3. Check the time and date on your device

Your browser may not be able to establish a safe connection if your device's time settings are incorrect. Some SSL certificates are valid for only a couple of months. They depend on accurate timing, and if it’s incorrect, your browser may mistakenly identify the certificate as outdated or fake. You can set the correct time on your device by following these instructions:

• On Windows. Right-click the clock on the taskbar > “Adjust date/time” > turn on “Set the time automatically” and “Set the time zone automatically.”
• On Mac. Go to Apple menu > “System settings/preferences” > “General” > “Date & time.” If you see the padlock at the bottom of the window, click on it and sign in with your username and password. Select “Set date and time automatically.”

4. Check Wi-Fi connection

Using public Wi-Fi can easily trigger the “Your connection is not private” error because open networks often block HTTPS until you log in and agree to the terms and conditions. If a sign-in page doesn’t pop up automatically and you try to visit a webpage, you’ll most likely see the error message.

To fix it, try visiting an HTTP website you trust, which should automatically bring up a sign-in page. If it doesn’t, you can also try typing “1.1.1.1” into your URL bar. However, remember to always use a VPN on public Wi-Fi to protect your browsing data from snoopers connected to the same network.

5. Clear the browser’s cookies and cache

Often, an old or corrupted browsing cache or cookies can cause a conflict with a new certificate, preventing you from visiting the site. Clear the cache and cookies to refresh the link between your device and the site.

After clearing, reload the page. You’ll probably need to log back in to some sites, but it’s worth the effort.

6. Update your OS

Old operating systems might not work with the newest encryption protocols, like TLS v.1.3. In fact, most web servers no longer support old encryption protocols, so if your OS doesn’t support TLS, you will not be able to establish a secure connection. To avoid this problem, make sure that your OS is up to date:

• On Windows. Click on the Windows icon and go to “Settings” > “Update & security” > “Check for updates.” If the system detects a new update, install it and then restart the device.
• On Mac. Go to “System settings” > “General” > “Software update” and install available updates.

7. Check your antivirus or firewall

Sometimes antivirus software might be stopping you from visiting websites. Try temporarily turning off the SSL scanning feature (or the entire antivirus software if that option isn’t available), or allowlist the site if you’re sure it’s safe. Then reload the page to see if the error disappears. Don’t forget to turn protection back on once you’ve fixed it.

8. Clear the SSL state on your device's browser

If you keep getting the “Your connection is not private” error, your browser might be holding on to an old or corrupted security certificate. Every time you visit a secure website, your browser stores parts of the SSL/TLS handshake to load pages faster in the future. If those cached certificates expire or don’t match the current certificate, you may see the error.

Clearing the SSL state clears the stored data and causes the browser to fetch fresh SSL certificates the next time you visit any site. You can do it on any browser:

• On Chrome. Click the three-dot menu icon and go to “Settings” > “Privacy and security” > “Delete browsing data” > “Delete data.” Make sure you’ve selected “All time” and “Cached images and files” before the last step. 
• On Safari. In the taskbar, click on “Safari” and select “Settings” (or “Preferences,” depending on your language settings) > “Privacy” > “Manage website data” > “Remove all.”
• On Mozilla Firefox. Click on the hamburger menu icon (three vertical lines) > “Settings” > “Privacy & security.” In the “Cookies and site data” section, click “Clear browsing data.” Select “Temporary cached files and pages” and click “Clear.”
• On Microsoft Edge. Click on the three-dot menu icon and select “Settings” > “Privacy, search, and services” > “Clear browsing data” > “Choose what to clear.” Set the time range to “All time” and select “Cached images and files.” Then, click “Clear now.”
• On Opera. Click on the Opera menu icon > “Privacy & security” > “Delete browsing data.” Make sure you’ve selected “Cached images and files,” then click “Delete data.”

9. Restart your devices

Sometimes a simple restart can fix the “Your connection is not private” error message. Restarting your computer clears temporary caches and resets internet services, which can resolve underlying connection issues. Ensure that you reboot all devices involved in your connection, including your computer or smartphone, and even your router.

10. Troubleshoot your VPN

Sometimes a VPN can interfere with your connection path. Temporarily turn off your VPN while connected to a secure network, then try visiting the webpage again. If the error disappears, check your VPN settings.

Sometimes the issue originates from VPN security add-ons, such as the Threat Protection Pro™. You can prevent  NordVPN’s Threat Protection Pro™ from blocking websites by temporarily turning off the feature. But keep in mind that it’s there to protect your device from malicious sites, so only turn Threat Protection Pro™ off for websites you know for a fact are safe.

11. Update your browser

An outdated browser can easily cause the “Your connection is not private” error. Older versions often miss new security certificate standards or stop supporting modern encryption protocols like TLS 1.3. Because of these issues, even trusted websites can appear unsafe simply because your browser doesn’t recognize their updated SSL setup.

Regularly updating your browser ensures it gets the latest security fixes and can verify website certificates correctly. If you haven’t updated in a while, this is a good time to check:

• On Chrome. Go to “Settings” > “About Chrome.” Chrome will automatically check for updates and install them. Click “Relaunch” when it’s done.
• On Mozilla Firefox. Go to “Settings” > “General.” Under “Firefox updates,” click “Check for updates” and “Restart” to update Firefox.
• On Microsoft Edge. Go to “Settings” > “About Microsoft Edge,” and Edge will download any available updates automatically.
• On Opera. Click on the Opera icon and go to “Update & recovery.” Wait while the browser checks for updates, and click “Relaunch” now if an update installs.
• On Safari. Open the Apple menu > “System settings” > “General” > “Software update,” then install any available Safari or macOS updates. 

12. Try another browser

If your current browser keeps failing, switch to a different one. Different types of web browsers handle certificates and add-ons differently, so if you have issues with one but not the other, the problem is local to your usual browser. For example, if the page loads in Firefox but not Chrome, your Chrome settings or extensions may be the problem.

13. Flush the DNS cache

A corrupted DNS cache can direct your browser to the wrong server. And when DNS points to the wrong server, certificates won’t match. Flushing the DNS cache resets stored data:

• On Windows, open Command Prompt by pressing the Windows key + “R” and typing “cmd” in the Run dialog. Then run the “ipconfig /flushdns” command.
• On Mac, press “Command” + “Space” on your keyboard to open Spotlight, type "terminal," and press “Enter.” Then type “sudo killall -HUP mDNSResponder” and press “Enter.”

14. Disable browser extensions

Some browser extensions can interfere with SSL requests. Try turning them off, reloading the page, then re-enabling one by one to find the offender:

• Chrome. Go to the Menu > “Extensions” > “Manage extensions,” and switch the toggle off next to each extension.
• Firefox. Open the Menu > “Extensions and themes” > “Extensions,” and toggle off each extension.
• Edge. Click on the Menu icon > “Extensions” > “Manage extensions” and turn off all extensions.
• Opera. Go to the Menu > “Extensions” > “Extensions” and toggle all extensions off.
• Safari. Click on “Safari” > “Safari extensions” > “Extensions” and uncheck or uninstall each extension.

15. Try another network

Switching internet sources can help you determine if the problem lies with your Wi-Fi. Try connecting to mobile data or another trusted Wi-Fi source to see if the page opens then.

16. Check the URL

Before trying more advanced methods, double-check the website address you’re trying to visit. A large number of “Your connection is not private” errors occur simply because of a mistyped URL. 

Attackers often create look-alike domains to run phishing attacks or spread malware, using subtle changes like switching an “l” for a “1” or adding an extra character. According to most phishing statistics, these slight variations are one of the most common ways users are tricked into entering sensitive information on unsafe pages. 

Always double-check if the address bar shows the correct domain and that it has a “https://” in the beginning. If the warning pops up on a webpage you don’t usually visit or on one you reached through a suspicious link, leave the page immediately.

17. Check the SSL certificate

If nothing else has worked so far, inspecting the certificate itself is a good idea. Click the padlock icon next to the URL to view certificate details. Confirm that the website’s SSL certificate is valid, not expired, and matches the domain. If any of this information looks off, leave the page immediately. 

18. Contact website admin

If the page you are trying to access is that of your bank, employer, or a site you trust, contact the owner or support team. Share the error message and any error code you see. They can renew or fix the certificate or adjust server settings so the error doesn’t occur anymore.

19. Bypass the “Your connection is not private” error

If you’re sure the webpage is safe and need access immediately, you can bypass the warning, but proceed with caution and only if you fully trust the site. And never enter sensitive information like passwords or payment data after doing so. After all, the error is meant to protect you from entering malicious webpages.

Most popular browsers allow you to bypass the “Your connection is not private” error:

• Chrome. On the error page, click on “Advanced” > “Proceed to [site] (unsafe).”
• Firefox. Go to “Advanced…” > “Accept the risk and continue.”
• Edge. Click on “Advanced” > “Continue to [site].”
• Opera. Click on “Help me understand” > “Proceed to [site] (unsafe).”
• Safari. Click on “Show details” > “Visit this website” > “Visit website” (you may need to enter your Mac password to proceed).

“Your connection is not private” on different browsers

Depending on your browser, your operating system, and how the web servers are configured, you might get different variations of the same message. Knowing what each error shows might help you find the problem faster.

“Your connection is not private” on Google Chrome

On Chrome, you will most likely see:

“Your connection is not private. Attackers might be trying to steal your information from [site] (for example, passwords, messages, or credit cards). Learn more about this warning.”

The following common error codes can follow this message:

• ERR_CERT_SYMANTEC_LEGACY
• NET::ERR_CERT_AUTHORITY_INVALID
• NET::ERR_CERT_COMMON_NAME_INVALID (this occurs when the certificate does not match the domain)
• NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
• NTE::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
• NET::ERR_CERT_DATE_INVALID
• SSL certificate error
• ERR_SSL_VERSION_OR_CIPHER_MISMATCH

“Your connection is not private” on Safari

On Safari, you’ll see:

“This connection is not private. This website may be impersonating [site] to steal your personal or financial information. You should close this page.”

Safari does not typically display explicit error codes, unlike Chrome or Firefox. It may offer a “Show details” option instead, which, when you click it, explains the underlying problem using plain language, like an expired certificate, a domain mismatch, or an untrusted certificate.

“Your connection is not private” on Microsoft Edge

On Microsoft Edge, you’ll see:

“Your connection isn’t private. Attackers might be trying to steal your information from [site] (for example, passwords, messages, or credit cards).”

The error message may also be accompanied by one of the following codes:

• NET::ERR_CERT_AUTHORITY_INVALID
• Error Code: 0
• NET::ERR_CERT_COMMON_NAME_INVALID
• NET::ERR_CERT_DATE_INVALID
• DLG_FLAGS_INVALID_CA

“Your connection is not private” on Firefox

On Mozilla Firefox, you’ll see:

“Warning: Potential security risk ahead. Firefox detected a potential security threat and did not continue to [site]. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.”

This message can also be accompanied by one of the following error codes:

• MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED
• SEC_ERROR_EXPIRED_ISSUER_CERTIFICATE
• SEC_ERROR_EXPIRED_CERTIFICATE
• SEC_ERROR_UNKNOWN_ISSUER
• MOZILLA_PKIX_ERROR_MITM_DETECTED
• ERROR_SELF_SIGNED_CERT
• SSL_ERROR_BAD_CERT_DOMAIN

“Your connection is not private” on Opera

On Opera, you’ll see:

“Your connection is not private. Attackers might be trying to steal your information from [site] (for example, passwords, messages, or credit cards).”

You might also see one of these errors accompanying the message:

• NET::ERR_CERT_AUTHORITY_INVALID
• NET::ERR_CERT_INVALID
• NET::ERR_CERT_COMMON_NAME_INVALID
• NET::ERR_CERT_DATE_INVALID
• NET::ERR_SSL_VERSION_OR_CIPHER_MISMATCH
• ERR_CERT_SYMANTEC_LEGACY

If none of the methods above fixed the problem, the problem is likely on the web server’s side, and you can’t fix it. It might be that:

• The website forgot to renew the SSL certificate. On Chrome, you can check its validity by right-clicking on the green padlock symbol.
• The SSL certificate might be using an outdated SHA-1 cryptographic hash algorithm, which is considered to be unsecure and is no longer supported by current browsers.
• An untrusted organization has issued the SSL certificate.

If the security issue is on the server side, you could ask for help on forums (for example, the Google Chrome Help Community) or access the website without an SSL connection. However, we do not recommend establishing an unsecure connection, because your data will be out in the open, and anyone can snoop on your sensitive information.

Plus, if the website was supposed to have a secure connection but doesn’t, you won’t know why. It could be an innocent mistake, or it could have been hacked.

How to keep your connection more private and secure 

Good habits won’t always stop the “Your connection is not private” warning, but they do reduce risk and protect your information elsewhere online. Use the tips below to keep your connection private and your data safer:

• Limit what you share. Avoid posting personally identifiable information (PII) and think before you enter data on any page.
• Use strong passwords. Take advantage of a password manager to help create and store unique passwords and add 2FA wherever possible for an extra layer of security. These steps don’t fix the error, but they strengthen your overall protection.
• Keep software up to date. Update your operating system, browser, and apps to reduce security bugs.
• Review privacy settings. Tighten security settings in your browser and remove unused extensions.
• Inspect every URL. Look for “https://” and the padlock in the URL bar before you continue.
• Be careful on public networks. Avoid logging in or making payments on open connections. To stay safer, use a reliable VPN, like NordVPN, that encrypts your traffic and protects your data, especially on public Wi-Fi.