Please explain this 502 Bad Gateway error

Igor Sysoev is at rambler-co.ru
Thu Dec 27 19:29:10 MSK 2007


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.


-- 
Igor Sysoev
http://sysoev.ru/en/





More information about the nginx mailing list