ECONNREFUSED error when connecting to mongodb from node.js

Question

I know I'm doing some very stupid and noobish, but I'm hoping someone can help me set up a basic database connection to mongodb from node.js on a mac.

I've installed mongodb using homebrew, seems to have worked quite well. I have started the server (mongod) as the locally logged in user, and opened a second terminal and confirmed that I can connect to it by using mongo. When I run mongo I get the message "connecting to: localhost:27017/test" followed by a command prompt. Ran a few commands in the mongo shell everything seems to be working there. Left both terminals open and running.

I've also confirmed that I can reach the web interface at localhost:28017.

I installed node.js and added the mongoose package. Now attempting to connect using a super simple node.js app (also running as locally logged in user):

var mongoose = require('mongoose');
mongoose.connect('mongodb://localhost/test');

I receive the following error

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: connect ECONNREFUSED
    at errnoException (net.js:901:11)
    at Object.afterConnect [as oncomplete] (net.js:892:19)

Banging my head against the wall trying to get something so simple to work. What am I missing?

Edit: Here are the logs from mongod. As you can see I tried multiple times and they're all failing rather instantaneously:

Thu Dec  5 08:19:43.700 [initandlisten] MongoDB starting : pid=14412 port=27017 dbpath=/usr/local/var/mongodb 64-bit host=mobadmins-MacBook-Pro-3.local
           08:19:43.700 [initandlisten] db version v2.4.8
           08:19:43.700 [initandlisten] git version: nogitversion
           08:19:43.700 [initandlisten] build info: Darwin mobadmins-MacBook-Pro-3.local 12.4.0 Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49
           08:19:43.700 [initandlisten] allocator: tcmalloc
           08:19:43.700 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/usr/local/etc/mongod.conf", dbpath: "/usr/local/var/mongodb", logappend: "true", logpath: "/usr/local/var/log/mongodb/mongo.log", rest: true }
           08:19:43.700 [initandlisten] journal dir=/usr/local/var/mongodb/journal
           08:19:43.700 [initandlisten] recover : no journal files present, no recovery needed
           08:19:43.729 [websvr] admin web console waiting for connections on port 28017
           08:19:43.729 [initandlisten] waiting for connections on port 27017
           08:22:34.561 [initandlisten] connection accepted from 127.0.0.1:52160 #3 (1 connection now open)
           08:22:34.563 [conn3] recv(): message len 1124073472 is too large. Max is 48000000
           08:22:34.563 [conn3] end connection 127.0.0.1:52160 (0 connections now open)
           08:24:41.298 [initandlisten] connection accepted from 127.0.0.1:52166 #4 (1 connection now open)
           08:24:41.304 [conn4] end connection 127.0.0.1:52166 (0 connections now open)
           08:25:06.938 [initandlisten] connection accepted from 127.0.0.1:52168 #5 (1 connection now open)
           08:25:06.943 [conn5] end connection 127.0.0.1:52168 (0 connections now open)
           08:25:18.220 [initandlisten] connection accepted from 127.0.0.1:52172 #6 (1 connection now open)
           08:25:18.225 [conn6] end connection 127.0.0.1:52172 (0 connections now open)
           08:25:38.811 [initandlisten] connection accepted from 127.0.0.1:52175 #7 (1 connection now open)
           08:25:38.816 [conn7] end connection 127.0.0.1:52175 (0 connections now open)

Try passing the default port in the connection URL: "mongodb://localhost:27017/test" — Hector Correa
– Hector Correa, Commented Dec 4, 2013 at 21:43
It maybe a port conflict issue.If we try running a node server with second time with a same port the same error will come — shanmugharaj
– shanmugharaj, Commented Dec 5, 2013 at 3:31
Good ideas both. However I've tried disconnecting any existing connections to the mongodb and adding the port to no avail. — agoldencom
– agoldencom, Commented Dec 5, 2013 at 13:26
Given that mongod is running and I can connect to it using mongo, this smells of some type of failure in my instance of node.js. Perhaps a reinstall could help? — agoldencom
– agoldencom, Commented Dec 5, 2013 at 14:41

Anshul · Accepted Answer · 2016-03-10 13:16:04Z

61

ECONNREFUSED error

There are few reasons of this error in node :

Your port is already serving some service so it will refuse your connection.

go to command line and get pid by using following command

$ lsof -i:port_number

Now kill pid by using

$ kill -9 pid(which you will get by above command)
Your server is not running e.g. in this case please check your mongoose server is running or run by using following command.

$ mongod
There is also possibility your localhost is not configured properly so use 127.0.0.1:27017 instead of localhost.

answered Mar 10, 2016 at 13:16

Anshul

9,51011 gold badges62 silver badges76 bronze badges

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

2 Comments

ttemple Over a year ago

The issue for me was that my local mongod was not running. My machine had crashed earlier and I forgot to start it up. Thanks for your answer! I gave it an up-vote.

Nick Taras Over a year ago

This issue I had was that I had dropped a few db's. I firstly had to use the mongod --repair flag which fixed MongoDb on my local machine. 👍

Jonathan · Accepted Answer · 2022-07-01 04:28:06Z

26

For me I had to change 'localhost' to '127.0.0.1' and then it started working again:

mongoose.connect('mongodb://127.0.0.1/test')

answered Jul 1, 2022 at 4:28

Jonathan

1,50722 silver badges16 bronze badges

Comments

agoldencom · Accepted Answer · 2017-01-18 02:50:40Z

22

OK, this was another case of not being truly forthcoming in the info I posted above. My node.js app was very simple, but I was including another couple lines in my node.js code that apparently caused this issue.

Specifically, I had another variable declared which was calling some other code that made a separate database call using incorrect db info. This is why, when using Xinzz's code, the console log error seemed not to change. It wasn't actually the mongoose.connect command that was throwing the error!

Lesson learned, localize the problem and comment out unrelated code! Sorry guys, I knew this was me being dumb.

edited Jan 18, 2017 at 2:50

answered Dec 5, 2013 at 15:17

agoldencom

1,2461 gold badge9 silver badges14 bronze badges

Comments

Xinzz · Accepted Answer · 2013-12-05 13:36:00Z

8

Use this code to setup your mongodb connection:

var mongoose = require('mongoose');

var mongoURI = "mongodb://localhost:27017/test";
var MongoDB = mongoose.connect(mongoURI).connection;
MongoDB.on('error', function(err) { console.log(err.message); });
MongoDB.once('open', function() {
  console.log("mongodb connection open");
});

Make sure mongod is running while you start the server. Are you using Express or just a simple node.js server? What is the error message you get with the above code?

answered Dec 5, 2013 at 13:36

Xinzz

2,2521 gold badge14 silver badges26 bronze badges

3 Comments

agoldencom Over a year ago

Unfortunately I receive the exact same error using the code above. Mongod is definitely running as I can view the mongod web page at localhost:28017. I am a noob so I'm not entirely sure, but I went through an installation process for node.js and I'm running the server by typing 'node app.js' in a terminal, so I believe that I'm running a simple node.js server.

Xinzz Over a year ago

ECONNREFUSED usually means that either mongo is not running or your application cannot access the port it's running on. You can access localhost:27017?

agoldencom Over a year ago

I can access localhost:27017 by using mongo from terminal. I can access localhost:28017 from a web browser. mongod is definitely running, and on that port!

Aditi Singh · Accepted Answer · 2022-12-22 11:30:19Z

6

You can just use your local IP address (e.g. 127.0.0.1), instead of using localhost.

(localhost = 127.0.0.1:27017)

'mongodb://127.0.0.1:27017/<ele.Name>'

This is how i got my solution

edited Dec 22, 2022 at 11:30

answered Dec 10, 2022 at 6:58

Aditi Singh

611 silver badge4 bronze badges

1 Comment

Roshan Over a year ago

Thank you! this worked for me. I suspect its because not everyone's local host points to 127.0.0.1:27017 by default, which can lead to problems in a node.js or python app.

pmont · Accepted Answer · 2022-08-20 03:41:58Z

5

mongod was running fine locally on my system. I could connect to it with Mongo Compass, but mongoose simply refused to connect. The magic word is directConnection=true, as in

mongodb://127.0.0.1:27017/test?directConnection=true

Versions:

mongoose 6.5.2
mongodb 4.4.13 Community
node 18.5.0

edited Aug 20, 2022 at 3:41

answered Aug 20, 2022 at 3:27

pmont

2,12923 silver badges44 bronze badges

Comments

Adit Chauhan · Accepted Answer · 2017-05-09 10:34:09Z

4

I had facing the same issue while writing a simple rest api using node.js eventually found out it was due to wifi blockage and security reason . try once connecting it using your mobile hotspot . if this be the reason it will get resolved immediately.

answered May 9, 2017 at 10:34

Adit Chauhan

693 bronze badges

1 Comment

Rahul Sonone Over a year ago

I was stuck with this for more than 5 hours and tried a lot of things, Thanks for the answer it worked immediately with hotspot. The firewall is blocking the connection.

itzhar · Accepted Answer · 2016-06-23 14:38:57Z

3

very strange, but in my case, i switch wifi connection...

I use some public wifi and switch to my phone connection

answered Jun 23, 2016 at 14:38

itzhar

13.1k6 gold badges62 silver badges65 bronze badges

1 Comment

Pero122 Over a year ago

This was also problem for me, despite it sounding strange ... i guess the local wifi had blocked some port-s, so switiching to my phone connection solved that

Sheikh Abdul Wahid · Accepted Answer · 2016-09-07 13:32:41Z

2

I had same problem. It was resolved by running same code in Administrator Console.

answered Sep 7, 2016 at 13:32

Sheikh Abdul Wahid

2,7832 gold badges29 silver badges25 bronze badges

Comments

Ezrqn Kemboi · Accepted Answer · 2019-01-12 06:16:28Z

1

I had the same issue. What I did is to run mongodb command in another terminal. Then, run my application in another tab. This resolved my problem. Though, I am trying other solution such as creating a script to run mongodb before connection is made.

answered Jan 12, 2019 at 6:16

Ezrqn Kemboi

9471 gold badge12 silver badges20 bronze badges

1 Comment

Enock Omondi Over a year ago

Did you find any other solution to this error? Just experiencing the same error when testing my REST API in Postman and I have tried figuring it out but no solution yet.

goodhyun · Accepted Answer · 2019-02-11 07:49:59Z

1

sometimes you need to check the rightfulness of the IP, firewall, port forwarding, etc, if your target database is in other machines.

answered Feb 11, 2019 at 7:49

goodhyun

5,0083 gold badges35 silver badges25 bronze badges

Comments

max · Accepted Answer · 2019-04-15 23:25:05Z

1

I had the same issue, all I did was add a setTimeout of about 10 seconds before trying to connect to the Mongo server and it solved the issue right up. I dont know why I had to add a delay but it worked...

answered Apr 15, 2019 at 23:25

max

111 bronze badge

Comments

Dashrath Mundkar · Accepted Answer · 2020-05-12 11:34:34Z

1

I also got stucked with same problem so I fixed it like this :

If you are running mongo and nodejs in docker container or in docker compose

so replace localhost with mongo (which is container name in docker in my case) something like this below in your nodejs mongo connection file.

var mongoURI = "mongodb://mongo:27017/<nodejs_container_name>";

answered May 12, 2020 at 11:34

Dashrath Mundkar

9,4823 gold badges34 silver badges48 bronze badges

Comments

Abhinit · Accepted Answer · 2021-05-25 11:45:15Z

1

I manually started the mongodb service.

Control Panel -> Administrative tools -> Services -> Mongodb

Then either start/restart it. It's done!

Happy Coding! :-)

answered May 25, 2021 at 11:45

Abhinit

211 bronze badge

Comments

Jan Švábík · Accepted Answer · 2022-09-15 13:20:36Z

1

If you're trying to connect to a remote MongoDB server and getting the ECONNREFUSED error, make sure the bind ip option is set up to 0.0.0.0.

See https://www.mongodb.com/docs/manual/core/security-mongodb-configuration/ for more information or use the MongoDB config file (mongod.conf, read more) like this:

net:
  bindIp: 0.0.0.0

answered Sep 15, 2022 at 13:20

Jan Švábík

4314 silver badges17 bronze badges

1 Comment

Stephen J Over a year ago

This is what worked for me. But first I had to systemctl stop mongod, then I used vim (I'm not a vim user, I just know i (for insert), esc (to get out of editing mode), :wq (to save file)). Now I can connect!

shriek · Accepted Answer · 2024-10-04 17:59:17Z

1

None of the answer actually answering the actual cause and just spit balling what worked for them. Here's an excerpt from the mongoose documentations itself. https://mongoosejs.com/docs/connections.html

For local MongoDB databases, we recommend using 127.0.0.1 instead of localhost. That is because Node.js 18 and up prefer IPv6 addresses, which means, on many machines, Node.js will resolve localhost to the IPv6 address ::1 and Mongoose will be unable to connect, unless the mongodb instance is running with ipv6 enabled.

answered Oct 4, 2024 at 17:59

shriek

5,8938 gold badges53 silver badges84 bronze badges

Comments

Nicholas Mberev · Accepted Answer · 2020-06-29 23:36:20Z

0

Check this post. https://stackoverflow.com/a/57589615

It probably means that mongodb is not running. You will have to enable it through the command line or on windows run services.msc and enable mongodb.

answered Jun 29, 2020 at 23:36

Nicholas Mberev

1,9211 gold badge16 silver badges14 bronze badges

Comments

bijayadhs · Accepted Answer · 2020-10-23 06:42:33Z

0

I tried every possible solution,butit didn't help me. I took a break and I changed the following. Simple typo. May help someone is same situation. From: app.listen((port)=>console.log(Server is running at port ${PORT}))

To: app.listen(PORT, console.log(Server is running at port ${PORT})) The earlier got me to connect to database mongo atlas but get request was Error: connect ECONNREFUSED

answered Oct 23, 2020 at 6:42

bijayadhs

813 bronze badges

Comments

Hakim Asa · Accepted Answer · 2020-10-29 12:08:54Z

0

you can go to mongoDB compass client and follow these steps: 1.Click Fill in connection fields individually:

2.In hostname type : 127.0.0.1

3. Click CONNECT.

answered Oct 29, 2020 at 12:08

Hakim Asa

4714 silver badges15 bronze badges

Comments

Jane Swannington · Accepted Answer · 2020-12-19 07:56:11Z

0

Mongodb was not running but I had the module for node.js The database path was missing. Fix was create new folder in the root so run sudo mkdir -p /data/db/ then run sudo chown id -u /data/db

answered Dec 19, 2020 at 7:56

Jane Swannington

31 silver badge3 bronze badges

Comments

Gabriel Aguiar Aquino · Accepted Answer · 2022-09-06 14:15:59Z

0

For my case this resolved:

Control Panel -> Administrative tools -> Services -> Start MongoDB Server

answered Sep 6, 2022 at 14:15

Gabriel Aguiar Aquino

72 bronze badges

Comments

Tigran Muradyan · Accepted Answer · 2024-10-09 02:18:10Z

I recently got the same problem, when I was connected to my iOS Personal Hotspot. I'm not sure that's only US carrier problem or no, but here what can cause an issue for connection:

1. Network Restrictions Personal hotspots, depending on the mobile carrier, can have restrictions on certain types of network traffic, such as blocking certain ports that MongoDB needs for connections. MongoDB connections often require stable and open network routes, and mobile networks can sometimes block or filter specific traffic for security or bandwidth reasons.
1. DNS Resolution ECONNREFUSED can sometimes be related to DNS issues. Hotspots may have unreliable or slow DNS resolution, especially if you're using SRV records (like mongodb+srv://), which require extra DNS lookups. If the network can't properly resolve the SRV records or the MongoDB server, you'll get connection refusal errors.

Go to MacOS Wifi Details setting -> Network -> Wifi you have connected -> Details

Add these 3 DNS : 0.0.0.0 8.8.8.8 8.8.4.4 DNS

Baboucarr Badjie · Accepted Answer · 2025-02-09 13:41:54Z

0

The following worked for me on macOS.

brew services restart mongodb-community

answered Feb 9 at 13:41

Baboucarr Badjie

3252 silver badges9 bronze badges

Comments

Capiyo · Accepted Answer · 2022-08-04 14:57:04Z

-1

Hello this is fun and I mean it's fun. Headover to start button and typeservice from there ho Down to and look for mongodb.right click it and click start. Mongod will start. Go back to your project and thank me later

answered Aug 4, 2022 at 14:57

Capiyo

11 bronze badge

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

J0s3 · Accepted Answer · 2024-01-19 10:34:18Z

-1

MongoDB Compass version 1.41.0
Windows 11

1. 2.

answered Jan 19, 2024 at 10:34

J0s3

91 bronze badge

Collectives™ on Stack Overflow

ECONNREFUSED error when connecting to mongodb from node.js

25 Answers 25

2 Comments

Comments

Comments

3 Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

25 Answers 25

2 Comments

Comments

Comments

3 Comments

1 Comment

Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Related