Fix: Nginx 504 Gateway Timeout
Time the upstream directly with curl
504 = upstream took longer than `proxy_read_timeout`. Raise the timeout only after you confirm the upstream isn't actually stuck.
Frequently Asked Questions
What causes Nginx 504 Gateway Timeout?
504 = upstream took longer than `proxy_read_timeout`. Raise the timeout only after you confirm the upstream isn't actually stuck.
How to fix Nginx 504 Gateway Timeout?
Confirm the upstream actually returns eventually. If so, raise `proxy_read_timeout` for that location block — or move the long work behind a job queue + polling.
Example fix from Kintify Fix
Input: Nginx 504 after 60 seconds on a long export endpoint
Output: Confirm the upstream actually returns eventually. If so, raise `proxy_read_timeout` for that location block — or move the long work behind a job queue + polling.
Used by developers debugging real production systems