Nginx drops server our LB if it see HTTP 400.

Brent Clark brentgclarklist at
Thu Nov 16 13:03:49 UTC 2017

Good day Guys

I'm sitting with a very peculiar problem, and I was hoping someone could
be of assistance.

Right now everything is a theory, but when I switch back to LVS
everything works. Reason I like and want Nginx is for the reverse
caching (caching of images).

As said, Im using Nginx for reverse caching and load balancing, and I'm
seeing the following in the Nginx error log.

2017/11/16 10:16:38 [error] 75140#75140: *27952 no live upstreams while
connecting to upstream, client:, server:
upstream: "https://sslloadbalance/1298310/SNIPPET_OF_URL", host:

I understand that, Nginx says is cant connect to the backend servers,
but the backend servers are 100%.

My theory is, when ever a URL is called and an HTTP 400 is returned,
Nginx picks this up, and does not like it, and then drops the server
out., e.g.

REMOVED_IP_OF_LB - - [16/Nov/2017:10:16:38 +0200] "GET
HTTP/1.0" 400 226 "-" "-"

My configuration(s) is very standard / basic.

I would have liked to have used 'health_check', but that is only
available in Nginx Plus.

If I run a tcptraceroute to port 80 in a while loop to the back end
servers, everything is ok, and going back to LVS, everything is ok.

I would like to ask, If is a way to either ignore 400 error status or if
I can ask, what is a better way to manage and handle this.

Many thanks, regards


More information about the nginx mailing list