Step-by-step fixes for WordPress, digital tools, e-commerce, and online business.
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
An update stopped, but what failed: downloading, unpacking, copying files, or running the new version? Keep the full message. It tells you where to start and whether another update attempt is appropriate. First open the homepage and dashboard. If they still work, you have time to investigate. If they show a maintenance message or critical … Read more
If scheduled posts, backups or maintenance tasks miss their times, first determine whether they never started or started and failed. One plugin’s blocked queue differs from a shared WP-Cron trigger problem. Check the configured time, server-trigger arrangement and task output before replaying jobs or changing scheduling settings. Guide reviewed: October 8, 2026. Interface labels may … Read more
A 503 page means the responding service cannot handle the request at that moment. Compare the dashboard, a dynamic post and a cached page before changing WordPress files: the failure may belong to hosting, a proxy or maintenance. Use the outage scope and incident time to decide which service and workload to investigate. Guide reviewed: … Read more
A Site Health REST API alert needs its endpoint, status and full message to become useful. A timeout, authentication refusal and unexpected HTML response lead to different investigations. Keep the diagnostic details and compare them with one harmless action that uses the affected feature. Guide reviewed: October 8, 2026. Interface labels may vary by version, … Read more
A 403 response can block a page, editor save or upload at WordPress, the web server or a firewall. First identify the exact action and whether access is intended for that account. Use matching logs and a working comparison to separate a valid restriction from a filesystem or security-rule fault. Guide reviewed: October 8, 2026. … Read more
An image can fail before reaching the server, while being saved or while WordPress generates resized versions. Check the exact message and whether an attachment exists before retrying the same file. Compare one small supported image with the failed file, then investigate the stage the evidence identifies. Guide reviewed: October 8, 2026. Interface labels may … Read more
“Allowed memory size exhausted” means one PHP request reached its memory allowance. Start by identifying the action that failed: opening a page, importing rows, building a backup or processing an image. A higher limit may help a legitimate job, but it cannot explain a sudden increase in memory use. Check the active allowance and compare … Read more