NGINX as proxy of Node.js

Question

I'm using NODE.js behind NGINX server, this is my Nginx configuration:

upstream example.it {
        server 127.0.0.1:8000;
}

server {
        server_name www.example.it;

        location / {
                proxy_pass      http://example.it;
                proxy_redirect  off;
                proxy_set_header   Host             $host;
                proxy_set_header   X-Real-IP        $remote_addr;
                proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
        }
}

All works good, the requests are correctly sent from nginx to node BUT I saw a problem in the log file generated from Express.js.

The problem is that ALL THE REQUESTS are saved as done from 127.0.0.1, why?

I don't seen any remove hosts (the real ip of who made the request).

Thanks

Andrew Newdigate · Accepted Answer · 2012-12-10 11:47:40Z

11

Assuming you're using Express 3.0, a better way to do this is through the trust proxy setting.

From the Express documentation:

trust proxy Enables reverse proxy support, disabled by default

In order to use it:

app.set('trust proxy', true);
app.use(express.logger('default'));

This has the added advantage of working correctly when you're using a proxy as when you're not (for example in a development environment).

answered Dec 10, 2012 at 11:47

Andrew Newdigate

6,2253 gold badges40 silver badges32 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Rodrigo Polo Over a year ago

You can also have different settings for loggin, one for development and one for production, like this: // Settings for development app.configure('development', function(){ app.use(express.logger('dev')); }); // Settings for production app.configure('production', function(){ app.set('trust proxy', true); app.use(express.logger('default')); }); Then change your enviroment vars like this (Linux/Unix) NODE_ENV=production PORT=3000 node app.js Windows: SET NODE_ENV=production && SET PORT=3000 && node app.js

Linus Thiel · Accepted Answer · 2012-02-19 16:26:15Z

10

That's correct, as nginx will be the remote host. You need to specify a custom log format to log the X-Forwarded-For header, see the connect logger documentation.

app.use(express.logger(':req[X-Forwarded-For] - - [:date] ":method :url HTTP/:http-version" :status :res[content-length] ":referrer" ":user-agent"'));

answered Feb 19, 2012 at 16:26

Linus Thiel

39.3k9 gold badges112 silver badges104 bronze badges

1 Comment

Douglas Muth Over a year ago

Thank you so much for posting this. I found it via a Google search to solve the same problem I was having just now.

Collectives™ on Stack Overflow

NGINX as proxy of Node.js

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related