emilyscoolnews.urbanvellum.com
←Back

How to Confirm Your Database Name Is Correct in cPanel

If a WordPress site suddenly shows “Error establishing a database connection,” a wrong database name is one possible cause—but it is not the only one. A database may exist and still be inaccessible because the database username, password, permissions, or server hostname is wrong. The hosting account may also be having an outage.

This guide shows you how to check the database name in cPanel and compare it with WordPress’s wp-config.php file. It starts with quick, reversible checks and explains what to record before making changes. You do not Additional reading need to install a plugin or modify the database to verify the name.

Start with Fast, Reversible Outage Checks

Before changing files or resetting passwords, check whether the problem is temporary. A recent outage, maintenance window, or server overload can produce the same WordPress error as incorrect credentials.

  1. Record the exact error and time. Copy the message shown in the browser and note when it first appeared, including your time zone. If the error changes, record the new wording and time too.
  2. Check more than one page. Try the homepage and a few other pages. If only one page fails, the issue may not be a site-wide database connection problem.
  3. Check your hosting provider’s status page. Look for database, server, or account incidents affecting your hosting platform or region.
  4. Try the site again after a short wait. If it recovers without a configuration change, avoid making edits that could introduce a new problem.
  5. Open cPanel in a separate tab. If cPanel is also slow or unavailable, note that. It may indicate an account or server issue, though cPanel availability alone does not prove that the database server is healthy.

Do not repeatedly edit wp-config.php while troubleshooting. First gather evidence and make sure you can restore the file. Changing the database name, username, and password all at once makes it harder to identify the actual cause.

Back Up Before Editing Anything

Merely viewing cPanel and wp-config.php is safe. If you plan to change the configuration, create a restorable copy first. Use cPanel’s File Manager or your usual secure file-transfer method to download wp-config.php to a private location. If you are making broader site changes, take a complete file and database backup using your host’s established backup tools.

Keep backup files private. wp-config.php contains sensitive credentials, so do not email it, post it in a public support forum, or paste its contents into a chat. If someone needs help, share only the specific values or error text required, with passwords and other secrets removed.

Find the Database List in cPanel

cPanel layouts differ between hosting companies and versions, but the database tools are commonly grouped under Databases. Look for an item named MySQL Databases, Manage My Databases, or, on some accounts, MySQL Database Wizard.

  1. Sign in to your hosting account and open cPanel.
  2. Open MySQL Databases or the equivalent database-management page.
  3. Find the section listing current databases. This is the database list for your cPanel account.
  4. Compare the complete database name shown there with the value in WordPress’s wp-config.php.

Watch for the account prefix. Shared hosting providers often attach a prefix to every database name. For example, cPanel may list acme_sitewp, even if you originally chose sitewp in a setup wizard. WordPress must use the exact full name that cPanel recognizes, including the prefix, spelling, and underscores.

Do not assume a database name from an old invoice, setup email, or migration note is still current. Databases may be renamed, recreated, or moved during a site migration. Use the current cPanel database list and, if available, your host’s account records to confirm what exists now.

Check the WordPress Database Name in wp-config.php

The file wp-config.php is usually in the WordPress installation’s main directory—the directory containing folders such as wp-admin, wp-content, and wp-includes. In cPanel File Manager, you may need to open the document root for the domain, such as public_html, or a separate folder used by that site.

In wp-config.php, look for the database settings. They typically look like this:

define( 'DB_NAME', 'acme_sitewp' ); define( 'DB_USER', 'acme_wpuser' ); define( 'DB_PASSWORD', 'replace-with-the-actual-password' ); define( 'DB_HOST', 'localhost' );

The DB_NAME value is the one to compare with the cPanel database list. A wp-config.php match means the full value between the quotes is identical to the database name shown in cPanel. For example, acme_sitewp does not match sitewp, and a small spelling difference can be enough to prevent a connection.

When viewing the file, do not share the password. If you use cPanel’s File Manager editor, avoid saving the file unless you intend to make a change. A read-only comparison is the fastest and safest first check.

Check All Database Credentials, Not Just the Name

A correct database name does not guarantee that WordPress can connect. Compare the other settings with the values available in cPanel or in your hosting account’s setup information.

Setting What to verify Common issue DB_NAME Exact full database name in the cPanel database list Missing account prefix or a typo DB_USER Exact database user assigned to the site Using the cPanel login name instead of the database user DB_PASSWORD Current password for that database user Password changed in one place but not the other DB_HOST Hostname specified by your host Assuming localhost when the account uses a different host

In cPanel, check which database users are assigned to the database and whether they have the required privileges. Some interfaces show this under Current Databases, Manage Database Users, or a similarly named section. The user listed in DB_USER needs to be associated with the correct database and have the privileges WordPress requires.

Do not reset a password just to test whether it might be wrong. First confirm which user WordPress is supposed to use. If you must change the password, make sure you have access to update wp-config.php at the same time; otherwise, the site can remain offline with mismatched credentials.

Safe Steps If the Database Name Does Not Match

If the database exists in cPanel but the name in wp-config.php is different, pause before editing. Confirm that you have identified the correct WordPress installation and the database intended for that site. An account can contain multiple databases, especially when it hosts more than one website or an old copy of a site.

  1. Save a private copy of the current wp-config.php.
  2. Confirm the correct database name and user from cPanel or reliable hosting records.
  3. Change only the incorrect setting, if you are certain of the correct value.
  4. Save the file and load the site again, noting the exact time and result.
  5. If the site does not improve, restore the saved file or undo only the change you made.

What changed: Record the setting you edited, the previous value, the new value, and the time of the change. Do not record or share the database password in an unsecured scratchpad.

How to roll back: Restore the private backup of wp-config.php, or put back the original value. If you changed a password or database-user assignment in cPanel, restore the corresponding prior setting only if you know it; best hosting for wordpress stability otherwise, stop and ask the host to confirm the correct credentials before making another change.

Never delete or recreate a database just because its name looks unfamiliar. It may contain the live site’s content, users, orders, or settings. A database name mismatch is a configuration problem to investigate, not a reason to remove data.

Check Hosting and Server Health

If the database name, user, password, and host appear correct, consider whether the database service or hosting account is healthy. A database server can be temporarily unavailable even when your WordPress configuration has not changed.

  • Review the host’s status page or account notifications for database maintenance or service incidents.
  • Check cPanel for account notices, resource-limit messages, or database-management errors.
  • Look for recent changes: a site move, password reset, restore, domain migration, or hosting-plan change.
  • Check the relevant hosting error logs if you know how to access them. Record the exact message and timestamp rather than guessing at its meaning.

Do not restart services or edit server-level configuration from a shared hosting account unless your host specifically instructs you to do so. Likewise, avoid installing troubleshooting plugins during an outage: they cannot fix a server-side database outage and may add extra changes to an already unstable site.

When to Ask Your Hosting Provider for a Specific Check

If cPanel confirms the database name and the configuration appears correct, give your host a concise, useful report. This is more effective than a general message such as “my site is broken.” Use the support channel provided by your host and do not include passwords.

  • “WordPress has shown ‘Error establishing a database connection’ since [date, time, time zone].”
  • “I confirmed that the DB_NAME value matches the full database name shown in cPanel.”
  • “Please confirm that the database is online, that this database user is assigned with the required privileges, and that the DB_HOST value is correct for my account.”
  • “Please check whether the account or database server has resource limits, an outage, or a recent configuration change.”

That script gives support a clear place to start without disclosing credentials. If you have changed a setting, tell them exactly what changed and when, and whether you rolled it back.

Quick Verification Checklist

  • The exact error and first-seen timestamp are recorded.
  • The current database appears in the cPanel database list.
  • DB_NAME in wp-config.php matches the full cPanel name, including its prefix.
  • DB_USER is the database user assigned to that database.
  • The user’s password and privileges are confirmed without sharing the password publicly.
  • DB_HOST matches the value specified by the hosting provider.
  • A backup exists before any configuration change, and the change and rollback plan are recorded.

In short, confirming your database name means comparing the complete DB_NAME value in the correct WordPress installation with the database list in cPanel. If they match, move on to the username, password, privileges, host value, and server health. Work one step at a time, keep a record of what changed, and preserve a clear route back to the original configuration.