Skip to the content

500 Internal Server Error

Something went wrong on the server, and it has no more specific code to give. Nearly always an error in the site's own software.

Class
5xx Server error. The request may have been fine, but the server failed to fulfil it.
Defined in
RFC 9110

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the application fails in a way nobody planned for: an exception that isn't caught, a database that can't be reached, a syntax error in a configuration file, a script that produces no valid output. The response says little on purpose, so as not to show strangers how the site works inside.

What to do about it

As a visitor: reload once, and try again later. Nothing on your side causes it.

As the owner: the cause is in the logs, not in the response. Look in the error log of the web server and of the application at the time of the request. On PHP sites the usual suspects are a faulty .htaccess file, a plugin that was just updated and a memory limit that was reached.

Don't answer 500 for mistakes of the client. Those are 4xx.

Not to be confused with

502 Bad GatewayThe error came from a server behind a proxy, or the proxy got no usable answer.
503 Service UnavailableThe server is deliberately not taking requests for now.
400 Bad RequestThe request is at fault, not the server.

How Google treats it

Google slows down its crawling when a site returns server errors, and removes pages that keep returning them from its index.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12