We usually get this error when we try to access a web page and the first web server is not receiving a response from another web server along with the route on which the data passes. Often this signifies a problem for the website and most of the time we can’t do anything about it, but there are exceptions when the problem can be from the network configuration or our own device.
A 502 Bad Gateway error means that the web server you are connecting to acts as a proxy for sending information from another server but has received a bad response from the other server.
This is called a 502 type error because it is the HTTP state code used by the web server to describe this type of error.
A number of different causes could cause these results. The server may be overloaded or there are network issues between the two servers, or it is only a temporary problem. It is also possible that an incorrectly configured firewall or even a coding error exists and that the problem will not be resolved until those issues are addressed.
As with 404 errors, site designers can customize how they show a 502 error.
For example, you might see things like:
HTTP 502 Bad Gate Error
HTTP 502
502 Temporary Overload Service
Temporary error (502)
Server Error 502
502 Bad Gateway Nginx
However, there are a few things you can try.
1. Change DNS servers
Sometimes, DNS issues can cause 502 errors. Changing DNS servers is not a likely solution, but it is possible. And it’s not too hard to do. If you have not modified them, DNS servers will probably be the one set by your ISP.
2. Check plugins and extensions
If you use extensions in your browser, one or more extensions may cause the problem. Try to disable all extensions and then visit the website. If the error disappears afterward, then a plugin may create the problem. Enable your plug-ins one by one to find the culprit.
3. Restart your devices
There may be strange, temporary problems with your computer or network equipment (Wi-Fi, router, modem). A simple restart of your computer and network devices can help resolve the issue.
4. Clear the cache and browser cookies
If you try another browser that works, your master browser may have stored outdated or corrupted files in your folders that could cause 502 error. Removing these saved files and trying to open the website could solve the problem.
5. Reload the page
Refreshing the page is always worth it. Often, error 502 is temporary, and a simple refresh could make this trick work.
Most browsers use the F5 key to refresh and also offer an update button somewhere in the address bar. It does not solve the problem very often, but it takes only a second to try.