upstream timed out

Francis Daly francis at
Thu Jul 11 22:21:31 UTC 2013

On Thu, Jul 11, 2013 at 12:43:06PM -0400, Reddirt wrote:

Hi there,

> The Nginx log has this error:
> 2013/07/11 10:06:46 [error] 21344#0: *201 upstream timed out (110:
> Connection timed out) while reading response header from upstream, client:
>, server: ,

That says that as far as nginx is concerned, its upstream (presumably
a Thin server) took too long before returning useful content. That
suggests a problem on that Thin server, or with the "timeout" values
that nginx and Thin have being different.

> 2013/07/11 10:05:11 [warn] 21345#0: *225 an upstream response is buffered to
> a temporary file /opt/bitnami/nginx/tmp/proxy/2/00/0000000002 while reading
> upstream, client:, server: , request: "GET
> /assets/application-b7b1695e978934a03ade49d20bf63139.js HTTP/1.1",
> upstream:

That just says that the response was too big to fit in nginx's memory
buffers, and so was written to disk. Not a problem, unless you don't
expect the response to be that big.

Francis Daly        francis at

More information about the nginx mailing list