Connection string is not working

Hi I’m trying to connect DB as mentioned in chapter 1 using the below command

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/aggregations?replicaSet=Cluster0-shard-0” --authenticationDatabase admin --ssl -u m121 -p aggregations --norc

It is not working. May I know the root cause?
Is cluster down, because getting below stack trace

MongoDB shell version: 3.2.8
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/aggregations?replicaSet=Cluster0-shard-0
2020-11-07T16:30:03.798+0530 I NETWORK [thread1] 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
2020-11-07T16:30:03.804+0530 I NETWORK [ReplicaSetMonitorWatcher] starting
2020-11-07T16:30:04.952+0530 I NETWORK [thread1] Detected bad connection created at 1604746804056431 microSec, clearing pool for cluster0-shard-00-00-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:06.033+0530 I NETWORK [thread1] Detected bad connection created at 1604746805184969 microSec, clearing pool for cluster0-shard-00-01-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:07.141+0530 I NETWORK [thread1] Detected bad connection created at 1604746806261726 microSec, clearing pool for cluster0-shard-00-02-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:07.142+0530 W NETWORK [thread1] No primary detected for set Cluster0-shard-0
2020-11-07T16:30:07.143+0530 I NETWORK [thread1] All nodes for set Cluster0-shard-0 are down. This has happened for 1 checks in a row. Polling will stop after 29 more failed checks
2020-11-07T16:30:08.765+0530 I NETWORK [thread1] Detected bad connection created at 1604746807870385 microSec, clearing pool for cluster0-shard-00-00-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:09.831+0530 I NETWORK [thread1] Detected bad connection created at 1604746808978799 microSec, clearing pool for cluster0-shard-00-02-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:11.022+0530 I NETWORK [thread1] Detected bad connection created at 1604746810071797 microSec, clearing pool for cluster0-shard-00-01-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:11.022+0530 W NETWORK [thread1] No primary detected for set Cluster0-shard-0
2020-11-07T16:30:11.024+0530 I NETWORK [thread1] All nodes for set Cluster0-shard-0 are down. This has happened for 2 checks in a row. Polling will stop after 28 more failed checks
2020-11-07T16:30:12.698+0530 I NETWORK [thread1] Detected bad connection created at 1604746811761579 microSec, clearing pool for cluster0-shard-00-00-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:13.823+0530 I NETWORK [thread1] Detected bad connection created at 1604746812923140 microSec, clearing pool for cluster0-shard-00-01-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:14.982+0530 I NETWORK [ReplicaSetMonitorWatcher] Detected bad connection created at 1604746814039582 microSec, clearing pool for cluster0-shard-00-02-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:14.982+0530 W NETWORK [ReplicaSetMonitorWatcher] No primary detected for set Cluster0-shard-0
2020-11-07T16:30:14.984+0530 I NETWORK [ReplicaSetMonitorWatcher] All nodes for set Cluster0-shard-0 are down. This has happened for 3 checks in a row. Polling will stop after 27 more failed checks
2020-11-07T16:30:16.616+0530 I NETWORK [thread1] Detected bad connection created at 1604746815713654 microSec, clearing pool for cluster0-shard-00-02-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:17.776+0530 I NETWORK [thread1] Detected bad connection created at 1604746816847926 microSec, clearing pool for cluster0-shard-00-00-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:19.877+0530 I NETWORK [thread1] Detected bad connection created at 1604746818996066 microSec, clearing pool for cluster0-shard-00-01-jxeqq.mongodb.net:27017 of 0 connections
2020-11-07T16:30:19.878+0530 W NETWORK [thread1] No primary detected for set Cluster0-shard-0
2020-11-07T16:30:19.880+0530 I NETWORK [thread1] All nodes for set Cluster0-shard-0 are down. This has happened for 4 checks in a row. Polling will stop after 26 more failed checks
2020-11-07T16:30:19.884+0530 E QUERY [thread1] Error: connect failed to replica set 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 :
connect@src/mongo/shell/mongo.js:223:14
@(connect):1:6

exception: connect failed

It could be your shell version issue
I can connect to the cluster with same command you used

Unable to connect to cluster - No primary detected

Thank you issue is because of mongo shell I am using, upgraded the shell version and now the connection string is working fine.

You can use either of them

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/aggregations?replicaSet=Cluster0-shard-0” --authenticationDatabase admin --ssl -u m121 -p aggregations --norc

mongo “mongodb://m121:aggregations@cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017/aggregations?authSource=admin&replicaSet=Cluster0-shard-0&readPreference=primary&ssl=true&norc=true