"Error Establishing a Database Connection" is a WordPress error message that appears when WordPress cannot communicate with its MySQL database. On Web60, this is almost always a temporary server-side issue rather than something you need to fix yourself.
What this error means
Every WordPress site stores its content, settings, users, and plugin data in a MySQL database. When you load a page, WordPress connects to the database to retrieve that information. If the connection fails for any reason, WordPress cannot build the page and shows this error instead.
On Web60, your database credentials are configured and managed by the platform automatically. Unlike self-hosted WordPress where you might have entered the wrong password in wp-config.php, your credentials are always correct. This means the usual self-hosted troubleshooting guides do not apply here.
Common causes on Web60
The most likely reasons you would see this error on Web60 are:
- Temporary database server load. During brief periods of high demand, the database server may take a moment to respond. This resolves itself within seconds to a few minutes.
- Scheduled maintenance. Rare, but the database server may be restarted during a maintenance window. These are announced on the status page in advance.
- A platform-level incident. If multiple sites are affected, the Web60 team is already aware and working on it.
What to do
1. Wait and refresh
Give it two minutes, then refresh the page. Most database connection issues on managed hosting are brief and resolve on their own without any action from you.
2. Check the status page
Visit the Web60 status page to see if there is a known issue affecting the database servers. If an incident is listed, the page will include updates and an estimated time to resolution.
3. Raise a support ticket
If the error persists for more than five minutes and the status page shows no known issues, raise a support ticket from the Web60 portal. Include your site domain and the approximate time the error started. This helps the support team locate the relevant server logs quickly.
What not to do
Do not edit the database credentials in your wp-config.php file. On Web60, these values are set by the platform and are correct. Changing them manually will prevent your site from connecting to the database even after the underlying issue is resolved.
If you have already modified wp-config.php, mention this in your support ticket so the team can restore the correct values.
FAQ
Q: Should I edit wp-config.php to fix the database credentials?
A: No. On Web60, database credentials are managed automatically by the platform. Editing wp-config.php manually can break your site further. If you have already changed database values in wp-config.php, raise a support ticket so the team can restore the correct settings.
Q: Does this error mean I have lost my data?
A: No. This error means WordPress cannot connect to the database server, not that your data is gone. Your database and all its content are intact. Once the connection is restored, everything will be exactly as it was.
Q: How will I know if there is a platform-wide issue?
A: Check the Web60 status page at status.web60.ie. Any known service disruptions, including database server issues, are posted there with estimated resolution times. You can also subscribe to status updates by email.
Frequently asked questions
Should I edit wp-config.php to fix the database credentials?
No. On Web60, database credentials are managed automatically by the platform. Editing wp-config.php manually can break your site further. If you have already changed database values in wp-config.php, raise a support ticket so the team can restore the correct settings.
Does this error mean I have lost my data?
No. This error means WordPress cannot connect to the database server, not that your data is gone. Your database and all its content are intact. Once the connection is restored, everything will be exactly as it was.
How will I know if there is a platform-wide issue?
Check the Web60 status page at status.web60.ie. Any known service disruptions, including database server issues, are posted there with estimated resolution times. You can also subscribe to status updates by email.
Last updated: 4 April 2026