MuleSoft · CloudHub 2.0
504 Gateway Timeout during or after traffic switch to CloudHub 2.0
Short answer
A 504 Gateway Timeout during or after the traffic switch to CloudHub 2.0 means a request ran longer than the load balancer waits. Keep client timeouts under 300 seconds, or raise Read Response Timeout in the private space's Advanced settings.
VerifiedLast verified
01Error text
504 Gateway Timeout02Likely causes
- The request takes longer than the load balancer's read timeout.
03How to fix it
- Keep client timeouts under 300 seconds.
- If the API needs longer, raise Read Response Timeout in the private space's Advanced settings. It can go up to 3,600 seconds.
- If latency is the cause, increase the replica vCore size or count.
04Official documentation
→Related errors
- 502 Bad Gateway during traffic switch to CloudHub 2.0A 502 Bad Gateway while switching traffic from CloudHub to CloudHub 2.0 usually means the dedicated load balancer cannot talk to the new app. Check that the upstream uses TLS 1.2 or higher and that the app's listener binds to 0.0.0.0.
- HTTP:GATEWAY_TIMEOUTHTTP:GATEWAY_TIMEOUT means a server acting as a gateway or proxy did not receive a response from its upstream within the specified time (HTTP 504). The timeout happened behind the gateway, not in your Mule app's own Response Timeout.
- HTTP:TIMEOUTHTTP:TIMEOUT means a request sent by the HTTP Request operation timed out before the response arrived. The wait is set by Response Timeout, which is 10000 milliseconds unless you change it, so raise it or make the remote service answer faster.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer