# Upstream timed out

**URL:** <https://www.ruby-forum.com/t/upstream-timed-out/175570>\
**Category:** NGINX\
**Created:** [September 15, 2009, 6:42pm UTC](https://www.ruby-forum.com/t/upstream-timed-out/175570 "2009-09-15T18:42:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![myschizobuddy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/50afbb/32.png) [@myschizobuddy](https://www.ruby-forum.com/u/myschizobuddy)\
**Post date:** [September 15, 2009, 6:42pm UTC](https://www.ruby-forum.com/t/upstream-timed-out/175570/1 "2009-09-15T18:42:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![myschizobuddy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/50afbb/32.png) [@myschizobuddy](https://www.ruby-forum.com/u/myschizobuddy)\
**Post date:** [September 16, 2009, 11:24am UTC](https://www.ruby-forum.com/t/upstream-timed-out/175570/2 "2009-09-16T11:24:19Z")

</div>

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