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

User · Answer

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;
}

User · Answer

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   HTH

User · Answer

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

User · Answer

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

User · Answer

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

[configuration] How do I prevent a Gateway Timeout with FastCGI on Nginx

Examples related to configuration

Examples related to nginx

Examples related to fastcgi