TLS/SSL error appears only with VPN
A TLS/SSL error means the browser could not complete a trusted HTTPS session. With VPN enabled, the trigger can be route-specific filtering, HTTPS inspection, stale DNS, or a site edge issue.
Quick answer
Check device date and time, try another browser, disable antivirus HTTPS scanning for one test, switch VPN server, and compare another network before assuming the certificate itself is bad.
Diagnose the certificate path
The exact browser message matters. NET::ERR_CERT_AUTHORITY_INVALID, protocol errors, and connection resets point to different layers.
Do not ignore certificate warnings on sensitive sites. Diagnose with a public test page first.
| Symptom | Likely cause | How to check | How to fix |
|---|---|---|---|
| Wrong date warning | Device clock | Compare system time | Enable automatic date and time |
| Unknown authority | HTTPS inspection or captive portal | Try another network | Sign in to portal or disable inspection |
| Protocol/reset error | DPI, CDN edge, or MTU | Switch VPN server | Change route and collect error text |
If it still happens
Capture the public hostname, browser, VPN server, and exact TLS error. Do not send private account paths or certificate dumps containing personal data.
If the error only appears on one corporate or school network, local HTTPS inspection may be the deciding factor.