Recommended Free Tools
Start with the exact message, when the failure began, and whether the public site, wp-admin, or both are affected. A blank page is only a symptom; PHP and database failures can look identical. Use WordPress Recovery Mode when it is offered, isolate plugins and themes methodically, and involve your host when logs point to the database, resource limits, or server configuration.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This guide gives a separate path for each common message and for sites where the dashboard is unavailable. Treat each suggested cause as a lead to test, not as a guaranteed diagnosis.
As an Amazon Associate I earn from qualifying purchases.
Make a safe triage record before changing anything
Write down the exact on-screen wording, the URL that fails, and whether the problem affects the whole site or one area. Record what changed immediately beforehand: a core, plugin, or theme update; a PHP or hosting change; a migration; or an edit to configuration files. Preserve a screenshot and the time of the failure. Those details let you correlate the symptom with server logs and make it possible to undo a change deliberately.
- Public site and dashboard both fail: prioritize the error text, the administrator email, server and database availability, and recent configuration changes.
- Only the public site fails: check the active theme, rewrite rules, and front-end plugins while confirming that
wp-adminstill responds. - Only
wp-adminfails: test administrator-facing plugins, authentication-related changes, and the server log; do not assume the public site has the same cause. - One URL or custom post type fails: inspect names and rewrite rules before disabling unrelated components.
Before an upgrade or risky file or database operation, make a current copy of both the WordPress files and the database. WordPress’s troubleshooting guidance treats those as separate backup jobs. A hosting snapshot or an external hard drive can be a destination, but neither is proof that a restorable backup exists; verify that the files and database are both included and that the backup can be retrieved.
#1 Best Overall
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Quick decision map
| What you see | Most useful first evidence | First branch |
|---|---|---|
| Blank or white screen | Whether wp-admin works, recent plugin/theme changes, PHP and database logs |
Isolate plugins or switch the theme; use file-based deactivation if the dashboard is inaccessible |
| “There has been a critical error on this website” | WordPress recovery email and its component notice | Enter Recovery Mode, repair or deactivate the named component, then test outside the recovery session |
| “Error Establishing Database Connection” | wp-config.php connection values and database-service status |
Verify name, user, password, and host; ask the host about outages, quotas, or limits if values are correct |
| Internal Server Error (HTTP 500) | Web-server error log and the last known change | Separate WordPress/plugin causes from server configuration and hosting causes |
| Connection timed out | Request timing, resource usage, memory and PHP execution limits | Reduce the failing workload temporarily and have the host confirm the applicable limit |
| Custom post type returns 404 | Names shared with pages and current permalink rules | Remove a naming collision and refresh rewrite rules through Permalinks settings |
The map is a routing aid, not a list of confirmed causes. The detailed sections below explain what to test and what the result means.
Blank or white screen
A white screen does not identify a plugin conflict by itself. WordPress documents both PHP errors and database errors as possible causes, so first establish whether the dashboard and other URLs respond.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When wp-admin still works
- Open Plugins and deactivate the plugins, preferably one at a time while checking the failing page after each change. The first plugin whose deactivation restores the page is a strong lead, not final proof; reactivate it only after testing the rest of the stack.
- If the failure began after a theme change, switch to an available default WordPress theme and reload the affected URL. Restoration implicates the theme or its interaction with another component.
- Use WordPress debugging information and the server’s PHP log to identify a file, function, or component. A log entry that names a plugin or theme is stronger evidence than the appearance of a blank page alone.
- Record every deactivation and reactivation. If several components are involved, restore them in a controlled order so that a second conflict does not obscure the first one.
When the dashboard is unavailable
Use the file access method provided by your host, such as FTP or a hosting file manager. Temporarily rename the plugins directory so WordPress cannot load those plugins, then request the site again. If the site returns, restore the directory name and isolate the plugins individually rather than leaving every plugin disabled. If plugins are not the cause, temporarily rename the active theme’s directory or otherwise switch to a default theme using the documented file-based procedure. Keep a note of each temporary name so you can restore it without deleting files.
Do not delete a plugin or theme as a first response. File-based deactivation is reversible and preserves the evidence needed to identify the conflict. If neither plugins nor the theme explains the symptom, compare the timing with a database or hosting event and consult the relevant logs.
“There has been a critical error on this website”
The full interface text is: There has been a critical error on this website. Please check your site admin email inbox for instructions.
This message commonly accompanies a fatal PHP error, but the message itself does not tell you which component is at fault.
Use Recovery Mode when WordPress offers it
Recovery Mode is a built-in WordPress feature introduced in version 5.2. For some fatal PHP errors, WordPress sends the site administrator a special login link. During that administrator’s Recovery Mode session, WordPress pauses the faulty plugin or theme and displays notices identifying the problem component.
Rank #2
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
- Open the administrator mailbox associated with the site and find the recovery message. Check spam or filtering rules if it is not in the main inbox.
- Follow the special link and read the notice for the paused plugin or theme, including any file and line information shown.
- Use the notice as a focused lead: update, configure, or deactivate the named component according to its documentation, and check whether a recent change caused the fatal error.
- Exit Recovery Mode, or use a normal browser session, and load the public site and dashboard again. Recovery Mode’s pause is for the administrator’s session; it is not a permanent repair for visitors.
If no recovery email arrives
Recovery Mode applies to some fatal errors, not every outage. If no message arrives, use WordPress’s alternate debugging methods and your server’s PHP error log. With file access, temporarily rename the directory of a plugin you strongly suspect, then test the site. Restore the directory and continue with one-at-a-time isolation once you regain access. Avoid changing several components simultaneously because you will lose the ability to connect the result to a cause.
“Error Establishing Database Connection”
This message means WordPress could not establish the connection it needs to read or write the site database. It does not prove that the database credentials are wrong; an unavailable service, quota, or host-side failure can produce the same result.
Check the four connection values
Using a safe copy of the file, inspect the database name, database username, database password, and database host in wp-config.php. Compare each value with the credentials and host name supplied by the hosting account. Look for an accidental edit, an extra character, or a credential change that was not carried through to the file. Do not publish these values in a support ticket or screenshot.
When the values appear correct
Ask the hosting provider whether the database service is running and reachable from the web server. Request checks for a database quota, a connection limit, maintenance, or an outage. The host can confirm conditions that are invisible from WordPress. If the provider reports a server-side problem, preserve the timestamp and error log entry for escalation.
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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDo not replace credentials or attempt database-table repair merely because this message appears. Make and verify a backup of both files and the database first, and only perform a repair when the evidence supports it and you understand the recovery path.
Internal Server Error (often HTTP 500)
An HTTP 500 is a generic server response with multiple possible causes. WordPress’s common-errors guidance does not establish that every 500 is a plugin or theme conflict. Start with evidence from the web-server error log and the most recent change, then branch according to what the log shows.
Rank #3
- 【Plug-and-Play Expandability】 With no software to install, just plug it in and the drive is ready to use in Windows（For Mac，first format the drive and select the ExFat format.
- 【Fast Data Transfers 】The external hard drives with the USB 3.0 cable to provide super fast transfer speed. The theoretical read speed is as high as 110MB/s-133MB/s, and the write speed is as high as 103MB/s.
- 【High capacity in a small enclosure 】The small, lightweight design offers up to 500GB capacity, offering ample space for storing large files, multimedia content, and backups with ease. Weighing only 0.35 Lbs, it's easy to carry "
- 【Wide Compatibility】Supports PS4 5/xbox one/Windows/Linux/Mac and other operating systems, ensuring seamless integration with game consoles,various laptops and desktops .
- Important Notes for PS/Xbox Gaming Devices: You can play last-gen games (PS4 / Xbox One) directly from an external hard drive. However, to play current-gen games (PS5 / Xbox Series X|S), you must copy them to the console's internal SSD first. The external drive is great for keeping your library on hand, but it can't run the new games.
WordPress-level branch
If the log identifies a plugin, theme, PHP file, or fatal error, isolate that component. With a working dashboard, deactivate plugins individually and test a default theme when the timing points to a theme. Without dashboard access, use reversible file-based deactivation. Recheck the log after each test so you can tell whether the same error is still being generated.
Server and hosting branch
If the log points to web-server directives, file permissions, PHP configuration, upstream services, or a host process, involve the provider rather than repeatedly reinstalling plugins. Give support the exact URL, UTC time, response code, and relevant log excerpt with secrets removed. A host may need to correct a configuration or service condition that WordPress cannot change.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Connection timed out
A timeout can occur when a request asks more of the server than it can deliver within the permitted period, particularly on restricted shared hosting. It can also be triggered by a slow external call, a heavy query, or a component that loops. The applicable limit depends on the hosting environment, so identify it before changing a setting.
- Note whether every page times out or only one operation, such as saving a post or opening a report. A single expensive action points to a narrower workload than a site-wide timeout.
- Temporarily deactivate plugins one at a time and test a default theme if the timing implicates a component. Restore each change deliberately.
- Review the configured PHP memory limit and PHP execution limits shown by your host or Site Health information. Do not raise a limit blindly; the provider may enforce a separate account-level ceiling.
- Ask the host which memory, execution-time, process, or database limits apply to the account and whether the server recorded resource exhaustion. Supply the time and URL of the timeout.
A successful test after reducing the workload identifies a useful lead, but it does not establish that the component is the only cause. Keep the log evidence and confirm the fix under normal traffic.
Custom post type returns a 404
When a custom post type’s single URL returns 404 while other parts of the site work, inspect naming and rewrite rules before treating it as a missing post.
Check for a naming collision
Confirm that the custom post type name and the slug of a single page are not the same. A collision can send the request to the wrong rewrite rule. Rename one of the conflicting items using the controls supplied by the plugin or registration code, then test a newly loaded single URL.
Rank #4
- Slim durable design to help take your important files with you
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Refresh permalink rules
- In the dashboard, open Settings → Permalinks.
- Select the default permalink structure and save the changes.
- Select your preferred structure again and save it.
- Open the custom post type URL in a fresh browser request. If it still returns 404, inspect the registration and server logs rather than repeatedly saving settings.
The two saves force WordPress to rebuild rewrite rules; they do not correct a conflicting name or faulty registration by themselves.
Plugin-specific failure
When the message names a plugin or the failure began immediately after its update, start with the plugin’s own documentation and support reports. Check the version, supported WordPress and PHP requirements, and known issues for the release you installed. Also note whether another plugin or the active theme changed at the same time.
Isolate before replacing
- Deactivate the suspected plugin while leaving other components unchanged.
- Reproduce the same action and record whether the error, log entry, or status code changes.
- Reactivate it only after the test, then deactivate other plugins individually if the result is inconclusive.
- If the dashboard is unavailable, use reversible file-based deactivation and restore the original directory name before testing another candidate.
Reinstalling or replacing a plugin should follow an identified compatibility, corruption, or version issue; it is not a universal first step. Preserve settings and make a backup before changing files or database data.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If you can access wp-admin
The dashboard lets you gather evidence without altering files directly. Open Tools → Site Health. The Status view flags configuration concerns, while the Info view exposes technical details about the server, database, themes, plugins, and media. Use those details to distinguish a WordPress setting from a host-side condition, and copy only the non-sensitive information needed for support.
Work in a controlled sequence: check Recovery Mode notices, inspect Site Health and logs, isolate one plugin or theme, test the exact failing URL, and record the result. Avoid bulk updates while diagnosing; an additional change can hide the original trigger.
If you cannot access wp-admin
Use the administrator email, hosting control panel, FTP, or another documented file-access method. Recovery Mode can restore a diagnostic dashboard session even when the normal site is broken. If it is unavailable, temporarily rename a suspected plugin directory or the active theme directory rather than deleting it. Make one change at a time and keep a written map of original names.
Best Value
- World’s First 6TB 2.5” Portable Hard Drive
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
For database, timeout, or server errors, file access alone may not be enough. Collect the exact message and timestamp, then ask the host for database and web-server logs, service status, quota information, and enforced PHP limits. Do not expose passwords or database credentials while sharing evidence.
Use logs and backups to confirm a cause
The visual symptom is rarely sufficient to prove a diagnosis. A PHP or web-server log that names a component, a database-service confirmation from the host, or a repeatable result after isolating one plugin is stronger evidence. Site Health adds configuration context but does not replace server logs.
Before core, plugin, or theme upgrades, retain a current backup of all WordPress files and the database. Verify that the backup completed and that you know how to restore it. If a risky change leaves the site worse, restore only after preserving the error evidence and confirming that the backup covers the affected data.
When to contact the hosting provider
Contact the host when the evidence points to an unavailable database, a database quota or connection limit, PHP execution or memory ceilings, web-server configuration, or a service outage. Include the domain, failing URL, UTC timestamp, exact message, recent change, and sanitized log excerpt. Ask the provider to identify the enforced limit or service condition instead of requesting a blind increase or a host migration.
Once the host confirms its side is healthy, return to WordPress-level isolation. Conversely, if a plugin or theme is named consistently in logs and disabling it restores the site, resolve that component before considering a hosting change.
A repeatable recovery sequence
- Capture the exact wording, scope, timestamp, and recent changes.
- Check the administrator email for Recovery Mode and follow its component notice when available.
- Make or confirm a backup of both files and the database before risky work.
- Use Site Health and server logs to separate WordPress, PHP, database, and hosting evidence.
- Isolate one plugin or theme at a time; use reversible file-based deactivation when
wp-adminis unavailable. - For database, timeout, or server-limit evidence, provide the host with the precise log and timing details.
- After a change, test the original failing URL, the dashboard, and representative unaffected pages, then restore components deliberately.
This sequence keeps a plausible lead separate from a confirmed cause and minimizes the chance that emergency changes destroy the evidence needed for a lasting fix.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →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.
