WordPress

WordPress loaded but could not log in to its database. Test the credentials in wp-config.php, then check the database server, connection limits, disk space and damaged tables, in that order.

PHP hit a fatal error, almost always in a plugin, theme or after a PHP upgrade. Use the recovery mode email, read the exact error in the log, and switch off the culprit without losing anything.

Two rules are sending visitors back and forth. Trace the loop with curl or the Network tab, then fix the WordPress URLs, the HTTPS setup behind your CDN, or the duplicate redirect rule causing it.

Your SSL certificate expired, or the visitor’s clock is wrong. Confirm which with one command, renew the certificate, and fix the DNS, CAA or blocked-challenge problem that stopped it renewing.

Contain it, preserve evidence, find how they got in, then rebuild from clean sources and rotate every credential. The order matters, and skipping a step is how sites get reinfected.

A DNS or hosting move often drops the records that prove your email is genuine. Check MX, SPF, DKIM and DMARC with dig, read the Authentication-Results header, and fix WordPress mail sending.

Editor stuck loading, or pages lost their styling after an update? Regenerate the builder’s CSS, clear caches in the right order, read the console and logs, then find the conflict or roll back.

The web server hit something it could not handle and gave up. Read the error log, test .htaccess, then check permissions, the PHP handler and security rules, in that order.

A proxy in front of PHP got a broken answer (502) or no answer in time (504). Read the upstream error, check PHP-FPM, then find the slow request.

Your account or server ran out of PHP workers, processes or CPU. Find which limit was hit, find the URLs and bots eating it, then cache, block or upgrade.

Cloudflare is up, but it could not get a good answer from your server. Each code names a different failure. Test the origin directly, then fix firewall, SSL or timeout.

The browser could not turn your domain into an IP address. Check the domain status in RDAP, then nameservers, records, glue and DNSSEC, then your own DNS cache.