Client and server errors, 400 and 500

These are client errors. They are usually the result of you trying to access a page that was deleted, password locked, doesn't exist, or has the wrong link.

Note: Captures may be deleted for violating our terms of service. Please see our Legal information for more details. We may not be able to provide information about the reasons for captures being deleted.

The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).

The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed).

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

These are server errors. They are usually the result of high activity overloading our servers, a bug in our code, or another issue we're facing.

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

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).

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

--

See the full list of HTTP status codes on Wikipedia. You can always contact us if you need help.

Please see this page: Can't connect to server / internet error, 12002, 12007, or 12029