-as of [17 APRIL 2024]–
.
5xx
server errors
The server failed to fulfil a request
Response status codes beginning with the digit “5” indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request.
Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition.
Likewise, user agents should display any included entity to the user.
These response codes are applicable to any request method
.
500
Internal Server Error
A generic error message,
given when an unexpected condition was encountered and no more specific message is suitable
.
501
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
Usually this implies future availability
(e.g., a new feature of a web-service API)
.
502
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server
.
503
Service Unavailable
The server cannot handle the request
(because it is overloaded or down for maintenance).
Generally, this is a temporary state
.
504
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server
.
505
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request
.
506
Variant Also Negotiates
(RFC 2295)
Transparent content negotiation for the request results in a circular reference
.
507
Insufficient Storage
(WebDAV; RFC 4918)
The server is unable to store the representation needed to complete the request
.
508
Loop Detected
(WebDAV; RFC 5842)
The server detected an infinite loop while processing the request
(sent instead of ‘208 Already Reported’)
.
510
Not Extended
(RFC 2774)
Further extensions to the request are required for the server to fulfil it
.
511
Network Authentication Required
(RFC 6585)
The client needs to authenticate to gain network access.
Intended for use by intercepting proxies used to control access to the network
(e.g., “captive portals” used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot)
.
.
.
*UNOFFICIAL CODES* –>
509
Bandwidth Limit Exceeded
(Apache Web Server/cPanel)
The server has exceeded the bandwidth specified by the server administrator;
this is often used by shared hosting providers to limit the bandwidth of customers
.
529
Site is overloaded
Used by Qualys in the SSLLabs server testing API to signal that the site can’t process the request
.
530
Site is frozen
Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity
.
598
(Informal convention)
Network read timeout error
Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy
.
Cloudflare
Cloudflare’s reverse proxy service expands the 5xx series of errors space to signal issues with the origin server
.
520
Web Server Returned an Unknown Error
The origin server returned an empty, unknown, or unexplained response to Cloudflare
.
521
Web Server Is Down
Error 521 occurs when the origin web server refuses connections from Cloudflare.
Security solutions at your origin may block legitimate connections from certain Cloudflare IP addresses
.
522
Connection Timed Out
Error 522 occurs when Cloudflare times out contacting the origin web server
.
523
Origin Is Unreachable
Cloudflare could not reach the origin server;
for example, if the DNS records for the origin server are incorrect
.
524
A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response
.
525
SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server
.
526
Invalid SSL Certificate
Cloudflare could not validate the SSL certificate on the origin web server.
Also used by Cloud Foundry’s gorouter
.
527
Railgun Error
Error 527 indicates an interrupted connection between Cloudflare and the origin server’s Railgun server
.
530
‘Error 530’ is returned along with a 1xxx error
.
.
561
Unauthorized
An error around authentication returned by a server registered with a load balancer.
You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user
.
.
*👨🔬🕵️♀️🙇♀️*SKETCHES*🙇♂️👩🔬🕵️♂️*
.
.
.
.
💕💝💖💓🖤💙🖤💙🖤💙🖤❤️💚💛🧡❣️💞💔💘❣️🧡💛💚❤️🖤💜🖤💙🖤💙🖤💗💖💝💘
.
.
🔥🔥🔥🔥🔥🔥*we won the war* 🔥🔥🔥🔥🔥🔥