Understand the symptom.
Decide without making it worse.

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.

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.

“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.

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.

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.

The browser gave up because two rules keep bouncing the request. Find the pair that disagrees — usually about HTTPS or www — before changing settings.

Losing admin access can be a password, a plugin lockout, a broken login or a compromise. Establish which — then use the right recovery route.

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.

Google indexes Japanese pages you never made because the payload only serves crawlers. Here is how to detect the cloaking and clean it.

The warning appears in the results and costs clicks immediately. Removing it needs a genuine cleanup, not just a reconsideration request. Here is the order.

Reinfection means the effect was removed but the persistence or entry point was not. Here are the five places it survives and how to check each.

An admin you did not create is not a glitch. Treat it as evidence of compromise and preserve it before deleting. Here is what to capture and check.