Skip to content

Embed URL

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Set up nginx as a reverse proxy to node.js.

The idea is to have nginx installed and node installed. I will extend this gist to include how to install those as well, but at the moment, the following assumes you have nginx 0.7.62 and node 0.2.3 installed on a Linux distro (I used Ubuntu).

In a nutshell,

1) nginx is used to serve static files (css, js, images, etc.) 2) node serves all the "dynamic" stuff.

So for example, www.foo.com request comes and your css, js, and images get served thru nginx while everything else (the request for say index.html or "/") gets served through node.

3) nginx listens on port 80. 4) node listens on port 8124 (for this example only. you can change this port for your node app).

So in your /etc/nginx/sites-available/default modify your location / stanza and add the second stanza of this code block:

location / { proxy_pass http://127.0.0.1:8124; #this is the ip:port where your node app runs root /var/www/yoursitename; expires 30d; #uncomment this is you want to name an index file: #index index.php index.html;
access_log off; }

    location ~* ^.+\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$ {
        root   /var/www/yoursitename/public;
    }

Note: I did not change the /etc/nginx/nginx.conf file. It is still the default nginx.conf from the nginx installation.

Now, restart nginx.

/etc/init.d/nginx restart

(Re)start your node app.

node /path/to/your/node/app.js

Navigate to your site and verify.

Enjoy blazing fast static files and blazing fast dynamic content.

@paulomcnally

I'm add:

location /socket/ {
    proxy_pass http://127.0.0.1:3300;
  }

load domain.com/socket/ Return

<?xml version="1.0"?><!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"><cross-domain-policy><allow-access-from domain="*" to-ports="*"/></cross-domain-policy>

What is the problem?

thanks

@mccarmo

Thanks a lot man!! :)

@bmrinal

well what will be the pcre if the static files needs to be served from the location /test/ location instead of root?

What portions would be changed in this:
location ~* ^.+.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$ {

@mm0

as long as /test/ is within the document root you don't need to change anything.

try this if that doesn't work:

location ~* .*.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$ {
access_log off;
expires max;
root /var/www/yoursitename/public;
}

@kahboom

Very helpful; thanks!

@hncen

3Q!

@mattvleming

"I will extend this gist to include how to install those as well." Did you ever get a chance to write those? This gist is handy. :)

@ghost
Unknown commented

The content you are editing has changed. Reload the page and try again.

helpful, thanks.

Attach images by dragging & dropping or selecting them. Uploading your files… Unfortunately, we don’t support that file type. Try again with a PNG, GIF, JPG. Yowza, that’s a big file. Try again with an image file smaller than 10MB. This file is empty. Try again with a file that’s not empty. This browser doesn’t support file attachments. We recommend updating to the latest Internet Explorer, Google Chrome, or Firefox. Something went really wrong, and we can’t process that file. Try again.

Nothing to preview

@sisingh

When nodejs provides sendfile(), how would nginx be beneficial over nodejs to serve static files ?

@efosao

@sisingh - Nginx is a lot faster than node at serving static files & performing optimizations such as gzip and caching. That is why even though node can serve static files as you correctly pointed out, this is not the best solution. Depending on your web server backend, it is best to let nginx, Apache, or IIS handle the serving of static files.

@cybermarkus1

Hi, whats happen if i have subroutes inside my node app? im not able to make it works, my app is running on 8002 port and i have the following conf:

  #proxy to a node app running on 8002 port
  location ^~ /auth/ {
      proxy_pass http://localhost:8002/;

redirect works, but when im trying to go to a any node app'subroute, nginx dont know what to do and returns a 404.

any idea?
thanks

@carlosazaustre

In my case I have API Rest on Node in localhost:3000 and I call this with:

location /api {
    proxy_pass              http://localhost:3000;
    proxy_buffering         on;
}

Now, my app on mydomain.com serves the frontend and if I call mydomain.com/api serves my API Rest.

I hope this help you :+1:

@murindwaz

@cybermarkus1 I am having exactly the same problem like you, do you remember how you solved that problem? thanks!

@idriskhenchil

Same problem here @cybermarkus1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.