Common Web Hosting Errors

By Marcus Feld, Infrastructure Editor

Every website eventually throws an error. The useful skill isn’t memorising every possible message — it’s recognising which family an error belongs to, because that family tells you where to look first. This page is the index: it groups the errors visitors and site owners hit most often, explains what each one actually means, and links to a dedicated, step-by-step fix guide for each.

What Web Hosting Errors Actually Mean

An error message is the internet’s way of telling you which layer of the request failed. A request to load a page passes through several layers in order: your browser and local network, DNS (translating the domain to an IP address), the web server that receives the request, and — for dynamic sites — the application and database behind it. Where the chain breaks determines the error you see.

5xx Codes (500, 502, 503, 504)

5xx codes mean the request reached a server, but that server failed, refused, or timed out while trying to respond. The fault is server-side.

DNS and Connection Errors

DNS and connection errors, such as “this site can’t be reached,” mean the request never got a server to respond at all. This is usually a domain, DNS, or network problem.

Database Connection Errors

Database connection errors are a specific 500-family failure where the web server works but the application can’t reach its database.

Mail Delivery Errors

Mail delivery errors are a separate failure path. Hosting email uses different servers and protocols (SMTP/IMAP) than the website itself, so a working website doesn’t guarantee working email.

Why Is My Site Slow

“Why is my site slow” isn’t a hard error at all, but the diagnostic process is the same discipline: identify which layer is adding the delay.

Common Web Hosting Errors, Ranked by How Often They Occur

Error	What it usually means	Typical cause
500 Internal Server Error	Generic server-side failure	Corrupt .htaccess, plugin/theme conflict, wrong file permissions, PHP memory limit
502 Bad Gateway	Upstream server sent an invalid response	Crashed PHP-FPM process, overloaded backend, misconfigured reverse proxy
503 Service Unavailable	Server temporarily can’t handle the request	Resource limits hit, maintenance mode, traffic spike
504 Gateway Timeout	Upstream server took too long to respond	Slow database query, script timeout, overloaded server
“Site can’t be reached”	Browser can’t resolve or connect to the domain	DNS misconfiguration, expired domain, server down, local network issue
Error establishing a database connection	App server is up but can’t reach the database	Wrong credentials, corrupted database, database server down
Hosting email not working	Mail send/receive failure	Wrong MX/SMTP settings, blacklisted IP, mailbox full
Website slow, not down	Not an error — a performance symptom	Unoptimised database, no caching, undersized plan, distant server location

Step-by-Step: General Triage for Any Hosting Error

Before jumping to a specific error’s guide, run this sequence — it resolves or narrows down the majority of hosting errors in under ten minutes.

1. Read the exact error text and code. “500,” “502,” “503,” “504,” and “can’t be reached” all point to different layers. Don’t guess — the code is the diagnosis.
2. Reload and check from a second network. Rules out a local ISP or Wi-Fi problem in seconds. Use a phone on mobile data.
3. Check your host’s status page. A known outage affecting your server or data centre explains the error immediately and means no local fix is needed.
4. Check what changed recently. A new plugin, theme, code deploy, or DNS edit is the cause far more often than a random server fault.
5. Check server resource usage in your hosting control panel (CPU, RAM, database connections). A resource ceiling explains 503s and slowness together.
6. Check the server error log, not just the browser message — cPanel, Plesk, or your host’s dashboard exposes the real underlying PHP or application error.
7. Roll back the most recent change (plugin, theme, code, config) if the timing lines up, then re-test.
8. Escalate to hosting support with the exact error, timestamp, and steps already tried once you’ve confirmed the fault is server-side.

Why Some Hosting Types See More Errors Than Others

The hosting type behind a site shapes which errors show up most. On shared hosting, resource ceilings are shared across many accounts on the same server. So 503 errors and slowness from a “noisy neighbour” — another site on the same server consuming heavy resources — are the most common complaint. On VPS and dedicated servers, you control the configuration directly. There, 500 and 502 errors more often trace back to a misconfigured PHP-FPM process, a bad reverse-proxy setting, or a resource limit you set yourself rather than one imposed by the host. Managed WordPress hosting tends to suppress most of these entirely through automated caching, staging, and pre-vetted plugin environments, at the cost of less low-level control when something unusual does go wrong. Understanding this pattern helps set realistic expectations before you commit to a plan. It’s one more reason hosting type should be decided before price.

Reading a Hosting Error Log, Not Just the Error Page

The message a visitor sees is deliberately generic — it’s a courtesy, not a diagnosis. The real information lives in your hosting control panel’s error log (cPanel’s “Errors” tool, Plesk’s “Logs” section, or your platform’s equivalent). A log entry typically names the exact file, line number, and type of failure: a PHP fatal error, a database timeout, or a permission denial. This turns a guessing exercise into a direct fix. Get in the habit of checking the log first, before trying fixes at random. It consistently cuts troubleshooting time from an hour of trial and error down to a few minutes of reading.

How to Prevent Hosting Errors

• Keep plugins, themes, and core software updated in small batches, not all at once, so a single bad update is easy to isolate.
• Monitor uptime with a third-party checker so you learn about downtime from an alert, not a customer complaint — see our uptime & SLA guide for what to expect from a host’s reliability guarantee.
• Keep a recent backup and a staging environment so a rollback is fast, not a re-build.
• Choose a plan with resource headroom for your real traffic, not just your launch-day traffic — undersizing is the single biggest driver of recurring 503/504 errors.
• Review your hosting comparison against your growth trajectory yearly, not just at signup.

When to Contact Your Host vs. Fix It Yourself

Fix it yourself when the error started right after a code, plugin, theme, or DNS change you made — that’s a configuration problem, not an infrastructure one. Contact your host when the error is intermittent with no code changes, the host’s own status page shows a problem, resource limits are being hit on a plan that should have headroom for your traffic, or server logs point to a hardware, network, or platform-level fault outside your application. A host worth keeping will confirm within minutes whether the fault is on their side. A track record of that responsiveness is itself a criterion when choosing a reliable host.

FAQ

What’s the difference between a 502 and a 504 error? A 502 means the upstream server sent back an invalid or garbled response. A 504 means the upstream server didn’t respond at all within the allowed time. Both point to a problem behind your web server, but 504 specifically points to a timeout.

Does a hosting error always mean my host is at fault? No. Plugin conflicts, bad code deploys, and misconfigured DNS are host-independent causes and are actually more common than genuine infrastructure faults.

Why does my site show an error for some visitors but not others? This usually points to caching (some visitors get a cached good copy), DNS propagation still in progress, or a CDN edge node in one region having an issue while others are fine.

Is there one page that lists every hosting-related status code? Yes — see the HTTP status codes cheat sheet for the full reference beyond just the errors covered here.

Should I panic if my site shows a 500 error? No. 500 errors are almost always resolved within minutes by identifying the recently changed plugin, theme, or file permission — see the 500 Internal Server Error guide for the exact sequence.