An HTTP 502 response means a server acting as a gateway or proxy received an invalid response from an upstream server. In proxy-based hosting stacks, the visible web server may not be the component that actually failed.
- Retest a simple static file and compare it with the dynamic page that returns 502.
- Review web-server and application logs available to the account.
- Check whether the error follows a PHP-version change, application deployment, restart-sensitive feature, or resource fault.
- If only one application endpoint fails, inspect that application before changing DNS or SSL.
Gateway configuration and upstream service health may be server-controlled. If the account interface exposes no relevant control, preserve the error details rather than making unrelated application changes.
