Fix 504 Gateway Timeout: Increase Timeout Limits (Nginx & PHP)

There are few things as frustrating as a 504 Gateway Timeout error. You’re waiting for a page to load, expecting data, and instead, you get a blunt “Gateway Timeout.” It feels like your server just gave up.

A 504 error essentially means your “Gateway” (the server receiving the request) waited too long for the “Upstream” (the server processing the code) to provide an answer. Before tweaking configs, ensure you aren’t just masking deeper issues—like unoptimized database queries or resource-starved servers.

Understanding the Timeout Chain

To fix this, you need to understand where the “link” in your server chain is breaking. It’s rarely just one setting; it’s a hierarchy.

How to Increase Timeout Limits

1. Increasing Limits in Nginx

If you are using Nginx to proxy requests to PHP, you must adjust the fastcgi_read_timeout directive. Edit your site configuration file (typically in /etc/nginx/sites-available/):

location ~ \.php$ {
    include fastcgi_params;
    fastcgi_pass unix:/var/run/php-fpm.sock;
    fastcgi_read_timeout 300s; 
}

After saving, don’t forget to test the configuration: nginx -t. If the output says “successful,” reload Nginx: systemctl reload nginx.

2. Increasing Limits in PHP (PHP-FPM)

Even if Nginx waits for 300 seconds, PHP will kill the script if it reaches its own max_execution_time limit. This is a common PHP configuration error.

• Open your php.ini file.
• Locate max_execution_time and set it to 300.
• If using PHP-FPM, check www.conf for request_terminate_timeout and set it to 300 as well.

SEO & Performance Considerations

While increasing these timeouts prevents the 504 error, it is not a performance fix. If your scripts consistently take 5 minutes to run, you have an application-level bottleneck. For deep dives into server efficiency, check out our guide on caching strategies to offload your servers.