Mongo server selection error

Jamelle_Mobley · 2022-09-04T15:37:23.431Z

Can someone help? I am getting this error.


May Node me with you
listening on 3000
MongoServerSelectionError: Server selection timed out after 30000 ms
    at Timeout._onTimeout (/Users/melle/Desktop/crud for demo/node_modules/mongodb/lib/sdam/topology.js:293:38)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  reason: TopologyDescription {
    type: 'ReplicaSetNoPrimary',
    servers: Map(3) {
      'ac-r8gp4rs-shard-00-01.adm9hgw.mongodb.net:27017' => [ServerDescription],
      'ac-r8gp4rs-shard-00-00.adm9hgw.mongodb.net:27017' => [ServerDescription],
      'ac-r8gp4rs-shard-00-02.adm9hgw.mongodb.net:27017' => [ServerDescription]
    },
    stale: false,
    compatible: true,
    heartbeatFrequencyMS: 10000,
    localThresholdMS: 15,
    setName: 'atlas-wpmlmp-shard-0',
    maxElectionId: null,
    maxSetVersion: null,
    commonWireVersion: 0,
    logicalSessionTimeoutMinutes: null
  },
  code: undefined,
  [Symbol(errorLabels)]: Set(0) {}
}

Doug_Duncan · 2022-09-04T19:38:27.161Z

Hi @Jamelle_Mobley and welcome to the MongoDB Community forums!

It looks like you’re attempting to connect to an Atlas cluster using code written in Node.js and are getting a timeout. Have you made sure that you have allowed access to the Atlas cluster from the machine that’s running the code? Can you connect via the mongosh command line tool?

Jamelle_Mobley · 2022-09-06T02:25:59.519Z

I recreated everything, even a new account just incase I did something wrong. I even tried compass and still get the same problem. I added and deleted the IP address more than once and it is still not working.

Doug_Duncan · 2022-09-06T03:26:55.604Z

Were you able to connect to your cluster via the mongosh command line tool? Did you temporarily allow access to 0.0.0.0/0 which will not block any access for testing? If you are not able to connect when 0.0.0.0/0, then it would seem that you would have a VPN or firewall blocking your access to the Atlas server.

I can verify that the connection gets closed after 30 seconds from my machine, which is what I would expect as my IP address is not in the allow list either explicitly or in a range of allowed IPs. My test was against the old cluster which is still running, because you didn’t give any information about the newly rebuilt one.

Jamelle_Mobley · 2022-09-07T22:55:53.920Z

It did not work with 0.0.0.0/0, but it did work with my iPhone, I used it as a hot spot. As of now I am not connected with a vpn, I guess it could be my router causing it. Because I have the IP address from my router.

MongoServerSelectionError: Server selection timed out after 30000 ms
    at Timeout._onTimeout (/Users/melle/Desktop/crud for demo/node_modules/mongodb/lib/sdam/topology.js:293:38)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  reason: TopologyDescription {
    type: 'ReplicaSetNoPrimary',
    servers: Map(3) {
      'ac-jas6yzg-shard-00-02.3anzuip.mongodb.net:27017' => [ServerDescription],
      'ac-jas6yzg-shard-00-01.3anzuip.mongodb.net:27017' => [ServerDescription],
      'ac-jas6yzg-shard-00-00.3anzuip.mongodb.net:27017' => [ServerDescription]
    },
    stale: false,
    compatible: true,
    heartbeatFrequencyMS: 10000,
    localThresholdMS: 15,
    setName: 'atlas-2hvnvb-shard-0',
    maxElectionId: null,
    maxSetVersion: null,
    commonWireVersion: 0,
    logicalSessionTimeoutMinutes: null
  },
  code: undefined,
  [Symbol(errorLabels)]: Set(0) {}
}

Chibuzo_Ekwue · 2024-05-06T08:29:15.508Z

Having the same issue trying to connect with prisma

Hirdesh_Parsediya · 2024-10-27T10:23:19.506Z

nodejs mongodb driver 6.9.0 is the culprit if you are using node version >=18.

downgraded mongodb driver worked for me. But took some time.

Manali_Dave · 2024-11-21T12:42:10.995Z

Hello MongoDB team,
I have mongodb server setup to which my pm2 service connects.
But randomly I am getting below error in pm2
MongoServerSelectionError: connection timed out
at Timeout._onTimeout (/opt/opin-portal-new-api/node_modules/mongodb/lib/sdam/topology.js:292:38)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)

but everything is proper in mongodb server like replica status, secondary mongodb instances, arbiter, telnet is also working to 27017 port
After killing pm2 service & restarting it again issue resolves.
Please help me to resolve this error without restarting PM2 service