what is 502 bad gateway error?
The 502 Bad Gateway error is an HTTP status code that means that one server on the internet received an invalid response from another server. 502 Bad Gateway errors are completely independent of your particular setup, meaning that you could see one in any browser, on any operating system, and on any device. The 502 Bad Gateway error displays inside the internet browser window, just like web pages do.
How you might see a 502 bad gateway error
- 502 Bad Gateway
- 502 Service Temporarily Overloaded
- Error 502
- Temporary Error (502)
- 502 Proxy Error
- 502 Server Error: The server encountered a temporary error and could not complete your request
- HTTP 502
- 502. That’s an error
- Bad Gateway: The proxy server received an invalid response from an upstream server
- HTTP Error 502 – Bad Gateway
How to Fix a 502 Bad Gateway Error As a User
- Reload the page.
- Look for server connectivity issues.
- Check for any DNS changes.
- Sift through your logs.
- Fix faulty firewall configurations.
- Comb through your website’s code to find bugs.
- Contact your host.
How to solve
502 errors as a web developer
As a web developer or owner of the website, there are a few reasons why you may be experiencing a
502 Bad Gateway error on your origin server. Therefore, you may need to try various methods to resolve the issue. Reference the list of suggestions below:
- Check if your FQDN (fully qualified domain name) is resolving correctly by using our DNS test tool.
- Verify if your server is reachable by using a ping test or traceroute.
- Check your firewall logs if you are seeing unusual drops.
- If you’re a Cloudflare user, try disabling it as once you’ve reached a certain limit Cloudflare will return a
502 Bad Gatewayerror to your visitors.