Errors starting with 4 mean the request was refused or couldn't be handled. The number tells you why. (404 errors have their own article: Fix "404 Not Found" errors.)
400 Bad Request
The request was malformed, often because of an old or damaged cookie. Clear your browser's cookies and cache for the site and try again. If it keeps happening on your own site, think about what changed recently and deactivate recently added plugins one by one to find the cause.
401 Unauthorized
The page needs a login, or a security check didn't let the request through. If you've password-protected part of your site with a plugin, check you're using the right details. Our bot protection can also answer automated tools, such as SEO crawlers or uptime monitors, with a 401. If a service you rely on is blocked, contact support and tell us which one.
403 Forbidden
The visitor isn't allowed to see the page. Common causes:
- A security plugin on your site blocking an IP address or country. Check its settings and logs.
- Our bot protection briefly blocking a real visitor, especially on the login page. This usually clears up after a short while.
- Our firewall blocking a form submission it found suspicious (a 403 right after you click Submit or Save).
If a 403 keeps happening, contact support with the page address, your IP address and the time it happened, and we'll check it.
429 Too Many Requests
Our platform protects sites against password-guessing and vulnerability scanners. If one IP address makes a lot of requests that fail, for example to pages or files that return 404 or 403, it is slowed down for a while with a 429.
It usually goes away if you wait a little, and the site should load meanwhile from another connection such as mobile data. To stop it coming back, fix broken links and missing images or scripts: your browser's developer console (press F12) lists anything that fails to load. If you need help, send support the steps that cause the error and your IP address, which you can find at ipinfo.io/ip.