Server selection timed out after 30000 ms mongodb compass. We modified our code and connection URL.

Server selection timed out after 30000 ms mongodb compass Now in mongoDB compass in URI I entered mongodb://localhost:27018 and I can see Server selection timed out after 30000 ms. actually am testing local connectivity to my mongodb, but the server running mongo should be accessible from our application which running in another aws ec2 machine that's why i have used the connection string usually used in code. _onTimeout I was able to connect to MongoDB Atlas Using MongoDb Compass, A timeout occured after 30000ms selecting a server while accessing MongoDB in Azure using C#. the default value is 30000 I think it's because nginx is mainly an HTTP server so when you redirect to Mongo it tries to use the http protocol yet Mongo expects a raw TCP connection. vyshali_santhi_kumar_56490 (vyshali santhi kumar kumar) April 22, 2020, 6:08am #4. You signed out in another tab or window. I’m running version 7. 21. No issue Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question. 4-rc0" } my connection parameters as follow Keep in mind that the disconnected handler is just for monitoring/debugging. Join us! But everytime I try to ‘connect’ it says ‘server timed out in 30000’ Ramachandra_Tummala (Ramachandra Tummala) February 8, 2020, 4:49pm #4 Hi @Kushal_Somkuwar,. Cannot connect to mongoDB Atlas using mongoose : { MongoNetworkError: failed to connect to server } 2. Similarly not able to access Db from compass, ssh and the website. I am unable to connect to either my own mongodb server (docker deployment) Server selection timed out after 30000 ms But surprisingly it is possible to use the same connection string with mongodb compass or mongosh that is installed on my machine I'm running a mongodb replicaset localy the containers are up the config is okay but when I try to connect with this connection string:"mongosh mongodb://appuser:apppassword@mongo1:27017, mongo2: Skip Server Hi, I am facing the below exception intermittently. Quite rare but it does happen. js events. Getting "MongoServerSelectionError: Server selection timed out after Loading Hello. We modified our code and connection URL. I’m still stuck with the occasional ReplicaSetNoPrimary errors. By default nobody is allowed to connect. Server selection timed out after 10000 ms - Cannot connect Compass to Mongodb Compass: Connection timed out. From what I can tell you have done the best practices in your setup such as creating the MongoClient outside of the handler connection. You can configure the timeout using the serverSelectionTimeoutMS option to mongoose. I tried everything but If you’ve encountered this frustrating timeout error while working with MongoDB, you’re not alone! The "Server selection timed out after 30000 ms" message indicates that I am using mongoose to connect to a remote mongodb server as below; when running on my local machine it works fine; I can also shell into the db without any problem I deployed my node js application so a hosted domain server which i’m using mongoDB as my database. EDIT: stream needs to be on he same level as the http block. 2 Server selection timed out after 30000 ms. js MongoServerSelectionError: Server selection timed out after 30000 ms – David Wei. Join us at AWS re:Invent Mongo server selection error - MongoDB Atlas - MongoDB Developer Loading Hey, just poking in here to report that I had the same issue. 5 MongoDB version (as used by mongoose ): v. js express to connect to mongodb atlas. But yesterday was working just fine. 146 ms 64 bytes from 172. MongoServerSelectionError: Server selection timed out after 30000 ms at Timeout. Note that when I start a single node mongo with no replication everything works as expected and I can login to Mongo via Compass, but in replication mode I have issues when trying to connect to my single node replication. aggregation, node-js. conf file and then restart the mongodb server. The app I'm trying to deploy is in node js (express js). MongoTimeoutError: Server selection timed out after 30000 ms while connecting to mongoDB. Details. 6. 3. Skip to main content. It means you are not able to reach the cluster from your current network. I’m getting Unable to connect: Server selection timed out after 30000 ms. Unfortunately, during the insert process colReceived. I have connected to atlas from local env by whitelisting my IP on MongoDB atlas also, I have whitelisted my GCP VPC CIDR and mongo connector as like below I I have deployed the percona operator and MongoDB server on my kubernetes cluster. It seems that adding maxIdleTimeMS, minPoolSize, and maxPoolSize Ok thanks, let me try that. Thanks, Shubham Ranjan Curriculum Support Hello. ORIGINAL: I am new to using MongoDB - currently taking a back end course online. Contribute to mongodb-js/compass development by creating an account on GitHub. I have deployed the percona operator and MongoDB server on my kubernetes cluster. Compass can't connect to mongodb running in docker. 9. cluster0-shard-00-00-jxeqq. But there is no fix for the latest stable version? It would be great if this is documented. Viewed 542 times 1 . I checked the ping, telnet and the port availability and all is working great, but still receive “Server selection timed out after 30000 ms” in Compass. Please try to connect from some other location such as your home network. 11. MongoDB Compass connect ECONNREFUSED 127. Connection Timeout for mongodb using mongoose. connecting, node-js. 1:27017. There are some scenarios mentioned in the Free Cluster and Shared Cluster Considerations section of the Modify a Cluster documentation:. mongodb. ×. net cluster0-shard-00-01-jxeqq. This is your localhost’s(your own machine’s) IP address. Technical articles and how to use MongoDB features. Export. _onTimeout (node_modules/mongo Join us at AWS re:Invent 2024! Learn how to use MongoDB for AI use cases. We are connecting like so: const Hi @vivek_25217,. Have you made sure that you have allowed access to the Atlas cluster from the machine that’s running the code? I am trying to solve an issue that's been happening to me for a little while now. I don't have this issue connecting to the server any other way, it's only MongoDB compass and I've had the same problem on multiple machines. I have already responded to you on this thread. The problem. Solution-1 : ( if you use mongoose)> you can update your mongoDB connection url with replicaSet=rs0 query. 0. connect (uri, { serverSelectionTimeoutMS: 5000 Timed out after 30000 ms while waiting for a server that - MongoDB Loading I have tested access to the host and port using telnet and I can use mongo from the host where I’m running Compass to access the database running on another host in a container, however, Compass fails to connect and times out. Thanks, Shubham Ranjan Curriculum Services Engineer get the connection string for application / get the connection string for compass try to access it. The "Server selection timed out after 30000 ms" message indicates that MongoDB couldn’t connect within the expected time. 0150000 }, OperationsCountServerSelector }. In our dev environment we were able to successfully connect to Cosmos through the MongoDB package MongoServerSelectionError: Server selection timed out after 30000 ms Stack: MongoServerSelectionError: If the MongoDB driver can't find a server to send an operation to after serverSelectionTimeoutMS, you'll get the below error: MongoTimeoutError: Server selection timed out after 30000 ms. ; You change from an M0 free cluster to Similarly not able to access Db from compass, ssh and the website. Recorded presentations and Twitch streams. local is coming to NYC! Use code Community50 for 50% off your registration. 3. Regarding connections into Atlas from AWS Lambda, the page Manage connections with AWS Lambda might be of interest to you. If you're using MongoDB Atlas, you might have forgotten to whitelist your IP . 13). You should try wrapping your server and upstream blocks for Mongo with a stream block. I read in another post with a lot of information that the problem is that latest mongoose cannot handle well local conections, and the solution that help me as well get down mongoose version into 5. 0 you are effectively turning off the firewall and allowing all hosts on the internet to attempt to connect to your database. When starting my app, I get the following error: error: MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkTimeoutError: connection timed out backend Hi, we have a couple of “microservices”, based on NodeJS 18 with MongoDB driver 4, run via Docker. I am unable to connect to compass using both the method provided in Chapter 0 lesson : Connecting to MongoDB Using Compass. 0. Working with Data. Hi, I am getting an “MongoServerSelectionError: Server selection timed out after 30000 ms” while running qry. Your ping request was not successful. setTimeout (E: \Digital\ MongoDB server doesn’t close when pressing Ctrl+C after changing the system date to a date in the past. 27. net Hope it helps! Thanks, Shubham Ranjan Curriculum Services Engineer Hello. json to force using last version of mongodb in resolutions as follow "resolutions" : { "mongodb" : "^3. Schedule Issue Undo Transition. it’s a MONGO + SRV connection MongoServerSelectionError: Server selection timed out after 30000 ms MongoDB connection error: MongoServerSelectionError: Server selection timed out after 30000 ms at EventTarget. How i resolved Error: MongoTimeoutError: Server selection timed out after 30000 ms ,couldn't connect to server 127. 5. _onTimeout" comes whenever your above things are not matched with your server configuration. Hi @cpwolf3, The Community version of Compass does not have Schema Tab, which you need to have in Compass in order to do the labs. You shouldn't have to do any sort of connection management in the disconnected handler in Mongoose >= 6. MongoServerSelectionError: Server selection timed out after 30000 ms at Timeout from mongo atlas on GCP cloud function 2 MongooseServerSelectionError: connect ETIMEDOUT Note that running all the nodes of a replica set on the same hardware is not really safe. connect(): mongoose. I run the container using: docker run --name mongodb -v /data/db:/data/db -v /etc/mongo:/etc/mongo -p 27017:27017 -d mongo --config Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question. Plugin not loading Hi @NIKHIL_27, thanks for reverting quickly. _onTimeout { MongoTimeoutError: Server selection timed out after 30000 ms. 1. 4 MongoServerSelectionError: connection timed out with NodeJS and Express. 1:27017 Server selection timed out after 30000 ms can anyone help to sort this out. Now I see: “Server selection timed out after 30000 ms” in my compass. interceptor. I'm using MongoDB Compass to perform an aggregation on a reasonably large dataset (~2,000,000 documents, 300MB) Server selection timed out after 10000 ms - Cannot connect Compass to mongoDB on Hello, I’m using MongoDB Atlas since a few days in my Node. I already have my ip address in trusted sources. I tried I have mongodb database in digital ocean. RESULT: Server selection timed out after 30000 ms. Important details MongoServerSelectionError: Server selection timed out after 30000 ms. js and are getting a timeout. 7. When I connect I do a ‘ps’ from another window and see serverSelectionTimeoutMS=2000, but I’m not setting that. The client view of the cluster state shows the state as seen from the Java driver (which spring data uses underneath). i am trying to test connectivity to my local mongodb through mongo compass, but i still reach out same error, however the service was running properly before. The exact same connection string works everywhere else (in my code, MongoDB compass etc) but MongoDB . Thanks and Regards. Please help to fix the mongoDB/node. So there are no errors. (Server selection timed out after 30000 ms) Posted on; February 10, 2022DigitalOcean Managed MongoDB Database MongoDB; Hello. I rly cannot youse your Discover smart, unique perspectives on Mongodb Compass and the topics that matter most to you like Mongodb, Mongodb Atlas, Server selection timed out after 30000 ms ) Explanation: The connectTimeoutMS is a MongoDB Connection Option and it sets the number of milliseconds a socket stays inactive before closing during the connection phase of the driver. There’s no problem with the connection on startup. Ask Question Asked 2 years ago. If you have any doubts, please feel free to reach out to us. 1, in the file, in which you are establishing your connection to the MongoDB Server. 6. 2): 56 data bytes 64 bytes from 172. . UnhandledPromiseRejection","er Here is my mongoose script: import mongoose from 'mongoose'; const connectDB = (url) => { return mongoose. You need to add your server’s IP address where you are deploying your application. I having this problem too. G-docs opened this issue Aug 11, 2022 Server selection timed out after 30000 ms at Timeout. It might be a network/firewall related issue. You should first check MongoDB is running or not? Second, if its not on the localhost, add public IP in bindIp option of mongod. Videos. 2: seq=2 ttl=64 Do you want to request a feature or report a bug? I can't run the app on Heroku with the mongodb database. Suraj_Anand_Kupale (Suraj Anand Kupale) March 1, 2023, 11:23am 1. Hello @Edouard_Finet,. Provide details and share your research! But avoid . js:174 throw er; // Unhandled 'error' event ^ MongoTimeoutError: Server selection timed out after 30000 ms at Timeout. I am trying to insert a sample document to MongoDB DB. Originally posted by @DrakeAnglin in #2311 (comment) The error “MongoTimeoutError: Server selection timed out after 30000 ms” indicates that the MongoDB client was unable to connect to a MongoDB server within the In playing around, I was able to get a similar timeout message while trying to connect to a local replica set using Compass if my replica set name was incorrect. also Server selection timed out after 30000 ms. connect(url); }; export default connectDB; Server selection timed out after 30000 ms. 26. Looking at the logging message - the driver is having trouble connecting to the primary node. Till now I haven’t encountered any issues connection to the mongo server, but all of a sudden I keep getting this error: MongoServerSelectionError: Server selection timed out after 30000 ms at Timeout. “errorMessage”:“MongoTimeoutError: Server selection timed out after 30000 ms”,“reason”:{“errorType Join us at AWS re:Invent 2024! Learn how to use MongoDB for AI use cases. 0 Mongoose request infinite hang. MongoDB for Startups. Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers; Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand; OverflowAI GenAI features for Teams; OverflowAPI Train & fine-tune LLMs; Labs The future of collective knowledge sharing; About the company Now I can connect to the mongo6 container from the outside world like via Compass using connection string: mongodb://mongo-mydb-user:[email protected] Server selection timed out after 30000 ms server mongodb://mongo-mydb-user:pass@mongo6:27017/mydb Share. Additional information, not “Server selection timed out after 30000 ms” in my compass. null XML Word Printable JSON. Here's how to fix it (from the page I just linked): How to fix the mongoDB/node. Are you on a corporate network or behind a firewall ? Hi @MCOM,. js issue "MongoTimeoutError: Server selection timed out after 30000 ms"?Helpful? Please support me on Patreon: https://www. MongoDB Basics. Like I said, it fails 2/3 times out of 100. ERROR Unhandled Promise Rejection {"errorType":"Runtime. For our connection URL, we added the following: {useUnifiedTopology: true, useNewUrlParser: true, maxIdleTimeMS : 270000, minPoolSize : 2, maxPoolSize : 4} as the options parameters. insert(doc) I got following error: SEVERE: Servlet. I have created a connection whitelist and can connect smoothly. However, some of these services fail to reconnect in a failover situation (MongoServerSelectionError: Server selection timed out after Our test suite is kind of flacky, because mongodb memory server with replSet: 2 sometimes throws MongoBulkWriteError: Server selection timed out after 30000 ms. Timed out after 30000 ms while waiting for a server that Compass ; COMPASS-6154 "Server selection timed out after 30000 ms" to Atlas cluster. findOne()` buffering timed out after 10000ms. We have an API working with MongoDB Atlas, connection works 99% of the time, but we occasionally get a MongoServerSelectionError: Server selection timed out after 30000 ms on a specific endpoint for some reason. MongoServerSelectionError: Server selection timed out after 30000 ms So when log in to docker container in nodejs-server if I run ping : /usr/src/app/api # ping mongodb PING mongodb (172. Reload to refresh your session. Sometimes it is a week apart, and sometimes it is disconnected within a day. Server selection timed out after 30000ms. Closed. Kay_Khan May I'm using an SSH jump host to connect to the document db and I can connect via the CLI through that SSH jump host without problems. GlobalExceptionHandler - Timed out after 30000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Discussions about I use docker-compose on aws ec2 to build node. 89 It was fixed my increasing the socket settings to the approximate time taken for cluster to come up again or reelect a leader. in 2 cases above, setting useUnifiedTopology as true resulted in MongooseTimeoutError: Server selection timed out after 30000 ms in 2 cases above, setting useUnifiedTopology as false resulted in MongoNetworkError: failed to connect to server [ip:port] on first connect [MongoError: Authentication failed. This causes a problem with our monitoring since it sometimes takes the 2 seconds to connect, fails, and we receive a Unable to connect to AWS DocumentDB got "A timeout occured - MongoDB Loading Is the database running in the mongodata service container? The extract of the logs you are showing concern the app service only with a connection timeout. You can also make include for /etc/nginx/conf. Stack Overflow. Server selection error: server selection timeout, current - MongoDB Loading Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question. If the issue still persists then please feel free to get back to us. When our webapp is starting up and handling requests - everything is working just fine. @Fedor_Vinogradov @Vivek_Patel3 Yes, we found the solution. Have We are seeing intermediate issue of pod crashing with error stating MongoTimeoutError: Server selection timed out after 30000 ms when it is trying to connect I have mongodb database in digital ocean. When our webapp gets inactive/idle a few hours we a getting timeouts on new requests: System. Beyond Atlas allows/enforces ip address restrictions. service() for servlet spring threw exception com. Mongodb server selection time out with nginx, nodejs. Related questions. 1 MongooseError: Operation `users. Although they should be treated as synonyms and as I was able to rule out the general problems (which you can find as an answer in similar questions) this might just be a caching issue with chrome, like in here. <anonymou MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms. It seems that Compass has changed their interface for adding a new connection, lately, and maybe some business logic, because all guides I find use the previous one. About; mongodb; timeout; nodejs-server; Share. Hi, We are using mongodb atlas using a mongodb+srv connection. conf outside of I guess in package. obs. If this hardware fails you lose your data. am failing to connect m001-student database 4 exam it keep saying Server selection timed out after 30000 ms please help. 122 ms 64 bytes from 172. That is to say, when the application initiates a connection, when a replica set connects to new members, or when a replica set reconnects to members. Now process is a bit slow but still more reliable. Also the blog post Write A Serverless Function with AWS Lambda and MongoDB | MongoDB might be useful. MONGODB_URI=mongodb+srv: NodeJS user1$ npm start > [email protected] start > node index. I am unable to connect to it through the connection string I pasted above. Commented Apr 25, 2024 at Hello. 8. I am exposing the service externally via Loadbalancer. Could it Context I'm using GCP, more specifically GKE to deploy my app in container/pod. TimeoutException: A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Server selection timed out after 10000 ms - Cannot connect Compass to mongoDB on localhost 7 MongoDB Compass connect ECONNREFUSED 127. 4. I have checked the mongodb server also it is working fine. 2: seq=1 ttl=64 time=0. I am using node version 16. You switched accounts on another tab or window. I’m connecting to my mongo database from the server. TimeoutException: A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = WritableServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00. Server selection timed out after 30000 ms. Are you able to connect with I seem to still be having connection timeout issues with the 1. What is the expected behavior? Applicaton or DB Compass should You signed in with another tab or window. I Server selection timed out after 10000 ms - Cannot connect Compass to mongoDB on localhost. UPDATE: Fixed!!! Found the solution! Weirdest thing, after lots of searching I found one weird piece of advice that suggested adding to the connection URI: NodeJS : MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 msTo Access My Live Chat Page, On Google, Search for "hows tech Compass can't connect to mongodb running in docker. Waiting for 30000 ms before timing out com. Ops and Admin. Join us! Server selection timed out after 30000 ms”,“reason”:{“errorType”:“MongoTimeoutError”,“errorMessage”:“Server selection timed out after 30000 ms”,“name”: MongoTimeoutError: Server selection timed out after 30000 ms while connecting to mongoDB. How do I change the default? I thought it was 30 seconds. When i roll back to 1. 1 it works. I get the following error: MongoServerSelectionError: Server selection timed out after 30000 ms mongosh --host k8s-mongodb-psmdbdbr Your MongoDB server is down or inaccessible. Also increase maxSize to like 10, spring could not handle 100 connections adequately. As of this new installation today i’m no longer able to externally connnect. Sourabh Bagrecha, MongoDB In my case, I'm using loopback-connector-mongodb, but I setup my package. but the problem is, i still could not access db from localhost using the mongo-compass Server selection timed out after 10000 ms - Cannot connect Compass to mongoDB on localhost 68 MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms Hello. Drivers. It was working fine for a while then i started getting when it tried to reconnect from Everything works fine locally on my device and IP is allowed on all. Podcasts. json you add latest mongoose. Local Events: MongoDB is heading out on a world tour to meet you and bring the best content directly to you. We are doing a replicaset connection using the nodejs dirver in version 3. Exception raised : System. Most of my database operations can be performed without any issues, but it seems like I am randomly getting How can I enable access to database through my private VPN? I don’t want to disable VPN every time I want yo use your services, which is a lot of downtime for my VPN secured connection. ServerSelectionError when connecting dockerized replica set - MongoDB Loading Hello friends I have node js app deployment in fastcomet host after upgrade mongoDB in atlas to M10 become when i test app and call api the response is : Server selection timed out after 30000 ms Although when dealing with the API that i developed by nodejs and connecting to mongoDB through localhost it doesn’t have any problems and it works properly This is your localhost’s(your own machine’s) IP address. The problem I'm encountering is this error: Server selection timed out after 30000 ms. Closed 1 task done. Ask Question Asked 4 years, 11 months ago. Server selection timed out after 10000 ms - MongoDB Loading Mongodb compass was working fine but it stops working now. Modified 2 years ago. If you apply an IP address allowance for IP address 0. MongoDB . But when I'm trying to connect to the MongoDB MLab DB account, code gives MongoTimeoutError: Server selection timed out after 30000 ms. Can not connect to mongodb locally: Server selection timed out after 30000 ms. Hi, Thanks for reaching out. 0 with thoses options Following up from my previous post. So, I’m closing this thread as duplicate. I myself am not using Docker or any vm. Hello. MongoDB. MongoServerSelectionError: Server selection timed out after 30000 ms. After some time. The same is true if I downgrade the node module to 3. d/*. Configure the IP for anywhere, username and password, the message is "MongoTimeoutError: Server selection timed out after 30000 ms Announcing MongoDB Atlas Vector Search and Dedicated Search Nodes for genAI use cases. MongoDB Developer Community Forums Getting "MongoServerSelectionError: Server selection timed out after 30000 ms" with AWS Lambda. “Connection ended” in my mongo logs. It looks like you’re attempting to connect to an Atlas cluster using code written in Node. net cluster0-shard-00-02-jxeqq. js API with mongodb version 4. 14. Getting time out errors when trying to Are you connecting via compass? What version of compass you are using? What are the connection parameters Are you able to ping the server Make sure no firewall I was able to connect to it when I first created the replica set, BUT when I restart my computer and then try to connect to it again, the connection will timeout. Community Day 2021 Sessions · 📺 Replay Community How-To's and Articles. Also to note is that this doesn't seem to happen all the time, however today I was unable to retreive any of my data Prerequisites I have written a descriptive issue title Mongoose version 6. Changing the cluster tier requires downtime in the following scenarios: You change from an M0 free cluster or M2/M5 shared cluster to an M10 or larger cluster tier. 1 Node. MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms 2 { MongoTimeoutError: Server selection timed out after 30000 ms I have a mongoDB atlas for application. MongoTimeoutException: Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Here is Hello. patre It’s possible that the public IP address that you’re connecting from changed. 2: seq=0 ttl=64 time=0. As @prasad_ pointed out, it can help to change localhost to 127. This app connects to MongoDB Atlas (free tier M0). Nick (Nick Singleton) December 10, 2020, 1:18pm 2. Export MongoDB timeout error - Other MongoDB Topics - MongoDB Developer Loading If you are not sure, you can check to see if you can reach the MongoDB port(27017 from your stacktrace) using a third party site, MongoDB connection error: MongoTimeoutError: Server selection timed out after 30000 ms. Mongodb compass was working fine but it stops working now. Asking for help, clarification, or responding to other answers. First, thanks for your kind advice. We have a huge debug output, and I cannot tell for sure which part of it is really relevant. So I was following this MongoDB tutorial and it tells me to make a hosted database with atlas MongoDB and then connect it with compass, but after I filled the connection fields it always shows this Skip to main content. 2022, 4:50pm 1. Hi @jiajing_zachmy_78370, The class atlas cluster consists of three different nodes and you must be able to make outgoing requests to all these three nodes. I recommend opening a support case hey, I tried adding my MongoDB to my chartbrew instance. Mostly "Server selection timed out after 30000 ms at Timeout. mongo 785×429 46 KB. js version 14 MongoDB version 5 Operating system macOS Operating Server selection timed out after 30000 ms? #12259. The GUI for MongoDB. I am using the connection as below. I think most developers would want to test with replica set due to multi document transaction requiring a replica set. But, the db connection will be disconnected suddenly, and the disconnection time is irregular. 13. Hi @Jamelle_Mobley and welcome to the MongoDB Community forums!. From the information provided, it does not look like there's any obvious issue with your setup. Those microservices connect to a PSA replica set (MongoDB 5. Hi, I am getting an Hello. Type: Bug Resolution: Gone away Mongoose version : v5. Modified 4 years, 11 months ago. 0 and mongoose version of 6. Debug Output. 2 Hi @Soni,. Daniel_20816 (Daniel Workneh) January 17, 2020, 9:45pm #1. dqsc. oqdjc mlebkx jgtog qsvryh opvrj klhxv trtx ejfliwlq vbbon sxfqf