Node.js connect only works on localhost


I've written a small node.js app, using Connect, that serves up a web page, then sends it regular updates. It also accepts and logs user observations to a disk file.

It works fine as long as I am on localhost, but I can't get other commputers on the same intranet to see it. I am using port 3000, but changing to port 8080 or 80 didn't help.

Here is the code I am using to set up the connection:

var io = require(''),
  connect = require('connect');

var app = connect().use(connect.static('public')).listen(3000);
var chat_room = io.listen(app);

As stated above, I've tried changing the port number to 8080 or to 80, and didn't see any difference, so I don't think that it is a firewall problem (but I could be wrong). I've also thought about, after reading similar questions dealing with HTTP, to add to the listen() but it doesn't seem that listen() takes an IP mask parameter.

Problem courtesy of: schaz


Most probably your server socket is bound to the loopback IP address instead of the "all IP addresses" symbolic IP (note this is NOT a netmask). To confirm this, run sudo netstat -ntlp (If you are on linux) or netstat -an -f inet -p tcp | grep LISTEN (OSX) and check which IP your process is bound to (look for the line with ":3000"). If you see "", that's the problem. Fix it by passing "" to the listen call:

var app = connect().use(connect.static('public')).listen(3000, "");
Solution courtesy of: Peter Lyons


Working for me with this line (simply add --listen when running) :

node server.js -p 3000 -a : --listen

Hope it helps...

Discussion courtesy of: Meloman

Fedora or Centos distro check your selinux and firewalld in my case firewalld prevented the connection:

Selinux: $sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   {{checkmode}}
Mode from config file:          {{checkconfig}}
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      30

Firewalld status: $systemctl status firewalld
Discussion courtesy of: soloproper

Binding to is half the battle. There is an ip firewall (different from the one in system preferences) that blocks TCP ports. Hence port must be unblocked there as well by doing:

sudo ipfw add allow tcp from any to any

Discussion courtesy of: Ashish Kaila

I have a very simple solution for this problem: process.argv gives you a list of arguments passed to node app. So if you run:

node server.js

You'll get:

process.argv[0] //=> "node"
process.argv[1] //=> "server.js"
process.argv[2] //=> ""

So you can use process.argv[2] to specify that as the IP address you want to listen to:

http.listen(3000, process.argv[2]);

Now, your app is listening to "all" IP addresses, for example:

I hope this will help someone!

Discussion courtesy of: akelec

On your app, makes it reachable from any device in the network:

app.listen(3000, "");

For NodeJS in Azure, GCP & AWS

For Azure vm deployed in resource manager, check your virtual network security group and open ports or port ranges to make it reachable, otherwise in your cloud endpoints if vm is deployed in old version of azure.

Just look for equivalent of it for GCP and AWS

Discussion courtesy of: ClusterAtlas

To gain access for other users to your local machine, i usually use ngrok. Ngrok exposes your localhost to the web, and has an NPM wrapper that is simple to install and start:

$ npm install ngrok -g
$ ngrok http 3000

See this example usage:

enter image description here

In the above example, the locally running instance of sails at: localhost:3000 is now available on the Internet served at: or

Discussion courtesy of: arcseldon

This recipe can be found in it's original form on Stack Over Flow.