A 502 Bad Gateway Error occurs when one server on the internet receives an invalid response from another server. In the context of WordPress, it usually means your PHP processing is taking too long or crashing, and the web server (like Apache, NGINX, or LiteSpeed) is timing out.
Step-by-Step Troubleshooting
1. Clear Your Cache and Reload
Sometimes the 502 error is a temporary hiccup. Clear your browser cache or try a different browser. If you use a caching plugin or a CDN like Cloudflare, purge the cache there as well.
2. Deactivate Your CDN / Firewall Temporarily
If you are using Cloudflare or Sucuri, a routing issue on their end can cause a 502 Bad Gateway. Try pausing Cloudflare temporarily from your Cloudflare dashboard to see if the issue is with the origin server (Hosticky) or the CDN.
3. Check for Plugin and Theme Conflicts
A heavy plugin script can cause PHP to timeout. Rename your wp-content/plugins folder to plugins_old via the Hosticky File Manager to deactivate all plugins instantly. If the site loads, you know a plugin is the culprit.
4. Increase PHP Max Execution Time
If a script just needs more time to run, increasing your PHP limits can help. In your Hosticky control panel, navigate to the MultiPHP INI Editor and increase max_execution_time to 300.
Note: Hosticky servers are highly optimized for speed and reliability. If you experience persistent 502 errors, contact our team to investigate the server error logs.
