What website error messages mean
A website error code tells you roughly where the problem is. 4xx codes usually mean the address or permission is wrong; 5xx codes mean the server or the website's code had a problem. Check a few safe things, then send us the exact message.
Applies to: Cloudflare Enhance
On this page
An error code on a web page tells you roughly where the problem is. Codes starting with 4 usually mean the address is wrong or the page isn't allowed to be seen. Codes starting with 5 mean the server, or the website's own code, had a problem. You can do a few safe checks yourself. After that, send us the exact message and we'll find and fix the cause.
What the common codes mean
| Code | What it says | What it usually means |
|---|---|---|
| 403 | Forbidden | The server refused to show that page or file. Often a permission setting, a security rule, or a folder with no home page. |
| 404 | Not Found | Nothing exists at that address. A mistyped link, a page that was moved or deleted, or a missing redirect. |
| 500 | Internal Server Error | The website's code failed. Often a plugin, a theme, an update or a settings file. |
| 502 | Bad Gateway | One server passed the request on and got a bad answer back. Often the website's code crashed or restarted. |
| 503 | Service Unavailable | The website can't answer right now: it's overloaded, being restarted, or in maintenance mode. |
| 504 | Gateway Timeout | The website took too long to answer. Often a slow page, a heavy plugin task or a busy database. |
Disk full
A website has a fixed amount of disk space. When it's full, the site can't save anything: uploads fail, logins stop working, and pages can show a 500 or 503 error or go blank. Large backups kept inside the website folder, old logs and big media files are common causes. We can find what's using the space and free it up.
Errors that mention Cloudflare (520 to 526)
If the error page has Cloudflare's name on it, such as 521, 522, 525 or 526, the visitor reached Cloudflare but Cloudflare couldn't get a good answer from the website. The same goes for "too many redirects" (ERR_TOO_MANY_REDIRECTS) and certificate warnings. These have their own guide: see Fix DNS and SSL errors.
Safe checks you can do
None of these change anything on your website.
- Reload the page once. A 502, 503 or 504 can clear in a few seconds.
- Open the same address in a private or incognito window. If it works there, the problem may be your browser's cache.
- Try another page on the same site, such as the home page. Note whether one page or the whole site is affected.
- Try from your phone with Wi-Fi off. If it works on mobile data, the problem may be your network.
- For a 404, check the address for a typo, and ask whoever sent the link where it should go.
- Think back: did anything change right before? A plugin update, a new plugin, a settings change or new content.
- Take a screenshot that shows the whole error and the address bar.
What to send us
Open a Website Support ticket at Support Departments and include:
- The full address that shows the error.
- The exact code and wording, and the screenshot.
- When it started, and whether it's every time or now and then.
- Whether the whole site is affected or one page.
- Anything that changed right before.
- Your browser and device, if only you see it.
If the whole site is down, choose a higher priority. See Report a website that's down or broken.
Leave passwords out
We never need your password to look into an error. Don't put passwords, keys or card numbers in a ticket. See What to include in a ticket, and what never to send.
You'll know it's fixed when
The page loads normally in a private window, on your phone and on your computer, and we've replied on the ticket with what caused it and what we changed.
If the error comes back
- It returns after a fix. Reply on the same ticket with the time it came back. Patterns, such as "every morning" or "only when I upload", help us find the cause.
- It only happens in WordPress admin. See Common WordPress errors and what to do.
- The site is slow before the error appears. That points to a 504 or a resource limit. Tell us which pages are slow.
Next steps
- How hosting changes work at Oogle today
- Report a website that's down or broken
- Fix DNS and SSL errors
Frequently asked questions
Is the error my fault?
Usually not. Most errors come from a plugin, an update, a setting or the server. Tell us what you were doing when it appeared, so we can trace it.
Why do I see an error and my colleague doesn't?
It may be cached in one browser, limited to logged-in users, or limited to one page. Try a private window, and tell us exactly which address shows the error and who sees it.
The error page has Cloudflare's name on it. What does that mean?
The visitor reached Cloudflare, but Cloudflare had trouble reaching the website behind it. See Fix DNS and SSL errors for what each Cloudflare code means.