I keep getting error when i try connecting node to mongodb

Rama_Nuril_Anwari_Bandung · 2024-09-19T11:23:23.238Z

i already whitelisted my ip but still error but if i set ip to 0.0.0.0/0 it works but i dont want to set it to 0.0.0.0/0 i want to set it to my own ip address. do you have any solution?

Clan_VI_T_NAM_TITAN · 2024-09-20T19:00:56.993Z

I added the IP address to the whitelist but it didn’t work. Even using 0.0.0.0

Alon_Berkman · 2024-09-23T18:46:46.237Z

It happened to me when I upgraded mongo node.js driver from 6.3.0 to 6.9.0.
Downgrading back to 6.3.0 and the issue is gone.

Filipe_Calixto_Oliveira · 2024-09-25T19:54:17.464Z

downgrading to 6.3 worked for me too

Filipe_Calixto_Oliveira · 2024-09-27T10:15:14.701Z

update: I updated my node version the latest LTS (v20.17.0) and everything is working fine with the new driver

Onur_Can_Ak · 2024-09-29T18:49:50.615Z

it seems there is an issuea with “6.9.0”, downgrading “6.1.0” (which I use my older projects) worked for me

fazil_MUHAMMED · 2024-09-29T18:50:23.726Z

This worked for me too!! thanks !

Alon_Berkman · 2024-10-17T20:08:12.018Z

Apparently, the issue is on version 6.9.0 which contains a breaking change:

image804×286 35.5 KB

Here are two ways I found to overcome this issue:

downgrading to a lower version (6.8.2 for ex)
passing autoSelectFamily: false overriding the default value of true

Hope someone on MongoDB will see this discussion and revert this breaking change, or alternatively - document this as a breaking change on their release notes.

P.S.
I would totally understand if this new behavior was communicated on previous release notes, allowing developers to get prepared for that (+ adding a runtime warning might do as well), but since I didn’t find any evidence for that - it is a breaking change published out on 6.9.0 without any prior notification.

Neha_H · 2024-10-17T20:10:26.703Z

upgrading to latest node version worked for me as well!

Sharbel_Mousa · 2024-10-20T23:31:52.606Z

Thanks alot man this is really helpoed me with option 2 adding the autoSelectFamily: false

Elia_Wise · 2024-10-27T10:25:33.437Z

Here a code that solve the issue for me:


const { MongoClient } = require("mongodb");

const uri =
  "mongodb+srv://<name>:<pw>@<server>/<db></db>?retryWrites=true&w=majority";

const client = new MongoClient(uri, {
  tls: true,
  serverSelectionTimeoutMS: 3000,
  autoSelectFamily: false,
});

async function connectToDatabase() {
  try {
    await client.connect();
    console.log("Connected to MongoDB successfully.");
    // Add your database operations here
  } catch (error) {
    console.error("Connection failed", error);
  } finally {
    await client.close();
  }
}

connectToDatabase();

Keval_Deepak · 2024-11-11T04:07:10.078Z

Amazing, Option 2 was a life saver!

Andrew_Parker · 2024-11-18T12:09:20.675Z

autoSelectFamily: false - This was what I needed. Thanks!

carlos_andres · 2024-11-28T23:16:12.803Z

if you mongoose version is 8> the problen never disapire you need to use a old version like 6 or 7 that resolved the error

Shai_Maarek · 2024-11-28T23:17:01.453Z

Than you so much, I’m new to Mongodb so this was very frustrating experience… Youre suggestion to use autoSelectFamily: false solved the problem!

Cesc_Riera_Amatriain · 2024-12-17T03:17:08.708Z

i know im mssing the version but wont work still

Cesc_Riera_Amatriain · 2024-12-17T03:17:19.034Z

Im trying to connect to my database from Render, when i do it locally it works but when i deploy my app on render it dosent i get the same error i tried lowering the version and autoSelectFamily false but nothing works

const client = new MongoClient(uri, {
serverApi: {

    autoSelectFamily: false
},

});

this is my client idk if here is the problem or what, im using atlas and put the 0.0.0.0 to allow all conections but nothing

Assad_Rahimi · 2025-01-05T22:06:27.417Z

this error comes me to and i just install the latest version and the error gone. there is the comment npm i mongodb@latest

Aditya_Madhav · 2025-01-07T11:25:32.756Z

I upgraded to node version 20 along with “mongodb”: “^6.12.0”,
It solved the issue.

Xander_Ash · 2025-04-04T07:51:01.750Z

Add 0.0.0.0/0 as an IP address (if at all security is not your concern) in network access tab