WordPress guides
WordPress critical error: regain access and fix the cause
Fix a WordPress critical error without adding a plugin: recovery mode, PHP logs, the faulty plugin, rollback, and verification.
Read the guide →WordPress errors: diagnosis and troubleshooting
Critical error, inaccessible screen or server timeout: identify the cause of a WordPress failure and follow a repair suited to your access.
16 guides
WordPress guides
WordPress database connection error: diagnosis and solutions
Repair WordPress’s database connection: configuration, MySQL access, an unavailable server, or missing tables, with no required plugin.
Read the guide →WordPress guides
WordPress 504 error: identify the timeout without blindly retrying
Diagnose a WordPress 504 error: gateway, PHP, or external API, using three paths without a new plugin or repeating a sensitive operation.
Read the guide →WordPress guides
WordPress HTTP 500 error: identify the failure and restore your site
Fix a WordPress 500 error with practical steps: plugins, SFTP, PHP logs, .htaccess code and memory, with or without a troubleshooting plugin.
Read the guide →WordPress guides
PHP memory exhausted in WordPress: fix the failing action
Does a WordPress action exhaust PHP memory? Identify its effective limit, compare processing in batches and verify the result on a copy.
Read the guide →WordPress guides
WordPress: fix “Headers already sent” at the PHP output source
Fix “Headers already sent” in WordPress: locate the first output, check the modified file or redirect and validate recovery.
Read the guide →WordPress guides
WordPress error 414: shorten the request and fix its cause
Does a WordPress search or bulk action fail with error 414? Identify the oversized URL and correct batching, the component or server.
Read the guide →WordPress guides
WordPress error 431: reduce headers and regain access
Is WordPress showing error 431? Compare the site’s cookies, fix growing headers, and check the limit enforced by the server.
Read the guide →WordPress guides
ERR_CONTENT_DECODING_FAILED in WordPress: fix response compression
Does a WordPress page fail despite status 200? Compare compressed responses, isolate the responsible layer, and restore consistent decoding.
Read the guide →WordPress guides
WordPress log not being created: find where errors are going
Is debug.log missing or empty in WordPress? Check configuration, the private path, and the PHP context, then verify logging without exposing errors.
Read the guide →WordPress guides
Cloudflare errors 525 and 526 on WordPress: repair origin TLS
Does Cloudflare show 525 or 526 on WordPress? Identify the origin server, check its certificate and TLS negotiation, then verify the repair.
Read the guide →WordPress guides
Cloudflare 524 during a WordPress import
Check whether a WordPress import or export continued after a Cloudflare 524 error, then choose a recovery method that preserves completed work.
Read the guide →WordPress guides
WordPress 502 error: diagnose the proxy and origin server
Fix a WordPress 502 error: identify the failing relay, check the origin, PHP and routing, then verify recovery without blind retries.
Read the guide →WordPress guides
Intermittent WordPress 503 error: find the cause and stabilize the site
A WordPress site intermittently displays 503? Distinguish maintenance, overload and processing, then verify stable recovery with your host.
Read the guide →WordPress guides
WordPress 403 error on a public path: find the blocking rule
A public WordPress path returns 403? Compare requests and logs, then correct the relevant access setting, permissions or security rule.
Read the guide →WordPress guides
WordPress 429 error: fix requests made too frequently
Resolve a WordPress 429 denial: respect the delay, identify the service limiting requests and correct the rate or rule without turning off security.
Read the guide →