Reputation: 1236

ECONNREFUSED error when connecting to mongodb from node.js

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)

Upvotes: 73

Answers (25)

Baboucarr Badjie

Reputation: 315

The following worked for me on macOS.

brew services restart mongodb-community

Upvotes: 0

Tigran Muradyan

Reputation: 123

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

Upvotes: 0

shriek

Reputation: 5833

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.

Upvotes: 1

J0s3

Reputation: 9

MongoDB Compass version 1.41.0
Windows 11

1. 2.

Upvotes: -1

Aditi Singh

Reputation: 61

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

Upvotes: 6

Jan Švábík

Reputation: 411

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

Upvotes: 1

Gabriel Aguiar Aquino

Reputation: 7

For my case this resolved:

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

Upvotes: 0

pmont

Reputation: 2129

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

Upvotes: 5

Capiyo

Reputation: 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

Upvotes: -1

Jonathan

Reputation: 1439

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')

Upvotes: 26

Abhinit

Reputation: 21

I manually started the mongodb service.

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

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

Happy Coding! :-)

Upvotes: 1

Jane Swannington

Reputation: 3

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

Upvotes: 0

Hakim Asa

Reputation: 461

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.

Upvotes: 0

bijayadhs

Reputation: 81

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

Upvotes: 0

Nicholas Mberev

Reputation: 1851

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.

Upvotes: 0

Dashrath Mundkar

Reputation: 9204

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>";

Upvotes: 1

max

Reputation: 11

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...

Upvotes: 1

goodhyun

Reputation: 5002

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

Upvotes: 1

Ezrqn Kemboi

Reputation: 937

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.

Upvotes: 1

Adit Chauhan

Reputation: 69

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.

Upvotes: 4

agoldencom

Reputation: 1236

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.

Upvotes: 22

Sheikh Abdul Wahid

Reputation: 2773

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

Upvotes: 2

itzhar

Reputation: 13031

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

I use some public wifi and switch to my phone connection

Upvotes: 3

Anshul

Reputation: 9480

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.

Upvotes: 62

Xinzz

Reputation: 2252

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?

Upvotes: 8

ECONNREFUSED error when connecting to mongodb from node.js

Answers (25)

Related Questions