Nginx reverse proxy causing 504 Gateway Timeout

Question

I am using Nginx as a reverse proxy that takes requests then does a proxy pass to get the actual web application from the upstream server running on port 8001   If I go to mywebsite com or do a wget  I get a 504 Gateway Timeout after 60 seconds    However  if I load mywebsite com 8001  the application loads as expected   So something is preventing Nginx from communicating with the upstream server   All this started after my hosting company reset the machine my stuff was running on  prior to that no issues whatsoever   Here s my vhosts server block   server       listen   80      server name mywebsite com       root  home user public html mywebsite com public       access log  home user public html mywebsite com log access log upstreamlog      error log  home user public html mywebsite com log error log       location             proxy pass http   xxx xxx xxx xxx 8001          proxy redirect off          proxy set header Host  host          proxy set header X-Real-IP  remote addr          proxy set header X-Forwarded-For  proxy add x forwarded for             And the output from my Nginx error log   2014 06 27 13 10 58  error  31406 0   1 upstream timed out  110  Connection timed out  while connecting to upstream  client  xxx xx xxx xxx  server  mywebsite com  request   GET   HTTP 1 1   upstream   http   xxx xxx xxx xxx 8001    host   mywebsite com

User · Answer

In my case i restart php for and it become ok

User · Answer

You can also face this situation if your upstream server uses a domain name  and its IP address changes  e g   your upstream points to an AWS Elastic Load Balancer   The problem is that nginx will resolve the IP address once  and keep it cached for subsequent requests until the configuration is reloaded   You can tell nginx to use a name server to re-resolve the domain once the cached entry expires   location  mylocation         use google dns to resolve host after IP cached expires     resolver 8 8 8 8      set  upstream endpoint http   your backend server       proxy pass  upstream endpoint      The docs on proxy pass explain why this trick works      Parameter value can contain variables  In this case  if an address is specified   as a domain name  the name is searched among the described server groups  and    if not found  is determined using a resolver    Kudos to  Nginx with dynamic upstreams   tenzer dk  for the detailed explanation  which also contains some relevant information on a caveat of this approach regarding forwarded URIs

User · Answer

Probably can add a few more line to increase the timeout period to upstream  The examples below sets the timeout to 300 seconds    proxy connect timeout       300  proxy send timeout          300  proxy read timeout          300  send timeout                300

User · Answer

If you want to increase or add time limit to all sites then you can add below lines to the nginx conf file    Add below lines to the http section of  usr local etc nginx nginx conf or  etc nginx nginx conf file   fastcgi read timeout 600  proxy read timeout 600    If the above lines doesn t exist in conf file then add them  otherwise increase fastcgi read timeout and proxy read timeout to make sure that nginx and php-fpm did not timeout      To increase time limit for only one site then you can edit in vim  etc nginx sites-available example com   location     php        include  etc nginx fastcgi params          fastcgi pass  unix  var run php5-fpm sock      fastcgi read timeout 300       and after adding these lines in nginx conf  then don t forget to restart nginx   service php7-fpm reload  service nginx reload   or  if you re using valet then simply type valet restart

User · Answer

If nginx ajp module is used  try adding ajp read timeout 10m  in nginx conf file

User · Answer

Had the same problem  Turned out it was caused by iptables connection tracking on the upstream server  After removing --state NEW ESTABLISHED RELATED from the firewall script and flushing with conntrack -F the problem was gone

User · Answer

user2540984  as well as many others have pointed out that you can try increasing your timeout settings  I myself faced a similar issue to this one and tried to change my timeout settings in the  etc nginx nginx conf file  as almost everyone in these threads suggest  This  however  did not help me a single bit  there was no apparent change in NGINX  timeout settings  After many hours of searching  I finally managed to solve my issue   The solution lies in this forum thread  and what it says is that you should put your timeout settings in  etc nginx conf d timeout conf  and if this file doesn t exist  you should create it   I used the same settings as suggested in the thread   proxy connect timeout 600  proxy send timeout 600  proxy read timeout 600  send timeout 600    This might not be the solution to your particular problem  but if anyone else notices that the timeout changes in  etc nginx nginx conf don t do anything  I hope this answer helps

User · Answer

Increasing the timeout will not likely solve your issue since  as you say  the actual target web server is responding just fine   I had this same issue and I found it had to do with not using a keep-alive on the connection  I can t actually answer why this is but  in clearing the connection header I solved this issue and the request was proxied just fine   server       location             proxy set header   X-Real-IP  remote addr          proxy set header   Host       http host          proxy http version 1 1          proxy set header Connection             proxy pass http   localhost 5000            Have a look at this posts which explains it in more detail  nginx close upstream connection after request Keep-alive header clarification http   nginx org en docs http ngx http upstream module html keepalive

User · Answer

NGINX itself may not be the root cause  IF  quot minimum ports per VM instance quot  set on the NAT Gateway -- which stand between your NGINX instance  amp  the proxy pass destination -- is too small for the number of concurrent requests  it has to be increased  Solution  Increase the available number of ports per VM on NAT Gateway  Context In my case  on Google Cloud  a reverse proxy NGINX was placed inside a subnet  with a NAT Gateway  The NGINX instance was redirecting requests to a domain associated with our backend API  upstream  through the NAT Gateway  This documentation from GCP will help you understand how NAT is relevant to the NGINX 504 timeout

[nginx] Nginx reverse proxy causing 504 Gateway Timeout

Examples related to nginx

Examples related to reverse-proxy

Examples related to proxypass

Examples related to http-status-code-504