Your site just crashed. Maybe you see a WordPress blank screen. Maybe the client calls first. This guide shows how to fix WordPress errors the quick way. You get causes, commands, and config fixes for every common problem.

Back up first. Use your host tool or an FTP client to copy files and the database. Test on staging when you can. Never debug blind on a live site.
Next, switch on WordPress debugging. Add the WP_DEBUG settings below to wp-config.php. Then read the log.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Good tools save hours. Install Query Monitor and the Health Check plugin. Troubleshooting Mode disables plugins for you only. Visitors never notice. Add WP-CLI and SSH for speed. Then open debug.log to read each WordPress error log entry. See the debugging guide.
A WordPress blank screen shows no message at all. Hidden WordPress PHP errors usually cause it. Newer versions show a WordPress critical error notice instead.
Recovery Mode emails a safe login link to the admin address. Check your spam folder too.
Four culprits appear most often. A WordPress plugin conflict, a WordPress theme conflict, low memory, or damaged core files. This table points you to the right fix.
| Cause | Log clue | First fix |
|---|---|---|
| Plugin conflict | Path inside wp-content/plugins | Rename the plugin folder |
| Theme error | Path inside the theme folder | Switch to a default theme |
| Low memory | “Allowed memory size” | Raise the limit |
| Damaged core | Missing file warnings | Reinstall core |
Read the log first. Then run wp plugin deactivate --all. Switch to the Twenty Twenty-One theme with wp theme activate twentytwentyone. Verify with wp core verify-checksums. Replace wp-admin and wp-includes if checks fail. Our full white screen guide goes deeper.
A 500 error leaves your WordPress site not loading. It is a vague WordPress crash message. The server log holds the real answer.
Rename .htaccess first. Then raise limits in php.ini. Finally set file permissions to 755 for folders and 644 for files.
On Apache, check .htaccess and mod_rewrite. Nginx has no such file. Read its error.log and PHP-FPM status instead. Caching and security plugins often write bad rules after updates. Always test one change at a time.
This error means WordPress cannot reach MySQL. These WordPress database errors trace back to four DB_ values in wp-config.php.
Knowing how to fix WordPress errors like this starts with basics. Test the login in phpMyAdmin. Confirm the database host.
Add the constant below. Then visit /wp-admin/maint/repair.php or run wp db repair. Remove the constant afterwards. The repair page needs no login. Check my.cnf limits too. Crashed tables are one of the classic shared hosting problems.
define( 'WP_ALLOW_REPAIR', true );A parse error means a typo in PHP code. The message names the file and line.
Undo your last edit in functions.php. Restore a backup if that fails. Hidden WordPress PHP errors often start here.
Parse error: syntax error, unexpected '}' in /wp-content/themes/mytheme/functions.php on line 88Use an editor with linting. Run php -l functions.php before you upload. Keep themes in Git. Test on staging first. Never edit functions.php in the dashboard editor. One stray bracket can take down the whole site.
Seeing “Allowed memory size exhausted”? You hit the WordPress memory limit. Raise it in wp-config.php.
Timeouts need a longer max_execution_time in php.ini. Slow code is still the real culprit.
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );memory_limit = 256M
max_execution_time = 120Raising limits only hides the problem. Profile first with Query Monitor. Disable plugins one at a time. Check heavy imports and cron jobs. Then raise memory. Large uploads can also fill tmpdir on busy servers.
A 502 means the upstream gave a bad reply. A 504 means it took too long.
Both often trigger a WordPress site down alert. Check PHP-FPM, firewalls, and your CDN.
| Error | Typical cause | Where to look |
|---|---|---|
| 502 | PHP-FPM crash, firewall, CDN | PHP-FPM log |
| 504 | Slow script, low timeouts | Nginx or Apache timeout settings |
Read the PHP-FPM log. Raise pool limits if workers run out. Increase fastcgi_read_timeout or proxy_read_timeout. Bypass the CDN to test. Process caps are common shared hosting problems and cause the same errors.
Posts show a WordPress 404 error while the homepage works. That points to broken rewrite rules.
Re-save permalinks or run wp rewrite flush. A WordPress permalink problem may also mean mod_rewrite is off.
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPresstry_files $uri $uri/ /index.php?$args;Register custom post types before you flush. Flush once only. Never flush rewrite rules on every page load. On WordPress Multisite, flush each site separately. Many developers forget this step after adding a new post type or taxonomy.
Stuck in a loop after login? Check siteurl and home. Clear cookies and cache too.
After a move, WordPress migration issues like old URLs cause loops. Fix them with wp search-replace. Handle proxy headers in wp-config.php.
if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https' ) {
$_SERVER['HTTPS'] = 'on';
}
Disable redirect and security plugins first. Then reset both URLs in wp-config.php. Server, CDN, and plugin redirects often fight each other. Strange redirects to other domains? That may be a WordPress hacked site. Scan it with Sucuri SiteCheck.
A WordPress maintenance mode stuck screen follows a WordPress failed update. Delete the .maintenance file from your root folder.
Here is how to fix WordPress errors after updates. If WordPress auto-update failed, run a WordPress manual update.
| Symptom | Quick test | Fix |
|---|---|---|
| Stuck maintenance screen | Look for the hidden file | Delete it |
| Blank after update | Rename the plugin folder | Roll back the version |
| Layout broken | Switch theme | Update or replace theme |
Clone the site to staging. Use Health Check Troubleshooting Mode. Roll back one version at a time. Check changelogs for PHP support. A WordPress plugin conflict often follows a major release. Rename wp-content/plugins if you lose dashboard access.
Uploads fail when upload_max_filesize is too small. Edit limits in cPanel or Plesk. Bad file permissions also block uploads.
Emails vanishing? Use SMTP instead of default wp_mail(). Add SPF, DKIM, and DMARC records.
| Problem | Check | Fix |
|---|---|---|
| Upload fails | upload_max_filesize, post_max_size | Raise limits |
| Image errors | GD or Imagick | Enable the library |
| Mail not sent | wp_mail() setup | SMTP plugin and DNS records |
REST API errors, failed cron jobs, “link has expired” notices, and Gutenberg “Updating failed” messages appear often. Check permalinks, loopback requests, upload limits, and security plugins. Each fix is usually one setting. Read the common errors page for more.
Build a safer workflow. Use staging, Git, and tested backups. Update plugins one at a time. That is how to fix WordPress errors before they start.
Add uptime alerts and log monitoring. Keep PHP supported. Scan often with Sucuri SiteCheck. Remove unused plugins and themes.
Plugin conflicts. Deactivate plugins first. This simple WordPress error fix solves most cases.
Turn on logging. Read the newest line in debug.log. It names the file and the line.
Yes. Use an FTP client, your host’s File Manager, or WP-CLI. Every fix above works through files.
Yes, when you have SSH. It is faster and scriptable. Always back up before bulk commands.
Call them when several sites fail. Do the same if you cannot reach your files or server logs.
Test updates on staging first. Update one item at a time. Keep a fresh backup ready.
Every error leaves clues. Read the log, test one change at a time, and keep backups close. With this routine, fixing WordPress errors becomes calm work instead of a Friday-evening panic.