Error establishing a database connection: how to fix the WordPress database error

Is there a hosting problem? Check the status page and panel

When error establishing a database connection appears, check the host’s status page and panel announcements before touching configuration; for scheduled maintenance or a database server outage, wait and open a support ticket. If other sites in the same hosting account have the same error, the problem is on the server rather than in one site’s settings.

Checks you can perform in a few minutes in the panel:

• Any active outage or maintenance announcement on the status page or panel
• Whether a database tool such as phpMyAdmin opens and lists tables
• Disk and database quota usage
• CPU, memory, or concurrent process limits being reached in resource usage charts

If phpMyAdmin opens and lists tables, the database server is running; attention shifts to credentials. For sites frequently hitting resource limits, server choice’s effect on speed and search visibility is separately explained in the web hosting selection guide.

How do you check wp-config database settings?

Check wp-config database settings by comparing four values in the site’s root wp-config.php character by character with database details in the hosting panel. Access the file through the panel file manager or FTP; WordPress documentation also recommends opening it through FTP and verifying these details as the first step.

According to WordPress’s wp-config.php documentation, DB_HOST remains the default localhost in most installations and probably does not need changing. For servers using another port, append it to the address, for example localhost:3307. Many panels prefix database and user names with the account name; leaving the prefix out breaks the connection.

If the password cannot be viewed, reset the user’s password in the panel and put the same value in wp-config.php. Also verify on that screen that the user has the necessary permissions for the database. Copy the file before saving changes; a missing quote or semicolon can leave the site entirely blank.

Do not share the database password

wp-config.php contains the database password in plain text. Do not send screenshots to forums, social media groups, or messaging apps; conceal the password line when requesting help. If support needs access, create a temporary user instead of sharing the main password, then delete that user and change the database password afterward.

How do you repair the database with WP_ALLOW_REPAIR?

For suspected damaged tables, enable WordPress’s built-in repair tool by adding define( 'WP_ALLOW_REPAIR', true ); to wp-config.php, then use it at /wp-admin/maint/repair.php on the site. It offers table repair and optional optimization.

1. Back up the current files and database.
2. Open wp-config.php and add the line before the comment meaning “stop editing here”.
3. Open alanadi.com/wp-admin/maint/repair.php in the browser.
4. Start repair and check the table list on the results screen.
5. Immediately remove the added line from wp-config.php, then test the site and dashboard.

Do not skip the final step. According to WordPress’s editing wp-config documentation, enabling this setting allows access to the repair page without login because login may be impossible with a broken database. The document recommends enabling it only when needed and disabling it after resolution; forgetting the line leaves the page publicly accessible.

The repair tool does not fix connection problems caused by incorrect usernames or passwords; it addresses only table issues. Without a dashboard repair warning, this step does not advance diagnosis.

When and how should you contact hosting support?

If panel details exactly match wp-config.php, phpMyAdmin will not open, or resource limits are exhausted, the solution lies with hosting support; restarting the database server or increasing quota is beyond the owner’s control. A clearer support ticket gets a faster response. Include:

• The domain and time the error first appeared
• Whether the error appears on the frontend, in the dashboard, or both
• Recent changes: updates, migration, password changes
• The status of other sites in the same account
• Whether phpMyAdmin opens

Do not put passwords in support tickets; use the host’s own panel and official support channel for authentication. If someone asks for the database password by phone or email, separately confirm the request comes through the company’s official channel.

When is restoring a backup the last resort?

If details are correct, the server works, and repair fails, or tables are severely damaged, restoring the last good backup is the safest solution for error establishing a database connection. Because restoring loses content and orders added afterward, first check the latest backup’s date and coverage.

WordPress’s backup documentation states that both files and the database are needed for full restoration. According to it, restore files first, then import the database and update configuration if necessary. If the host provides automatic backups, restoration can often be started in the panel.

Also back up the faulty state before restoring. If the restored backup turns out to have the wrong date, this copy may be the only source for recovering lost content.

Database connection errors after migration

Error establishing a database connection after moving to new hosting most often results from wp-config.php retaining old server details. WordPress’s migration documentation states that wp-config.php must be updated if the database name or user changes.

The post-migration checking order is:

• Was the database created on the new server and the backup imported?
• Was the new user authorized for this database?
• Do the four wp-config.php values match the new panel?
• Is DB_HOST localhost on the new host, or a separate address supplied by the company?
• If the domain still points to the old server and its database was deleted, could the error be coming from there?

The same document notes that using the same database name and creating a user with the same credentials on the new server simplifies matters. If migration is planned, these checks are performed beforehand as part of the WordPress site migration process.

Independent intervention or specialist support?

Checking hosting status and comparing wp-config details with the panel are tasks owners can handle; specialist support reduces risk when file editing, repair, restoration, or suspected attacks enter the picture. Online quick-fix lists often suggest trying every step at once, while controlled diagnosis first identifies the responsible layer.

Specialist support makes sense for error establishing a database connection when it persists after repair, there are signs of attack, the latest backup is old or absent, migration is incomplete, or the error recurs frequently. For sites gaining customers through orders, appointments, or forms, longer downtime means direct business loss.

At Onur Freelance, we follow this order for WordPress problems: first back up the current state, narrow the error layer by layer, and share changes with the owner. One-time faults are handled through the WordPress troubleshooting service. Onur Freelance is not an official support channel for WordPress or hosting companies; only the hosting company can fix server infrastructure faults.

Preventing WordPress database errors: maintenance, backups, and resource monitoring

There is no single way to completely prevent error establishing a database connection; three habits reducing risk are regular maintenance, tested backups, and resource monitoring. WordPress’s backup documentation recommends weekly backups for infrequently updated sites and daily backups for frequently updated sites, keeping at least 3–5 current backups across locations such as server, cloud, and local computer.

• Update core, themes, and plugins after backing up
• Occasionally test whether automatic backups can actually be restored
• Regularly monitor disk, database quota, and resource usage
• Remove unused plugins and themes
• Keep hosting, FTP, and database passwords strong and never share them

For sites frequently reaching resource limits, a more suitable hosting plan may be part of a lasting solution. At Onur Freelance, hosting costs 2,000 TL annually and is opened in the business’s name; details appear on the hosting prices page. WordPress maintenance is planned at 500–2,000 TL per month depending on site size and scope.