WordPress cannot connect to its database and displays the database-connection error.
You do not have to become a server administrator because one part of your website stopped cooperating. Start with the checks that stay inside WordPress. If the problem moves into hosting or server configuration, I will show you where the risk begins—and where it may make more sense to hand the headache to me.
Start with the checks inside WordPress
- Check the hosting company’s status page for a database outage.
- Confirm that you are visiting the correct live domain, not an old staging address.
- Notice whether the error is constant or appears only during traffic spikes.
After each change, test the same action again. Change one thing at a time so you know what helped and what did not.
A good place to pause
When this leaves normal WordPress editing
This message means WordPress cannot complete its database connection. The credentials and server name live in wp-config.php, and a wrong change there can connect the site to the wrong database.
If you inherited the website, took over after parting ways with a developer, or normally use WordPress only to add photographs and text, you may have never opened cPanel before. That is normal, but if you are new to backend server configuration, you need to proceed with caution. This is where you can break your site.
You also do not need to end up with more damage than you bargained for just to solve one aggravating problem. The standard repair is $149.00 if you would rather hand it off.
If you are comfortable with backend server configurations, continue with the technical steps below.
Technical checks
- Compare the database name, user, password, and host in wp-config.php with the correct hosting database.
- Confirm that the database server is running and accepting connections.
- Check that the database user still has the required privileges on the correct database.
- Use database repair tools only when the logs or table checks show actual corruption.
Proceed with caution
Treat database credentials as sensitive and verify the database name before saving. Connecting to the wrong database can make the site appear replaced or missing.
Test the repair without making a second problem
- Keep a note of the original setting or filename before you change it.
- Make one change, clear only the relevant cache, and repeat the exact test.
- Check both the public page and the WordPress dashboard.
- If the error changes, stop and record the new message before continuing.
You can hand this off
If these checks have taken you beyond the part of WordPress you normally use, you can stop. I can trace the cause, make the repair, test the site, and tell you what was changed without turning one problem into your new full-time job.