---
title: "HTTP 520 Web Server Returns Unknown Error — Meaning & Fix"
description: "HTTP 520 Web Server Returns Unknown Error explained: what it means, common causes, how to fix it and how to monitor for it."
url:
https://uptrack.app/http/520
---
# HTTP 520 Web Server Returns Unknown Error
A Cloudflare-specific status code meaning the origin server returned an empty, unknown, or unexpected response that Cloudflare could not process. This is not a standard HTTP status code — it exists only in the Cloudflare ecosystem.
## What does HTTP 520 mean?
A Cloudflare-specific status code meaning the origin server returned an empty, unknown, or unexpected response that Cloudflare could not process. This is not a standard HTTP status code — it exists only in the Cloudflare ecosystem.
## Common causes
1. 1
The origin server returned an empty response (no headers, no body) or closed the connection before sending anything.
2. 2
The origin server returned response headers that exceed Cloudflare's 32KB header size limit, or the headers are malformed.
3. 3
The origin server crashed mid-response, returning a partial or corrupted HTTP response that Cloudflare cannot parse.
## How to fix it
1. 1
Check origin server logs for errors. A 520 is Cloudflare telling you something is wrong on your server — the real error is in your server logs, not Cloudflare's.
2. 2
Reduce response header size. Remove excessively large cookies, debug headers, or unnecessary custom headers that push total header size over 32KB.
3. 3
Ensure your origin server completes responses properly. If the server process is crashing, check for out-of-memory errors or unhandled exceptions.
## Monitor for HTTP 520 errors
If you use Cloudflare, a 520 indicates your origin server is misbehaving. Uptrack detects these Cloudflare-specific errors and alerts you, even though they are not standard HTTP codes.
## Catch HTTP errors before your users do
Start free, or choose a plan, for 30-second monitoring and alert confirmation.
[See plans](
https://uptrack.app/pricing)
from $3/mo · 30-day money-back guarantee
## Other HTTP status codes
- [HTTP 522 Connection Timed Out](
https://uptrack.app/http/522)
- [HTTP 504 Gateway Timeout](
https://uptrack.app/http/504)
- [HTTP 503 Service Unavailable](
https://uptrack.app/http/503)
- [HTTP 502 Bad Gateway](
https://uptrack.app/http/502)
- [HTTP 500 Internal Server Error](
https://uptrack.app/http/500)
- [HTTP 451 Unavailable For Legal Reasons](
https://uptrack.app/http/451)
- [HTTP 429 Too Many Requests](
https://uptrack.app/http/429)
- [HTTP 422 Unprocessable Entity](
https://uptrack.app/http/422)
- [HTTP 415 Unsupported Media Type](
https://uptrack.app/http/415)
- [HTTP 413 Payload Too Large](
https://uptrack.app/http/413)
- [HTTP 410 Gone](
https://uptrack.app/http/410)
- [HTTP 409 Conflict](
https://uptrack.app/http/409)
- [HTTP 408 Request Timeout](
https://uptrack.app/http/408)
- [HTTP 405 Method Not Allowed](
https://uptrack.app/http/405)
- [HTTP 404 Not Found](
https://uptrack.app/http/404)
- [HTTP 403 Forbidden](
https://uptrack.app/http/403)
- [HTTP 401 Unauthorized](
https://uptrack.app/http/401)
- [HTTP 400 Bad Request](
https://uptrack.app/http/400)
- [HTTP 304 Not Modified](
https://uptrack.app/http/304)
- [HTTP 302 Found](
https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](
https://uptrack.app/http/301)
- [HTTP 204 No Content](
https://uptrack.app/http/204)
- [HTTP 201 Created](
https://uptrack.app/http/201)
- [HTTP 200 OK](
https://uptrack.app/http/200)