A WordPress database error can make your whole website look broken, even when the problem is temporary. The safest goal during an outage is to preserve evidence, avoid making the problem worse, and give visitors a clear alternative while support investigates.
Start with reversible checks. Don’t install troubleshooting plugins, edit database tables, or repeatedly change passwords while the site is down. If your website handles enquiries, bookings, or legal matters, also think about what visitors should see—and whether paid ads should keep sending people to a broken page.
First: record the error and the time
Before changing anything, write down what you see and when you saw it. Keep this short incident note somewhere accessible to you and your support provider:
- Time and time zone: for example, “15 October, 10:42 a.m. BST.” Exact error text: copy it rather than paraphrasing. Common messages include “Error establishing a database connection” and “The site is experiencing technical difficulties.” What is affected: the entire website, only the admin area, or particular pages. Recent changes: hosting, DNS, password, plugin, theme, or WordPress updates—if any. What you tried: include the time and result of each check.
Don’t post screenshots or configuration files publicly if they could reveal private information. A screenshot of the visible error is useful for support, but redact account details, email addresses, and any credentials.
Fastest reversible checks
Check the site in a private browser window. Also try a phone using mobile data. This helps distinguish a local browser or network issue from an outage affecting visitors. Don’t clear caches or change DNS just because one device can’t load the site. Check the hosting control panel. Look for a service-status notice, account alert, maintenance message, resource-limit warning, or billing issue. These checks don’t change the site. Check whether the outage is widespread. If your host has a public status page, check it. If you have another website on the same account, see whether it loads—but don’t make changes to that site as a test. Stop repeated retries. Refreshing every few seconds won’t restore a database and can add noise to logs. Check again after a few minutes or when support responds.Change: put a static fallback page in front of the outage
If you can wordpress site down mysql safely publish a plain static page through your hosting panel or an existing website-management process, use it to tell visitors what is happening. A static fallback page is a simple HTML page served without needing WordPress or its database. It can be temporary; it does not repair the database or preserve dynamic functions such as forms, search, or online payments.
Keep the message factual and brief. Include your business name, a way to contact you that you know is working, and an update time. For https://stateofseo.com/how-do-payment-plans-work-for-criminal-lawyers-in-brisbane/ a law firm or another business handling sensitive enquiries, direct people to an established phone number or secure contact method rather than asking them to send confidential details to an unverified address.
- What changed: visitors see a static service message instead of a broken WordPress page. How to roll back: restore the previous homepage or web-root configuration using the hosting control panel or your saved copy. If you’re unsure which file is being served, ask support before replacing it.
Don’t overwrite WordPress files to publish a fallback unless you know exactly how to restore them. Before editing a site file, save a copy and confirm you can put it back. If the host provides a built-in maintenance or static-page feature, that is usually less risky than manual file changes.
Change: pause ads that send visitors to the broken site
If active ads are sending paid traffic to pages that don’t load, pause the relevant campaigns or ad groups using your advertising account. This is a reversible operational step, not a website fix. If only one landing page is affected and you have a tested alternative, you may be able to redirect traffic there instead; don’t send people to an unrelated or unverified page.
- What changed: the selected campaigns stop buying visits to an unavailable page. How to roll back: resume the same campaigns once the site and target pages have been tested. Note which campaigns you paused and when.
Change: publish a status page update
If you already use a status page or a business social channel, post a concise update with the time and what customers should do. Avoid promising a restoration time until your host gives you one. A simple message might be:
“We’re investigating a website issue affecting access to our site. We’re sorry for the disruption. Please call [published phone number] for assistance. We’ll update this page when we have more information. Last updated: [time and time zone].”
- What changed: customers have a reliable place to check for updates and an alternative contact route. How to roll back: replace the notice with a resolution update; keep the incident note for your records.
Check database credentials without exposing them
WordPress uses settings in wp-config.php to connect to its database. The key values are commonly named DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST. If one of these no longer matches the database account or server details in your hosting panel, WordPress may show a database connection error.
Use your hosting panel to compare the configured values with the database details shown for this website. Don’t paste a password into a support chat, email, public forum, or screenshot. Don’t guess at a replacement, and don’t create a new database or user as a quick experiment. On some hosts the database host is not simply localhost; use the exact value the host provides.
When a credential change is plausible
A mismatch is more plausible if someone recently changed the database password, migrated the site, restored a backup, or changed hosting. If no such change happened, a server-side database outage or resource problem may be more likely. In either case, ask support to verify the connection details and database service before changing them.
If you have authorization and are comfortable accessing files, inspect wp-config.php without posting or sharing its contents. If a value clearly differs from the current hosting-panel value, first download a copy of the file. Change only the specific confirmed value, then test once. If you are uncertain, leave the file untouched and give support the discrepancy you found.
- What changed: only a confirmed database setting, if you had evidence it was wrong. How to roll back: restore the saved original wp-config.php file or revert the single edited value. Keep the original private because it may contain secrets.
What to know about wp-config.php
wp-config.php is a core WordPress configuration file, usually in the main WordPress directory. It contains database connection settings and may contain security keys and other site-specific configuration. A typo, missing quote, or accidental extra character can cause a different error or take the site further offline.
- Make a copy before editing, and store it securely. Change only a value you have verified against the hosting provider’s current details. Do not share the whole file with support unless they provide a secure, approved method—and redact secrets if they only need a snippet. Do not add guessed settings or copy configuration code from an unrelated website. If you cannot confidently restore the file, stop editing and ask support to make or guide the change.
A database error does not automatically mean the database is damaged. Avoid running repair commands or altering tables unless support has confirmed that is the correct next step and a current backup is available.
Ask hosting support a specific question
Use the host’s official support channel and send a concise report. This is more useful than “my site is broken” and helps support check server-side causes without you making speculative changes.
Suggested message:
“My WordPress site, [domain], began showing ‘[exact error]’ at [time and time zone]. The issue occurs on [whole site/admin/particular pages], and I tested from [private browser/mobile data]. Please check whether the database service is healthy, whether this account has hit a connection or resource limit, and whether there were recent server, database, or migration changes. I have not changed database credentials or edited the database. Please confirm the correct DB_HOST and whether the configured database user can connect. Let me know if you need a recent error-log timestamp. Please don’t send credentials in an unsecured message.”
If support asks for logs, provide the relevant time range and exact error. Don’t enable public debugging or make log files accessible to visitors. If you are unsure how to retrieve logs safely, ask support to check them on the server.
Quick triage guide
What you observe Possible direction Safe next step The database error appears across the whole site Database service, credentials, connection limit, or hosting issue Record the exact message and ask the host to check database health and account limits The site fails after a known password or migration change Configuration may not match the current database account or host Compare values privately with the hosting panel; don’t guess or share the password The error happens intermittently Temporary server load, connection limits, or an underlying service problem Record each occurrence and time; ask support to correlate it with server logs Only your device or network fails Local browser, network, or cached content may be involved Test from another network and device before changing the siteWhat not to do during the outage
- Don’t install random plugins or a “database repair” tool while the site is unavailable. Don’t repeatedly change passwords, database users, or DNS records without a confirmed reason. Don’t delete files, tables, or backups to free space unless support has identified the issue and explained the recovery plan. Don’t restore an old backup without checking what data it would overwrite, especially new enquiries or orders. Don’t keep making changes after support begins investigating; tell them what you already did.
When the site returns
Test the homepage, several important pages, the WordPress login, and any critical forms or booking functions. If you published a static fallback page, confirm it is removed or no longer taking precedence. Resume paused ads only after checking the exact landing pages they use. Update your status page with the resolution and time, then keep your incident notes and any support reference number.
The safest temporary plan is simple: capture the error and timestamp, use a static fallback page if you can publish one safely, pause ads that lead to broken pages, post a status page update, and let hosting support verify server health and database credentials. Preserve a backup before any file change—and make every change easy to reverse.