Best Ways to Troubleshoot Errors on Your WordPress Site

What do you do when your WordPress site breaks? If the answer is “open a support ticket saying my site is not loading”, you are in for a slow week. Support teams handle hundreds of tickets and, reasonably, give faster attention to the ones that arrive with information: what changed, what you tried, what the error log says.

There is a second reason to troubleshoot yourself first: a large share of WordPress problems are caused by a plugin or theme conflict that you can find in twenty minutes with a systematic approach, no support needed. This guide sets out that approach, from the quick checks to the layered isolation process, and finishes with how to ask for help effectively when you do need it.

Last updated: 2026 for WordPress 6.8 and PHP 8.2+.

Backup

Before you change anything, take a complete backup of files and database, even if the site is currently broken. Troubleshooting involves deactivating things, renaming folders and sometimes replacing core files, and you want a known state to return to. Use your existing backup plugin (UpdraftPlus, Solid Backups, BlogVault or Jetpack VaultPress Backup) or your host’s snapshot tool; if you have none, export the database from phpMyAdmin and download wp-content plus wp-config.php over SFTP. Our backup plugin comparison helps if you need to pick one now.

Also check your admin email inbox. Since WordPress 5.2, a fatal error triggers recovery mode: WordPress emails a link that lets you log in with the failing plugin or theme paused, and the message names the file that failed.

Initial Steps

Several common faults have quick fixes. Run through these before deeper work:

• Clear caches. Browser cache, your caching plugin, server cache and CDN cache, in that order. A surprising number of “errors” are a cached error page from a problem already fixed, including the 508 error.
• Refresh permalinks. Go to Settings > Permalinks and click Save Changes without altering anything. This rewrites the rewrite rules and fixes many 404s on posts that exist.
• Regenerate .htaccess. On Apache, a corrupt .htaccess causes 500 errors. Download it over SFTP as a backup, delete it, then save permalinks again to create a clean one. On NGINX there is no .htaccess; skip this step.
• Check the URLs. Under Settings > General, WordPress Address and Site Address should match and use https://. A mismatch after a migration or SSL change causes redirect loops and mixed content.
• Check reading settings. Under Settings > Reading, “Discourage search engines from indexing this site” should be unticked on a live site. It gets left on after development more often than you would think.
• Read Site Health. Tools > Site Health lists failed scheduled events, an unreachable REST API, outdated PHP, missing modules and inactive-plugin clutter. The Info tab shows your PHP memory limit, upload limit and server versions.
• Check mail. If password resets or form notifications are not arriving, install an SMTP plugin (WP Mail SMTP or similar) rather than relying on PHP mail.
• Scan for malware. Unexpected redirects, spam pages or admin users mean a compromise, not a bug; follow our guide to scanning for hidden malware.

The Process Of Troubleshooting

The quick fixes handle common errors like the 502 error. When they do not, you need to isolate the cause, and the efficient way is by layer, starting where problems are most likely:

1. Plugins
2. Theme
3. WordPress core
4. Database and server

First, turn on logging so every step gives you evidence. Add to wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Errors now go to wp-content/debug.log instead of the screen. Read it after reproducing the problem; the file path in the message tells you which plugin or theme is involved. If the site is live and you would rather not deactivate things for visitors, the Health Check & Troubleshooting plugin adds a troubleshooting mode that disables plugins and switches themes for your session only.

Plugins

Plugins cause most conflicts because they are numerous, come from many authors, and change often. To find the one responsible:

• Deactivate all plugins. From the dashboard: Plugins > select all > Bulk actions > Deactivate. If you are locked out, rename wp-content/plugins over SFTP; details in our plugin deactivation guide.
• Check whether the problem is gone. If it persists with no plugins active, move to the theme layer.
• Reactivate plugins one at a time, testing after each. When the error returns, the last activated plugin is involved.
• Deactivate that plugin and continue reactivating the rest, since two plugins can conflict with each other rather than with WordPress.
• Update the culprit to the latest version, check its support forum for the same report, and if there is no fix, replace it.

Themes

Switch to a default theme (Twenty Twenty-Five or whichever is bundled) from Appearance > Themes, or rename the active theme’s folder over SFTP so WordPress falls back. If the problem disappears, it lives in the theme. Common fixes are updating the theme, reverting a recent edit to functions.php or a template, or clearing customisations made in the Site Editor (Appearance > Editor > Templates > Reset). If you edit theme files directly, use a child theme so updates do not overwrite your changes. Report anything that survives an update to the theme author with the debug log line.

Core Files

Corrupted core files are rare but happen after a failed update or a partial upload. The simplest fix is Dashboard > Updates > Re-install version 6.8.x, which replaces every core file without touching wp-content. If the dashboard is unavailable:

• Download the current release from wordpress.org and unzip it.
• Over SFTP, delete the site’s wp-admin and wp-includes folders. Do not touch wp-content or wp-config.php.
• Upload the fresh wp-admin, wp-includes and the root PHP files (everything except wp-content and wp-config-sample.php), overwriting what is there.
• Load the site. If a database update prompt appears, run it. Then reactivate plugins and your theme.

If the fault survives a clean core, look at the database and server: a corrupt table (repair via phpMyAdmin or WP_ALLOW_REPAIR), an exhausted PHP memory limit, or a PHP version the site’s code does not support. Site Health and the server error log will point at which.

Contacting Support

By now you know which component is at fault, and updating, rolling back or replacing it has either worked or not. If not, contact the developers of that plugin or theme. Premium products usually have a ticket system with a response in a day or two; free products on wordpress.org have a support forum where the author and volunteers answer as time allows.

Whichever you use, give them what they need: WordPress, PHP and plugin versions (copy from Site Health > Info), the exact error text from debug.log, the steps you took to isolate it, and a screenshot if the problem is visual. Search the forum first; the same issue has often been reported and answered. The general WordPress.org support forums are the right place for core or unclear issues. And for hosting-level problems (server errors, resource limits, mail), your host’s support has access you do not.

Which Canyon theme fits

The theme layer is easier to rule out when the theme follows WordPress standards and updates through the normal updater. Ours do, and they are kept compatible with each WordPress release and PHP 8.2+, so a theme conflict is rare and a fix is a version bump away. If your troubleshooting ends with “replace the theme”, Bloge for blogs and Business Way for business sites are both maintained and light.

The Wrap Up

Most WordPress errors are found by working down the layers, plugins, theme, core, then database and server, with logging turned on. When that is beyond the time you have, hiring a developer to do the same process is reasonable, and your notes will shorten their job. Either way, when you ask for support, be precise, be polite, and include everything you have learned so far; it is the fastest route to a fix.

Further reading from our partners: Online Casinos Fun.