Chromebook 'Not Private' NET::ERR_CERT_AUTHORITY_INVALID Fix

1. Your Chromebook's clock is wrong — this is the most common cause

I've seen this trip up people for years. Chromebooks use certificate-based encryption to verify a website's identity. If your system clock is off by more than a few minutes, Chrome will reject the certificate and throw NET::ERR_CERT_AUTHORITY_INVALID on every single site. This happens when the battery completely drains, or after a long sleep (days or weeks), because the internal CMOS battery can't keep time. You'll also see it after a time zone change without a network sync.

Fix it:

1. Click the time in the bottom-right corner of the shelf.
2. Select the gear icon to open Settings.
3. Go to Advanced > Date and time.
4. Make sure Set automatically is toggled on.
5. If it's already on, turn it off, wait 5 seconds, turn it back on.
6. Restart your Chromebook (shut down, not just close the lid).

If that doesn't work, manually set the time by turning off automatic sync, picking the correct time zone, and entering the right time. Then re-enable automatic sync. I've had to do this on three different models (Pixelbook Go, Lenovo Duet, Acer Spin 713) after they sat idle for weeks.

2. Your Wi-Fi network is injecting a bad certificate

This one's less common but more insidious. Some public Wi-Fi networks, corporate networks, or even home routers with captive portals (like hotel logins) intercept HTTPS traffic by replacing certificates. If the router's certificate isn't trusted by ChromeOS, you get the error on all sites. I once spent an hour troubleshooting a friend's Chromebook only to find their home router's security firmware had a busted certificate.

Fix it:

1. Forget the current Wi-Fi network: Settings > Network > Wi-Fi > select your network > Forget.
2. Reconnect fresh — this clears any cached captive portal certificates.
3. If you're on a public or corporate network, try connecting to a different network (like your phone's mobile hotspot). If the error disappears, the original Wi-Fi is the problem. Report it to the network admin.
4. On home networks, reboot your router and modem. Also update the router's firmware — I've seen old Netgear and TP-Link routers cause this.

Skip: messing with Chrome flags or installing third-party root certificates on a Chromebook. It's unnecessary and risky.

3. Corrupted Chrome profile or browser cache

Sometimes the issue isn't the network or time — it's Chrome itself. A corrupted profile or a bad cache can cause certificate errors site-wide. This is rarer on Chromebooks than on Windows, but I've fixed it on ChromeOS 120 and later versions. You'll know it's the profile if the error persists across different Wi-Fi networks and after restarting.

Fix it:

1. Clear the browser cache: Settings > Privacy and security > Clear browsing data > select 'All time' and 'Cached images and files' — clear it.
2. Create a new Chrome profile: Click your profile picture in the top-right > Manage people > Add person. Switch to that new profile and test the same sites. If they load fine, your old profile is toast. Export your bookmarks from the old profile and delete it.
3. As a last resort, Powerwash your Chromebook: Settings > Advanced > Reset settings > Powerwash. This wipes all local data. Only do this if nothing else works and you've backed up everything.

Powerwashing is nuclear — I recommend it only after trying the first two causes. But it's a clean fix that always works.

Quick-reference summary table