WordPress does not publish an official ranking of its “most annoying” errors, but it documents many familiar problems—from blank pages and database errors to broken permalinks. The safest way to troubleshoot is to note exactly what you see, back up the site before changing it, and use logs or controlled tests to narrow down the cause. A symptom such as a blank screen is not, by itself, a diagnosis.
Start with safe troubleshooting
- Record the symptom. Note the exact error text and whether it affects the public site, the dashboard, or both. WordPress’s common-errors guide describes symptoms, but many can have more than one cause.
- Back up the site before making changes. A full backup gives you a recovery point if a troubleshooting step causes a new problem. Learn WordPress recommends backing up before troubleshooting plugin and theme conflicts.
- Check Site Health. In the dashboard, open Tools > Site Health. Its status and information screens can show critical or recommended improvements and configuration details; they are diagnostic aids, not a guarantee that every fault will be identified. See the Site Health screen documentation.
- Use logs and controlled tests. For a critical error, check the site-admin email and, when needed, enable debugging and inspect
wp-content/debug.log. Keep debug details private; they can reveal technical information about the site. WordPress explains the critical-error steps in its common-errors guide. - Escalate server-level symptoms. If the likely issue involves the database service, web-server configuration, or a setting you cannot safely access, contact your host rather than guessing at file or server changes.
WordPress errors and site failures
1. White screen or blank page
A blank screen is a symptom, not proof of a particular fault. WordPress lists PHP or database errors, plugin compatibility problems, and theme problems among possible causes. Check for a recovery email and relevant logs, then use a backup and controlled plugin or theme tests to narrow it down. Avoid changing several things at once; that makes the cause harder to identify. See WordPress’s guidance on the White Screen of Death.
2. “There has been a critical error on this website”
The full notice may read: “There has been a critical error on this website. Please check your site admin email inbox for instructions.” Start by checking that inbox, including spam, for a recovery message. If it does not identify the failing component, WordPress recommends enabling debugging as appropriate and reviewing wp-content/debug.log. A critical error can have multiple causes, so use the log to guide the next test rather than assuming a plugin is responsible. The steps are in the WordPress critical-error documentation.
3. “Error establishing a database connection”
This message means WordPress could not connect to its database; it does not identify why. Check that the database settings are correct and whether the database service or hosting account is experiencing an issue. If you do not manage those settings or cannot confirm service status, give the exact message and its start time to your host. WordPress lists possible causes in its database connection guidance.
4. Internal server error
An internal server error is a broad server-side symptom, not a single WordPress diagnosis. Check the host’s error logs or ask support to inspect them around the time the error occurred. The WordPress common-errors guide lists the problem but does not establish one universal fix.
5. Site connection timeout
A timeout means the site did not respond within the expected period; it is not necessarily a WordPress-only fault. Record when it happens and whether it affects the dashboard as well as the public site. If it persists, ask the host to check server response and logs. WordPress lists the symptom but does not prescribe a universal cause or fix in its common-errors guide.
6. Site stuck in maintenance mode after an upgrade
If visitors continue to see a maintenance message after an upgrade should have finished, first confirm whether an update is still running. If the message persists, contact your host or consult WordPress-specific instructions for your setup before deleting or changing files. WordPress names this failure in its common-errors guide, but that listing does not provide a verified recovery sequence for every hosting configuration.
7. Automatic upgrade fails
A failed automatic upgrade can leave the site or update process incomplete. Note what was being updated and any displayed error, then check the host’s guidance or ask support to confirm the site’s current state before attempting another update. WordPress lists failed upgrades as a common error, but its overview does not establish a single current recovery procedure for all cases. Avoid following unverified file-deletion instructions.
Recommended Free Tools
Rank #3
Plugin, theme, PHP, and memory problems
8. Plugin conflict
If the problem began after installing or updating a plugin, isolate it instead of disabling or replacing several components at once. With dashboard access, WordPress’s Health Check troubleshooting mode can help test changes without affecting ordinary visitors. If that is not available, back up first, deactivate plugins, and reactivate them one at a time, checking the site after each activation. When the problem returns, the last change is a useful lead, not conclusive proof; check compatibility and logs. See WordPress troubleshooting guidance, Health Check troubleshooting instructions, and the Learn WordPress lesson on plugin and theme conflicts.
9. Theme conflict
If the issue appeared after a theme change, test with a default WordPress theme to see whether the problem depends on the active theme. Make sure the test will not overwrite or discard custom theme work, and back up first. You can also use Health Check troubleshooting mode where available. WordPress outlines conflict diagnosis in its troubleshooting documentation and Health Check instructions.
10. PHP version or compatibility problem
A PHP-related error may involve the server’s PHP version or code that is not compatible with it; the error alone does not tell you which. Review the server and configuration information in Tools > Site Health, then confirm supported PHP settings with your host. Before a version change, check compatibility for the active WordPress version, theme, and plugins. Do not change the server version simply because PHP appears in an error message. WordPress describes PHP and compatibility as possible error sources in its common-errors guide and documents Site Health at Site Health screen.
11. Memory-limit failure
A memory-limit failure is one possible explanation for a critical error, not a diagnosis that applies to every blank or broken page. Check the error log and hosting configuration first. Ask your host to confirm the limit and the appropriate remedy before changing it, especially if you do not manage the server. WordPress includes memory-related failures among possible issues in its common-errors guide.
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 problemsChanges and URL problems
12. Changes appear not to take effect
If “You Make Changes and Nothing Happens,” first confirm that you edited the intended page on the intended site and that the change was saved or published. If the correct content is present in the editor but not visible publicly, identify which caching layers apply to your site and consult their documentation or your host. WordPress lists this symptom in its common-errors guide; the right next step depends on the site’s setup.
13. Pretty permalink URLs return 404
If the home page works but attractive, human-readable post URLs return 404 errors, check the rewrite configuration. WordPress notes that Apache’s mod_rewrite may need to be enabled. If you have dashboard access, open Settings > Permalinks and save the settings to refresh rewrite rules; this is a useful check, not a fix for every server configuration. If you are unfamiliar with .htaccess or server settings, ask your host to check them. See the WordPress permalink troubleshooting guidance.
14. Custom post type URLs return 404
For a custom post type that returns 404 while other pages work, check whether a page has the same name as the post type; duplicate names can cause conflicts. Then open Settings > Permalinks and save the settings to flush rewrite rules. WordPress covers both checks in its common-errors guide.
15. Uploaded images or files produce 404 errors
If uploaded files return 404, check whether the problem is limited to those URLs and ask the host to verify the server’s rewrite configuration. WordPress notes that upload-related 404s can be associated with mod_rewrite; that does not establish an image-plugin fault. The WordPress common-errors guide identifies the issue in connection with rewrite configuration.
When to stop and contact your host
- The error points to a database service, server response, PHP configuration, or rewrite setting you cannot inspect safely.
- You are unfamiliar with
.htaccessor other server-side files. - The issue persists after a backup and a controlled plugin or theme test, or the logs do not make the failing component clear.
- An upgrade appears incomplete and you cannot confirm which changes are safe to reverse.
When you contact support, provide the exact message, when the problem began, whether it affects the front end or dashboard, and any relevant log details you can share safely. This gives the host a clearer starting point than a general report that the site is broken.
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.
