Among the many HTTP errors received when browsing the web, HTTP error 502 (bad gateway) is among one of the mysterious ones for people who do not know much about the web. There might be no solution to this problem, but you can do some tasks on your end to try to correct the issue.

Causes

It is most likely that when you browse the web and get a bad gateway error, your gateway (what you connect to the Internet through, including any proxies you might be using) is not able to agree on how to communicate with the destination server.

Probable Fixes

If you are experiencing a bad gateway error with isolated incidents, clear your browser cache. If you are using any proxies, try loading the page without a proxy.

Other Potential Problems

A bad gateway error every time you load a page could mean that your ISP or your Internet connection might be at fault. In such a case, you should give your ISP a call so that they can see whether the issue comes from your end or theirs.

Misconceptions

A bad gateway error does not mean that the website you were trying to access no longer works. This error is common when communication through HTTP cannot be established.

Expert Insight

Since requests from your computer can go through several different routes, one of the switches in your data route could be causing the 502 error to happen. In other words, there might be no problem with your ISP, the destination server or even your own network equipment.

Source:

HTTP Error 502 Bad Gateway