9 messages in ru.sysoev.nginxRe: Please explain this 502 Bad Gatew...
FromSent OnAttachments
just startingDec 27, 2007 7:20 am 
Igor SysoevDec 27, 2007 8:28 am 
Aleksandar LazicDec 27, 2007 8:30 am 
just startingDec 27, 2007 9:05 am 
Igor SysoevDec 27, 2007 9:13 am 
just startingDec 27, 2007 10:39 am 
Igor SysoevDec 27, 2007 10:52 am 
just startingDec 27, 2007 11:32 am 
Igor SysoevDec 28, 2007 2:01 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Please explain this 502 Bad Gateway errorActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Dec 27, 2007 8:28:47 am
List:ru.sysoev.nginx

On Thu, Dec 27, 2007 at 08:50:47PM +0530, just starting wrote:

I am testing nginx as a proxy server + static file server for my test site deployed on jetty.

Can you please explain the error mentioned here.

Error Log Entry : [2007/12/27 10:44:07 [error] 2625#0: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.234, server: localhost, request: "GET /KdocProj/dboard.html?_dc=1198726407859 HTTP/1.0", upstream: " http://192.168.0.241:8080/KdocProj/dboard.html?_dc=1198726407859", host: " 192.168.0.241:8000"]

man errno:

61 ECONNREFUSED Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the for- eign host.

The "Connection refused" usually means that backend does not listen on 192.168.0.241:8080 or its listen queue is full: it can not handle all requests.