Error-Message.Net

Request cannot be fulfilled due to bad syntax

Authentication is possible but has failed

Payment required, reserved for future use

Server refuses to respond to request

Requested resource could not be found

Request method not supported by that resource

Content not acceptable according to the Accept headers

Client must first authenticate itself with the proxy

Server timed out waiting for the request

Request could not be processed because of conflict

Resource is no longer available and will not be available again

Request did not specify the length of its content

Server does not meet request preconditions

Request is larger than the server is willing or able to process

URI provided was too long for the server to process

Server does not support media type

Client has asked for unprovidable portion of the file

Server cannot meet requirements of Expect request-header field

Used by the Laravel Framework when a CSRF Token is missing or expired.

Request unable to be followed due to semantic errors

Resource that is being accessed is locked

Resource that is being accessed is locked

Client should switch to a different protocol

Origin server requires the request to be conditional

User has sent too many requests in a given amount of time

Used by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.

Server is unwilling to process the request

The client's session has expired and must log in again.

Used internally[89] to instruct the server to return no information to the client and close the connection immediately.

The server cannot honour the request because the user has not provided the required information.

The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.

Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users' mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.

Client closed the connection with the load balancer before the idle timeout period elapsed.

The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.

Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.

Client sent too large request or too long header line.

An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.

An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.

An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.

Used when the client has closed the request before the server could send a response.

Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.

Generic error message

Server does not recognise method or lacks ability to fulfill

Server received an invalid response from upstream server

Server is currently unavailable

Gateway did not receive response from upstream server

Server does not support the HTTP protocol version

Content negotiation for the request results in a circular reference

Server is unable to store the representation

Server detected an infinite loop while processing the request

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.

Further extensions to the request are required

Client needs to authenticate to gain network access

The origin web server returned an empty, unknown, or unexpected response to Cloudflare.

The server is powered off. Perhaps in the middle of rebooting.

Due to the high usage of Cloudflare, the 522 connection timed out error is one of the most common browser error messages

The server has an issue and has become unreachable.

The server is not responding. It probably needs rebooting.

The SSL/TLS handshake between Cloudflare and the origin web server failed.

Used by Cloudflare and Cloud Foundry's gorouter to indicate failure to validate the SSL/TLS certificate that the origin server presented.

Used by Qualys in the SSLLabs server testing API to signal that the site can't process the request.

Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity.

Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.

DNS points to prohibited IP

DNS resolution error

DNS points to Prohibited IP

Restricted

Access Denied: Direct IP Access Not Allowed

Host Not Configured to Serve Web Traffic

Access Denied: Your IP address has been banned

The owner of this website has banned your access based on your browser's signature

Access Denied (Hotlinking Denied)

Access Denied

HTTP hostname and TLS SNI hostname mismatch

CNAME Cross-User Banned

You are being rate limited

Origin DNS error

Could not find host

Compute server error

Access denied

Please check back later

Rendering error

Rendering error

Cache connection limit