A 504 Gateway Timeout means a gateway or proxy server did not receive a response from the backend server within the expected time. The gateway waited for the upstream server to process your request, but the backend took too long and the gateway gave up. This is a server-to-server timeout, not a client-to-server timeout.
The 504 error differs from 502 (invalid response) because with 504, the backend simply did not respond in time. It may still be processing the request. Common on sites running heavy database queries, complex API calls, or under high traffic load.
Fix as a Visitor
Wait a few minutes and hard refresh (Ctrl+F5). Clear browser cache and cookies. Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1). Try Incognito mode. If the site is down for everyone (check downdetector.com), wait for the server team.
Fix as a Site Owner
Check server error logs for the specific timeout location. Increase gateway timeout values: in Nginx set “proxy_read_timeout 300s,” in Apache set “ProxyTimeout 300.” Optimize slow database queries that exceed the timeout. Add caching (Redis, Memcached) to reduce backend processing time. Scale server resources if traffic exceeds capacity.
Frequently Asked Questions
What is the difference between 502 and 504?
502 means the gateway got an invalid response from backend. 504 means the gateway got no response at all within the timeout. Both are server-side, but 504 specifically indicates the backend is too slow, while 502 indicates it crashed or sent bad data.
Does a 504 error mean the server is down?
Not necessarily. The backend server may be running but processing a request that takes longer than the gateway’s timeout allows. Heavy queries, large file processing, and traffic spikes can all cause the backend to respond slowly without being fully down.
How long should I wait before retrying after a 504?
Wait at least 30 seconds before the first retry. If it fails again, wait 2-5 minutes. Rapid retrying adds more requests to an already overloaded server. Check the response headers for a Retry-After value that tells you the recommended wait time.
