This knowledge base explains common WordPress error messages. You’ll find server errors (like 500–504), PHP errors, login and access issues, and messages that appear after updates or changes.
For each error, you’ll learn what it means, the most likely causes, and which checks you can safely run to pinpoint the issue.
A 500 Internal Server Error can take your WordPress site offline instantly, but the cause is usually traceable and fixable.
This error means WordPress can’t connect to your database, which takes your entire site offline.
The “There has been a critical error on this website” message sounds severe, but it’s usually fixable with a clear step-by-step plan.
The White Screen of Death is a notorious WordPress error where your site shows nothing but a blank white page.
A redirect loop makes your site unreachable. The steps below break the loop and bring your site back online.
This error means your site needed more memory than was available.
This maintenance message usually isn’t serious and can be fixed quickly by removing the .maintenance file.
A 403 Forbidden error on your WordPress site is frustrating, but it’s usually straightforward to fix once you address the underlying cause step by step.
If you keep getting redirected to the login screen, this step-by-step guide will help you regain access.
This message means WordPress thinks you don’t have the right permissions. The steps below usually restore access quickly.
A 502 Bad Gateway error is usually temporary, but you still want to know the cause fast and get your site back online.
A 503 Service Unavailable means your server can’t process requests temporarily. These steps help you fix it and prevent it from returning.
A 504 Gateway Timeout means a server responds too slowly, so your WordPress site won’t load. With this step-by-step plan you can get your site back online.
A 404 Not Found error on a WordPress page is frustrating, but usually quick to fix with a few targeted steps.
The “HTTP error” when uploading media is vague and frustrating, but usually fixable with a few targeted checks.
This error means a PHP script ran too long and was stopped by the server.
A small mistake in PHP code can take your whole site down. The steps below usually fix it fast.
If WordPress doesn’t send email, you miss contact forms and notifications. This guide helps you fix it.
All 5xx codes mean the server couldn’t complete the request. The key difference is the cause and who can fix it.
Start with performance topics: slow wp-admin, high TTFB, CPU spikes, and intermittent slowness.
