A 500 Internal Server Error is one of the most common "it just broke" moments for webmasters, and also one of the most generic — the server knows something failed but isn't telling you what. Here's where to actually look.
Check your error logs first – PHP error logs, server logs (Apache/Nginx), and application-level logs almost always contain the real cause, even when the browser just shows a blank 500 page.
Recently installed a plugin or update? – This is the single most common cause. Disable the most recent change and see if the error clears.
Check PHP memory limits and execution timeouts – Scripts that run out of memory or time often throw a generic 500 instead of a clear error.
File permissions – Incorrect permissions on files/folders (especially after a migration) are a frequent and easy-to-miss cause.
Database connection issues – Wrong credentials, exhausted connection limits, or a crashed database service will often surface as a 500 on the frontend.
What's the weirdest cause of a 500 error you've ever tracked down?
Last edited: