How do I prevent a Gateway Timeout with FastCGI on Nginx

Question

I am running Django, FastCGI, and Nginx. I am creating an api of sorts that where someone can send some data via XML which I will process and then return some status codes for each node that was sent over.

The problem is that Nginx will throw a 504 Gateway Time-out if I take too long to process the XML -- I think longer than 60 seconds.

So I would like to set up Nginx so that if any requests matching the location /api will not time out for 120 seconds. What setting will accomplish that.

What I have so far is:

    # Handles all api calls
    location ^~ /api/ {
        proxy_read_timeout 120;
        proxy_connect_timeout 120;
        fastcgi_pass 127.0.0.1:8080;
    }

Edit: What I have is not working :)

It seems bad that the data is not being streamed... ie for a server to start responding back in 60 seconds or more seems unacceptable. — Adam Gent, Feb 20 '13 at 17:14

score 257 · Accepted Answer · edited Nov 03 '21 at 16:14

257

Proxy timeouts are well, for proxies, not for FastCGI...

The directives that affect FastCGI timeouts are client_header_timeout, client_body_timeout and send_timeout.

Edit: Considering what's found on nginx wiki, the send_timeout directive is responsible for setting general timeout of response (which was bit misleading). For FastCGI there's fastcgi_read_timeout which is affecting the FastCGI process response timeout.

edited Nov 03 '21 at 16:14

answered Feb 18 '09 at 19:34

zgoda

12,775
4
37
46

8

For anyone using uwsgi and having this error, uwsgi_read_timeout 600; fixed my problem. – Homer6 Jul 17 '12 at 18:50
2

My question here would be (as a server admin amateur) where do I go to change this? httpd.conf file? – jeffkee Aug 02 '12 at 20:35
2

If it helps, mine was at /etc/nginx/ at Media Temple's DV system. – jeffkee Aug 02 '12 at 21:37
Abdo gives a nice way to debug. If you still have trouble, you might need to increase the max client message size in nginx.conf (client_max_body_size **M;) – Sam Grondahl Oct 17 '13 at 18:09
2

Increasing the timeout imho is not a proper solution. – JazzCat Jan 14 '16 at 15:44
Yes, uwsgi_read_timeout 600; fixed my problem too in: flask + uwsgi + nginx – Stan Zeez Jul 12 '16 at 10:19

Abdo · Answer 2 · 2013-01-28T15:32:29.373

25

For those using nginx with unicorn and rails, most likely the timeout is in your unicorn.rb file

put a large timeout in unicorn.rb

timeout 500

if you're still facing issues, try having fail_timeout=0 in your upstream in nginx and see if this fixes your issue. This is for debugging purposes and might be dangerous in a production environment.

upstream foo_server {
        server 127.0.0.1:3000 fail_timeout=0;
}

edited Jan 28 '13 at 15:32

answered Dec 11 '12 at 15:48

Abdo

13,549
10
79
98

3

I think that people downvoted it because this is about Django, however your answer fixed my gateway timeout issue with Rails + Unicorn :) – ZiggyTheHamster Sep 17 '13 at 23:19

Jose Carlos Ramos Carmenates · Answer 3 · 2017-03-28T20:42:19.360

9

In http nginx section (/etc/nginx/nginx.conf) add or modify:

keepalive_timeout 300s

In server nginx section (/etc/nginx/sites-available/your-config-file.com) add these lines:

client_max_body_size 50M;
fastcgi_buffers 8 1600k;
fastcgi_buffer_size 3200k;
fastcgi_connect_timeout 300s;
fastcgi_send_timeout 300s;
fastcgi_read_timeout 300s;

In php file in the case 127.0.0.1:9000 (/etc/php/7.X/fpm/pool.d/www.conf) modify:

request_terminate_timeout = 300

I hope help you.

edited Mar 28 '17 at 20:42

answered Jan 30 '17 at 20:14

Jose Carlos Ramos Carmenates

2,649
1
37
54

Would anything "bad" happen if I change the time to 10000 seconds? – utdev Mar 06 '18 at 12:06
Not happen nothing bad, but your service wait more time. You can change it value as you want. – Jose Carlos Ramos Carmenates Mar 06 '18 at 15:06

score 1 · Answer 4 · answered Dec 09 '15 at 00:55

If you use unicorn.

Look at top on your server. Unicorn likely is using 100% of CPU right now. There are several reasons of this problem.

You should check your HTTP requests, some of their can be very hard.
Check unicorn's version. May be you've updated it recently, and something was broken.

score 1 · Answer 5 · answered Mar 17 '20 at 14:25

In server proxy set like that

location / {

                proxy_pass http://ip:80;                

                proxy_connect_timeout   90;
                proxy_send_timeout      90;
                proxy_read_timeout      90;

            }

In server php set like that

server {
        client_body_timeout 120;
        location = /index.php {

                #include fastcgi.conf; //example
                #fastcgi_pass unix:/run/php/php7.3-fpm.sock;//example veriosn

                fastcgi_read_timeout 120s;
       }
}

How do I prevent a Gateway Timeout with FastCGI on Nginx

5 Answers5

Linked

Related