Contents
How to remove 502 bad gateway error?
Troubleshoot a 502 error message
- Refresh the page.
- Start a new browser session or load the site on a different browser.
- Restart your computer and networking equipment.
- Clear your cache and cookies.
- Change your DNS server.
- Contact the website administrator or your internet service provider.
Why am I getting a 502 bad gateway error?
A 502 Bad Gateway Error means that the web server you’ve connected to is acting as a proxy for relaying information from another server, but it has gotten a bad response from that other server. It’s possible the server is overloaded or there are network issues between the two servers, and it’s just a temporary problem.
What does error bad gateway mean?
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.
How do I fix a bad gateway error?
How to Fix a 502 Bad Gateway Error
- 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.
What does error 502 mean on a website?
What Is Error 502? Error 502 is an HTTPs Status Code that is indexed or listed by developers to define a certain type of web error and its possible reasons. It occurs when a server tries to communicate to another server on the internet and receives an invalid response.
Why is IIS application Request Routing ( ARR ) error 502.3?
When working with IIS Application Request Routing (ARR) deployments, one of the errors that you may see is “HTTP 502 – Bad Gateway”. The 502.3 error means that – while acting as a proxy – ARR was unable to complete the request to the upstream server and send a response back to the client.
What does it mean when ARR says 502.3?
HTTP 502 – Overview. When working with IIS Application Request Routing (ARR) deployments, one of the errors that you may see is “HTTP 502 – Bad Gateway”. The 502.3 error means that – while acting as a proxy – ARR was unable to complete the request to the upstream server and send a response back to the client.