502 bad gateway error: What it is and how to fix it

First things first, error codes are normal when browsing, and can actually help us determine what the problem is. Even so, they can be confusing. But don’t panic; we’re here to explain exactly what a 502 error is and what to do if you see one.

Every time you type in a URL, that request goes through a gateway. Think of a gateway as the middleman between two servers. In the case of a 502 bad gateway error, the server acting as the gateway, or proxy, received an invalid response from the main server.

In other words, there’s been a communication breakdown. While it’s out of your hands for the most part, there are a few things you can try to resolve the issue.

A 502 bad gateway error isn’t as bad as it sounds

A 502 error is one of many HTTP status codes, and it’s also fairly common. While it may look serious, it generally just means there’s an error in communication between servers and it’s easy to fix. You might also see it show up as:

• error 502
• 502 error
• HTTP 502
• 502 service temporarily overloaded
• 502 bad gateway NGINX
• Bad gateway

Reasons you may be getting a 502 error

There are a handful of possibilities as to why the 502 error message appears on the website you’re trying to access.

1. DNS changes – During server migration, domains sometimes need changes in the Domain Name System or DNS, the communication link between domain names and IP addresses. This can take hours to become fully activated.
2. The origin server isn’t working – The server might be down, there might be a connectivity issue or there’s simply too much traffic. This could be caused by an event causing unusually high numbers of visitors or just simply coincidence. 
3. The server has failed – This can, and does, happen due to a crash or routine maintenance. Servers can fail for a number of reasons but usually from being overloaded with requests. 
4. The firewall is blocking the server transmission – A firewall is in place to block transmission between servers and its main purpose is to provide protection. Sometimes, a firewall can mistake safe content for malicious content and stop the safe content in its tracks.

6 ways to troubleshoot a 502 error message

Most often, a 502 bad gateway error has nothing to do with you as a visitor to the site. There are, however, a few things you can try just to be sure it’s not something on your side. Try these troubleshooting ideas in order because you might fix the issue faster than expected.

1. Refresh the page – Just click the refresh button in your browser window or press F5 on your keyboard. If you get lucky, this will solve the problem so you can get back to the task at hand.
2. Start a new browser session – When starting a new session, simply close all open browser windows and then open a new one.
3. Restart your equipment – Sometimes a restart is all it takes to get things back to normal. Be sure to also reboot your networking equipment such as your modem and router.
4. Clear your cache and cookies – If you previously visited a site with a 502 error and the files were saved, clearing your cache and cookies is a smart idea. Keep in mind that cookies keep track of where you’ve been on a site, what you like on the site, etc.
5. Change your DNS server – You might have the default servers assigned by your ISP. Try using open DNS servers like Google’s Public DNS.
6. Contact the website administrator or your ISP – Notifying the right people can make a difference especially if they’re unaware of the problem.

A couple of additional factors to consider are VPNs and browser extensions. They can sometimes interfere with the communication between your browser and website server. Try turning off your VPN or disabling your browser extension and reloading your web page to see if this fixes the problem.

Other common error codes

Anytime you see an error message beginning with “5” that means the server isn’t able to perform the request. A “4” means it’s a client-side error, or rather, the error occurs from your side of the computer, not the server you’re trying to reach. In addition to a 502 bad gateway error, you might also see:

• 500 Internal Server error: This is a generic error code that means the server encountered an unexpected problem preventing it from fulfilling the request.
• 501 Not Implemented error: The server is unable to perform the request because it does not support the required functionality to fulfill the request.
• 503 Service Unavailable error: The server is unable to process a request.
• 504 Gateway Timeout error: The server acting as the gateway or proxy did not get a response in time to fulfill the request.
• 403 Forbidden error: The web server understands your request, but cannot give you access to that resource.
• 404 Page not found error: The requested page cannot be found.

502 error FAQs