502 Bad Gateway when using ExpressJS with nginx

Mark picture Mark · Mar 22, 2011 · Viewed 19.8k times · Source

If I run my expressjs app like so: coffee server.coffee and navigate to localhost:8080, everything works just fine.

However, when I reverse proxy 8080 with nginx with the following configuration:

server {
    listen 0.0.0.0:80;
    server_name localhost;
    access_log /var/log/nginx/nodetest.log;

    location / {
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $http_host;
      proxy_set_header X-NginX-Proxy true;

      proxy_pass http://node/;
      proxy_redirect off;
    }
}

upstream node {
    server 127.0.0.1:8080;
}

I get the following error in the Chrome Dev console:

GET http://184.73.217.204/socket.io/xhr-polling//1300750540040 502 (Bad Gateway)

and the following in nginx's error.log

2011/03/22 13:07:59 [error] 10269#0: *18 upstream prematurely closed connection while
reading response header from upstream, client: 168.229.58.68, server: localhost, 
request:     "GET /socket.io/xhr-polling//1300799281533 HTTP/1.1", upstream:     
"http://127.0.0.1:8080/socket.io/xhr-polling/1300799281533", host: "184.73.217.204",    
referrer: "http://184.73.217.204/"

Any guidance appreciated!

Answer

CyberDem0n picture CyberDem0n · Mar 22, 2011

Try this patch...

    -proxy_pass http://node/;
    +proxy_pass http://node;