How to fix HTTP errors: the overview

An HTTP error is the short answer a server gives when a request did not work. The number tells you roughly where the problem is: codes starting with 4 usually point to the request (login, permissions, too many requests), codes starting with 5 point to the server. Below you find our step by step guides for the errors our readers search for most, with a quick hint on who can actually fix it.

ErrorWhat it meansWho can fix it
401 UnauthorizedLogin or access token missing or wrongUsually you (log in again, check the key)
402 Payment RequiredThe service wants a payment or an active planYou (check plan, billing, quota)
403 ForbiddenThe server understood you but refuses accessOften the site owner, sometimes your IP or VPN
407 Proxy Authentication RequiredA proxy between you and the site wants a loginYou or your IT (proxy settings)
420 Enhance Your CalmUnofficial code some services use for too many requestsYou (slow down, wait)
429 Too Many RequestsToo many requests in a short time, rate limit reachedYou (wait, reduce requests)
502 Bad GatewayA server in between got no valid answer from the next oneAlmost always the site owner
TimeoutThe answer took longer than allowedBoth, depending on where it hangs
Client-side exceptionThe page’s JavaScript crashed in your browser (Next.js)Try the visitor steps first, then the site owner

Three checks that solve many errors

Reload without cache (Windows Ctrl + F5, Mac Cmd + Shift + R). Try a private window or another device to rule out extensions and stored data. Wait a few minutes on 429, 420 and 502: these often fix themselves once the limit resets or the server is back.

Our take

Most HTTP errors look technical, but the first question is always the same: is it my side or theirs? If the error appears on two devices and two networks, it is the website, and the best fix is to report it. If it only appears for you, the guides above walk you through the usual causes in a few minutes.

Contents