English
Magyar
A database connection error does not necessarily mean that your website’s content has been corrupted or lost. If WordPress fails to load and visitors cannot access the site, the ‘WordPress database connection error’ message may be caused by an incorrect setting, a temporarily unavailable database server or a database issue. Rather than guessing, first identify the symptoms clearly, then check the possible causes in a safe order.
This guide provides a step-by-step explanation of how to match the database details in the wp-config.php file with the values specified by your hosting provider, and how to distinguish between a WordPress configuration error and a hosting-related access issue. Before making any changes, we’ll also explain why backups are important, and when it’s advisable to repair the database or restore it to a previous state.
If local checks prove unsuccessful, aWh’s support team can help you investigate whether the database server is accessible. You can check the details provided for your hosting account via the cPanel interface, and support team can help you pinpoint the cause of the fault. This allows you to follow clear, step-by-step instructions and know when it is worth seeking further assistance.
What does a WordPress database connection error mean, and when does it occur?
WordPress loads the site’s content, settings and user data from a database. This requires a working connection between the website’s files and the database server. WordPress uses a MySQL or MariaDB database to manage its data. If the system cannot connect, it cannot retrieve the information needed to display the site.
In short: a database connection error means that WordPress cannot access or use the database that stores the website’s data.
A WordPress database connection error therefore does not simply indicate slow loading times. An error message often appears instead of the website, and it may also happen that the admin panel is unavailable. The symptoms help to determine what needs to be checked, but they do not, on their own, reveal the underlying cause.
What symptoms indicate a database connection error?
Visitors may see the message ‘Error establishing a database connection’. A blank page or other errors preventing content from being displayed may also occur. If the wp-admin interface does not open either, the administrator may encounter the same or a similar connection error.
Make a note of when the error occurred and what happened beforehand. Check whether all pages are affected, or whether it is just the login that isn’t working, and whether the problem started after an update or a change to the hosting settings. This symptom does not necessarily mean that the database is corrupted. A faulty configuration or a temporary server-side glitch could also cause a connection error.
What are the most common possible causes of the error?
WordPress stores its database connection details in the wp-config.php file. If any of these do not match the settings on your hosting account, the connection may fail. Please check the following:
- the database name,
DB_NAME; - the database username,
DB_USER; - the password,
DB_PASSWORD; - The name of the database server is
DB_HOST.
Temporary unavailability of the database service is also a possible cause. In such cases, the settings may be correct, but WordPress is still unable to access the server. Do not change the authentication details at random, and do not assume that the error message indicates database corruption. You can narrow down the exact cause by checking the configuration and the availability of the hosting server.
How can you securely check your WordPress database settings?
Before modifying the wp-config.php file, make a copy of it and keep the original in a safe place. This way, you can restore the previous state in the event of an error. When checking the file, start by simply reading the data. Only make corrections if you find any discrepancies compared to the values specified in your hosting account.
Where can you find the wp-config.php file, and what should you check in it?
The file is usually located in the WordPress installation directory, alongside the website’s other core files. You can open it for viewing in your hosting provider’s file manager – for example, via the cPanel interface – or download it to your own device. Look for the database settings, but do not copy them into a public forum or message.
The details shown in the hosting control panel must be checked against the relevant lines in the file. Compare the database name, username, password and server name specified in the hosting control panel with the values for DB_NAME, DB_USER, DB_PASSWORD and DB_HOST respectively.
The server name may vary depending on the hosting plan, so do not use a generic example or a value belonging to another website. The official WordPress troubleshooting guide on WordPress.org also recommends checking your configuration details in the event of a connection error.
How can you adjust the settings so that you can go back?
When troubleshooting a WordPress database connection error, follow the steps below:
- Make a backup of the file. Save the original version of
wp-config.phpand make a note of where you’ve saved it. - Compare the data. Check the configuration settings in the hosting control panel. Do not include your password in public messages, and do not send it via an unsecure channel.
- Just correct the difference. For example, if the username is different, change only that value. Leave the other lines unchanged and make a note of what you have changed.
- After saving, check the page. Open the website and the admin panel. If the error persists, restore the original file, then continue troubleshooting by checking the hosting server’s availability.
Manage your password via a secure hosting control panel and do not publish it in a screenshot. If the connection still does not work despite entering the correct details, check the settings in your cPanel hosting control panel, then contact aWh’s support team for assistance in checking server-side accessibility.
How can you distinguish between a database access error and a hosting-related issue?
You can narrow down the source of the error by checking the WordPress settings and the database service running on the hosting server separately. If the database management tool is accessible but the website is not connecting, check your WordPress settings and the database user’s permissions as well. If the database management tool itself does not open, or if several websites become inaccessible at the same time, there may be an issue with the hosting service.
In short: if the WordPress data is incorrect, the website will not attempt to connect using the correct connection details. In the event of a database service error, the server will be unavailable to WordPress.
When should you check the cPanel or phpMyAdmin interface?
In the cPanel interface, check whether the database management tool, such as phpMyAdmin, opens and whether the relevant database is accessible within it. Access to the interface is a useful indicator, but it does not prove that WordPress can connect using the same data and permissions. If the interface or database is unavailable, make a note of the error message displayed.
Checking phpMyAdmin is no substitute for a backup of your files and databases. Do not delete tables or run any SQL commands whose effects you do not understand. An overview of the options available in the cPanel hosting control panel may help with further checks.
What signs might indicate a hosting-related fault?
If the details in the configuration match those provided by your hosting provider but the WordPress database connection error persists, do not change the settings at random. Check whether your hosting provider has reported any service disruption, then try reopening the page later. If the problem persists or if multiple websites hosted on the same hosting server are affected, please contact aWh support team. Please provide the time the error first occurred, a list of the affected pages and the error message displayed, but do not send your password.
WPBeginner’s detailed guide also provides guidance on the next diagnostic steps. If local checks do not identify the cause, aWh’s support team will investigate database availability on the server side.
In what order should you try to fix a WordPress database error?
When carrying out a recovery, proceed from reversible checks towards more risky interventions. If the website or database is still accessible, create a fresh backup of both the files and the database. Before making any changes, create a backup of the files and the database so that, in the event of a failed repair, you can restore the system to its previous state.
- Check the circumstances of the error. Make a note of when it started, which pages are affected, and whether any updates or configuration changes were made beforehand. Do not start replacing files at random.
- Back up the available data. Back up the WordPress files and the database separately. A file backup does not automatically include the contents of the database, so please check that both backups have been completed and that they correspond to the correct site.
- Investigate the option that corresponds to the symptom. If there are signs of a configuration discrepancy, check the connection details. Only use a repair tool if you actually find evidence of damage to database tables and a suitable backup is available.
- If you’re unsure, stop. Ask for help from aWh’s support team or a knowledgeable system administrator before making any further changes.
When is it advisable to use the WordPress database repair tool?
WordPress’s built-in repair option may be useful for certain table errors, but it is not a universal solution for all WordPress database connection errors. The WP_ALLOW_REPAIR setting can temporarily enable the repair page. As the page may become accessible to others, only enable it for as long as necessary, restrict access to it, and then remove the setting from the wp-config.php file immediately after the operation. If you are unable to securely restrict access, or if it is unclear whether a database error is actually present, do not run the repair on your own.
When should you restore a backup, and when should you not attempt it on your own?
Restoration from a known, suitable backup point is only justified if the error occurred following an identifiable change and the backup covers both the files and the database associated with the website. The files and the database are separate backup units; therefore, an older file copy alone will not necessarily restore the site to its complete state.
If you are unsure which database belongs to your website, or if you are unable to verify the integrity of the backup, do not delete tables or run unfamiliar SQL commands. For further troubleshooting, please consult the hosting knowledge base or contact aWh’s support team for assistance.
How can you prevent a WordPress database connection error from happening again?
Prevention is based on regular checks, documented changes and restorable backups. A WordPress database connection error cannot always be prevented, but a clear routine helps you identify more quickly whether the problem began following an update, a configuration change or an issue on the hosting side.
Before updating, make a backup of your WordPress files and database. Then, carefully update the core WordPress system, plugins and themes. If you modify several elements at once, it is more difficult to determine which change caused any errors. After updating, check your website and the admin panel.
What backup and access control procedures can help minimise the risk?
Don’t just check whether automatic backups are being carried out. Also check whether the backup includes both files and the database, and make sure you are familiar with the restoration process. Regularly checking your recovery capabilities helps to avoid discovering, in the event of a fault, that the necessary data is missing.
Use a strong, unique password for administrator accounts and restrict access to authorised users only. Two-factor authentication and HTTPS provide protection for authentication and data transmission. These are useful security measures, but they do not, on their own, resolve the database connection error.
When should you ask your web hosting provider for help?
If the details in your WordPress configuration are correct but the connection still isn’t working, please contact aWh’s support team to check the availability of the database service. The same applies in the event of a recurring error or an outage affecting several sites on the same hosting account.
To help us diagnose the issue more quickly, please note down the time the error first occurred, the message displayed, the pages affected and any recent changes. Please also check any notifications from us in your hosting control panel. Please do not send passwords or other login details in public messages.
If the error recurs regularly, reviewing your hosting environment may also help you determine what steps to take next. Find out more about aWh’s WordPress and web hosting solutions, as well as the support information available.
Ensure your website runs smoothly
When dealing with a WordPress database connection error, effective troubleshooting begins by identifying the exact cause. First, create a backup, then check the configuration details. If these are correct but the connection still isn’t working, there may be a hosting-side issue in the background. Only begin database repair or restoration if you understand the implications of the action and have a suitable backup in place.
You can reduce the likelihood of a WordPress database connection error recurring by regularly checking that file and database backups are in place, backing up before updates, and keeping a record of important changes. Automatic backups, HTTPS and two-factor authentication are valuable security measures, although they do not, on their own, fix the connection.
With over 10 years’ experience in the web hosting industry, aWh offers hosting solutions and support information. Take a look at aWh’s WordPress and hosting solutions, and choose the environment that best suits your needs. With careful monitoring and up-to-date backups, you too can be better prepared to deal with similar issues.
Frequently asked questions about the WordPress database connection error
What does a WordPress database connection error mean?
This error means that WordPress is unable to connect to the database from which it loads the site’s content and settings. As a result, the website or the admin panel is not displaying correctly. The message alone does not prove that the database is corrupted. It could also be caused by incorrect connection details or a temporarily unavailable database service, so please check your settings and the availability of your hosting first.
Why does the message ‘Error establishing a database connection’ appear?
This message appears when WordPress cannot access the database using the details specified in the configuration. Common possible causes include an incorrect database name, username, password or server name. A temporary outage of the database service may also be the cause. You can determine the exact cause by comparing the settings on your hosting account with the contents of the wp-config.php, and, if necessary, by contacting aWh’s support team.
Where can I find the name and password for my WordPress database?
You will usually find the database name and username in your hosting control panel, such as cPanel, whilst the values used by WordPress are listed in the wp-config.php file in the installation directory. The password can also be found in the configuration, but for security reasons, do not publish it or send it in a public message. If you are unsure about the values, check them against the details shown in your hosting control panel.
How can I check the database settings in the wp-config.php file?
First, make a copy of the file, then open it for viewing in your hosting account’s file manager, or download it to a secure device. Locate the DB_NAME, DB_USER, DB_PASSWORD and DB_HOST values, then compare them with the details provided by your hosting provider. Do not use a generic server name, as this value may vary depending on the environment. Only amend details that are proven to be incorrect.
Can a hosting service outage cause a database connection error?
Yes. If the database service is temporarily unavailable, WordPress will still be unable to connect, even if the details in wp-config.php are correct. Check the notifications displayed in your hosting control panel and see if other sites on the same hosting account are also affected. In the event of a recurring outage or one affecting multiple websites, please provide aWh’s support team with the time the fault began and the error message displayed.
How can you repair the database if WordPress cannot connect?
First, check whether there are any signs of database table corruption, as a connection error alone does not necessarily warrant a fix. If the data is accessible, create separate backups of your files and database. WordPress’s repair option may help with certain table errors, but use the WP_ALLOW_REPAIR setting with caution: restrict access and remove it after the operation is complete. If in doubt, contact aWh’s support team for assistance.
Could I lose my data due to a WordPress database connection error?
A connection error does not in itself mean that data has been lost. Often, it simply means that the database cannot be accessed. However, there may be a risk of data loss if the database has been corrupted or if the repair or restoration process is carried out incorrectly. Do not delete tables or restore from an unknown backup. Check the file and database backups separately, and only select a restore point that you know belongs to this site.