Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm using a fresh install of Centos 5.5. I have Node installed and working (I'm just using Node -- no apache, or nginx.), but I cannot figure out how to make a simple server on port 80. Node is running and is listening to port 80. I'm just using the demo app:

var http = require('http');
http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World\n');
}).listen(80, "x.x.x.x");
console.log('Server listening to port 80.');

When I visit my IP, it does not work. I obtained my ipaddress using ifconfig. I've tried different ports. So there must be something I am missing.

What do I need to configure on my server to make this work? I would like to do this without installing apache or nginx.


Edit-- Ok so, I installed nginx and started it up, to see whether or not it is related to node, and I don't see its welcome page. So it definitely has something to do with the server.

Am I retrieving the IP Address correctly by running: ifconfig then reading the inet addr under eth0?

share|improve this question
Best not to have your server running as root. If you need root to bind to port 80, drop the permissions after any listen() method calls. e.g. add something like this to the end of your script: try { process.setgid(desiredGroupName); process.setuid(desiredUserName); } catch (e) { console.log('will not run as root: ' + e); process.exit(1); } – Walf Mar 1 '12 at 12:26

Are you running it as root? Otherwise, you will not be able to bind to port 80.

What happens if you change the port number to something (free) above 1024?

Also, what happens if you specify the IP address to listen on, as in the example here?

share|improve this answer
I'm running "sudo node app.js" to run the app, so I think it's binding properly. I have tried other ports above 1024, but they don't work either, so I believe it has something to do with the server. Same deal when specifying the IP address. – Luke Burns Jun 8 '11 at 19:30
After installing and running nginx, I don't see its welcome page. So it's not a problem with node. – Luke Burns Jun 8 '11 at 20:05
There seems nothing wrong with your code! When I run it through node.js only on either localhost ( or my local servers IP (192.168.x.y) on port 88 I get "Hello World". Both with "lynx"; or with Firefox. – Henk Jun 8 '11 at 20:10
The little experience I have running a server tells me that there's a lot I could be completely unaware of. I do believe I'm obtaining my IP the correct way. – Luke Burns Jun 8 '11 at 20:35

As said in my comment the code works (I ran it as root on FreeBSD).

In Linux (aka localhost) is bound to interface "lo". Interface "eth0" should have a different IP-address.
Stop node; turn off nginx (so port 80 is free); put the eth0-address (so not in the above code instead; restart node and try to connect again to port 80 on the other IP-address.

Hint: check with "netstat -ltn" to what IP-address port 80 is bound and try to connect to that address.

share|improve this answer
Oops sorry, I was using the eth0-address. Sorry for the confusion. Node binds the address to port 80, so when I run netstat, I just get the same address I configured my node app with. – Luke Burns Jun 8 '11 at 21:20

don't know if this is still bothering you, however I once ran into kinda the same error on my Debian 6.0: I could connect with a local browser (same machine) using:



firefox http://[public_ip]:80

from any other computer to the named Debian system resulted in "connection refused". So what I did was to just leave out the ip setting inside my demo code:

var http = require('http');
var port = 8080 ;
var now  = new Date();
// create server
http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.write('Hello World - this is node.js\n');
  res.write('Date on server: ' + now.toGMTString());
}).listen(port, "");
console.log('Server running at port: ' + port);

hope that helps, that did it for me. Note that I changed the port setting to 8080 because there was another server running on port 80 already.

share|improve this answer

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.