Robomongo: Replica set not using SSH tunnel?

[phw]

Using Robomongo 1.0.0-RC4 I try to connect to a replica set using an SSH tunnel, but I always get the error message "No member of the set is reachable". Using a direct connection to connect to the primary however works, it is just when I try to use the new replica sets option that it fails. The members are all specified correctly

I cannot currently test with a server that allows me direct connection, but I have that suspicion that the replica set option does not use the SSH tunnel properly and tries to do a direct connection.

[simsekgokhan]

Hi @phw , sorry for the inconvenience, unfortunately SSH support for replica set connections is not completely supported for all cases. I will update our page accordingly: https://github.com/paralect/robomongo. For now you may use single connection.

Or you can use SSH port forwarding using Putty on Windows and using terminal on MAC. But you will have to setup instances of port forwarding for nodes of replica set.

Workaround solution:
SSH port forwarding on MAC, Linux and Windows:
RM-SSH_port_forwarding_on_MAC_Linux_and_Windows-130217-1049.zip

We definitely plan to provide full SSH support for Replica Set connections in the next releases.
Please, let us know if you need further help.

[phw]

Thanks for the quick response. Yes, I could setup individual port forwarding, but for now I will just stick to connect to a primary directly, that works for me ok for now :) Just wanted to make sure the issue is known.

Looking forward to the 1.0 final release. Great work so far 👍

[simsekgokhan]

Thanks a lot : )

[pauln]

This sounds as though it might be the same issue as #1297 - see my comment over there for more detail, but essentially RoboMongo is overwriting the list of hosts which you configure in the connection with one retrieved from the first host - so it tries to connect using the remote addresses rather than your local ports which are being forwarded/tunnelled to the actual server(s).

[simsekgokhan]

Hi @pauln , thanks for your comments. SSH is implemented for single server connections. For replica set connections, it needs to be re-implemented. We will consider your comments, when SSH support for replica sets is implemented. Best Regards.

[jardiacaj]

Hi, it would be nice if the user is at least warned that it does not work. I wasted some hours trying to make it work until I found this thread and I guess I am not the first one.

[simsekgokhan]

@jardiacaj , absolutely agree, sorry for the wasted hours. We have disabled SSH tab for replica set connections and added a mouse on-hover tip about the lack of support. Change is already in v1.4.3-beta.

[jardiacaj]

Wow, I'm impressed by the fast reaction. Thanks for your work!