Hello all, we are using MongoDB Serverless and connecting to it from AWS Lambda. I realized that after a while (a few minutes) of idle, subsequent database queries returns this error:
MongoNetworkError: connection 1 to *IP*:27017 closed
at Connection.onClose (.../node_modules/mongodb/lib/cmap/connection.js:134:19)
at TLSSocket.<anonymous> (.../node_modules/mongodb/lib/cmap/connection.js:62:46)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.emit (node:domain:489:12)
at node:net:301:12
at TCP.done (node:_tls_wrap:588:7)
The next few requests will continue to fail as each connection within the pool fails and reconnects. At one point the failures will subside, until I leave it idle for X minutes, and the problem will surface again.
Maybe it’s because your current ip address and ip address in mongodb atlas are not the same.
you need to add your current address to network access in mongodb atlas project that are you working on or add 0.0.0.0/0 to ip address list and this will make any Someone who can log in has a connection to the database (I recommend the first method)
the second option is really an easy alternative to do with. can you specifying the first option, please? Like we need to adding extra option script inside our code or something.
because it will throw some error when you just adding a character. you need to add your currenet IP address over and over after you make changes.
Through Network access option , Whitelist your current IP address or simply allow access from everywhere, i.e. 0.0.0.0/0 (includes your current IP address), also ensure that you have good internet connection.
This worked in my case. Hoping same for others.
Currently getting the same error inside AWS using a lambda connecting to a mongodb instance.
What is different is that the connection does work for most of the collections in the database. It is only one collection that while not large in terms of mongo collections is the larger than our other collections in our instance.
Very weird that it would be happening with just one collection.
edit: this is related to the size of the collection being read. In testing, limiting the size of the collection to 50 items does get past the error, but not useful for a production solution.