Common HTTP Error Messages

The web server uses HTTP error messages to inform you when an error has occurred.

Here you will find explanations of the most common HTTP error messages.

• 400 - Bad request: An incorrect syntax or an unknown character in the request causes the error message. We recommend that you check your Internet connection and update your browser if necessary.
• 401 - Unauthorized: User authentication failed. This occurs in connection with password-protected directories. Please check the validity of your user data.
• 403 - Forbidden: The request was not executed due to lack of client authorization. This can have several reasons:
  1. Check whether the called page has the necessary read rights (files: 644, directories: 755).
  2. The error may also mean that no start page could be found. In this case, make sure that the start page has a valid name and has been uploaded to the correct directory.
  3. Check if directory listing is enabled.
• 404 - Not Found: The document was either removed, moved or renamed and therefore cannot be found. Check and correct the link specified in the document in the HTML/PHP text.
• 410 - Gone: No website can be reached under the specified URL. Furthermore, no forwarding address is known.
• 500 - Internal Server Error: You receive this message if the server could not execute an action (delivery of an HTML page, execution of a script) because it caused an internal error. Since this error message is very general, there can be many reasons: a faulty script, a software error on the web server or even reaching server limits (script runtime, memory usage, etc.).
• 501 - Not Implemented: The required functionality or prerequisite for the server does not exist.
• 502 - Bad Gateway: An invalid response from another server in gateway or proxy mode.
• 503 - Service unavailable: The server is either overloaded, down or under maintenance.