Incident Post-Mortems
Marketing claims are cheap; diagnostic logs are not. These are engineering post-mortems of the recoveries we perform — the symptom, the evidence, the root cause, and the exact commands that fixed it.
Details are anonymized and composited from recurring incidents of the same failure class to protect client confidentiality.
Post-Mortem: ERR_TOO_MANY_REDIRECTS After an SSL Migration
Symptom: ERR_TOO_MANY_REDIRECTS on every page for every visitor
Cloudflare (proxy) · Ubuntu 22.04 · Apache 2.4 · PHP 8.2 · WordPress
Post-Mortem: Host Suspension From a Hidden Cryptominer
Symptom: Account suspended by host; "Resource Limit Is Reached" (508) errors for weeks prior
Shared cPanel/CloudLinux · Apache 2.4 · PHP 8.1 · WordPress · MySQL 8.0
Post-Mortem: Magento 28-Second Loads After a Catalog Import
Symptom: TTFB of 20–30 s on category pages; admin timeouts; abandoned carts spiking
AlmaLinux 9 · NGINX 1.24 · PHP-FPM 8.2 · MySQL 8.0 · Magento 2.4 · Redis 7
Post-Mortem: White Screen After a Forced PHP 8.2 Upgrade
Symptom: Completely blank page on every URL, including wp-admin
Managed LAMP hosting · Apache 2.4 · PHP 8.2 · WordPress · custom child theme
Post-Mortem: Japanese Keyword Hack via mu-plugins Backdoor
Symptom: Google results showing Japanese spam titles; "This site may be hacked" SERP label
Shared cPanel hosting · Apache 2.4 · PHP 8.1 · WordPress · MySQL 8.0
Post-Mortem: WooCommerce Checkout 504s From a Table Lock
Symptom: HTTP 504 on /checkout during traffic peaks; storefront intermittently slow
Ubuntu 22.04 · NGINX 1.24 · PHP-FPM 8.2 · MariaDB 10.11 · WooCommerce
Every repair ends with a report written exactly like these.