How do I fix 502 Bad Gateway?
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.
When should I use 502 Bad Gateway?
A 502 Bad Gateway Error is a general indicator that there’s something wrong with a website’s server communication. Since it’s just a generic error, it doesn’t actually tell you the website’s exact issue. When this happens, your website will serve an error web page to your site’s visitors, like the photo below.
What causes a 502 Bad Gateway error?
The primary reason we typically see a 502 bad gateway error is due to an issue with the web host. Sometimes a query, script, or request will take too long and so it is canceled or killed by the server.
What does error 502 Bad Gateway mean?
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 called a 502 error because that’s the HTTP status code that the web server uses to describe that kind of error.
What’s “Bad Gateway 502” mean?
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 called a 502 error because that’s the HTTP status code that the web server uses to describe that kind of error.
Why am I getting bad gateway message?
Bad Gateway errors are often caused by issues between online servers that you have no control over. However, sometimes, there is no real issue but your browser thinks there is one thanks to a problem with your browser, an issue with your home networking equipment, or some other in-your-control reason.
