CODEWITHSUNDEEP
node.jsmongoosemongodb-atlas
Arvind Krmar
Arvind Krmar

Reputation: 2602

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

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?

Upvotes: 71

Views: 271343

Answers (30)

DasElias
DasElias

Reputation: 569

Even though the top answer seems to have the problem solved for me at first glance, it didn't fix the underlying root cause. In particular, this workaround has the downside of forcing the connection to a single MongoDB instance, hence bypassing the benefits of high availability and failover provided by replica sets.

For me, the issue was that I was connecting to a replica set, but forgot to initialize it. According to the MongoDB documentation, this can be done by connecting via mongosh to the instance and run

rs.initiate()

Note that the replica set needs to be initiated just once.

Upvotes: 0

jethiya007
jethiya007

Reputation: 57

LISTEN I EXPERIENCED A SIMILAR SITUATION BEFORE EVEN THOUGH I ALREADY SET MY IP: 0.0.0.0/0

just log in to Mongo Atlas (Click on your project) then go to the network option on the left side it will be towards the bottom of the menu.

Just change your IP use choose my current IP option.

Image to navgate

after a while, this method also stopped working and I tried to write this in cmd mongosh that's when I saw the directConnection=True and tried and it worked though I have neglected this before since I didn't understand how: https://stackoverflow.com/a/70204195/22236947

enter image description here

Upvotes: 0

abhi3700
abhi3700

Reputation: 170

I tried all the possible approaches like IP whitelisting. But still it didn't work.

These are the URI formats that I had tried:

MONGODB_URI=mongodb://USERNAME:[email protected]:27017,ac-xdtjxkm-shard-00-01.xrlfvc5.mongodb.net:27017,ac-xdtjxkm-shard-00-02.xrlfvc5.mongodb.net:27017/?ssl=true&connectTimeoutMS=30000&serverSelectionTimeoutMS=30000&w=majority&tlsAllowInvalidCertificates=true&authSource=admin&replicaSet=atlas-3wdz0g-shard-0
MONGODB_URI=mongodb+srv://USERNAME:[email protected]/
MONGODB_URI=mongodb://USERNAME:[email protected]:27017
MONGODB_URI=mongodb+srv://USERNAME:[email protected]/?retryWrites=true&w=majority&appName=Cluster0

Also, I tried these URIs with other providers than heroku like Koyeb, Render, Azure.

In fact, I also switched the cluster from M0 to M10, switching from FREE to Premium. Reason being may be the DB caller (i.e. API server) is not able to discover the Server location fast enough before timeout error.

But, same issue.

Then, finally I thought about changing the MongoDB provider altogether to providers like DigitalOcean (don't have FREE plan unlike MongoDB).

It worked! 🎉

Upvotes: 0

Hm Elius Hossain Himel
Hm Elius Hossain Himel

Reputation: 88

This solution fixed the problem for me.

const client = new MongoClient(uri, {
  serverApi: {
    version: ServerApiVersion.v1,
    strict: true,
    deprecationErrors: true,
    directConnection: true,
  },
});

Upvotes: 0

Aswin
Aswin

Reputation: 511

Finally found the solution after so many trial and error. All I had to do was to add this at the end of my Mongodb URI :

mongodb+srv://<username>:<password>@YourAppName.wo509tr.mongodb.net/**?retryWrites=true&w=majority&appName=YourAppName**

retryWrites=true&w=majority&appName=YourAppName <- this was the part i was missing

Upvotes: -1

mahdi
mahdi

Reputation: 493

In my case i blocked the ip scan in the server using a script and because of that my app could not connect to db

Check the scripts you have ran

Upvotes: 0

Matthias Harter
Matthias Harter

Reputation: 106

This error also occurs when the declared hosts do not match the specified replica set. e.g.mongodb://cluster-name1-shard-00-00.wplyy.mongodb.net:27017,cluster-name1-shard-00-01.wplyy.mongodb.net:27017,cluster-name1-shard-00-02.wplyy.mongodb.net:27017/my-database?ssl=true&authSource=admin&replicaSet=other-cluster-name-shard-0

Upvotes: 0

Abdelrahman Khallaf
Abdelrahman Khallaf

Reputation: 533

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

Upvotes: 0

Irfan wani
Irfan wani

Reputation: 5075

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.

Upvotes: 0

Shakil- The Coding monster
Shakil- The Coding monster

Reputation: 1077

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.

Upvotes: -1

Oluwatimilehin Odubola
Oluwatimilehin Odubola

Reputation: 199

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

Upvotes: 10

Ashfaq nisar
Ashfaq nisar

Reputation: 2709

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.

Upvotes: 1

Margach Chris
Margach Chris

Reputation: 1729

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

Upvotes: 0

Shriram Balakrishnan
Shriram Balakrishnan

Reputation: 509

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

Upvotes: 19

java-addict301
java-addict301

Reputation: 4106

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.

Upvotes: 83

Bathiya Seneviratne
Bathiya Seneviratne

Reputation: 302

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

  1. Log into your Mongo Atlas account
  2. Go to the security tab -> Network Access -> Then whitelist your IP
  3. Then go to the security tab -> Database Access -> and delete your current user.
  4. Create a new user by providing new username and password.
  5. 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.

Upvotes: 10

basil faheem
basil faheem

Reputation: 91

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

Here are the steps to Turn ON the MongoDB Services:

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

Upvotes: 9

atul beniwal
atul beniwal

Reputation: 37

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

Upvotes: -2

dkovskij
dkovskij

Reputation: 11

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

Upvotes: 1

Lalit Sharma
Lalit Sharma

Reputation: 374

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.

Upvotes: 1

rekwet
rekwet

Reputation: 1

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.

Upvotes: 0

Daniel Danielecki
Daniel Danielecki

Reputation: 10512

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.

Upvotes: 6

Foz
Foz

Reputation: 98

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.

Upvotes: 0

Smartniggs
Smartniggs

Reputation: 300

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

Upvotes: 7

Walid Ahmed
Walid Ahmed

Reputation: 243

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.

Upvotes: 0

Adarsh Pawar
Adarsh Pawar

Reputation: 738

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:[email protected]/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}`);
});

Upvotes: 0

Kushal
Kushal

Reputation: 31

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.

Upvotes: 2

Arvind Krmar
Arvind Krmar

Reputation: 2602

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

Upvotes: 3

vaibhav
vaibhav

Reputation: 297

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.

Upvotes: 0

Kunal Usapkar
Kunal Usapkar

Reputation: 551

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

Upvotes: 55

Related Questions