Skip to the content

520 Web Server Returns an Unknown Error

Cloudflare's catch-all: the origin server sent back something empty, unknown or unexpected. Not part of the HTTP standard.

Class
Unofficial codes. Not in the IANA registry. These are made up by one piece of software and mean nothing outside it, but they turn up in logs and on error pages often enough.
Used by
Cloudflare

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When Cloudflare reaches the origin and can't make sense of the reply. Its documentation names the usual causes: the application on the origin crashed, the response came without a status code or a body, or its headers were larger than Cloudflare accepts, which is often down to cookies.

What to do about it

As a visitor: wait and reload. The problem is on the side of the site.

As the owner: look in the error logs of the origin at the time of the error, check that the server or its firewall isn't cutting off Cloudflare's connections, and look at the size of the response headers. A request straight to the origin, around Cloudflare, shows what it really answers.

Not to be confused with

502 Bad GatewayThe standard code for a bad answer from the server behind a proxy.
521 Web Server Is DownThe origin refused the connection.
522 Connection Timed OutThe origin did not respond to the connection attempt in time.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12