A 500 error means the server received the request, tried to produce the page, and failed. Unlike a missing page, it is always a fault on your side, and the visitor sees a blank error where your website should be. Five causes account for nearly all of them, and the server error log names the cause directly.
What the common codes actually mean
| Code | Meaning | Whose problem |
|---|---|---|
| 404 | The page does not exist at that address | Usually a link or a moved page. Not an outage |
| 500 | The server tried to build the page and failed | Always yours. Something is broken |
| 502 and 504 | One server waited on another and got nothing | Usually the host or an upstream service |
| 503 | The service is unavailable, often deliberately | Maintenance mode, or the server is overloaded |
| 403 | Access refused | A permissions or security rule, often overly broad |
The distinction that matters most is between 404 and 500. A 404 is a routine part of the web and is handled by having a useful 404 page. A 500 means your site is not working.
The five usual causes
An update went wrong
The most common by a distance. A plugin, theme, or platform update conflicts with something and the site stops building pages. It is also why updates belong on a staging copy first rather than on the live site.
A code or configuration edit
A single character wrong in a configuration file will produce a 500 across the entire site instantly. If the error began the moment someone edited something, that is the cause.
Resource limits reached
The account exceeded its memory or process allocation, so requests fail. This produces intermittent errors that cluster at busy times, and it is a sign the site has outgrown its plan.
A database that is not responding
The site cannot retrieve content, so it cannot build the page. Usually the database service, sometimes credentials changed during a move.
File permissions
Files uploaded or restored with the wrong permissions become unreadable by the server. Common after a migration or a manual restore.
Where the answer actually is
The server error log, which records the specific failure with a file name and a line number. It is available in the hosting control panel and it turns guesswork into a named cause in about a minute.
The browser deliberately shows a generic message, because the detail could reveal information about the server. So the page tells the visitor nothing and the log tells you everything, and going to the log first is the difference between fixing it and theorising about it.
What to do, in order
- Check whether it is every page or one page. Site-wide points at configuration or resources. A single page points at that page's content or code.
- Ask what changed. An update, an edit, a plugin installed, a migration. The answer is nearly always something that happened in the last day.
- Read the error log, which usually names the file responsible.
- Reverse the most recent change if the log points at it. Restoring one plugin to its previous version is faster than a full restore.
- Restore from backup if the cause is not obvious and the site is down. Diagnosing can happen afterwards on a copy rather than in public.
Who fixes it
It depends on which layer failed, and the log usually makes that clear.
Errors caused by your site's own code, plugins, or configuration are yours or your developer's. Errors caused by the server itself, the database service, or resource limits are the host's, and a host with real support will investigate rather than pointing back at you.
A 502 or 504 is almost always upstream and worth raising with the host immediately rather than investigating your own site.
What prevents most of them
Updates applied to a staging copy first, backups that can actually be restored quickly, monitoring that tells you before a customer does, and enough headroom that busy periods do not exhaust the account.
None of that is exotic. It is the ordinary difference between hosting where you find out from a customer and hosting where somebody is already working on it, which is what monitoring and response actually buys.
Frequently asked questions
What does a 500 internal server error mean?
The server received the request, tried to build the page, and failed. Unlike a missing page it is always a fault on your side, and the visitor sees an error instead of your site.
What is the difference between a 404 and a 500?
A 404 means the page does not exist at that address, which is routine. A 500 means something is broken and the site cannot produce the page at all.
What usually causes a 500 error?
An update that went wrong, a code or configuration edit, hitting resource limits, a database not responding, or incorrect file permissions after a migration or restore.
Where do I find out what caused it?
The server error log in your hosting control panel, which names the file and line responsible. The browser shows a generic message deliberately, so the log is the only place with the detail.
Is a 502 or 504 error my fault?
Usually not. Those mean one server waited on another and received nothing, which normally points at the host or an upstream service and is worth raising with them immediately.
How do I prevent server errors?
Apply updates on a staging copy first, keep backups you can restore quickly, monitor so you learn before a customer does, and keep enough headroom that busy periods do not exhaust the account.
West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.
Site showing an error and nobody can say why?
We read the log, name the cause, and fix it, then put staging and monitoring in place so the next update does not take the site down.
Start a Conversation