/ Plain-English guides](https://getfullstacksolutions.com/guides/index.html)/ Error establishing a database connection — how do I fix it? Infrastructure · people search: “Error establishing a database connection — how do I fix it?” # Error establishing a database connection — how do I fix it? This WordPress white screen means the site can't reach its database. The cause is usually small, but the order you fix it in matters. Here's the path. Plain English · no jargon · 4-minute read By Rodrigo Valenzuela Iturrieta](https://getfullstacksolutions.com/about/index.html), the engineer who does the work · Published August 12, 2026 · Updated September 20, 2026 Part of **Servers & Infrastructure](https://getfullstacksolutions.com/services/infrastructure/index.html) — read first, then fix it in 48h. Copy link Print Share Know someone with this exact problem? Pass it on — no email gate. 'Error establishing a database — Where your site stores its content and user data; overloaded or corrupted, it throws errors instead of pages. connection' is WordPress giving up because it can't talk to the database that stores every page, user, and order. You'll see a plain white page with that one line. It can be caused by a bad credential after a move, a database server that's down or out of space, or a database that's been corrupted — and the fix differs for each, so identify before you act. ## Check these first, yourself - Check your host's panel: is the database server marked online, and how much of its disk quota — A cap on the disk, memory or emails your plan allows; hitting it is a common cause of sudden failures. is used? A full disk is a very common cause. - If you recently moved hosts or changed the site URL, suspect the credentials or hostname in the config file (wp-config.php) before anything else. - Don't start deleting plugins or rewriting files while you're guessing — you can turn a recoverable fault into real data loss. - If the database itself is damaged, stop writing to it and take a copy first; every further write reduces what can be recovered. ### When to call a rescue instead of doing it yourself If the database server is up and the credentials are right but the error persists, the database has likely been corrupted — and that calls for careful repair from a snapshot, not trial and error on your live data. A Database Rescue identifies whether it's access, capacity, or corruption, recovers the data, and documents what happened. 48 hours, flat rate, no fix no fee. ### Should you fix it yourself or call a rescue? **Have you tried the free fixes (images, caching, plugins)?If yes and it's still slow → the problem is deeper. **Is your hosting or server the bottleneck?Shared hosting, old PHP, no object cache → server-level problem. **Yes → Speed Rescue Fixed in 48h · from $2,000 ](https://getfullstacksolutions.com/rescue/speed/index.html) **Not sure → Send symptom We'll diagnose for free ](https://getfullstacksolutions.com/contact/index.html) ## Still have questions? Did I lose all my content when this error appeared?Almost never. The data is usually still on disk; the site simply can't open it. In most cases the database is repaired from a snapshot and content comes back intact — which is why stopping writes early matters.Can my host fix it for me?Hosts will confirm the database service is running and may restore a recent snapshot, but they won't repair a corrupted schema or untangle a bad migration. That's the part that needs the rescue. Skip the diagnosis ## Get this fixed in 48 hours, flat rate Same problem, less sleep lost. One of these rescues maps directly to what you're dealing with. performance **Database Performance Rescue $4,500 · 48 hours ](https://getfullstacksolutions.com/rescue/database/index.html) infrastructure **Hosting Consolidation & Cost Cut $2,500 · 48 hours ](https://getfullstacksolutions.com/rescue/hosting/index.html) performance **VPS Optimization & Server Tuning $3,500 · 48 hours ](https://getfullstacksolutions.com/rescue/vps/index.html) infrastructure **Backup System & Restore Test $2,000 · 48 hours ](https://getfullstacksolutions.com/rescue/backup/index.html) Keep reading ## Related plain-English guides More of the questions business owners actually search — same plain-English style, same no-jargon promise. Infrastructure guide **Web Hosting 101: What You're Actually Paying For Shared, managed, VPS and dedicated sound like price tiers. They are really a single trade-off: how much of a server you control, and how alone you are on it. Read the plain-English guide → ](https://getfullstacksolutions.com/guides/web-hosting-101/index.html) Infrastructure guide **Shared Hosting vs VPS: Which Do You Actually Need? Shared hosting is fine until it isn't. Here is how to tell which one your site needs, and the warning signs you have already outgrown the cheap plan. Read the plain-English guide → ](https://getfullstacksolutions.com/guides/shared-hosting-vs-vps/index.html) Infrastructure guide **Host Suspended My Website — Abuse or Resources A suspension notice is your host protecting the shared server. Whether it's malware, a traffic flood, or an honest spike, the recovery order is the same. Read the plain-English guide → ](https://getfullstacksolutions.com/guides/host-suspended-abuse/index.html) ## Don't want to become an expert in this? Send the symptom — get a flat-rate ticket and a plain-English plan within 12 hours. Start the Rescue