Disable plugins in WordPress without admin access
Disable WordPress plugins through files or database access when wp-admin is unavailable because of a 500, 502, or database error.
Step-by-step guides for checking logs, rolling back changes, fixing DNS, repairing WordPress config, and tracing nginx upstream issues.
Disable WordPress plugins through files or database access when wp-admin is unavailable because of a 500, 502, or database error.
Learn how to inspect access logs, error logs, status codes, timestamps, upstream failures, and recent changes during HTTP outages.
Use a safe rollback workflow for website errors by preserving evidence, restoring the smallest change, and verifying recovery.
Repair redirects, permalink rules, rewrite configuration, and route mismatches that cause 404s or redirect loops after site changes.
Trace a 502 Bad Gateway across browser, CDN, reverse proxy, origin server, upstream app, and logs to find the failing layer.
Check nginx upstream definitions, Unix sockets, proxypass targets, service health, permissions, and logs when nginx returns 502.
Flush DNS cache and compare resolvers to separate local browser or ISP cache problems from domain-wide DNS record issues.
Audit DNS records after hosting or nameserver changes by checking A, AAAA, CNAME, MX, TTL, and authoritative nameserver answers.
Check and repair WordPress database settings in wp-config.php, including database name, user, password, host, charset, and table prefix.
Verify MySQL or MariaDB service health, connection limits, credentials, database availability, and hosting status for WordPress errors.
Stabilize Chrome when pages crash by testing extensions, profiles, cache, hardware acceleration, browser updates, and device conditions.
Check WordPress ownership and permissions when uploads, plugins, themes, cache files, or PHP includes fail after a migration or deploy.
Check PHP version, required extensions, memory limits, and fatal errors when WordPress fails after hosting, plugin, theme, or core changes.
Clear WordPress cache layers in the right order so stale pages, object cache, or CDN responses do not hide the real fix.
Turn on WP_DEBUG_LOG without displaying errors publicly so WordPress 500, white screen, plugin, theme, and PHP failures leave evidence.
Recover from a WordPress white screen when the admin area is unavailable by checking debug logs, plugins, themes, PHP memory, and recent changes.
Restore WordPress files and database carefully after a failed update, bad migration, broken plugin, or damaged wp-config.php change.
Use wp-config.php as the starting reference for database credentials, debug logging, salts, table prefixes, and environment-specific WordPress settings.