Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →A WordPress site can be down because of an external outage, a DNS or SSL mistake, a failed update, a plugin or theme fatal error, or a resource limit. Start by recording the exact error and HTTP status, checking both the public site and /wp-admin, and confirming whether every visitor is affected. Make a full backup before changing files, database settings, or code. Then work from infrastructure checks toward reversible WordPress isolation steps.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
First, identify what “down” means
Different symptoms point to different layers of the stack. A browser timeout or DNS error usually deserves an infrastructure check before you edit WordPress. A branded “critical error” page usually indicates PHP, plugin, theme, or custom-code failure. A site that loads but shows broken links may have a rewrite or SSL problem rather than a complete outage.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Record the exact message, URL, time, and HTTP status code (such as 404, 500, 502, 503, or 504).
- Test the front end and
/wp-adminin a private browser window and, if possible, from a different network. - Ask whether all visitors see the failure or only one device, location, or authenticated account.
- Check the hosting control panel, provider status page, and support channel before changing WordPress files.
- Make a complete file and database backup before troubleshooting changes. Keep the backup separate from the live account.
Change one thing at a time and retest. This preserves a clear cause-and-effect trail and makes it possible to undo a bad change.
Quick diagnosis by symptom and access
| What you see | Most likely layer | Access commonly needed | Safest first action |
|---|---|---|---|
| Domain does not resolve, or points to an unfamiliar server | DNS, nameservers, or hosting | Registrar or hosting panel | Verify DNS records and nameservers; do not edit WordPress yet |
| Certificate warning, redirect loop, or HTTPS-only failure | SSL configuration or forced HTTPS | Hosting panel and host support | Have the host verify the certificate, virtual host, and redirect settings |
| “Error Establishing a Database Connection” | Database credentials, availability, quota, or server health | Files and hosting/database panel | Check the four database values in wp-config.php, then ask the host about availability and quota |
| “Critical error” or a blank/white page after a change | Plugin, theme, custom PHP, PHP version, or memory | Recovery Mode, dashboard, FTP/file manager, or logs | Use Recovery Mode or isolate plugins before editing code |
| “Briefly unavailable for scheduled maintenance” that never clears | Stale update marker | FTP or file manager | Remove the root .maintenance file only after confirming the update has finished |
| Home page works but internal links return 404 | Permalink rules or .htaccess |
Dashboard and, if needed, host support | Save Settings → Permalinks, then have the host check rewrite support |
| Visitors can browse, but scheduled tasks or Site Health loopbacks fail | Firewall, DNS, SSL, or HTTP authentication | Host or security-control access | Ask the host to inspect outbound and loopback requests |
12 common causes and the correct fix
1. Hosting or server outage
A server outage can make every page time out, return a 5xx response, or show a provider-generated error. A database quota can also be exhausted while the web server itself remains reachable. Check the host’s status page and control panel for maintenance, resource exhaustion, suspended services, disk limits, or database incidents.
If the panel is unavailable or the status page does not explain the failure, contact hosting support with the domain, exact timestamp, HTTP status, and any request or incident ID shown in the panel. Do not repeatedly restart services or alter WordPress files while the provider is investigating; those changes can obscure an infrastructure fault. The host can verify web-server health, database availability, account quotas, and recent configuration changes.
2. DNS or domain misconfiguration
When a domain does not resolve, resolves to an old address, or displays another site, WordPress is not yet the problem. Common causes include expired registration, incorrect nameservers, an outdated A or AAAA record, a misdirected CNAME, or a recent migration that has not propagated consistently.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Confirm the domain is registered and not suspended at the registrar.
- Compare the authoritative nameservers with the ones your host expects.
- Check the A, AAAA, and CNAME records against the current server’s documented values.
- Remove stale or conflicting records only after confirming which server should answer for the domain.
- Wait for DNS caches to expire and test from more than one network.
Changing wp-config.php or reinstalling WordPress cannot repair a name that points to the wrong server. If records look correct but some networks still fail, have the registrar or host inspect delegation and DNSSEC rather than making repeated random edits.
3. SSL or HTTPS failure
A certificate that is expired, issued for a different hostname, incompletely installed, or paired with the wrong virtual host can trigger browser warnings or prevent requests entirely. A forced-HTTPS rule can also create a redirect loop when the proxy or origin does not agree about the connection scheme. The same mismatch may break WordPress loopbacks used by scheduled tasks and Site Health.
Use the hosting panel to confirm that the certificate covers the exact domain and its required subdomain, is attached to the active site, and has a complete certificate chain. Have the host verify TLS termination, proxy headers, and HTTP-to-HTTPS redirects. Avoid disabling certificate validation or switching the site repeatedly between HTTP and HTTPS; those actions can create mixed-content and login-cookie problems without fixing the underlying certificate or server configuration.
4. Database connection failure
“Error Establishing a Database Connection” means WordPress could not connect to the database using the configuration or service currently available. In wp-config.php, verify the database name, database user, database password, and database host. Compare each value with the hosting panel’s database details, taking care with capitalization, punctuation, and a host-specific socket or hostname.
Recommended Free Tools
If the values are correct, ask the host whether the database server is running, the account has reached its quota, connections are being refused, or the database has been affected by a security incident. Do not guess new credentials or overwrite tables. The host can reset a database password, confirm privileges, repair a damaged service, or investigate resource and compromise indicators while preserving the correct account relationship.
5. Plugin conflict or fatal error
A plugin can cause a PHP fatal error after activation, an update, or a change in another component. WordPress may display a “critical error” message and offer Recovery Mode. Recovery Mode, introduced in WordPress 5.2, creates a temporary administrator session in which the failing plugin or theme is paused for that session.
When the recovery email or link is available, follow it, read the component named in the error details, and deactivate that component. If the dashboard remains inaccessible, use FTP or the host’s file manager:
- Open the site’s
wp-contentdirectory. - Rename
pluginsto a temporary name such asplugins.off. - Test the site and
/wp-admin. - If the site returns, restore the directory name to
plugins, then deactivate or rename suspected plugin folders individually. - Reactivate plugins one at a time, testing after each activation, until the failure recurs.
This method is reversible and does not delete plugin settings. Once the offending plugin is identified, update it, roll it back using a known-compatible version, replace it, or contact its developer. Keep the rest of the plugins inactive until the cause is clear so that simultaneous changes do not mask the trigger.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
6. Theme or custom-code fatal error
A recently edited theme file, a code snippet, or a child-theme customization can stop PHP execution. Recovery Mode may identify the theme; otherwise, a default WordPress theme can provide a temporary test. From the dashboard, switch to an installed default theme. If you cannot reach the dashboard, rename the active theme’s directory through FTP or a file manager so WordPress falls back to an available default theme.
Inspect wp-content/debug.log and the server’s PHP error log for the file and line number named in the fatal error. Correct the syntax or incompatible function, or restore the last known-good version of the edited file. Do not paste full debug output into a public page: stack traces can disclose paths, usernames, configuration values, and other sensitive details. Disable debugging display on the live site after collecting the information.
7. Incompatible PHP version or extension
A host-side PHP upgrade can expose an outdated plugin, theme, or custom function. The reverse can also happen: an old PHP release or missing extension may no longer satisfy current WordPress components. Fatal errors often begin immediately after a PHP-version change.
Record the PHP version and enabled extensions in the hosting panel, then compare them with the stated requirements of the current WordPress release, active theme, and plugins. Ask the host for a supported PHP configuration rather than selecting a random version. If the host offers a staging environment, test the upgrade there first. Once compatibility is restored, update or replace components that still require obsolete PHP behavior; do not leave an unsupported version in production as a permanent workaround.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems8. Exhausted memory or execution limits
White screens, intermittent 500 errors, and critical errors can result when PHP exhausts its memory allocation or reaches a maximum execution time while processing a large request. Import jobs, image processing, backup tasks, and page builders can expose the limit even when ordinary pages work.
Use the host’s resource graphs and PHP logs to determine whether memory, CPU, processes, or execution time is the constraint. Increase WordPress or PHP limits only after a backup and with host guidance, particularly on shared hosting where account-level caps may override application settings. A higher limit treats the symptom if a plugin is leaking memory or a request is unbounded; profile or disable the responsible task rather than continually raising limits. Remove temporary troubleshooting settings after confirming stability.
9. Failed update and stuck maintenance mode
During a core, plugin, or theme update, WordPress places a file named .maintenance in the site root and shows a maintenance notice. If the update has completed but the notice remains, the marker may be stale because the request was interrupted.
- Confirm through the hosting panel or update logs that no update process is still running.
- Open the WordPress root with FTP or a file manager, including hidden files.
- Delete only the root
.maintenancefile. - Load the front end and
/wp-admin, then review the Updates screen for incomplete components.
If files are missing or the update stopped halfway, restore the affected component from a known-good backup or reinstall it after the maintenance marker is cleared. Do not delete arbitrary hidden files while looking for the marker.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
10. Corrupted WordPress files
Damaged or incomplete core files can produce fatal errors that do not disappear when plugins and themes are isolated. Causes include interrupted updates, disk errors, unsafe deployments, or unauthorized changes. Compare the failure with server logs and the isolation tests before assuming corruption.
Restore a known-good backup when it is recent and trustworthy. Otherwise, download a fresh package matching the site’s WordPress version and replace the core files while preserving wp-content, wp-config.php, and other site-specific configuration. WordPress guidance specifically notes that re-uploading wp-admin and wp-includes can correct some failures. Use the host when file ownership, permissions, malware indicators, or uncertain backup integrity are involved; a blind overwrite can remove legitimate customizations or leave the underlying compromise in place.
11. Permalink or .htaccess rewrite failure
If the home page loads but posts, pages, or other pretty URLs return 404 errors, rewrite rules may be missing or invalid. In the dashboard, go to Settings → Permalinks and click Save Changes without changing the selected structure. WordPress will flush its rewrite rules.
If the problem persists, inspect .htaccess only if your server uses Apache and the file is part of the site’s documented configuration. A host should verify that mod_rewrite is enabled, overrides are permitted, and the virtual host points to the correct document root. Nginx and other servers use different rule systems, so copying an Apache file into an Nginx configuration will not fix the issue.
12. Firewall, authentication, loopback, or security block
A site can appear normal to visitors while WordPress reports failed loopbacks, missed scheduled tasks, or Site Health warnings. Outbound requests may be blocked by a web-application firewall, host firewall, DNS policy, SSL mismatch, or HTTP authentication placed in front of the site. Security plugins and rate limits can also block the server’s own requests.
After plugin and theme causes have been isolated, give the host the failed URL, timestamp, response code, and Site Health details. Ask it to inspect firewall events, outbound restrictions, DNS resolution from the server, certificate validation, proxy rules, and any HTTP basic-authentication layer. Do not broadly disable security controls without a specific test and a plan to restore them; a temporary allow rule for the documented loopback path is safer than removing an entire firewall policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A safe troubleshooting sequence
Use this order when the cause is not obvious:
- Preserve evidence and make a backup. Save the exact error, status code, timestamps, recent change history, and a complete file/database backup.
- Separate scope. Test the front end and
/wp-adminfrom another network, and determine whether the issue affects all visitors. - Check infrastructure. Review hosting status, account quotas, domain registration, DNS, and SSL before editing WordPress.
- Use built-in diagnostics. Follow Recovery Mode when offered and read Site Health warnings without exposing debug details publicly.
- Review logs. Check server/PHP logs and
wp-content/debug.logfor the first relevant error, not merely the last browser message. - Isolate components. Disable plugins, then test the theme, using FTP or a file manager if the dashboard is unavailable. Reactivate one item at a time.
- Check compatibility and limits. Compare PHP and extension requirements, memory, execution time, and account resources with the failing request.
- Repair files or updates. Clear a confirmed stale
.maintenancemarker, restore a backup, or replace core files while preserving configuration and content. - Flush rewrites and retest. Save the Permalinks screen, then verify representative posts, pages, media, login, forms, and scheduled tasks.
- Escalate with evidence. Give the host the domain, timestamps, status codes, logs, and changes already tested so it can inspect server-side controls efficiently.
Make each change reversible and record what you changed. If a test makes the site worse, revert that single change before proceeding.
What to do after the site returns
- Finish any interrupted core, plugin, or theme update and check the Updates screen for components left in an inconsistent state.
- Remove temporary directory renames, test accounts, permissive firewall rules, and diagnostic settings that are no longer needed.
- Turn off public debug display and protect log files from web access.
- Review hosting resource usage, database quotas, PHP errors, cron/loopback status, and certificate expiry dates.
- Maintain automated WordPress backups with off-site retention and periodically verify that a restore actually works.
- Use WordPress uptime monitoring that checks both availability and meaningful response content, not only whether a TCP port answers.
- Document the working PHP version, DNS records, SSL arrangement, active theme, and plugin set so the next incident has a known baseline.
When to stop troubleshooting yourself
Contact the host immediately when the server, database service, DNS delegation, certificate installation, quota, firewall, or file ownership is outside your account’s control. Stop and seek specialist help when logs suggest malware, when a backup cannot be verified, or when replacing files could destroy custom code. A precise handoff containing the error, status, timestamp, affected URLs, and completed tests is more useful than repeated reinstallations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
