Nginx stalled cache updating

Rated 4.7/5 based on 510 customer reviews

Visit Stack Exchange We have a situation where a site starts to serve a 502 Bad Gateway but doesn't seem to recover after the upstream servers rebound.

The nginx server is setup to proxy/load balance requests for two upstream servers.

The second and more complex case is when there is dynamic content: the web server parses the URI, notices it’s meant for a PHP file, passes the request via Fast CGI to the PHP processor.

However, choosing the software is only the first step on the path to blazing fast web services.

Here are some tips on how to optimize Nginx for serving static files and dynamic PHP content.

What is strange though is that it seems that nginx doesn't pick up on when the web servers rebound and we must restart nginx to get it to start serving the site again. I'm looking through the proxy settings currently to see if there is something to set but not having much luck finding anything.

No matter how good your web service is, if it takes 5 seconds to load a page, people will dislike using it.

Leave a Reply