Unable to connect to Atlas Cluster via Compass - getting error “read ECONNRESET”.
Connection was working fine since last 6 months but suddenly started throwing error today. All configuration related to IP access, etc. is correctly in place and I am also able to connect to other clusters.
It is only one cluster that is throwing error. Need help urgently.
Hello @Ashish_Kapoor ,
Welcome to The MongoDB Community Forums!
Can you please confirm a few details for me to have a better understanding of this issue?
- MongoDB Compass Version being used
- Atlas Cluster tier
- Check if the number of connections in Atlas cluster exceeds the cluster tier limit
- Use the Url provided in the Atlas connection tab for the particular compass version
- Make sure the user you are trying to login with is having required roles.
PFB the answers inline:
MongoDB Compass Version being used
1.39.3 (latest version on mac)
Atlas Cluster tier
Check if the number of connections in Atlas cluster exceeds the cluster tier limit
0 connections at the moment
Use the Url provided in the Atlas connection tab for the particular compass version
Using the same URL since last several months. Was working 2 days back but not today. It is same as shown in connection tab in Atlas.
Make sure the user you are trying to login with is having required roles.
Using the same user since last several months. Was working 2 days back but not today. Even if I use a wrong username and password, I get connection error instead of auth error.
I have tried connecting to this cluster via mongodb tools and atlas cli too. Both throw same error.
I also set up the data API and tried calling it via postman. Getting the same error - “Failed to find documents: FunctionError: error connecting to MongoDB service cluster: failed to ping: connection() error occurred during connection handshake: EOF”.
I would mention here again that if I create a new cluster, which uses the same user and network access configuration, it works right away. Only the existing cluster has issues. I think it was recently automatically updated to mongodb version 7 and that has broken it. Can it be downgraded or at least restarted?
I would advise you to bring this up with the Atlas support team or connect with support via the in app chat support available in the Atlas UI. They may be able to check if anything on the Atlas side could have possibly caused this issue. In saying so, if a chat support is raised, please provide them with the following:
- Cluster link / name which experienced the issue
- Time & date including timezone for when it occurred
- Exact error message output
- Any additional details that you think will help them point to the issue