MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms

Question

I am trying to create a fullstack app reading the following tutorial:

https://medium.com/javascript-in-plain-english/full-stack-mongodb-react-node-js-express-js-in-one-simple-app-6cc8ed6de274

I followed all steps and then tried to run:

node server.js

But I got the following error:

MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms at Timeout._onTimeout (C:\RND\fullstack_app\backend\node_modules\mongodb\lib\core\sdam\server_selection.js:308:9) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7) { name: 'MongoTimeoutError', reason: Error: connect ETIMEDOUT 99.80.11.208:27017 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14) { name: 'MongoNetworkError', [Symbol(mongoErrorContextSymbol)]: {} }, [Symbol(mongoErrorContextSymbol)]: {} } (node:42892) UnhandledPromiseRejectionWarning: MongoTimeoutError: Server selection timed out after 30000 ms at Timeout._onTimeout (C:\RND\fullstack_app\backend\node_modules\mongodb\lib\core\sdam\server_selection.js:308:9) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7)

My code at server.js is as follows:

const mongoose = require('mongoose');
const router = express.Router();

// this is our MongoDB database
const dbRoute =
    'mongodb+srv://user:<password>@cluster0-3zrv8.mongodb.net/test?retryWrites=true&w=majority';

mongoose.Promise = global.Promise;

// connects our back end code with the database
mongoose.connect(dbRoute, 
    {   useNewUrlParser: true,
        useUnifiedTopology: true
    });

let db = mongoose.connection;

db.once('open', () => console.log('connected to the database'));

Any suggestions?

Did you changed `user:password` to your `username and password` in connection string? — Shivam, Dec 03 '19 at 17:30
To add to the info, I tried to connect using MongoDB compass community but it gave the same error. Can it be some settings at atLas Mongodb? — Arvind Krmar, Dec 04 '19 at 09:41
application is running well with local MongoDB "mongodb://127.0.0.1/FullStack". Appears connectivity to atlas MongoDB is the issue. — Arvind Krmar, Dec 04 '19 at 14:24
I am able to solve it. Firewall was blocking access,the same could be tested with this: http://portquiz.net:27017/ — Arvind Krmar, Dec 18 '19 at 14:45
Check here if using ProtonVPN: https://www.mongodb.com/community/forums/t/connection-timeout-over-vpn-unable-to-access-the-service/215155/1 — atineoSE, Apr 15 '23 at 15:35

score 48 · Answer 1 · edited Jun 20 '20 at 09:12

48

just go to mongodb atlas admin panel.Go in security tab>Network Access> Then whitelist your IP by adding it

See this image to locate the particular menu

Note:Check your IP on google then add it

edited Jun 20 '20 at 09:12

Community

1
1

answered Dec 14 '19 at 19:14

Kunal Usapkar

481
3
8

7

Did that, but no luck. Rather I allowed all IPs, still did not work – Arvind Krmar Dec 16 '19 at 15:06
2

bro, have you set up the DB configuration properly – Kunal Usapkar Dec 17 '19 at 05:43
I have created roles for db access: username: arvind Authentication method: SCRAM MongoDBRoles: atlasAdmin@admin Do I need to create something in cluster or 'Data Lake'? – Arvind Krmar Dec 18 '19 at 12:19
2

able to solve it, everything was correct, but the firewall was blocking access to port 27017 same can be tested here:http://portquiz.net:27017/ – Arvind Krmar Dec 18 '19 at 14:51

score 45 · Answer 2 · answered Dec 02 '21 at 17:47

45

I wasted whole day on this because the whitelist suggestion was not my issue (I'm running in docker compose with --bind_ip option set properly and I can see the Connection accepted in the mongo logs each time my client tried to connection).

It turns out, I simply needed to add this to the end of my connection string in the code:

?directConnection=true

connection string:

mongodb://myUserId:myPassword@mongodb/myDatabase?directConnection=true

I hope mongodb documents this better because I only stumbled across it from looking at the mongosh logs when I connected using that client.

answered Dec 02 '21 at 17:47

java-addict301

3,220
2
25
37

4

OMG. Cost me a day until I found this tip!! Thanks! – BruceJo Mar 14 '22 at 20:43
8

I was so happy to see this answer but it didn't help me unfortunautly as I'm using 'SRV' connection string. This is the error I'm getting after trying this solutions: "MongoAPIError: SRV URI does not support directConnection" – benshabatnoam May 25 '22 at 18:06
3

This answer is just soo helpful :) – thisisashwani Nov 04 '22 at 12:38
2

This is really helpful, wasted days before I found this. – Arun Bohra Feb 26 '23 at 07:14
`directConnection=true` is not recommended for production environments – Dennis Mar 09 '23 at 06:22
@Dennis I haven't seen this mention anywhere. Do you have a source? – java-addict301 Mar 09 '23 at 14:01
MongoDB replica set is a group of connected instances that store the same set of data. This configuration provides data redundancy and high data availability. By enabling `directConnection=true`, you are losing this feature. https://www.mongodb.com/docs/drivers/go/current/fundamentals/connection/ – Dennis Mar 09 '23 at 18:26
1

Useful for an initial connection to an instance before the replica set has been initialized. In particular, when you're connecting in order to initialize the replica set! – polo-language Mar 27 '23 at 14:05
@benshabatnoam can you instead use the connection string you see in mongosh? – java-addict301 Aug 09 '23 at 17:16

score 14 · Answer 3 · answered Jan 15 '22 at 13:21

14

In my case, this issue happened after NodeJS version upgrade from Node 14 to Node 17 and the mongoose was not connecting to MongoDB in local.

Solution - In connection string, change localhost to 127.0.0.1.

Ref - https://github.com/Automattic/mongoose/issues/10917#issuecomment-957671662

answered Jan 15 '22 at 13:21

Shriram Balakrishnan

439
5
15

Thank you. Same for me running Node 17.4.0 - There's probably a way to get Node resolving localhost but makes no difference to me so using 127.0.0.1 was a good quick fix – Alex May 13 '22 at 14:26
Simplest and most correct answer. – Kagiso Marvin Molekwa Dec 19 '22 at 19:05
Thank you, same for me upgrading from Node 14 to Node 18 – Alex Lam Aug 25 '23 at 04:48

Oluwatimilehin Odubola · Answer 4 · 2022-10-05T21:09:54.077

10

Sometimes this error occurs due to the IP Address given access to in your database.

Mind you, your application can be working well then come up with such an error. Anytime this happens, most times your IP address has changed, which is not on the whitelist of addresses allowed. (IP addresses can be dynamic and are subject to change)

All you have to do is to update the whitelist with your current IP addresses

edited Oct 05 '22 at 21:09

answered Feb 11 '20 at 09:56

Oluwatimilehin Odubola

179
2
10

4

What if 0.0.0.0 is in ip address which includes my IP address and the problem still persists? – jkalandarov Apr 16 '22 at 14:41

Bathiya Seneviratne · Answer 5 · 2020-08-05T16:53:20.863

8

I got the same error. These are the steps I followed for resolve it

Log into your Mongo Atlas account
Go to the security tab -> Network Access -> Then whitelist your IP
Then go to the security tab -> Database Access -> and delete your current user.
Create a new user by providing new username and password.
Provide that newly created username and password in the .env file or mongoose.connect method

After these steps it worked as usual. hope this will help you guys.

edited Aug 05 '20 at 16:53

answered Feb 09 '20 at 00:56

Bathiya Seneviratne

182
2
13

1

I would suggest another first step before current first step saying "Log into your Mongo Atlas account". It would make things much clearer. – okram Aug 03 '20 at 09:58
Thank you! I needed the Network Access step. – Aundra Miller Sep 25 '22 at 18:11

score 8 · Answer 6 · edited Jun 05 '20 at 13:01

8

Sometimes it will also happen when your MongoDB services are turned OFF.

Here are the steps to Turn ON the MongoDB Services:

Press window key + R to open Run window.
Then type services.msc to open services window.
Then select MongoDB server, right-click on it, finally click on the start.

edited Jun 05 '20 at 13:01

Pedro Mutter

1,178
1
13
18

answered Jun 04 '20 at 13:30

basil faheem

81
1
1

Worked for me. Thank you!! I was getting " UnhandledPromiseRejectionWarning: MongooseServerSelectionError: connect ECONNREFUSED" earlier. This hack is awesome! – Sanya Feb 16 '21 at 22:57
not seeing any MongoDB server in open services window. – s.j Apr 06 '21 at 12:38
that worked for me as well if you are using MongoDB in local that's the answer. – alireza Apr 23 '22 at 17:37

score 6 · Answer 7 · answered Jan 22 '20 at 04:16

6

Ensure that the "<" and ">" are removed when you replace the user and password fields. This worked for me

answered Jan 22 '20 at 04:16

Smartniggs

173
2
5

Daniel Danielecki · Answer 8 · 2020-02-16T18:10:30.227

4

Are you using any Antivirus, Firewall, VPN or on the restricted network (e.g. work/commercial Wi-Fi/LAN connection)? Then try to turn it off/reconnect to a different network. Some IPs/connections might be blocked by the administrator of a network that you're using or simply antivirus might have firewall policies. Even though if you have 0.0.0.0 in your IP Address at the MongoDB Atlas.

edited Feb 16 '20 at 18:10

answered Feb 14 '20 at 13:36

Daniel Danielecki

8,508
6
68
94

score 2 · Answer 9 · answered Dec 18 '19 at 14:54

I am able to solve the issue. Everything was fine, but the firewall was blocking access to port 27017. connectivity can be tested at http://portquiz.net:27017/ or using telnet to the endpoint which can be retrieved from clusters->Metrics.

Thanks, everybody for the suggestions

score 2 · Answer 10 · answered Dec 25 '19 at 07:46

Whitelist your connection IP address. Atlas only allows client connections to the cluster from entries in the project’s whitelist. The project whitelist is distinct from the API whitelist, which restricts API access to specific IP or CIDR addresses.

NOTE

You can skip this step if Atlas indicates in the Setup Connection Security step that you have already configured a whitelist entry in your cluster. To manage the IP whitelist, see Add Entries to the Whitelist.

If the whitelist is empty, Atlas prompts you to add an IP address to the project’s whitelist. You can either:

Click Add Your Current IP Address to whitelist your current IP address.

Click Add a Different IP Address to add a single IP address or a CIDR-notated range of addresses.

For Atlas clusters deployed on Amazon Web Services (AWS) and using VPC Peering, you can add a Security Group associated with the peer VPC.

You can provide an optional description for the newly added IP address or CIDR range. Click Add IP Address to add the address to the whitelist.

score 1 · Answer 11 · answered Dec 11 '19 at 15:23

1

You can remove { useUnifiedTopology: true } flag and reinstall mongoose dependecy! it worked for me.

answered Dec 11 '19 at 15:23

Matheus

27
2

3

it gives the following error when { useUnifiedTopology: true } removed: (node:10020) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor. – Arvind Krmar Dec 18 '19 at 12:32

score 1 · Answer 12 · answered Apr 12 '20 at 09:35

To anyone still struggling through this issue. I resolved this issue by setting all the parameters like username, password and dbName in mongoose options itself.

Earlier the code was like this. (When I was getting the error).

import mongoose from "mongoose";
mongoose.Promise = require("bluebird");

let dbName = process.env.DB_NAME;
const dbAddress = process.env.DB_HOST;
const dbPort = process.env.DB_PORT;
if(!dbName || !dbAddress || !dbPort){
    throw new Error("Mongo error unable to configuredatabase");
}

let options = {
    useNewUrlParser: true,
    useUnifiedTopology: true,
    user:process.env.DB_USER,
    pass: process.env.DB_PASS
};

mongoose.connect(`mongodb://${dbAddress}:${dbPort}/${dbName}`, options).catch(err => {
    if (err.message.indexOf("ECONNREFUSED") !== -1) {
        console.error("Error: The server was not able to reach MongoDB. Maybe it's not running?");
        process.exit(1);
    } else {
        throw err;
    }
});

Note that url in mongo connect. mongodb://${dbAddress}:${dbPort}/${dbName}.

New code without error.

import mongoose from "mongoose";
mongoose.Promise = require("bluebird");

let dbName = process.env.DB_NAME;
const dbAddress = process.env.DB_HOST;
const dbPort = process.env.DB_PORT;
// console.log("process.env", process.env)
if(!dbName || !dbAddress || !dbPort){
    throw new Error("Mongo error unable to configuredatabase");
}

let options = {
    useNewUrlParser: true,
    useUnifiedTopology: true,
    user:process.env.DB_USER,
    pass: process.env.DB_PASS,
    dbName: dbName
};

mongoose.connect(`mongodb://${dbAddress}:${dbPort}`, options).catch(err => {
    if (err.message.indexOf("ECONNREFUSED") !== -1) {
        console.error("Error: The server was not able to reach MongoDB. Maybe it's not running?");
        process.exit(1);
    } else {
        throw err;
    }
});

Note the options and the url.

This is my local env. Not production env.

Hope It'll be helpful.

score 1 · Answer 13 · answered Apr 21 '20 at 17:59

1

try to specify the node driver, version 2,2,12 in cluster --> connect --> connect your application. new string must be with mongodb://. use this string to connect. do not forget to enter a password

answered Apr 21 '20 at 17:59

dkovskij

11
1

score 1 · Answer 14 · answered Jul 21 '22 at 15:02

1

Most of the answers present in this thread should fix you're issue, I tried all the answers and whitelisted all the IP's but still I was not able to connect to the database.

Interestingly, my system was connected to a VPN while I was trying to connect to the mongo atlas. So, I just disconnected the VPN and was able to connect to the db. This was just an simple issue due to which I was not able to connect to the database.

answered Jul 21 '22 at 15:02

Ashfaq nisar

2,500
1
12
22

Confirmed. I was connected to a VPN and it blocked me although it was set as 0.0.0.0 for the IP range on the network access. It seems Atlas MongoDB blocks IP ranges of some known proxies. – sametcodes Jan 13 '23 at 11:58
Check here if using ProtonVPN: https://www.mongodb.com/community/forums/t/connection-timeout-over-vpn-unable-to-access-the-service/215155/1 – atineoSE Apr 15 '23 at 15:35

score 0 · Answer 15 · answered Dec 11 '19 at 00:49

0

i was has this problem, to me the solution was check if my ip be configured correctly and before confirm in this screen

enter image description here

answered Dec 11 '19 at 00:49

thiago rodrigues de santana

39
2

1

I found the solution. The issue was in firewall settings at my network system. http://portquiz.net:27017/ can be used to test if the connection is through. Though i did not change the firewall as that is managed by network admins at my end, but once the firewall corrected its working now. Thanks everybody for suggestions. – Arvind Krmar Dec 18 '19 at 14:38

score 0 · Answer 16 · answered Dec 16 '19 at 11:57

0

Please Check your Password, Username OR IP configuration. Mostly "Server selection timed out after 30000 ms at Timeout._onTimeout" comes whenever your above things are not matched with your server configuration.

answered Dec 16 '19 at 11:57

vaibhav

199
1
3

1

it was a firewall issue at my end. I corrected it and now its working – Arvind Krmar Dec 18 '19 at 14:50

score 0 · Answer 17 · answered Jan 02 '20 at 12:22

Try to make new User in Database Access with the default Authentication Method which is "SCRAM". Then make a new Cluster for that. It worked for me! My server.js file

const express = require('express');
const cors = require('cors');
const mongoose = require('mongoose');

require('dotenv').config();

const app = express();
const port = process.env.PORT || 5000;

app.use(cors());
app.use(express.json());

//const uri = process.env.ATLAS_URI;
mongoose.createConnection("mongodb+srv://u1:u1@cluster0-u3zl8.mongodb.net/test", { userNewParser: true, useCreateIndex: true,  useUnifiedTopology: true}
    );

const connection = mongoose.connection;
connection.once('once', () => {
    console.log(`MongoDB databse connection established successfully`);
})

app.listen(port, () => {
    console.log(`Server is running on port: ${port}`);
});

score 0 · Answer 18 · answered Jan 06 '20 at 13:40

0

What is your mongoose version? because there is an issue with a certain mongoose version. Please visit this link for more details "https://github.com/Automattic/mongoose/issues/8180". Anyway, I was facing the same issue but after using an older version (5.5.2), it worked for me. Please give a try and let me know what happened.

answered Jan 06 '20 at 13:40

Walid Ahmed

243
1
12

I was running into the same issue, however, I frequently develop with my VPN toggled on and off. By turning my VPN on again, I managed to connect to the DB. I'm hoping this issue is temporary, because I can't always have my VPN on. – Mike K Jan 07 '20 at 10:46

score 0 · Answer 19 · answered Feb 05 '20 at 11:29

It might basically be because of an npm update. I just updated to npm v 6.13.7. and I began to get that error.

Following instructions from @Matheus, I commented the line "{ useUnifiedTopology: true }" and I was able to get through it.

I updated mongoose and everything works fine.

score 0 · Answer 20 · answered Mar 22 '20 at 20:02

0

I had the same issue. I could connect from MongoDB Compass or my Node app using the connection strings Atlas gave me. I resolved it by adding my IP Address into the Whitelist in Atlas.

answered Mar 22 '20 at 20:02

rekwet

1
1

Margach Chris · Answer 21 · 2022-07-21T12:56:07.017

For anyone who may face this problem with mongoose v6+ and nodejs and white listing your ip has not solved it or changing from localhost to 127.0.0.1.

Solution Set the following options for the mongoose client connection options:

 mongoose.connect(url, { 
                        maxIdleTimeMS: 80000,
                        serverSelectionTimeoutMS: 80000,
                        socketTimeoutMS: 0,
                        connectTimeoutMS: 0
                        }

These options stop the mongoose client from timining out the connection before it selects a primary from the DB cluster.

Please remember to set any other options relevant to your setup like if you are running a cluster, make sure to set the replicaSet option or if you have authentication enabled, set the authSource option or the database you are connecting to dbName.

Some of these options can be set in the connection string.

The full list of options can be found here: https://mongodb.github.io/node-mongodb-native/4.2/interfaces/MongoClientOptions.html#authSource

score 0 · Answer 22 · answered Jan 23 '23 at 05:04

If your config is alright and still the error shows up, it maybe because of too much data in the db (Like for me, I am using the free tier for testing my app where I upload posts and the posts are images with some description), so I just deleted the db and it worked fine after that. Hope this helps someone.

score 0 · Answer 23 · answered Jun 13 '23 at 23:09

0

Your problem is that you don't have MongoDB installed on your computer. Once you download it you can change

mongoose.connect('mongodb://localhost:27017/blog')

to

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

answered Jun 13 '23 at 23:09

Abdelrahman Khallaf

379
3
10

score -1 · Answer 24 · answered Nov 14 '22 at 09:15

-1

This must be a temporary network issue. Please try to connect after some time and hopefully it should be fine. but make sure you white list your ip address.

answered Nov 14 '22 at 09:15

Shakil- The Coding monster

653
8
8

score -2 · Answer 25 · answered May 24 '20 at 16:51

I have solved this problem by using the following way, use a callback.

const uri = '';

mongoose
  .connect(uri, { useNewUrlParser: true, useUnifiedTopology: true }, () => {
    console.log("we are connected");
  })
  .catch((err) => console.log(err));

MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms

25 Answers25

Linked

Related