Call our Toll free Number
Talk to Our Tech Support Experts
Watch The Tech Fixing Your Problem
100% Certified Support Technicians.
The error “502 Bad Gateway” popping up on Google Chrome or any other browser is an HTTP status code error returned by the online server. It suggests that the server has got an invalid response from another one. The servers connect via their Domain Name System, which acts as a phone directory for distinct connections on the web. In general, the error occurs on a browser due to issues at an online server’s end, not necessarily the internet connection. Yet if you come across the issue while surfing the web on Google Chrome, try the below things to troubleshoot it on your side. Note that you should try each of these troubleshooting steps and proceed to the subsequent step only if the previous one does not work.
Most online server issues are temporary only, so they can be resolved by reloading the web page in which you encountered the problem. For that, click on the Reload this page button next to the address bar or press F5 key when on an active Chrome tab.
Try closing active tabs on Google Chrome, by pressing Ctrl, Shift, and Q simultaneously on the keyboard, and then open the browser and reopen the error page to see if that has resolved the 502 Bad Gateway error. You can use this step even to troubleshoot Chrome not responding issues.
To clear the browsing data, press Ctrl, Shift, and Delete keys simultaneously and choose Clear data button highlighted in blue color. Usually, the respective checkboxes of Cookies and other site data and Cached images and files will be selected, but make it a point to put a tick mark next to each one in case they are not. This can also fix Chrome not responding problems.
Sometimes, the extensions installed in the browser may conflict with responses received from an online server. To know if a plugin is causing it, you have to identify the problem extension by surfing the error web page on Chrome’s private browsing mode. To open the Incognito window, press Ctrl, Shift, and N on an active Chrome tab.
You can choose to surf the particular web page on Chrome incognito or remove the flawed extension and then browse on its standard browsing mode. If it is a one-off browsing session, Incognito will suffice. However, if you visit the site frequently, make it a point to remove the extension.
Since the Incognito mode disables plugins, and if you can open the web page on that mode, it is likely an extension is to blame. So, after ensuring which extension is causing the error, get rid of it from Chrome. For that, you have to disable all extensions at first and then enable them one by one while browsing on the same page.
Type chrome://extensions on the address bar of the browser, and press Enter. From the list of extensions, deselect them all. This will disable all the plugins. Now enable one plugin at a time and see if your issue persists. This way, you can figure out which one is to blame.
Note that removing faulty and corrupted extensions can also fix Chrome constantly crashing errors or other browser issues for which this step is recommended.
The 502 Bad Gateway error may well be related to the browser itself, so try opening the web page on a different one. For instance, if you are using Google Chrome, open it on Mozilla Firefox, and see if the error is resolved.
Sometimes, the temporary problems on a PC may cause the faulty connection to online servers, so it is a good idea to reboot the PC. While it is rebooting, restart the router or modem you are connected to. Once the PC and internet equipment come back online, retry opening the web page.
DNS usually speeds up the internet connection, but at times, faulty cache in the web browser may cause the issue. In case the earlier step fails to resolve it, try clearing the cache.
Click the Start button, search for Command Prompt in the search box, and open it from the search results. On the DOC box, type the command ipconfig /flushdns and press Enter. When done, you will see a message saying, “Windows IP configuration successfully flushed the DNS Resolver Cache”.
In nations where the internet is censored, the 502 Bad Gateway error is more likely to happen due to local DNS servers, which take a long time to resolve worldwide site addresses. In that case, you can try using the public DNS of Google in place of the default one from your internet service provider.
In case public DNS fails to resolve the issue, try using a proxy or VPN server. This will bypass corrupted local DNS servers and use private DNS to access the web page. Using a Virtual Private Network, you can switch the local DNS server and access a site akin to doing that from a local location.
If none of these troubleshoots resolve the problem, contact the website owner to notify them of the same. If you feel a malware or virus might have rendered your browser unusable, get in touch with our certified tech support experts for quick assistance.