How to Fix Chrome 502 Bad Gateway Error

Understanding the 502 Bad Gateway Error in Chrome

The 502 Bad Gateway error in Chrome occurs when a server acting as a gateway or proxy receives an invalid response from the upstream server. This issue is often temporary but can be persistent in some cases. Resolving the Chrome 502 error typically involves checking network settings or the server status.

Quick Fixes to Try First

• Refresh the Page: Sometimes, the error is momentary. Press F5 or Ctrl + R (Windows/Linux) or Command + R (Mac) to reload the page.
• Clear Cache and Cookies: A corrupted cache can cause a 502 bad gateway in Chrome. Select More > Delete browsing data, check “Cached images and files” and the cookies box, then select Delete data. Our guide to clearing browsing data has the details.
• Check the Website: Open the site on another device or network, such as your phone on mobile data, to see if it is down for everyone or just you.

Refreshing and Clearing Cache

A significant cause of the 502 error is a corrupted cache or outdated cookies. Follow these steps to clear them:

1. Open Chrome and click on the three-dot menu (More) in the top-right corner.
2. Select Delete browsing data, or press Ctrl + Shift + Delete (Command + Shift + Delete on Mac).
3. Select All time as the time range.
4. Check Cached images and files and the cookies box. Deleting cookies signs you out of most sites.
5. Click Delete data.

Checking Server Status

Sometimes the issue is with the website’s server, not your browser. Here’s how to verify:

1. Try the site on another device or network, or ask someone elsewhere to open it.
2. Check the site’s social media or status page, if it has one, for reports of an outage.
3. If the site is down, you will need to wait for the website’s server to resolve the issue.

Trying Different DNS Settings

A 502 error usually comes from the website’s servers, so changing DNS helps only occasionally. Here’s how to switch to Google Public DNS, following Google’s setup guide. Write down your current DNS settings first so you can switch back.

Windows

1. Open the Control Panel and go to Network and Internet > Network and Sharing Center.
2. Click on Change adapter settings.
3. Right-click your Ethernet or Wi-Fi connection and select Properties.
4. On the Networking tab, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
5. Select Use the following DNS server addresses and enter:
   • Preferred DNS server: 8.8.8.8
   • Alternate DNS server: 8.8.4.4
6. Click OK to save changes.

macOS

1. Choose Apple menu > System Settings, then click Network in the sidebar.
2. Click your active network service, click Details, then click DNS (Apple’s steps).
3. Click the + button at the bottom of the DNS servers list.
4. Add the following DNS servers:
   • 8.8.8.8
   • 8.8.4.4
5. Click OK.

Linux

1. Most modern distributions manage DNS through NetworkManager. Open your network settings and edit the connection you use.
2. On the IPv4 tab, enter 8.8.8.8, 8.8.4.4 in the DNS servers field.
3. Apply the change and reconnect. Only edit /etc/resolv.conf directly if your system does not use NetworkManager.

If none of this helps, the problem is almost certainly on the website’s side. Wait a while and try again, or let the site owner know.