Practical WordPress and website diagnostics covering hosting, DNS, SSL, errors, performance, publishing, media, email, security, and site management. Guides focus on identifying the failing layer before changing settings.
A parse error after a snippet edit or update means PHP could not interpret a file as valid syntax. The message’s file path is the starting point; its line number may identify where PHP noticed an earlier missing quote or bracket. Restore access with a known working copy, then investigate the specific change before reapplying … Read more
If an import, backup or update stops with “Maximum execution time exceeded,” PHP ended a request at its execution limit. Check how far the task progressed before retrying: some records or files may already exist. The steps below distinguish oversized work, a repeatable failing item and a separate server timeout so you can choose a … Read more
A 401 response means the requested resource did not receive authentication it accepts. That may happen in the WordPress editor, at a hosting protection screen or during an external API request—and each one can expect a different login method. Start with the exact URL that returned 401 and the action that triggered it. This keeps … Read more
A 413 upload error means the responding service rejected a request that exceeded its accepted size. One attachment, a combined form submission and an import package can reach different limits. Compare a small test with the failing request, locate the rejecting layer and choose a suitable file size or a documented allowance. Guide reviewed: October … Read more
When the editor reports an invalid JSON response after Save or Publish, preserve your text and check whether the server stored the change. The editor may have received HTML, a redirect or warning text instead of the structured reply it expected. Follow the actual failed request to distinguish authentication, routing, security rules and PHP output. … Read more
A 429 response during checkout, an import or a background integration means a service is limiting request frequency. Pause the repeated action, read any waiting instruction and check whether earlier attempts already created an order or record. This guide distinguishes the WooCommerce Store API from other APIs and hosting limits, then shows how to reduce … Read more
A page that waits and then returns 504 indicates a gateway did not receive its upstream response in time. A checkout or import may still finish behind the error page, so check its result before retrying. Compare cached and dynamic requests, match the failure with server logs and reduce work in the request that actually … Read more
If a site begins returning 502 after a PHP version switch or server change, record the changed setting and failure time before rolling back. The gateway received an invalid upstream response; the status alone does not identify the faulty WordPress component. Use the maintenance history and service logs to recover the affected path and plan … Read more
cURL error 28 means a server-side network operation reached its allowed timeout. The rest of your website can work while one plugin cannot contact an external API or your own site. Start with the destination and complete message, then compare DNS, connection and response timing from the hosting server. Guide reviewed: October 8, 2026. Interface … Read more
A blank media grid does not prove your image files disappeared. Compare the library list, one attachment’s preview and its original file before re-uploading media or deleting records. These checks distinguish a filtered view, a failed interface request, a missing generated size and an unavailable file. Guide reviewed: October 8, 2026. Interface labels may vary … Read more