Network security technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, Wi-Fi troubleshooting, TLS/SSL & HTTPS errors, VPN & firewall conflicts, DNS & IP configuration, browser security

Fix TLS/SSL errors on Wi-Fi — “Your connection is not private”, secure connection failed, HTTPS not working

Technician avatar Technician
Hi! We’ll get these TLS/SSL errors on Wi-Fi sorted so secure sites load normally again. To target the fix, tell me a bit more:

• Are you seeing messages like “Your connection is not private”, “Secure connection failed”, NET::ERR_CERT_AUTHORITY_INVALID, or ERR_SSL_PROTOCOL_ERROR?
• Do all HTTPS websites fail on this Wi-Fi, or only some (for example bank, email, or work sites)?
• If you switch that same device to mobile data or another Wi-Fi, do the TLS/SSL errors disappear?
• Are you using any VPN, antivirus with HTTPS scanning, corporate proxy, or content-filtering router?

TLS and SSL errors over Wi-Fi are usually caused by one of three things: wrong date/time on the device, a man-in-the-middle filter (VPN, firewall, or captive portal) injecting its own certificate, or broken DNS / network settings that stop the TLS handshake from finishing. We’ll walk through each piece step by step.
Customer
On my home Wi-Fi, almost every secure site shows an error. Chrome says “Your connection is not private” with NET::ERR_CERT_AUTHORITY_INVALID. Firefox shows “Secure connection failed” or “Warning: Potential Security Risk Ahead”. But if I turn off Wi-Fi and use mobile data, the same sites work fine. I do have a VPN client installed for work and Kaspersky antivirus, but the errors happen even if I disconnect the VPN app.
Technician avatar Technician
Thanks, that’s very helpful. The fact that HTTPS works on mobile data but not on your Wi-Fi means the issue is on the home network path — often router, DNS, VPN driver, or antivirus HTTPS scanning.

First, let’s rule out the simplest TLS/SSL problem: wrong system clock.

1) On the affected computer, open the date and time settings.
2) Make sure the time zone, date, and time are correct. Turn on “Set time automatically” and “Set time zone automatically” if available.
3) Restart the browser and try a site that was failing (like your bank or Gmail).

A skewed clock makes certificates look expired or “not yet valid”, which triggers SSL certificate errors on Wi-Fi but not always on mobile. While you’re testing, can you also tell me: do phones or another laptop on the same Wi-Fi see the same TLS/SSL error messages, or is it this one PC only?
Customer
Time and date were already correct. I toggled the automatic time setting anyway but nothing changed. My phone on the same Wi-Fi also shows “Connection is not secure” in Firefox for some sites, but most apps work. On the PC, almost every HTTPS site fails over Wi-Fi, but a few random ones still load. Plain HTTP pages work, just not secure ones.
Technician avatar Technician
Got it. Since multiple devices on the same Wi-Fi show TLS/SSL errors, the problem is likely at the router or upstream DNS/gateway level, not just this PC.

A few common reasons for TLS/SSL errors on home Wi-Fi:
• The router or ISP is forcing traffic through a captive portal or content filter with a self-signed certificate.
• Custom DNS servers (on the router or device) are redirecting HTTPS to the wrong place, causing certificate name mismatch.
• A VPN or security suite installs a local proxy that breaks when Wi-Fi is used but not when on mobile data.

Let’s do a quick isolation test on the PC:
1) Temporarily disable Kaspersky’s HTTPS/SSL scanning or “Encrypted connection scanning” feature (just for a few minutes).
2) Disconnect from VPN fully — ensure its adapter is not active in Network Connections.
3) In Windows, open Control Panel → Internet Options → Advanced and click “Reset” or at least clear SSL state (if available).
4) In Command Prompt (run as admin), enter:
  • ipconfig /flushdns
  • netsh winsock reset

Then restart the PC and try an HTTPS site again while still on the same Wi-Fi. Let me know if the TLS/SSL errors change or if some sites now load.
Customer
I disabled Kaspersky’s encrypted traffic scan, flushed DNS, and ran the Winsock reset. After reboot, a few more sites work, but I still get NET::ERR_CERT_AUTHORITY_INVALID on my banking site and SEC_ERROR_UNKNOWN_ISSUER in Firefox. Also, when I click the “Advanced” link in Chrome, it says the certificate is issued by something with my router’s brand name, not by a normal certificate authority.
Technician avatar Technician
That detail is huge: if the certificate shows your router’s brand as the issuer, the router (or an attached security box) is trying to intercept HTTPS and re-sign it with its own TLS certificate. Because that root certificate isn’t trusted by Windows, Chrome, or Firefox, you see constant SSL certificate errors on Wi-Fi.

Many “security” or parental-control features do this by acting as a local TLS proxy.

Next step — turn off HTTPS interception on the router
1) Connect to your router’s admin page (ex: 192.168.0.1 or 192.168.1.1).
2) Look for features like Web Filter, Content Filter, Safe Browsing, HTTPS Inspection, SSL Proxy, or Parental Controls.
3) Temporarily disable any feature that mentions HTTPS, TLS, SSL, or certificate inspection.
4) Save changes and reboot the router.
5) Reconnect your PC and phone to the Wi-Fi and try those failing HTTPS sites again.

If TLS/SSL errors go away after this, we’ve confirmed that the Wi-Fi router’s filtering feature was causing “secure connection failed” and NET::ERR_CERT_AUTHORITY_INVALID on all devices.
Customer
I logged into the router and found a “Safe Web & HTTPS inspection” option that I had turned on when setting up parental controls. After disabling HTTPS inspection and rebooting the router, most TLS/SSL errors on Wi-Fi disappeared. My bank and Gmail now open in Chrome without any warnings. However, one internal work site we access over VPN still says “This site can’t provide a secure connection – ERR_SSL_PROTOCOL_ERROR” when I’m on Wi-Fi.
Technician avatar Technician
Great — that confirms the router’s HTTPS inspection was the main source of TLS/SSL errors on your home Wi-Fi.

For that work site over VPN:
• Make sure the VPN client is fully connected before you open the browser.
• In the VPN app settings, check if there is split tunneling. Try disabling split tunneling so all traffic, including HTTPS, goes through the VPN tunnel instead of partly over your local Wi-Fi.
• Some older corporate servers only support certain TLS versions. In your browser’s advanced settings, ensure TLS 1.2 is enabled and experimental “min TLS 1.3 only” flags are turned off.

Also, since we’ve touched a lot of network pieces, let’s refresh the browser profile for that VPN site:
1) Open an incognito/private window and try the same HTTPS URL inside the VPN session.
2) If it still shows ERR_SSL_PROTOCOL_ERROR, try another browser (for example Edge instead of Chrome) while VPN is on.

If the site works in one browser but not another, we’ll clear that browser’s SSL state, HSTS cache, and any pinned certificate next.
Customer
I turned off split tunneling so everything goes through the VPN. In an incognito window, the internal site finally loads without TLS errors. In normal Chrome windows it kept failing until I cleared browsing data. Firefox over the VPN works fine too. So at this point, all HTTPS sites are working on Wi-Fi as long as I’m either on VPN for work stuff or just using normal Wi-Fi for personal sites.
Technician avatar Technician
Excellent — sounds like we’ve eliminated the TLS handshake failed and SSL certificate not trusted problems on your Wi-Fi.

To reduce the chances of SSL errors coming back on this network:
• In your router’s Internet/DNS settings, use reliable DNS servers (for example your ISP’s defaults or a trusted public resolver) instead of random third-party DNS that might hijack HTTPS.
• Avoid enabling any feature that says it will “decrypt HTTPS traffic” or “inspect SSL” unless you are ready to install the router’s root certificate on every device (and understand the security implications).
• Keep your browsers updated so they support modern TLS 1.2 / TLS 1.3 and can properly validate certificates.
• Let Kaspersky handle malware scanning but keep its HTTPS scanning mode in ‘compatibility’ or ‘no interception’ if available, so it doesn’t break secure Wi-Fi connections again.

If you ever start seeing “certificate expired”, “name mismatch”, or “NET::ERR_CERT_COMMON_NAME_INVALID” on many sites again, we’ll know to first check whether something on the Wi-Fi is inserting its own TLS certificate.
Customer
That makes sense. One more thing: sometimes on public Wi-Fi (like at a café or hotel), I also get “Your connection is not secure” before I can even see their login page. Is that the same kind of TLS/SSL error, or something different I should handle another way?
Technician avatar Technician
Great question. On public Wi-Fi, TLS/SSL warnings often come from a captive portal rather than a broken router at your home.

Typical pattern:
• You join the café Wi-Fi and your device has IP connectivity, but the network wants you to accept terms or enter a room number first.
• When you go straight to https://example.com, that site’s certificate won’t match the café’s login page, so the browser shows a certificate name mismatch or “your connection is not secure” warning.

Safer way to handle this:
1) After joining public Wi-Fi, first browse to a plain http://neverssl.com or another non-HTTPS site to trigger the captive portal.
2) Complete the sign-in page there.
3) Once you see you’re fully online, then go to your normal HTTPS sites and confirm there are no TLS/SSL errors.

Still avoid clicking “Proceed anyway” on certificate errors for banking or login sites — that’s where real attacks can hide. If you’re ever unsure whether a Wi-Fi TLS/SSL error is safe to bypass, you can always open a chat with an expert and we’ll review it together.
Customer
Got it. I’ll use a non-HTTPS site first on public Wi-Fi and avoid bypassing certificate warnings on sensitive pages. At home, everything loads normally now — no more “Your connection is not private” messages. Thanks for walking through all the TLS/SSL stuff with me.
Technician avatar Technician
You’re welcome — happy we could get your HTTPS and Wi-Fi back to normal.

Summary: To fix TLS/SSL errors on Wi-Fi, confirm the device’s date/time, temporarily disable antivirus HTTPS interception, flush DNS and reset Winsock, then log into the router to turn off any SSL inspection or web filtering that re-signs certificates. For VPN and work sites, adjust split tunneling and browser caches so the TLS handshake can complete cleanly. If you keep seeing “secure connection failed” or NET::ERR_CERT_AUTHORITY_INVALID, you can always start a chat with an expert and we’ll trace the connection live with you.
Customer
Perfect. Now I actually understand why those TLS/SSL warnings were happening instead of just clicking around randomly. Really appreciate the detailed help!
Technician avatar Technician
Anytime! If a friend or coworker complains that HTTPS sites aren’t working on Wi-Fi, they’re seeing “Your connection is not private” everywhere, or they keep getting SSL certificate errors, you can share this checklist — and if you’d like someone to go through the TLS/SSL settings with you in real time, just start a chat with an expert and we’ll take it from there.

Quick answer: the accepted fix

Accepted fix when you get TLS/SSL errors on Wi-Fi: verify your device date and time, turn off any HTTPS/SSL inspection in antivirus or router settings, flush DNS and reset network stacks, and make sure the router isn’t inserting its own untrusted certificate. For work or VPN sites, use the VPN’s full tunnel and clear browser caches so “Your connection is not private” and “Secure connection failed” warnings disappear.

Why TLS/SSL errors happen on Wi-Fi (certificates, DNS, routers, VPNs)

Most TLS/SSL errors on Wi-Fi are caused by something between your device and the website changing how secure connections work. A wrong system clock makes certificates look expired or not yet valid. A router or firewall that does HTTPS inspection may re-sign traffic with its own untrusted certificate, leading to NET::ERR_CERT_AUTHORITY_INVALID or SEC_ERROR_UNKNOWN_ISSUER. Misconfigured DNS servers can send you to the wrong IP address so the certificate name doesn’t match, causing “This site can’t provide a secure connection” or “SSL certificate error” warnings.

VPN clients and corporate proxies can also affect the TLS handshake. If the VPN forces older TLS versions or intercepts TLS without installing a proper root certificate, browsers will show secure connection failed messages whenever you’re on that Wi-Fi but not when you use mobile data. Separating the path into device → Wi-Fi → router → DNS/VPN → website lets you see where the SSL connection starts failing.

How to tell if TLS/SSL errors are from your device, Wi-Fi, or the website

To quickly narrow down TLS/SSL errors on Wi-Fi, change one thing at a time:

Start by testing the same HTTPS site on another network — for example, mobile data or a different Wi-Fi. If the error only appears on your home Wi-Fi, focus on the router, DNS, and any filtering or parental-control features. If every network shows “your connection is not private” on the same sites, the problem is more likely that site’s certificate or your browser/OS trust store.

Then compare different devices and browsers. If only one browser shows SSL connection error while others work, clearing that browser’s cache, HSTS data, and SSL state usually helps. If all devices on that Wi-Fi show TLS/SSL warnings, the router or gateway is almost always the cause — especially if the certificate issuer’s name matches your router brand or ISP instead of a public certificate authority.

TLS/SSL errors on Wi-Fi — quick troubleshooting tips

Confirm the device clock, then fix router HTTPS inspection, DNS, and VPN/antivirus settings.

Fast path: check that your device’s date/time are correct → test the same HTTPS site on mobile data vs. Wi-Fi → temporarily disable VPN and antivirus HTTPS scanning → flush DNS and reset network settings → log into the router and turn off any SSL/TLS inspection or web filtering that injects its own certificate. Once the browser sees a valid certificate chain and the TLS handshake completes, “Your connection is not private”, “Secure connection failed”, and other TLS/SSL errors on Wi-Fi should disappear.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your devices, router model, and VPN/security software, please consult a verified expert on Whizz-Tech before making decisions.

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for TLS/SSL errors on Wi-Fi, “Your connection is not private” warnings, HTTPS not working, and more.

Expert will respond in minutes

We match you with a networking and security specialist who understands HTTPS, TLS/SSL handshakes, VPN clients, DNS, and router security across Windows, macOS, Android, iOS, and smart devices.

Save time & stay secure

Stop guessing whether it’s safe to bypass an SSL certificate error. Get a clear, step-by-step TLS/SSL fix in chat so your Wi-Fi is both working and secure.

FAQ

Why am I getting TLS/SSL errors only on my Wi-Fi?

If TLS/SSL errors like “Your connection is not private” happen only on a specific Wi-Fi network but not on mobile data, something on that network is interfering with HTTPS. Common causes include the router doing HTTPS/SSL inspection with its own untrusted certificate, custom DNS servers redirecting traffic, or a local firewall/VPN proxy that alters the TLS handshake only when you’re on that Wi-Fi.

How do I fix “Your connection is not private” on home Wi-Fi?

First, confirm your device’s time and time zone are correct. Then temporarily disable VPN and antivirus HTTPS scanning, flush DNS, and reboot the device. Log into the router and turn off any SSL/TLS inspection, web filter, or parental control feature that injects its own certificate. After that, restart the router and reconnect to Wi-Fi; most “Your connection is not private” and “Secure connection failed” errors will clear.

Is it safe to ignore TLS/SSL certificate warnings?

In general, no — you should not ignore or permanently bypass TLS/SSL warnings for banking, email, shopping, or login sites. These errors indicate that the certificate is expired, not trusted, or doesn’t match the website’s name, which can be a sign of misconfiguration or an attack. Fix the underlying Wi-Fi, DNS, or router problem instead of clicking “proceed anyway”, especially on public networks.

Why do HTTPS sites fail when I use a VPN over Wi-Fi?

When a VPN is active, your traffic may be split between the VPN tunnel and local Wi-Fi. If split tunneling is misconfigured or if the VPN’s DNS and TLS settings conflict with your router’s, some HTTPS sites can show ERR_SSL_PROTOCOL_ERROR or “secure connection failed”. Setting the VPN to route all traffic, refreshing DNS, and disabling router-level HTTPS inspection usually resolves these mixed Wi-Fi/VPN TLS issues.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.