Search guides

Fix a browser that says connection not secure

We'll check system clock, clear cache, rule out antivirus or proxy interception, and tell you when to proceed cautiously or back away.

Troubleshooting · Security basics
5–15 min
What you'll need
  • Browser showing the warning
  • Access to system date/time settings
  • Antivirus settings (if installed)
Step 1 of 9

Quick triage — pick your path

Quick triage — pick your path

Choose the option that matches what you see. You can jump straight to that section.

Show full guide

Steps

Goal: Check system clock, clear cache, rule out antivirus, and know when to proceed or back away.

  • Note the exact error (e.g. ERR_CERT_DATE_INVALID, ERR_CERT_AUTHORITY_INVALID). Click “Advanced” in Chrome to see the code.
  • Good: You have the code. Proceed to Check system clock.
  • Bad: No code visible—still check clock first; it fixes many cases.

Check system clock

Goal: Rule out wrong date or time—a common cause of SSL warnings.

  • Windows: Settings > Time & language > Date & time. Turn on “Set time automatically.”
  • Mac: System Settings > General > Date & time. Enable “Set date and time automatically.”
  • Confirm the date and time match reality. Reload the site.
  • Good: Clock was wrong and is now fixed—the warning may disappear. Bad: Clock was correct—proceed to Try incognito.

Try incognito

Goal: Rule out cached bad state.

  • Open an incognito (Chrome) or private (Firefox, Safari) window. Visit the site again.
  • Good: The warning is gone in incognito—clear cached data for the site or use incognito when visiting. Bad: The warning persists—proceed to Check antivirus.

Check antivirus

Goal: Rule out antivirus or corporate proxy intercepting HTTPS.

  • Open your antivirus settings. Look for “HTTPS scanning,” “SSL inspection,” or “Web protection.”
  • Temporarily disable to test, or add the site to exclusions. If on a work network, IT may manage this—contact them.
  • Good: Antivirus was intercepting—disable or exclude, retest. Bad: No antivirus HTTPS scanning—proceed to When to proceed.

When to proceed

Goal: Know when it is safe to click “Advanced” and proceed.

  • Never proceed on banking, email, or shopping sites—an attacker could be intercepting. Close the tab. Contact the site or IT.
  • Proceed cautiously only for local or internal sites you control (e.g. router at 192.168.1.1, NAS). Do not enter passwords. If the site asks for a password, close the tab and fix the underlying cause first.
  • Good: You have a clear rule. Bad: When in doubt, close the tab.

When to get help

Goal: Know when to escalate.

  • Call IT if you are on a work network and the error appears on many sites. They may manage certificates or proxy.
  • Call the site if the error appears only on their site and persists after you fix clock and cache. Provide the exact error code and browser/OS version.
  • Confirm you have tried the steps above before calling.

Verification

  • The browser shows no “connection not secure” or “Your connection is not private” warning when visiting the site.
  • System date and time are correct and set to automatic.
  • If you proceeded for a local site, you did not enter passwords or sensitive data.

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Check clock Fix system date and time; wrong clock causes many SSL errors.
  2. Incognito and cache Try incognito window; clear cached data if it helps.
  3. Antivirus Check if antivirus HTTPS scanning is enabled; disable to test or add exclusion.
  4. Test on other device Confirm whether the error is site-wide or device-specific.
  5. Escalate Contact IT (work network) or the site owner (their cert problem).

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • Exact browser error code (e.g. ERR_CERT_DATE_INVALID)
  • System date and time
  • Whether antivirus has HTTPS scanning
  • Whether error appears on other devices or networks
  • Browser and OS version

Is the system date and time correct?

Wrong clock causes ERR_CERT_DATE_INVALID and many generic SSL warnings.

Check system date and time. Windows: Settings > Time & language > Date & time. Mac: System Settings > General > Date & time. Turn on automatic time. Good: clock correct—proceed. Bad: clock wrong—fix it, reload the site.

Yes No

You can change your answer later.

Fix system clock

Enable "Set time automatically" (Windows) or "Set date and time automatically" (Mac). Reload the site. The warning often disappears. If it persists, proceed to incognito and antivirus checks.

Done

Does the error persist in incognito or private mode?

Cached state can cause repeated errors.

Open an incognito (Chrome) or private (Firefox, Safari) window. Visit the site. Gone: clear cache for the site or use incognito. Persists: proceed to antivirus check.

Yes (persists) No (gone)

You can change your answer later.

Clear cache

Clear cached images and files for the site, or use incognito when visiting. The warning should not return. If it does, check antivirus.

Done

Does antivirus or corporate proxy intercept HTTPS?

HTTPS scanning replaces certificates and can trigger the warning.

Check antivirus settings for "HTTPS scanning," "SSL inspection," or "Web protection." Temporarily disable to test, or add the site to exclusions. Work network: IT may manage this. Yes: disable or exclude, retest. No: proceed to site check.

Yes No

You can change your answer later.

Disable HTTPS scanning or add exclusion

Disable antivirus HTTPS scanning temporarily, or add the site to exclusions. Retest. If the warning disappears, keep the exclusion or contact IT if on work network.

Done

Is this a known trusted site (bank, email) or an unknown site?

Never proceed on banking or email—an attacker could be intercepting.

If bank, email, or major service: do not proceed. Close the tab. Contact the site or IT. If local device (router at 192.168.1.1) or internal tool you control: you may proceed cautiously—no passwords. Known/important: escalate. Local/internal: proceed with caution.

Known (bank, email) Local or internal

You can change your answer later.

Escalate

Do not enter passwords. Contact the site if the error appears only on their site. Contact IT if you are on a work network and the error appears on many sites. Provide the exact error code and browser/OS version.

Done

Proceed cautiously

For local or internal sites only: click "Advanced" and proceed. Do not enter passwords or sensitive data. If the site asks for a password, close the tab and fix the underlying cause first.

Done

Reviewed by Blackbox Atlas

Frequently asked questions

Why does my browser say "Your connection is not private"?
Common causes are wrong system clock, expired certificate on the site, antivirus or corporate proxy intercepting HTTPS, or a broken certificate chain. Check the system clock first—it fixes many cases.
Is it safe to click "Advanced" and proceed anyway?
Only for sites you fully trust (e.g. your own router at 192.168.1.1). Never proceed on banking, email, or shopping sites—an attacker could be intercepting. If unsure, close the tab and contact the site or IT.
What if the error appears only on one site?
The site may have an expired or misconfigured certificate. Try again later—sites sometimes fix certs quickly. If it persists, contact the site. Do not enter passwords until the warning is gone.

Rate this guide

Was this helpful?

Continue to