Mongodb Atlas mongodb+srv connection fails timeout
hi,
i am migrating my existion db from mLab to mongoDB Atlas
from mLab my connection is fine - type: mongodb://
when i try connection to my new Atlas db with type: mongodb+srv:// it fails by time out
connection by Node.js is fine
connection by mongodb shell is fine
mongoBooster log:
17:25:48.459 *** Starting MongoClient.connect ***
{"options":{"appname":"NoSQLBoosterV5.2.3-beta.1_213154.520","autoReconnect":true,"keepAlive":60000,"poolSize":0,"promoteLongs":false,"promoteValues":false,"reconnectTries":172800,"socketTimeoutMS":0,"ssl":true,"sslValidate":false,"useNewUrlParser":true},"uri":"mongodb+srv://*******:******@farmer-develop-wibuu.mongodb.net/farmer_develop?authSource=farmer_develop&retryWrites=true&ssl=true&w=majority"}
17:26:40.581 *** Connect Error ***
{"code":"ETIMEOUT","errno":"ETIMEOUT","hostname":"_mongodb._tcp.farmer-develop-wibuu.mongodb.net","message":"querySrv ETIMEOUT _mongodb._tcp.farmer-develop-wibuu.mongodb.net","stack":"Error: querySrv ETIMEOUT _mongodb._tcp.farmer-develop-wibuu.mongodb.net\n at QueryReqWrap.onresolve [as oncomplete] (dns.js:197:19)","syscall":"querySrv"}
I like this idea 
this is my connection URI:
mongodb+srv://<username>:<password>@farmer-develop-wibuu.mongodb.net/farmer_develop?retryWrites=true&w=majority
this is my connection URI:
mongodb+srv://<username>:<password>@farmer-develop-wibuu.mongodb.net/farmer_develop?retryWrites=true&w=majority
if i use legacy URI:
mongodb://<username>:<password>@farmer-develop-shard-00-00-wibuu.mongodb.net:27017,farmer-develop-shard-00-01-wibuu.mongodb.net:27017,farmer-develop-shard-00-02-wibuu.mongodb.net:27017/farmer_develop?ssl=true&replicaSet=farmer-develop-shard-0&authSource=admin&retryWrites=true&w=majority
i can get connection but no db collections available - see image:
if i use legacy URI:
mongodb://<username>:<password>@farmer-develop-shard-00-00-wibuu.mongodb.net:27017,farmer-develop-shard-00-01-wibuu.mongodb.net:27017,farmer-develop-shard-00-02-wibuu.mongodb.net:27017/farmer_develop?ssl=true&replicaSet=farmer-develop-shard-0&authSource=admin&retryWrites=true&w=majority
i can get connection but no db collections available - see image:
I can confirm the same problem with Atlas.
@Daniel Givoni you can actually use the From URL button to import the mongodb+srv url
It should work with your database but the $external database will cause error popups on the bottom right forever.
I can never make the legacy URI work, it only shows $external and admin databases as your screenshot shows, which is not the database I told it to use. And I can use the nodejs MongoDB module to connect the database with the same URI.
I can confirm the same problem with Atlas.
@Daniel Givoni you can actually use the From URL button to import the mongodb+srv url
It should work with your database but the $external database will cause error popups on the bottom right forever.
I can never make the legacy URI work, it only shows $external and admin databases as your screenshot shows, which is not the database I told it to use. And I can use the nodejs MongoDB module to connect the database with the same URI.
Thank you for your feedback. Version 5.2.3 is a little out of date. Please download the latest version(5.1.12) and try again. I tried my own atlas server and it works well. If the latest version cannot be successfully connected, can you give me a temporary read-only test account? in order to solve this problem, I first need to reproduce the problem locally.
Thank you for your feedback. Version 5.2.3 is a little out of date. Please download the latest version(5.1.12) and try again. I tried my own atlas server and it works well. If the latest version cannot be successfully connected, can you give me a temporary read-only test account? in order to solve this problem, I first need to reproduce the problem locally.
i successfully connected after restarting mongoBooster -thanx
i updated to 5.2.12 and all is good.
you can close issue
i successfully connected after restarting mongoBooster -thanx
i updated to 5.2.12 and all is good.
you can close issue
Replies have been locked on this page!