Compass Error Message Trying to Connect via Favorites

MongoDB University
#1

I’m now in Chapter 3 but am posting here because it has to do with Compass connection. My favorites links have been working but today trying to connect to the class’s Atlas cluster to answer a quiz question, I got the error message – An error occurred while loading navigation: ‘not master and slaveOk=false’: It is recommended to change your read preference in the connection dialog to Primary Preferred or Secondary Preferred or provide a replica set name for a full topology connection.

I’ll try to go forward using a shell connection instead but really want to get the Compass connection working again. No idea how to do that.

#2

Use one of these two connection strings in Compass and you’ll be fine going forward:

  • mongodb://m001-student:m001-mongodb-basics@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&replicaSet=Cluster0-shard-0&readPreference=primary

  • mongodb+srv://m001-student:m001-mongodb-basics@cluster0-jxeqq.mongodb.net/test?authSource=admin&readPreference=primary

1 Like
#3

Thanks!

Oddly, my favorites connection sprang to life and worked again!

But if the failure reoccurs I’ll know what to do.

Again - many thanks.

#4

There’s a difference between what you currently have (which can cause the error during a Primary node election) and what I shared above. Suggest changing your connection string or you’ll get the same error message in the future.

1 Like
#5

Thanks for the heads up. I may just have to go back to Chapter 1 and start from scratch connecting first to the class’s Atlas database, then to my own, uploaded database in order to get new connection strings.

#6

The connection string above is for the Class (public) cluster.
You can re-use the same connection string for your own Sandbox (private) cluster by changing the jxeqq part of the node(s) accordingly. Or get it directly from Atlas, no need to start from scratch.

#7

Hi @Margaret_38982,

In addition to @007_jb,

Most likely your are directly connecting to a node in the cluster. Nodes can change their state form Primary to secondary and vice-a-versa from time to time due to various reasons.

So, you are able to connect fine when the node is in Primary state but when it switches to secondary state you get an error message.

Please make the changes recommended by @007_jb in the above post.

~ Shubham

#8