Help Center

  1. StackPath Help
  2. CDN
  3. Troubleshooting

Learn and Troubleshoot 502 and 504 Errors

Avatar
Christopher Hotze
Updated:

Overview

You can use this document to learn how to troubleshoot 502 and 504 errors that your users may see. 

Review examples of 5xx response codes

500-class response codes indicate a server failure occurred while the CDN processed a request.

Error type Description
502 - Bad Gateway

You use the edge server (CDN) as a proxy, and then the CDN receives an invalid response from the origin server, also known as the upstream server.

  • For example, imagine the request as a phone call. You answer the phone; however, the caller was not who you were expecting. 
504 - Gateway Timeout

You use the edge server (CDN) as a proxy, and then the CDN does not receive a timely response from the origin server. 

  • For example, imagine the request as a phone call; however, the phone never rings. Instead, the caller hears, "Please try your call again later." 

 

View 5xx errors in the browser

Since the base HTML for your site is not cached on the CDN by default, a 502 or a 504 error in the browser indicates that the web server is unable to respond to the CDN's initial request to your server for that HTML, which will return a 5xx error. 

Review the following table to view examples of different message types you may see in a browser: 

502 error examples 504 error examples
  • “502 Bad Gateway”
  • “HTTP Error 502 – Bad Gateway”
  • “502 Service Temporarily Overloaded”
  • “Error 502”
  • “502 Proxy Error”
  • “HTTP 502”
  • “502 Bad Gateway NGINX”
  • “504 Gateway Timeout”
  • “HTTP 504 Gateway Timeout”
  • “HTTP 504 Error”
  • “HTTP 504”
  • “504 Gateway Time-Out”
  • “Nginx 504 Gateway Timeout”
  • “Gateway Timeout (504)”
  • “504 Gateway Timeout NGINX”
Note: 

Each error has multiple examples with different wording, which can vary from site to site; however, all examples indicate the same overall message.

View 5xx errors in the terminal

To view these errors via terminal, use a cURL command to send an HTTP request to your site via your edge address. 

cURL against the edge address to make sure that the CDN is proxying the connection to the origin. 

Review the following example: 

curl -I myEDGEADDRESS.stackpathcdn.com
HTTP/1.1 504 Gateway Timeout
date: Thu, 13 Dec 2018 14:53:45 GMT
accept-ranges: bytes
cache-control: max-age=10
X-HW: 1544712810.cds078.da2.h2,1544712810.cds117.da2.sc,1544712825.cds117.da2.p
access-control-allow-origin: *
Connection: keep-alive
Content-Length: 0

In the above example, note that: 

  • A response of 504 Gateway Timeout is present
  • The X-HW header ends in p, which indicates that this request was proxied to the origin, not served from cache.
    • The X-HW is inserted by the CDN and indicates where an asset is served from, what PoP the request is going to, and if the response came from cache or was from a proxied connection to the origin. 

When the CDN proxies a request, the CDN passes the request to the origin server and then reports to the browser what was received. In this case, the server gave a 504. 

Troubleshoot a 502 error

Review common causes for this error and how to troubleshoot: 

Cause Troubleshoot
The CDN does not connect to the correct server.

Ensure that the IP address set in your origin is correct. 

If you use a domain as your origin, then ensure that the domain resolves to the correct IP address. 

A firewall (or other security device) blocks the request.

  • In other words, some thing that is not your origin is blocking the request from the CDN.

Verify that your firewall does not drop requests from the CDN.

Verify that DDoS protection settings have not been triggered by origin pull requests from the CDN.

Disable CMS security plug-ins, and then refresh your site. 

  • Some CMS security plug-ins may cause complications; as a result, disable one plug-in at a time, and then refresh your site.

Verify that you have allowlisted StackPath IP blocks on your server's firewall. 

The domain is not resolving properly

Verify that your DNS records are properly configured and propagated.

Origin pull encounters a redirect loop

cURL the origin URL to see where the redirect is going. 

  • Many times, the origin tries to redirect to itself or to the CDN, which can cause a redirect loop. 

 

 

Troubleshoot a 504 error 

By default, the CDN will maintain a connection with an origin before the connection times out for 20 seconds. 

  • This time limit is configured to avoid negatively affecting the network and overall performance of the CDN.

Review the following ways to troubleshoot a 504 error:

  • Verify that the host header is set correctly in the StackPath Control Portal.
  • Verify that the HTACCESS file is correct on the server, especially if WordPress has been recently reinstalled or restored.
  • Verify that you have allowlisted StackPath IP blocks on your server's firewall. 
  • Verify that the server is not having problems at the WordPress, the Apache/NGINX/WebServer, or at the Operating System level, such as:
    • Permissions issues in the operating system
    • Database corruption
    • Server hardware/infrastructure issues
    • Issues with server's resources (RAM, Disk i/o, CPU)
    • Server issues that prevent WordPress from properly accessing its database or other resources
    • If you are unsure how or what to check or you do not have access to your server's operating system, then contact your hosting provider.
Was this article helpful?

Related articles

Not finding what you need?

95% of questions can be answered using the search tool. This is the quickest way to get a response.

Contact Us