HTTP Error 502 Bad gateway

The 502 Bad Gateway error typically occurs due to network errors between a computer and internet servers. This error indicates that a server, acting as a gateway or proxy, received an invalid response from an upstream server. In most cases, the issue is not with the user's computer or internet connection but rather with the website's server. This means that the problem lies with the website's server, and not with the individual user's system or network connection.

How To Troubleshoot HTTP Error 502: Bad Gateway

HTTP status code

The 502 Bad Gateway error is an HTTP status code, which is a three-digit code used to indicate the outcome of an HTTP request. These status codes are categorized into five classes, and the class can be determined by looking at the first digit of the code:

  1. 1xx: Informational
  2. 2xx: Success
  3. 3xx: Redirection
  4. 4xx: Client Error
  5. 5xx: Server Error

The 502 'Bad Gateway' error is typically generated by the server hosting the website, and it is not related to the user's PC. This error occurs when a website uses a proxy server as a relay point to keep data separate from the main server hosting the site's main page. If there is an issue with the connection between the main server and the proxy server, such as incorrect Transmission Control Protocol (TCP) data, the user's browser identifies the proxy or gateway as 'bad', leading to the 502 error.

Error Messages

Different sites and services will often customize their error messages , both for the sake of them appearing unique, and also help tech-savvy users to better understand the cause of the error.

  1. 502 Bad Gateway

  2. 502 Proxy Error

  3. 502. That's an error

  4. HTTP Error 502 - Bad Gateway

  5. 502 Service Temporarily Overloaded

  6. Bad Gateway: The proxy server received an invalid response from an upstream server

  7. 502 Server Error: The server encountered a temporary error and could not complete your request

Cause of 502 Bad Gateway Errors

The 502 Bad Gateway error is a common HTTP status code that occurs when a server acting as a gateway or proxy receives an invalid response from an upstream server. In other words, the server that your browser is communicating with is acting as an intermediary and passes your request to another server (upstream server) to process it. However, the upstream server fails to respond or sends back an invalid response, leading to the 502 error. There are several potential causes for 502 Bad Gateway errors:
  1. Server Overload: The upstream server may be overloaded with requests, leading to delayed or failed responses.
  2. Network Issues: Network problems between the gateway/proxy server and the upstream server can cause communication failures.
  3. Server Downtime: If the upstream server is down or experiencing technical issues, it will be unable to respond to requests, triggering the 502 error.
  4. Misconfigured Proxy: If the proxy or gateway server is misconfigured, it may not be able to communicate properly with the upstream server.
  5. DNS Issues: Incorrect DNS settings can result in the gateway server being unable to find the correct IP address of the upstream server.
  6. Firewall or Security Restrictions: Sometimes, firewall or security settings can block the communication between the gateway and upstream servers.
  7. Content Delivery Network (CDN) Problems: If a website uses a CDN, issues with the CDN servers can also lead to 502 errors.
  8. Web Application Bugs: Errors in the web application code can cause issues with responses from the upstream server.

How to Fix a 502 Error

Fixing a 502 Bad Gateway error can involve several troubleshooting steps, as the error may be caused by various factors. Here's a step-by-step guide to help you address the issue:
  1. Refresh the Page: Sometimes, the 502 error is temporary and caused by a momentary glitch. Try refreshing the page to see if the error goes away.
  2. Check Other Websites: Verify if the 502 error occurs on multiple websites or just one. If it's specific to one website, the problem is likely with that particular site's server.
  3. Clear Browser Cache: Your browser's cache may contain outdated or corrupted data, which can cause conflicts with the website. Clear your browser cache and try accessing the site again.
  4. Check Internet Connection: Ensure you have a stable internet connection. Try accessing other websites to confirm if the issue is specific to the website showing the 502 error.
  5. Wait and Retry: If the 502 error is due to server overload or temporary server issues, waiting for a while and trying again later might resolve the problem.
  6. Check Proxy Settings: If you are using a proxy server, ensure that it is correctly configured. Incorrect proxy settings can lead to a 502 error.
  7. Disable VPN or Firewall: If you use a VPN or firewall, temporarily disable them to check if they are causing the 502 error. Sometimes, they can interfere with the connection to the website.
  8. Contact Website Administrator: If the 502 error persists and affects only one specific website, contact the website's administrator to inform them about the issue.
  9. Use an Alternative Browser: If the error occurs on one browser, try accessing the website using a different browser to check if the problem is browser-specific.
  10. Restart Modem/Router: If you suspect network issues, restart your modem and router to refresh the connection.
  11. Try Incognito/Private Mode: Open the website in incognito/private mode, which bypasses browser extensions and cache, to check if any of them are causing the 502 error.
  12. Contact Your Internet Service Provider (ISP): If the issue seems to be related to your internet connection, get in touch with your ISP for assistance.
  13. Wait for Website Maintenance: If the website is undergoing maintenance or updates, the 502 error might be temporary. Check the website's official social media channels or status page for any announcements.


It's essential to remember that the 502 Bad Gateway error is typically beyond the control of the end-user, and resolving it may require action from the website's administrators or server operators. If none of the above steps work, and the issue persists, it's best to wait for the website's technical team to address the problem.