Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've just set up nginx as a reverse proxy, so some sites served from the box are served directly by it and others are forwarded to a Node.js server.

The site being served by Node.js, however, is displayed with no CSS or images, so I assume the links are somehow being broken, but don't know why.

The following is the only file in /etc/nginx/sites-enabled:

server {

    listen   80; ## listen for ipv4
    listen   [::]:80 default ipv6only=on; ## listen for ipv6


    access_log  /var/log/nginx/localhost.access.log;

    location / {
            root   /var/www;
            index  index.html index.htm;

    location /myNodeSite {
            proxy_redirect off;
            proxy_set_header Host $host;

I had thought perhaps it was trying to find them in /var/www due to the first entry, but removing that doesn't seem to help.

share|improve this question
Can you please save your resulting HTML files from when the proxy is on and when it's off and run diff against them? – Jeff Ferland Mar 14 '12 at 14:07
No difference in the HTML file at all according to diff. – tsvallender Mar 14 '12 at 14:22
up vote 4 down vote accepted

Without more details this is just a guess, but on your frontend you've made your node.js available at /myNodeSite. If your node.js site returns something like this:

<img src="/images/myimage.png"/>

The client will request /images/myimage.png...which will not get directed to your node.js site, since it doesn't start with /myNodeSite. There are a few solutions:

  • Make your node.js application(s) aware of the prefix you're using on the frontend so that they generate appropriate links. Always generate links via some sort of function that takes this into account, rather than statically encoding links.
  • Implement some sort of rewriting feature on the frontend. I don't know nginx, but for Apache there's mod_proxy_html.

You may also be able to use exclusively relative links (no leading /) on your node.js site, but this implies a very flat site layout and is easy to break.

share|improve this answer
My brain was almost there but for some reason wasn't quite thinking from the right angle. Cheers. – tsvallender Mar 14 '12 at 14:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.