What is a 502 Bad Gateway Error?
The 502 Bad Gateway error, which is an HTTP status code, occurs when an invalid response by one server is received by another server on the internet. You have no control over such issues between servers online. However, sometimes the problem resides within your browser, home networking equipment or any other thing that is under your control. The browser perceives this as a real issue, and you see the 502 Bad Gateway error on your screen.
This error is described differently by different web servers. Some common ways it appears are: 502 Bad Gateway, 502 Service Temporarily Overloaded, Error 502, 502 Proxy Error, HTTP Error 502 – Bad Gateway; and there are a lot of other descriptions too.
Just like web pages, the 502 Bad Gateway error is seen inside the internet browser window and not outside or in another dialogue box or something. This error is completely independent of your particular setup. This means that it can appear on any device, operating system or browser.
How To Fix The 502 Bad Gateway Error?
The 502 Bad Gateway error is often caused by a network error between servers on the internet. This means that the problem doesn’t lie within your computer or your network connection. However, at times, it is also possible that the issue is occurring at the your end. If this is the case, down under are some fixes that may work.
- Press F5 on the keyboard or click the refresh/reload button to load the URL again. The cause of error probably lies outside your control, but it is also possible that the error is extremely temporary. If the error is temporary, reloading the page can act as a refresh and might even result in success.
- Close all open browser windows and then start a new browser session by opening a new one. Then open the web page again. The error can be caused by an issue on the computer while you were using the browser. If this is causing the issue, a simple restart of the browser may resolve the issue on the computer, and the problem may solve.
- Clear the browser’s cache and load the page again. Sometimes, the browser stores outdated or corrupt files that can give way to 502 Bad Gateway issues. If this happens, clearing the browser’s cache can remove all such problematic files. Once removed, the error may dissolve itself, without requiring any more effort.
- Delete the browser’s cookies. As mentioned above, cookies can also account for the 502 Bad Gateway error. Once they are deleted, the issue can be managed and solved. However, if you don’t want to delete all cookies, then delete the cookies associated with the site you want to load. If the problem still prevails then all the cookies should be deleted. That might solve the error.
- Start the browser in Safe Mode. When you start the browser in safe mode, the browser (including toolbars) runs without add-ons or extensions and with default settings only. By doing this, if the error does not appear anymore, it can be confirmed that the cause of the problem was some browser extension or setting. Once confirmed, disable all browser extensions and return to default browser settings. That will fix the problem permanently.
- Download and try another popular browser like Firefox, Chrome, Internet Explorer or Safari. If the error is not seen while using an alternate browser, it can be made sure that the previous browser had the issue. Reinstalling the current browser can also correct the problem.
- Install MS Forefront TMG SP1 and then download Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1. This may not be a common solution to 502 Bad Gateway error but can apply in a situation when you, while accessing a web page, receive the message Error Code: 502 Proxy Error. The network login failed. (1790) or something similar to this.
- Restart the computer. 502 errors can also be caused by temporary issues with the computer and its ability to connect to the network. If the error is seen on more than one websites, this restarting the computer technique can help solve the issue.
- Restart the network equipment. 502 Bad Gateway error can also be caused by issues with the modem, switches, router or other networking devices. If this is the case, a simple restart of these devices can help dissolve the problem. However, the order of turning each device off is not important, but it is important to make sure that the devices are turned back on from the outside in.
- Change the DNS servers on the router or the computer or the device. Temporary issues with the DNS servers can also cause 502 errors. If the DNS servers haven’t been changed previously, the current ones are probably the ones assigned by the ISP. However, this is not a problem. There are a number of DNS servers available that can be chosen.
- Contact the website directly. This can also be a good idea, as it is possible that they might be at fault. If that is the case, the website administrators might already be working on solving the issue. Most websites can be contacted through social networking accounts, and some can be contacted through telephone and email.
- Contact the Internet Service Provider. If the browser, computer, network and website associated with the page are all working fine, the ISP may be responsible for the 502 Bad Gateway issue. The network issue by ISP might be the cause and contacting the Internet Service Provider can help resolve the problem.
- Come back later. If nothing else works, the cause of the error can be associated with the ISP or the website’s network. Contacting either may confirm this. Once confirmed, it can be made sure that the error is being witnessed by a lot of other people too. So waiting may solve the 502 Bad Gateway error.