<div>ohh..I forgot to mention that bit to you. I had it setup as <a href="http://127.0.0.1">127.0.0.1</a> and in that case also it was not working. Then for a change i altered it to <a href="http://192.168.0.241">192.168.0.241
</a>. I will test it further and let you know how it goes.</div>
<div> </div>
<div>>>>Then it's prbably firewall.</div>
<div> </div>
<div>How is it possible if both my servers are hosted on the same machine with ip <a href="http://192.168.0.241">192.168.0.241</a>.</div>
<div> </div>
<div>Thanks</div>
<div>Rakesh.<br><br></div>
<div class="gmail_quote">On Dec 27, 2007 10:43 PM, Igor Sysoev <<a href="mailto:is@rambler-co.ru">is@rambler-co.ru</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">On Thu, Dec 27, 2007 at 10:36:00PM +0530, just starting wrote:<br><br>> hi,<br>><br>> First of all my sincere thanks.<br>><br>> Error Log Entry : [2007/12/27 10:44:07 [error] 2625#0: *7 connect()
<br>> failed (111: Connection refused) while connecting to upstream, client:<br>> <a href="http://192.168.0.234/" target="_blank">192.168.0.234</a>, server: localhost, request:<br>> "GET /KdocProj/dboard.html?_dc=1198726407859 HTTP/1.0", upstream: "
<br>> <a href="http://192.168.0.241:8080/KdocProj/dboard.html?_dc=1198726407859" target="_blank">http://192.168.0.241:8080/KdocProj/dboard.html?_dc=1198726407859</a>", host: "<br>> <a href="http://192.168.0.241:8000/" target="_blank">
192.168.0.241:8000</a>"]<br>><br>> Let me explain a few things.<br>><br>> The machine where I am testing the hosting is <a href="http://192.168.0.241/" target="_blank">192.168.0.241</a>.<br>> nginx is hosted on port 8000 and jetty on 8080 on the same machine mentioned
<br>> above.<br>><br>> There is a statement in the error log like : "while connecting to upstream,<br>> client: <a href="http://192.168.0.234/" target="_blank">192.168.0.234</a>,", please note that <a href="http://192.168.0.234/" target="_blank">
192.168.0.234</a> is the local proxy<br>> server for internet access. So, what i think happening here is that nginx is<br>> trying to access the local jetty server via proxy.<br><br></div>The "client: <a href="http://192.168.0.234/" target="_blank">
192.168.0.234</a>" means that someone on <a href="http://192.168.0.234/" target="_blank">192.168.0.234</a> has connected<br>to nginx and request. nginx proxies the request to <a href="http://192.168.0.241:8080/" target="_blank">
192.168.0.241:8080</a>.<br><br>Probably you should set "proxy_pass <a href="http://127.0.0.1:8080/" target="_blank">http://127.0.0.1:8080</a>" instead<br>of <a href="http://192.168.0.241:8080/" target="_blank">
192.168.0.241:8080</a>.<br>
<div class="Ih2E3d"><br>> For Igor:<br>> >>>>The "Connection refused" usually means that backend does not listen<br>> on <a href="http://192.168.0.241:8080/" target="_blank">192.168.0.241:8080
</a> or its listen queue is full: it can not handle all<br>> requests.<br>><br>> I am the only one testing this implementation. So, I dont think the listen<br>> queue is full and also I made sure that jetty is listening on port 8080.
<br><br></div>
<div>
<div></div>
<div class="Wj3C7c"><br><br>--<br>Igor Sysoev<br><a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br><br></div></div></blockquote></div><br>