[COMPASS-3470] ERROR: Could not connect to MongoDB on the provided host and port Created: 26/Feb/19  Updated: 07/Mar/19  Resolved: 07/Mar/19

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: 1.17.0-beta.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mickael DBOUK Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

TEST


Attachments: PNG File screenshot-1.png    

 Description   

I am not able to connect to Atlas using  below credentials,

I am getting this error:  Could not connect to MongoDB on the provided host and port

knowing that  2 weeks ago  I could connect to the Atlas server without a problem and I don't have firewall restriction on port 27012.

Hostname: cluster0-shard-00-00-jxeqq.mongodb.net

Username: m001-student

Password: m001-mongodb-basics

Replica Set Name: Cluster0-shard-0

Read Preference: Primary Preferred

 



 Comments   
Comment by Massimiliano Marcon [ 07/Mar/19 ]

Hi mickael.dbouk@gmail.com, I have tried to reproduce the problem but I couldn't.

From your last comment, I see that you are unable to connect via the shell, so the problem is definitely not Compass. You might have some issues related to your network configuration.

Comment by Mickael DBOUK [ 28/Feb/19 ]

Hi Brian,

thank you for your feedback! 

my mistake, the port number is 27017

however, I am still not able to reach the Altas student cluster

thank you for your help 

 

mongo "mongodb://cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017/test?replicaSet=Cluster0-shard-0" --authenticationDatabase admin --username m001-student --password m001-mongodb-basics

MongoDB shell version v4.0.5

connecting to: mongodb://cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017/test?authSource=admin&gssapiServiceName=mongodb&replicaSet=Cluster0-shard-0
2019-02-28T14:47:20.749+0100 I NETWORK [js] Starting new replica set monitor for Cluster0-shard-0/cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017
2019-02-28T14:47:20.937+0100 W NETWORK [ReplicaSetMonitor-TaskExecutor] Unable to reach primary for set Cluster0-shard-0
2019-02-28T14:47:20.937+0100 I NETWORK [ReplicaSetMonitor-TaskExecutor] Cannot reach any nodes for set Cluster0-shard-0. Please check network connectivity and the status of the set. This has happened for 1 checks in a row.
2019-02-28T14:47:21.751+0100 W NETWORK [js] Unable to reach primary for set Cluster0-shard-0

 

 

 

Comment by Brian Blevins [ 27/Feb/19 ]

Hi Mikael,

> don't have firewall restriction on port 27012.

Please note that the M001 student cluster uses the default MongoDB port, 27017. See also the screenshot from Massimiliano.

The port you mentioned is not correct for the M001 student cluster.

Regards,
Brian

Comment by Massimiliano Marcon [ 26/Feb/19 ]

Can you try 1.17-beta.6? I just tried and I can't reproduce the problem. I attached my connection screen.

Generated at Wed Feb 07 22:33:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.