 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
9 messages in ru.sysoev.nginxRe: Please explain this 502 Bad Gatew...| From | Sent On | Attachments |
|---|---|---|
| just starting | Dec 27, 2007 7:20 am | |
| Igor Sysoev | Dec 27, 2007 8:28 am | |
| Aleksandar Lazic | Dec 27, 2007 8:30 am | |
| just starting | Dec 27, 2007 9:05 am | |
| Igor Sysoev | Dec 27, 2007 9:13 am | |
| just starting | Dec 27, 2007 10:39 am | |
| Igor Sysoev | Dec 27, 2007 10:52 am | |
| just starting | Dec 27, 2007 11:32 am | |
| Igor Sysoev | Dec 28, 2007 2:01 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread 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 error | Actions... |
|---|---|---|
| From: | just starting (just...@public.gmane.org) | |
| Date: | Dec 27, 2007 9:05:37 am | |
| List: | ru.sysoev.nginx | |
hi,
First of all my sincere thanks.
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"]
Let me explain a few things.
The machine where I am testing the hosting is 192.168.0.241. nginx is hosted on port 8000 and jetty on 8080 on the same machine mentioned above.
There is a statement in the error log like : "while connecting to upstream, client: 192.168.0.234,", please note that 192.168.0.234 is the local proxy server for internet access. So, what i think happening here is that nginx is trying to access the local jetty server via proxy.
For Igor:
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.
I am the only one testing this implementation. So, I dont think the listen queue is full and also I made sure that jetty is listening on port 8080.
Thanks, Rakesh.
PS: I appreciate for your quick reply. Frankly I haven't hoped for such quick reply. Hope you do well in the future.
On Dec 27, 2007 10:00 PM, Aleksandar Lazic
<al-n...@public.gmane.org> wrote:
Hi,
On Don 27.12.2007 20:50, just starting wrote:
hi,
I am using version 0.5.34.
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:
Which clearly say:
the connection to 192.168.0.241 on port 8080 with protocol http was not successful.
What is in the jetty log? Are you able to reach jetty with curl, curl -v http://192.168.0.241:8080/ ? Is a FW between nginx & jetty?
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"]
Cheers
Aleks