WordPress errors usually point to a failing layer, not a single universal fix. Before editing files or switching off plugins, record the exact message, URL and time, check recent changes, and confirm that a usable backup exists. For changes that could affect visitors or data, reproduce the issue on staging.
Quick checks before troubleshooting
- Check whether the issue affects everyone, one account, one browser or one network.
- Note the affected URL, time and timezone, exact steps, and recent updates or deployments.
- Check hosting, PHP, web server, database and WordPress logs for the same time.
- Avoid displaying debug errors publicly. Keep logs private because they can reveal paths or data.
- Change one variable at a time and record how to reverse it.
- After a repair, test the affected flow and nearby pages, forms, checkout and integrations.
30 common WordPress errors
1. White screen or blank page
Check: PHP and web server logs around the first failure, plus recent code or plugin changes. Avoid: editing memory limits or disabling every plugin before identifying evidence.
2. “There has been a critical error on this website”
Check: the recovery email, WordPress fatal-error log and hosting PHP log. Next: use recovery mode or staging to isolate the component. Do not share recovery links publicly.
3. HTTP 500 internal server error
Check: server logs, deployment history, PHP errors and rewrite configuration. Next: ask the host to confirm server-side limits. A 500 response alone does not identify the cause.
4. Error establishing a database connection
Check: database service status, credentials, host value, connection limits and recent configuration changes. Next: involve the host or database administrator before running repair commands.
5. Connection timed out
Check: whether the timeout is limited to one request, whether the server is reachable, and the relevant proxy and server logs. Next: compare resource use with the host’s limits.
6. “Briefly unavailable for scheduled maintenance” remains on screen
Check: whether a core, plugin or theme update is still running and whether files changed part-way through. Remove a maintenance marker only after confirming no update process is active and keeping a backup.
7. PHP syntax or parse error
Check: the file and line named in the private error log and the latest code edit. Restore the known-good file or correct the code in staging; do not edit production code by guesswork.
8. Image upload fails
Check: file type and size, available storage, upload limits, permissions, and PHP or proxy logs. Avoid broad permission changes such as 777.
9. Administrator cannot log in
Check: account status, password reset email, URL and HTTPS settings, security logs and recent access changes. Preserve another authorised administrator account while diagnosing.
10. WordPress or extension update fails
Check: update logs, available disk space, file ownership, network access and compatibility. Do not upload arbitrary files over a live site; make a backup and follow the official update or recovery procedure.
11. Website email is not sent
Check: whether the message was generated, mail logs, sender domain authentication and recipient rejection. A form’s success notice does not confirm delivery. Use a monitored mail provider and test delivery.
12. HTTPS certificate warning
Check: certificate validity and hostname, renewal status, proxy/CDN mode and origin configuration. Do not disable certificate checks to hide the warning.
13. Plugin conflict or feature stops working
Check: logs and the first change before the failure. Reproduce on staging and test likely components one at a time. Avoid deactivating security, payment or cache components at random on production.
14. Theme layout or template breaks
Check: browser console, server logs, recent theme changes and template compatibility. Test a supported default theme on staging before changing the live theme.
15. Internal links lead to missing pages
Check: the destination URL, redirect chain, deleted content and recent permalink changes. Update links or redirect only to a genuinely relevant replacement.
16. Pages load slowly
Check: server response, browser network timings, large assets, third-party scripts, database activity and cache behaviour. Measure before installing another optimisation plugin.
17. Hosting bandwidth or resource limit is reached
Check: the host’s usage report, traffic pattern, backup jobs and large downloads. Reduce avoidable transfers and agree capacity changes with the provider.
18. RSS feed is invalid or unavailable
Check: the feed URL, response status, recent template or plugin changes and XML output. Correct the source of malformed output rather than inserting arbitrary whitespace fixes.
19. Sidebar or content appears in the wrong place
Check: browser console, HTML structure, CSS changes and the affected template at different widths. Validate the markup and isolate recent style changes.
20. Theme reports a missing stylesheet
Check: that the correct installable theme folder was uploaded and that its style.css is at the expected location. Do not upload a vendor’s entire download bundle as the theme.
21. PHP memory limit is exhausted
Check: the fatal error, workload, PHP configuration and plugin or theme activity. Raising a limit may only hide inefficient code; confirm the host allows the change and monitor the result.
22. Email reaches spam or is rejected
Check: bounce messages, sender alignment, SPF, DKIM and DMARC configuration, sending reputation and recipient filters. Coordinate DNS changes with the domain owner.
23. HTTP error while uploading media
Check: the browser response, server and PHP logs, image dimensions, storage and request-size limits. Test with a smaller copy to isolate size-related failures without replacing the original.
24. WordPress notifications are duplicated or missing
Check: form or order logs, plugin hooks, mail queue and duplicate integrations. Test one submission and trace its delivery end to end.
25. Social sharing shows the wrong image or title
Check: Open Graph metadata in the page source, the canonical URL, image accessibility and the social platform’s cache. Correct the page metadata first, then request a new preview where supported.
26. PHP code produces a parse error after editing
Check: the exact file and line in the error log and the last code change. Restore a known-good copy or use version control; avoid making additional production edits until syntax is valid.
27. Theme update is incomplete
Check: the theme version, update log, file ownership and whether customisations were made in the parent theme. Keep custom code in a child theme or managed codebase and use the vendor’s supported recovery steps.
28. Custom post type URLs return 404
Check: whether the content type is registered, its rewrite settings and the generated URL. Refresh rewrite rules through the supported application flow after confirming the configuration; check redirects and server rules too.
29. Dashboard controls do not respond
Check: browser console and network errors, JavaScript optimisation, permissions and recent plugin changes. Reproduce in a clean browser session and staging before disabling extensions.
30. The site returns a generic server error
Check: the status code, request time, server logs and recent infrastructure changes. Ask the host to trace the request if the application logs do not contain it; do not assume every server error is a WordPress fault.
When to stop and escalate
Pause self-service changes if the site may be compromised, data may be damaged, checkout or personal data is affected, or a recovery step is unclear. Give the specialist the timeline, affected URLs, exact messages, recent changes, relevant logs and backup status. Never send passwords or personal data in a public support thread.
For an operational issue affecting a live WordPress site, see Ulement’s emergency WordPress support.
Sources checked on 20 October 2026: WordPress debugging, WordPress troubleshooting and WordPress backup guidance.