{"id":15081,"date":"2026-11-09T11:43:35","date_gmt":"2026-11-09T11:43:35","guid":{"rendered":"https:\/\/logicalzone.com\/blog\/?p=15081"},"modified":"2026-11-09T12:35:19","modified_gmt":"2026-11-09T12:35:19","slug":"error-establishing-a-database-connection","status":"publish","type":"post","link":"https:\/\/logicalzone.com\/blog\/error-establishing-a-database-connection\/","title":{"rendered":"How to Fix \u201cError Establishing a Database Connection\u201d in WordPress"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"WordPress\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

You type in your own web address, and instead of your homepage you get a plain white screen with one line: error establishing a database connection<\/b>. No menu, no posts, no login page. Just that message.<\/p>\n

I have seen this on client sites at the worst possible moments, including the morning of a product launch. The good news is that it looks scarier than it is. Most of the time you can fix it in under 30 minutes without writing any code.<\/p>\n

What Does This Error Actually Mean?<\/h2>\n

WordPress stores your posts, pages, settings and users in a database. Every time someone visits, WordPress asks that database for the content. If the question gets no answer, you see this error instead of your site.<\/p>\n

So the message is not about your theme or your plugins. It means WordPress and the database cannot talk to each other. That is a useful clue, because it narrows the search a lot.<\/p>\n

The Most Common Causes<\/h3>\n
    \n
  1. Wrong database credentials<\/strong> after a migration, a host change or a password reset.<\/li>\n
  2. A MySQL server that is down or overloaded<\/strong>, often on cheap shared hosting during traffic spikes.<\/li>\n
  3. A corrupted database<\/strong>, usually after a failed update or a crashed plugin.<\/li>\n
  4. Damaged WordPress core files<\/strong> from an interrupted update.<\/li>\n
  5. A hacked site<\/strong>, which is actually the rarest cause on this list.<\/li>\n<\/ol>\n

    Many guides jump straight to \u201cyou were hacked.\u201d In my experience that is the exception. Check the boring causes first. The fix is usually a typo or a hosting hiccup.<\/p>\n

    Before You Start: Take a Quick Backup<\/h2>\n

    If you can still reach your hosting control panel, download a copy of your files and database first. Most hosts offer a one-click backup tool. If you edit something and make things worse, you will be glad you have a copy.<\/p>\n

    You will also need file access, either through your host’s File Manager or an FTP client like FileZilla.<\/p>\n

    Step 1: Check Whether the Admin Area Shows the Same Error<\/h2>\n

    Visit yoursite.com\/wp-admin<\/em>. What you see tells you where to look next.<\/p>\n

      \n
    1. Same error message:<\/strong> your credentials or your MySQL server are the likely problem. Go to Step 2.<\/li>\n
    2. \u201cOne or more database tables are unavailable\u201d:<\/strong> WordPress is telling you the database needs repair. Skip to Step 5.<\/li>\n<\/ol>\n

      This ten-second check is the triage step. It saves a lot of guessing.<\/p>\n

      Step 2: Check Your Database Credentials in wp-config.php<\/h2>\n

      This is the cause behind most cases I have fixed. Your site reads its login details for the database from a file called wp-config.php<\/strong>, which sits in the root folder of your WordPress install.<\/p>\n

      Open it in your File Manager and look for these four lines:<\/p>\n

      define( 'DB_NAME', 'your_database_name' );\ndefine( 'DB_USER', 'your_database_user' );\ndefine( 'DB_PASSWORD', 'your_password' );\ndefine( 'DB_HOST', 'localhost' );<\/code><\/pre>\n
      Compare them with your hosting account. Open the MySQL databases section and confirm the database name, the username, and that the user is actually assigned to that database. A lot of people skip that last check.<\/p>\n
      These four values are your database credentials<\/strong>. One wrong character, even a trailing space, breaks the connection. If you are unsure about the password, reset it in your hosting panel and paste the new one into the file. The official WordPress documentation on editing wp-config.php<\/a> explains each setting.<\/p>\n
      A Real Example<\/h3>\n
      One small business owner I helped had changed her hosting password and her database password in the same session. She updated her login but never touched the config file. Her site had been down for two days. Fixing one line brought it back in a minute.<\/p>\n
      Step 3: Check the DB_HOST Value<\/h2>\n
      On most hosts, DB_HOST is localhost<\/em>. Some use a specific server name like mysql.yourhost.com<\/em> or an IP address. If you recently moved hosts, this is a common slip.<\/p>\n
      Look in your hosting dashboard or welcome email for the right value. If it is not localhost, update it in wp-config.php and save.<\/p>\n
      Step 4: Test the Connection Using phpMyAdmin<\/h2>\n
      If your settings look right but the error stays, test the database directly. Log in to your hosting panel and open phpMyAdmin<\/strong>, the free tool most hosts include for managing databases.<\/p>\n
      Select your WordPress database from the left menu. If you see tables like wp_posts<\/em> and wp_options<\/em>, the database exists and holds your data. That means the problem is the connection, not lost content.<\/p>\n
      If phpMyAdmin itself will not load or shows a connection refused message, the issue is on the server side. Skip ahead to Step 6.<\/p>\n
      Step 5: Repair a Corrupted Database<\/h2>\n
      A corrupted database often follows a crash during an update, or a server that ran out of disk space mid-write. You have two safe ways to repair it.<\/p>\n
      Option A: Use the Built-In WordPress Repair Tool<\/h3>\n
      Open wp-config.php again and add this line above the comment that says \u201cThat’s all, stop editing\u201d:<\/p>\n
      define( 'WP_ALLOW_REPAIR', true );<\/code><\/pre>\n
      Then visit yoursite.com\/wp-admin\/maint\/repair.php<\/em> and click \u201cRepair Database.\u201d When it finishes, delete that line right away. The repair page needs no login, so leaving it active is a security risk.<\/p>\n
      Option B: Repair Through phpMyAdmin<\/h3>\n
      Select your database, tick all tables, then choose \u201cRepair table\u201d from the dropdown at the bottom. It takes seconds on a small blog and longer on a large store.<\/p>\n
      If repair fails, do not keep forcing it. Move on to Step 7.<\/p>\n
      Step 6: Check Whether Your MySQL Server Is Down<\/h2>\n
      Sometimes your settings are perfect and the MySQL server<\/strong> simply is not responding. This happens during hosting maintenance, resource overload or plan limits on shared hosting.<\/p>\n
      Here is a quick test. If you run more than one site on the same hosting account, visit the others. If they all show the error, the MySQL server is almost certainly the problem.<\/p>\n
      Contact your host and ask directly: \u201cIs the MySQL server running for my account, and am I hitting any resource limits?\u201d A good host answers within minutes. If you hit this error often, an underpowered plan is probably behind it, and that is a sign to upgrade.<\/p>\n
      Step 7: Replace Core Files or Restore a Backup<\/h2>\n
        \n
      1. Replace core files.<\/strong> Download a fresh copy of WordPress from wordpress.org and upload the wp-admin<\/em> and wp-includes<\/em> folders over your existing ones. Do not overwrite the wp-content folder or your config file.<\/li>\n
      2. Restore a backup.<\/strong> Use your host’s backup tool or a plugin backup to roll back to the last working date.<\/li>\n<\/ol>\n
        Replacing core files is safe because it leaves your content, themes and plugins untouched. It only swaps the engine.<\/p>\n
        How to Stop This Error From Coming Back<\/h2>\n
          \n
        1. Schedule automatic backups<\/strong> and keep a copy off your server. A backup stored only on a failing server is not much of a backup.<\/li>\n
        2. Save a private copy of wp-config.php<\/strong> so you can restore your settings in seconds.<\/li>\n
        3. Update during quiet hours<\/strong> and never close the browser mid-update.<\/li>\n
        4. Delete plugins you do not use.<\/strong> Fewer plugins means fewer database queries and fewer ways to crash.<\/li>\n
        5. Choose a host with solid database resources.<\/strong> Cheap plans are where I see this error most.<\/li>\n<\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t
          Frequently Asked Questions<\/h2>
          1. Will I lose my content if I see the error establishing a database connection message?<\/h3>
          Almost never. The error means WordPress cannot reach the database, not that the data is gone. If you can open your tables in your hosting panel’s database tool, your posts and pages are still there.<\/p>
          2. Why does the WordPress database connection error appear after I change my hosting password?<\/h3>
          Your site uses separate database credentials stored in the config file. Changing your hosting login does not update them. If you also reset the database password, paste the new value into the file.<\/p>
          3. How do I know if my database is corrupted or the server is down?<\/h3>
          Check \/wp-admin. A message about tables needing repair points to a corrupted database. If every site on your account fails and your database tool will not open, the server is the likely cause.<\/p>
          4. Can a plugin cause this error?<\/h3>
          Yes, but indirectly. A badly coded plugin can overload the server or damage tables during an update. If the error started right after installing one, rename that plugin’s folder in your File Manager and test again.<\/p>
          5. How long does it take to fix?<\/h3>
          A wrong password or host value takes minutes. A repair takes a bit longer. If the problem is on your host’s side, you wait for them, usually under an hour.<\/p>
          Final Tips<\/h2>
          Start with the simple checks. Nine times out of ten, the answer is wrong database credentials or a hosting hiccup you did not cause. Change one thing at a time so you know what worked, and write it down.<\/p>
          If you are still stuck, send your host the exact error and what you have already tried. And once your site is back, set up backups today, not next week.\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"
          You type in your own web address, and instead of your homepage you get a plain white screen with one line: error establishing a database connection. No menu, no posts, no login page. Just that message. I have seen this […]<\/p>\n","protected":false},"author":1,"featured_media":15083,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[269],"tags":[],"class_list":["post-15081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-quick-fixes","entry"],"_links":{"self":[{"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/posts\/15081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/comments?post=15081"}],"version-history":[{"count":10,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/posts\/15081\/revisions"}],"predecessor-version":[{"id":15093,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/posts\/15081\/revisions\/15093"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/media\/15083"}],"wp:attachment":[{"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/media?parent=15081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/categories?post=15081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/logicalzone.com\/blog\/wp-json\/wp\/v2\/tags?post=15081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}