HOSTING101 / HTTP ERRORS

HTTP Errors

Understand what the browser or server is telling you, then try the fastest safe checks.

400 RESPONSE
https://example.com/request
400
Bad Request

Check the URL, request headers, cookies, and malformed form data.

Bad Request

Try a private window; clear site cookies; verify the request URL and form fields.

4xx • Request response
401 RESPONSE
https://example.com/request
401
Unauthorized

The resource requires valid authentication.

Unauthorized

Sign in again; verify username/password or API credentials; check authentication rules.

4xx • Request response
403 RESPONSE
https://example.com/request
403
Forbidden

The server understood the request but access is denied.

Forbidden

Check file/folder permissions, ownership, `.htaccess` rules, IP blocks, and index file.

4xx • Request response
404 RESPONSE
https://example.com/request
404
Not Found

The requested page or file cannot be found at that path.

Not Found

Check spelling and URL; confirm the file exists in the correct document root; review redirects and WordPress permalinks.

4xx • Request response
405 RESPONSE
https://example.com/request
405
Method Not Allowed

The URL does not allow the HTTP method used by the request.

Method Not Allowed

Check the form/API method and application routing; review server rules.

4xx • Request response
408 RESPONSE
https://example.com/request
408
Request Timeout

The server did not receive the complete request in time.

Request Timeout

Retry; check connection stability, proxy behavior, and server load.

4xx • Request response
413 RESPONSE
https://example.com/request
413
Content Too Large

The request body or upload exceeds a configured limit.

Content Too Large

Reduce file size; check PHP `upload_max_filesize` and `post_max_size` or platform limits.

4xx • Request response
429 RESPONSE
https://example.com/request
429
Too Many Requests

A rate limit or security rule is throttling requests.

Too Many Requests

Wait before retrying; review API limits, bot protection, and request frequency.

4xx • Request response
500 RESPONSE
https://example.com/request
500
Internal Server Error

A generic server-side failure occurred.

Internal Server Error

Check hosting error logs and PHP logs; inspect recent `.htaccess`, PHP, plugin, or theme changes.

5xx • Server response
501 RESPONSE
https://example.com/request
501
Not Implemented

The server does not support the requested functionality or method.

Not Implemented

Check the application/server feature and supported request method; escalate platform-level gaps.

5xx • Server response
502 RESPONSE
https://example.com/request
502
Bad Gateway

A gateway or proxy received an invalid response from an upstream service.

Bad Gateway

Check upstream/PHP-FPM or app service health, recent deploys, and proxy configuration.

5xx • Server response
503 RESPONSE
https://example.com/request
503
Service Unavailable

The service is temporarily unavailable, overloaded, or in maintenance.

Service Unavailable

Check hosting status, resource limits, maintenance mode, and service health.

5xx • Server response
504 RESPONSE
https://example.com/request
504
Gateway Timeout

A gateway did not receive a timely response from an upstream service.

Gateway Timeout

Investigate slow scripts, database queries, upstream health, and timeout settings.

5xx • Server response
505 RESPONSE
https://example.com/request
505
HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

HTTP Version Not Supported

Check client/proxy protocol settings and server support; confirm whether a proxy is sending an unsupported version.

5xx • Server response
These are recreated visual examples of typical browser/server error pages, not screenshots from a live GoDaddy customer account. A 4xx code generally points to a request/client-side issue; a 5xx code indicates a server-side failure, but always inspect the actual logs and response.
← Back to dashboardEscalation guide →