When WordPress is offline, throwing server errors or returning a blank page, the goal is to restore service without losing the ability to go back. The same visible outage can come from very different causes, so the safe path is to read the evidence before disabling or replacing anything.
Step 1 — Classify the outage
What exactly do you see? A 500 or 502, a database-connection error, a critical-error screen, a blank page, or a hosting suspension notice each lead down a different path. Note the exact message, the time it started, and whether it hits the whole site or one route. Check whether /wp-admin/ still loads — a working admin narrows the problem dramatically.
Step 2 — Read the logs before touching files
Enable logging in wp-config.php (WP_DEBUG_LOG on, WP_DEBUG_DISPLAY off) and read /wp-content/debug.log, plus your host’s PHP and server error logs. The log usually names a file and line, reports exhausted memory, or shows a timeout — which is far more reliable than guessing from the visible symptom.
Is your website affected right now?
Send the URL and the symptom you can see. Jordi Ensenyat reviews the case personally and defines the scope and quote before anything is changed. This form never asks for passwords.
Step 3 — The standard isolation sequence
- Plugins: rename
/wp-content/pluginstoplugins_offover SFTP. If the site returns, re-enable one by one to find the culprit. - Theme: rename the active theme’s folder so WordPress falls back to a default theme.
- .htaccess (Apache): rename it to
.htaccess_oldand reload; if that fixes a 500, regenerate clean rules by re-saving permalinks rather than leaving the site without them. - Core files: reinstall WordPress core over itself — it replaces core files without touching your content — if the log points at missing or corrupt core files.
Step 4 — When it is infrastructure, not WordPress
If every site on the server is down, or the host’s status page shows an incident, the fastest route is the provider — not your files. A database-connection error across all sites, a disk-quota message, or a suspended account are infrastructure problems that no amount of plugin renaming will fix.
Preserve first, always
Back up the current broken state before you change anything. If there is no recent backup, that is the single most important thing to fix once service is restored.
When to escalate
Call a specialist if the outage touches a store, there is no viable backup, the logs point at core or database corruption, or the site is also behaving strangely (redirects, unknown users) which suggests a compromise. Send the exact error, the start time and the recent changes and the incident can be assessed before any access is granted.
EVIDENCE-LED WORDPRESS RECOVERY
A controlled route back from a broken WordPress site
In WordPress form, SMTP and email delivery repair, the visible symptom may be far from the cause. The objective is to trace the full route from browser submission to mailbox and restore verifiable delivery. A site that is offline or returning server errors can have several causes with the same visible symptom. The safest repair starts by preserving a recovery route, checking recent changes and reading the available evidence before disabling or replacing anything.
What we verify
- The complete journey, not only the screen where the error appears
- External dependencies, logs and evidence before configuration changes
- HTTP status, PHP and web-server logs around the first failure
- Recent plugin, theme, core, PHP or hosting changes
- Database availability, disk capacity, memory and file integrity
- Front end, admin, forms and business-critical journeys after repair
What a verified outcome means
Close-out documents the cause found, the change applied and the tests performed. The result must be observable and repeatable—not a feeling that it “seems to work”.
BEFORE THE ASSESSMENT
Common questions about this WordPress incident
How do you verify that the problem is genuinely resolved?+
The affected journey is reproduced, its dependencies are checked and post-change evidence is recorded.
Can you repair WordPress without making the outage worse?+
The first objective is to preserve a backup or rollback route and collect evidence. Changes are then limited to what the diagnosis supports.
How quickly can an emergency WordPress repair start?+
Availability and urgency are confirmed during assessment. The scope, access required and quote are agreed before intervention begins.
What should I send before access is granted?+
Send the URL, visible error, approximate start time, recent changes and business impact. Do not send passwords through the public form.