Question

"connect ETIMEDOUT .........:27017" When connecting to MongoDB database

I have two identical databases, one for staging and another for production, each on a separate droplet and I already added my IP to the “Inbound Rules” so I can connect. I was able to connect to the database using the uri that belongs to the production database, but failing to connect to the staging one. An important note here is that others are able to connect to both.

Any idea what could be causing this?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @rashagh22,

Assume you are trying to access MongoDB Managed database cluster from your local machine. I will suggest you try again after removing and re-adding your local machine IP address in the database cluster trusted source.

To fetch local machine IP: https://whatismyipaddress.com/

If you are still not able to access the MongoDB cluster after the above step, please open a support case with DigitalOcean.

https://docs.digitalocean.com/support/

Regards, Rajkishore