The connection dialog says Set Name is (Optional), however, if I don't enter the name of the replica I get:
Cannot connect to replica set "connection"[server:port]. Set's primary is unreachable.
Reason:
No member of the set is reachable.
Entering the name of the replica makes this error go away.
Hi, May I ask how you connect to repl Set?
below is the error message i got
Cannot connect to replica set "repl_2"[localhost:28002].
A primary with different host name [127.0.0.1:28001] found in server side. Please double check if same host names and ports are used as in server's replica set configuration.
If same set name is used for different replica sets, this configuration is supported only on different instances of Robomongo. Please open a new Robomongo instance for each replica set which has the same set name.
Reason:
Different members found under same replica set name "test".
+1
Tried connecting to Replica set without name and got the error
Set's primary is unreachable.
Reason:
SSL tunnel failure: Network is unreachable or SSL connection rejected by server.
However, if I entered my replica set name into Optional set name field which was case senstive (capital letter for cluster name.) Then it worked.
Try using mongodb Compass and seeing if you can connect
The ask here is simply to remove "(Optional)" from the GUI.
I ran into this also, but got connected thanks to the comments here.
As a developer, not a DBA, I didn't realize what exactly the replica set name was so my first few attempts to name it were unsuccessful. I eventually found it through db.isMaster(). In addition to making this field mandatory, it might be helpful to add a quick tooltip letting users know what exactly this is and where to find it.
+1 confirmed this is still a thing on 1.2.1. I also got the SSL tunnel failure: Network is unreachable or SSL connection rejected by server. Entering the name fixed it
Confirmed. Adding name fixes SSL tunnel failure: Network is unreachable or SSL connection rejected by server. error. I recommend making the name, not optional. I will say it worked for a while without the name then for some reason stopped working but adding the name fixed it.
Luckily a google search brought up this thread.
Same issue here with version 1.2.1.
I'm able to establish a direct connection with each member but not to the entire replica set.
As a further information to investigate this issue, in my configuration I'm using authentication (SCRAM-SHA-1) and SSL (self-signed certificate).
I am able to connect using Robomongo 1.3.1

Removing the name, worked for me
I couldn't manage to get around this problem. But in the end I managed to make it work.
Specifying/removing the name wasn't working for me. I had to:
cmd + q)I guess it is somehow stuck with other connections that are open and it tries to connect to the new one expecting the cluster name to be the name of one of the already open connections.
I can connect just fine to my Heroku instance using Robomongo, but Robo3t times out with SSL or fails with the set name missing.
I can not connect even if set name is empty. anyone please help
I can not connect even if set name is empty. anyone please help
Use Robomongo, or if you want to save queries, Nosqlclient instead.
Update: Manually importing the connection string data worked. 'Twasn't a replicaSet using SSL as the (badly sized) "From SRV" button set for me!
Removing the name, worked for me
this worked for me too
For me the network security in Atlas was configured to allow only IP whitelist. Just added my IP and it workes.
Can someone please guide here: https://stackoverflow.com/questions/52945978/unable-to-connect-to-mongodb-replica-set-from-other-server-using-robo3t-and-in-c ?
I am using Robo 3T 1.3.1. I want to connect to my replica set using SSH. How do I do this?
I tried all possible solutions listed in GitHub.
Already done
Error showing as
Failed to connect to
via SSH tunnel
Question
I need to add the IP address or replica name as a member? None worked though.
I couldn't manage to get around this problem. But in the end I managed to make it work.
Specifying/removing the name wasn't working for me. I had to:
- disconnect from all the other connections (I had other connection to clusters open)
- Quit Robo3T. (With a mac, do not close it but quit it with
cmd + q)- Re-open Robo3T, Now the connection should work since it is the first one you will open
I guess it is somehow stuck with other connections that are open and it tries to connect to the new one expecting the cluster name to be the name of one of the already open connections.
It perfectly worked for me. Thanks
Set the primary and secondary members of the set.
Example:
cluster-shard-00-00-zzzz.mongodb.net:27017
cluster-shard-00-02-zzzz.mongodb.net:27017
cluster-shard-00-01-zzzz.mongodb.net:27017
And enable SSL protocol with Self-signed Certificate as the authentication method.
I also managed to make it work by using v 1.3 which has the option to specify from Mongo SRV connection string.
mongodb+srv://username:[email protected]/dbname?retryWrites=true&w=majority
@jtavara23 - Thanks for the response.
I'm using below URL for making a connection in Robo Mongo, it still not working
mongodb://user:password@abc0011:27027,xyz0012:27027,mno0013:27027/employees?replicaSet=Employee_Stage_RS&authSource=employees
- Set the primary and secondary members of the set.
Example:
cluster-shard-00-00-zzzz.mongodb.net:27017
cluster-shard-00-02-zzzz.mongodb.net:27017
cluster-shard-00-01-zzzz.mongodb.net:27017- And enable SSL protocol with Self-signed Certificate as the authentication method.
I also managed to make it work by using v 1.3 which has the option to specify from Mongo SRV connection string.
mongodb+srv://username:[email protected]/dbname?retryWrites=true&w=majority
This helped me, thank you!
What worked for me was the following
Downloading the version 1.3.1 for MacOs from here
Using the option From SRV where you must input the string that Atlas should provide you. This autofill most fields.
Check the tabs Authentication and SSL. _Perform authentication_ should be checked and also _Use SSL protocol_ with _Self-signed Certificate_.
Auth mechanism SCRAM-SHA-1
Hope this help somebody, bye!
Hi,
I am trying to connect to local host using Robo3t 1.3 to via SSH and get the below error.
Failed to create SSH Tunnel to xxx.xxx.xxx.xx:22,.
Error: Resource temporarily unavailable. Error when starting up SSH session: -8
. (Error #11).
I tried with both password authentication as well as Private key. No luck!
Any help on this is appreciated.
Most helpful comment
The ask here is simply to remove "(Optional)" from the GUI.