Quick Answer: ERR_TOO_MANY_REQUESTS (HTTP 429) means the server has rate-limited your Chromebook because it received too many requests in a short window, often from a stuck extension, an auto-refreshing tab, or a shared network IP that other users have already used up the request quota on. Waiting it out and clearing cookies for the site usually resolves it.
What Causes This Error
- The site’s server enforces a rate limit and your requests, or requests from your shared IP, briefly exceeded it
- A browser extension or a background tab repeatedly polling the same API endpoint
- A corrupted cookie or session token causing the site to reject and immediately retry a request in a loop
- Being on a school, office, or public Wi-Fi network where many devices share one public IP, so one heavy user can trigger the limit for everyone
- Automated scripts or bots on the same network address tripping the site’s abuse protection
How to Fix It
Step 1: Wait a few minutes before retrying
Rate limits are almost always temporary. Most sites reset their limit window within 1 to 15 minutes, so a hard reload immediately after the error rarely helps and can extend the lockout.
Step 2: Close duplicate tabs and check for auto-refresh
Look for other open tabs on the same site, or extensions that periodically refresh pages in the background, since these can be quietly generating the excess requests.
Step 3: Clear cookies for that specific site
See how to clear cache and cookies on a Chromebook, or use the padlock icon in the address bar to clear data for just the affected domain, which can break a stuck request loop.
Step 4: Test in an incognito window
Press Ctrl + Shift + N to rule out an extension that’s making repeated background calls to the same API.
Step 5: Switch networks if the problem follows you across sites
On a shared school or office network, try a phone hotspot. If the error disappears, your shared IP address had already hit the site’s limit before you got there.
Step 6: Log out and back in
If the error appears only while signed in to a specific account on the site, sign out, clear cookies, and sign back in to get a fresh session token.
Still Not Fixed?
If the error clears after 15–30 minutes on its own, it was a genuine temporary rate limit and no further action is needed. If it returns immediately every time you retry on that same site, an extension, a saved script, or a background app on your network is most likely still hammering the same endpoint.
FAQ
Is ERR_TOO_MANY_REQUESTS my fault?
Not usually. It’s a server-side protection, and on shared networks it’s often triggered by someone else’s traffic on the same public IP, not anything you personally did.
Does this mean my Chromebook has malware?
Rarely. It’s far more common for this to be a normal rate limit or a misbehaving extension than malware, but if it happens on many unrelated sites simultaneously, run a check via ERR_CACHE_MISS-style troubleshooting and review your installed extensions.
Will a VPN help or hurt?
It depends. A VPN can give you a fresh IP address that isn’t already rate-limited, but it can also share you with other VPN users who’ve already triggered the same limit.
