-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 1.13.0
-
Component/s: Compass, Connectivity, Security
-
None
Attempting to use the SSH tunnel option in Compass to connect to an Atlas cluster secondary member fails. Even if the user identifies a secondary member for the connection and specifies a read preference of "Secondary", the following error is displayed.
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.
Note that while there are special restrictions on M0 (free tier) clusters, the example in the screenshots is an M30 cluster.
- is related to
-
COMPASS-2744 Stuck in "loading navigation": db.admin() does not inherit full settings from db
- Closed