HTTP 500 Internal Server Error

What does HTTP 500 mean?

The server hit an unexpected condition and could not complete the request. The generic “something broke” error. It is never the client’s fault; the details are in the server’s error log, not in the response.

5xx Server error: The request looked valid, but the server failed to fulfil it. The fix is on the server side.

Common causes of a 500 error

• An unhandled exception in application code.
• Syntax error in .htaccess or a misconfigured server module.
• Database connection failures.
• Wrong file permissions on scripts (e.g. PHP files with execute-only or overly open permissions under suEXEC).

How to fix 500 Internal Server Error

• Check the application and web server error logs.
• Roll back the latest deployment or configuration change.
• Validate .htaccess and server configs after editing.

500 and SEO

Short outages are tolerated, but persistent 500s cause Google to crawl less and eventually drop the pages. Monitor for them.

Example response

HTTP/1.1 500 Internal Server Error

Related status codes

• 502 Bad Gateway — A gateway or proxy got an invalid response from the upstream server.
• 503 Service Unavailable — The server is temporarily unable to handle the request.
• 504 Gateway Timeout — A gateway or proxy did not get a response from the upstream server in time.
• 501 Not Implemented — The server does not support the functionality required to fulfil the request.

Check which status code a URL returns with the HTTP header checker.