WordPress White Screen of Death: How to Diagnose It Safely
A blank page means PHP stopped and the error is hidden, not absent. Here is the exact command-level sequence to find the cause without exposing anything.
WORDPRESS RESCUE JOURNAL
Understand the symptom.
Decide without making it worse.
Specialist-reviewed guides for broken, compromised or blocked websites. Diagnosis, security and practical decisions without blind recipes.
START WITH THE VISIBLE SYMPTOM
WordPress repair guidance organised by incident.
These guides help you preserve evidence, avoid risky shortcuts and decide when the problem needs a controlled technical intervention.
01
WordPress critical error
Understand the fatal error behind the generic message and the evidence worth preserving before changing plugins or themes.
Open the guide 02WordPress white screen
Learn why a blank page should be diagnosed through protected logs instead of exposing debug information publicly.
Open the guide 03Malicious redirects
See where conditional redirects hide and why clearing one server rule may not remove the infection.
Open the guide 04WordPress admin lockout
Separate a legitimate access problem from signs of compromise and recover control without leaving a bypass.
Open the guide 05A plugin update broke the site
Compare rollback, compatibility repair and safe update routes when production fails after a release.
Open the guide 06WooCommerce checkout failure
Trace the sales journey from browser and session through payment callback, order creation and stock.
Open the guideExplore: Errores y diagnóstico
Errors & Diagnosis
Malware & Security
Malware y seguridad
Recovery & Prevention
Recuperación y prevención
WooCommerce Critical
WooCommerce crítico
Read the guide ↗
Error Establishing a Database Connection in WordPress
This message means WordPress could not reach the database with its current settings. It rarely means data loss. Here is how to triage and fix it safely.
WordPress 500 Internal Server Error: Finding the Real Cause
A 500 is the server refusing to finish the request. The detail is in the log, not on screen. Here is the safe command-level order to work through it.
“There Has Been a Critical Error on This Website”: What to Do
WordPress shows this when a fatal PHP error stops the page. The recovery email and the log name the component. Here is how to act on them, step by step.
WordPress 502 Bad Gateway: What It Means and How to Fix It
A 502 means the front-end server got an invalid response from PHP behind it. Usually a timeout, a crashed worker or a resource limit — here is how to trace it.
WordPress Memory Exhausted Error: Causes and Safe Fixes
“Allowed memory size exhausted” means PHP hit its ceiling. Raising it is only right once you know what consumed it. Here is how to check and fix it.
Maximum Execution Time Exceeded in WordPress: What to Check
PHP stopped a request that ran too long. The fix is rarely a bigger timeout — it is finding the operation that should not take that long.
WordPress HTTP Error When Uploading Images: How to Fix It
The media library says “HTTP error” and stops. It is usually memory, file size, permissions or the image library — and each has a different fix.
WordPress Redirect Loop: Fixing ERR_TOO_MANY_REDIRECTS
The browser gave up because two rules keep bouncing the request. Find the pair that disagrees — usually about HTTPS or www — before changing settings.
Locked Out of WordPress Admin: Safe Ways Back In
Losing admin access can be a password, a plugin lockout, a broken login or a compromise. Establish which — then use the right recovery route.
WordPress Redirecting to Spam Sites: How to Find the Injection
Malicious redirects often fire only on mobile or from search. Here is where the payload hides and the exact commands to find it before you clean.
WordPress Japanese Keyword Hack: Detection and Cleanup
Google indexes Japanese pages you never made because the payload only serves crawlers. Here is how to detect the cloaking and clean it.