Upstream timed out

upstream timed out (10060: A connection attempt failed because the
connected
party did not properly respond after a period of time, or established
connection failed because connected host has failed to respond) while
reading response header from upstream, client: 127.0.0.1, server:
dev.flow3.local, request: “GET / HTTP/1.1”, upstream: “fastcgi://
127.0.0.1:9000”, host: “dev.flow3.local”

I’m assuming one the tons of fcgi params can help. but which one

On Tue, Sep 15, 2009 at 09:26:17PM +0500, Ziyad S. wrote:

upstream timed out (10060: A connection attempt failed because the connected
party did not properly respond after a period of time, or established
connection failed because connected host has failed to respond) while
reading response header from upstream, client: 127.0.0.1, server:
dev.flow3.local, request: “GET / HTTP/1.1”, upstream: “fastcgi://
127.0.0.1:9000”, host: “dev.flow3.local”

I’m assuming one the tons of fcgi params can help. but which one

fastcgi_read_timeout 2m; # 60s is default

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs