Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for Mongo 3.6 connection strings
See original GitHub issueI’m using the MongoDb from https://cloud.mongodb.com/ and the version 3.6 offers me a connection string like this:
mongodb+srv://foo:myRealPassword@cluster0.mongodb.net/test
When I try to use it, I simply receive MongoError: getaddrinfo ENOTFOUND. Any thoughts? If I switch back to mongodb://foo:myRealPassword@mycluster0-shard-00-00.mongodb.net:27017,mycluster0-shard-00-01.mongodb.net:27017,mycluster0-shard-00-02.mongodb.net:27017/admin?ssl=true&replicaSet=Mycluster0-shard-0&authSource=admin it works.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@michaelauderer In my opinion Monk should be updated. It is a tiny layer over mongo and it should bring in the new driver to support enhancements and features offered by new version of mongo.
The package is still using “mongodb”: “^2.1.18”, which does not support the new connection string format by mongo. As per the official mongo docs mentioned here, the native driver needs to be updated to v3.0.0 in order to utilise the new DNS Seedlist Connection Format.