Welcome! Log In Create A New Profile

Advanced

Re: upstream timed out

September 16, 2009 05:16AM
On Tue, Sep 15, 2009 at 09:26:17PM +0500, Ziyad Saeed 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


--
Igor Sysoev
http://sysoev.ru/en/
Subject Author Posted

upstream timed out

MySchizoBuddy September 15, 2009 12:36PM

Re: upstream timed out

Igor Sysoev September 16, 2009 05:16AM

Re: upstream timed out

Falko Timme April 13, 2012 05:28AM

Re: upstream timed out

Maxim Dounin April 13, 2012 06:34AM

Re: upstream timed out

Francis Daly July 11, 2013 06:22PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 241
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready