Connect to mongodb via SSH dosn't work in new update

[Mai-Lapyst]

Same issue as in #286: Mingo errors when trying to connect to a mongodb database via SSH just with the password set. (No keyfile)

This errors pop open when you try to open an a collection in a already configured connection:

Also this error appears when using the "Test" button inside the connection settings:

Mingo Version: 1.6.4 (PRO)

[tothradoslav]

Thanks for this. I found the issue and corrected it. Will let you know here when a new build is ready.

[dmolin]

@tothradoslav any update on this? I know the fix has been already applied 2 weeks ago but no release yet. This is pretty much a game breaking issue for an audience that intends to use this in prod environments. Is there any ETA for the next release?

[tothradoslav]

It's about to be released in the upcoming days. Saw your twitter post, uploading the linux RC so you can test it.

https://github.com/mingo-app/mingo/releases/tag/v1.6.5

[dmolin]

Thanks a lot @tothradoslav !! Mingo.io it's a fantastic Mongo client and my colleagues and I are already loving it! ssh support is the only bit preventing us from purchasing a license and I'm sure the early access to the RC will make everyone happy here!

[tothradoslav]

Please let me know if it worked for you.

[dmolin]

@tothradoslav so, we're still having issue even with RC1.
The error is now the following one (when testing the connection):
"Error: MongoServerSelectionError: Server selection timed out after 5000 ms"

Worth noting:

1. we're connecting through ssh
2. we're connecting to a server with a replica set (the error is the same whether we try to connect to the master or one of the slaves)

Hope it helps!

[tothradoslav]

Thanks! Going to test it properly, my connection works.

Are you using ssh with privateKey, password or agent?

Will let you know when I find something.

[dmolin]

I'm using ssh with a privateKey file.
Though, there's something that seems to be missing. When using a privateKey file, I should also be required to provide a "passphrase" that the server will use to parse the private key. this element seems to be missing in the Mingo connection configuration dialog (it asks either for a password or a privateKey)

[tothradoslav]

Just uploaded a new pre-release, could you please try this? We added the passphrase option in SSH.

https://github.com/mingo-app/mingo/releases/tag/v1.6.5-rc.2

Thank you!

[dmolin]

Hey @tothradoslav , thanks a lot for the hard work!

We're definitely "getting there"!
So, with the passphrase I can successfully "test" the connection. (the test succeeds).

Though, I see these issues:

• the passphrase is written in clear (it should be showing up as a password field, with "*")
• the passphrase is not persisted. if I close the configuration panel and reopen it, it's gone and I've to re-enter it again
• Not sure if connected to the previous point, but when I try to switch to the connection I just created my DB shows up as completely empty (like, no collections are there). Not sure if this is a failure to actually connect to the DB itself. I'm using the mongodb connection string with this format "mongodb://uid:pwd@url:port/dbname" and I assume everything is fine since the "test connection" doesn't report any error.

Another thing that might interest you, feature wise: there's no option for connecting through TLS/SSL (something we use for some of our DBs). Take NoSqlBooster as an example here:

They allow you to setup a configuration for your connection that accounts for all these possibilities.

[tothradoslav]

Great, thanks for this. I will go through all your points and make sure it all works, including the SSL / TLS connections.

[tothradoslav]

Just 2 questions:

1. point 2, I can't reproduce it, it remembers the passphrase. Could you tell me more about the situation? If you could try to create a blank new connection and add it there? Just looking for some clues. Tried many options, can't reproduce.
2. Have you tried the refresh connection button in the left sidebar? Or if you close / open Mingo? (I know these are dummy solutions, just trying to find a way to debug this).

Thanks for all your help!

[dmolin]

So, good news on the passphrase :)
Creating a new connection seems to fix it and it's persisted correctly, so that's a win :)
The issue with the empty database remains though: I tried hitting the "refresh collection" button: it spins for a wile but then the result is still "0" at the end.
Let me stress: this happens when I try to connect to a production DB; if I connect to my local instance of Mongo I've no issues at all.
I do wonder if this can be related to the fact I'm connecting to a slave instance of a replica-set. Tentative question: are replica set supported in Mingo?

Happy to help! I want to see this product succeed. I already love it and prefer it much more than NoSQLBooster!

[tothradoslav]

Well, that's great to hear.

The database connection is bugging me. I am using replica sets with secondaryPreferred option and even SSH tunnel and connects properly. My connection looks something like this:

mongodb://uns:@mongo1:9000,mongo2:9000/uns?authSource=admin&replicaSet=rs0&readPreference=secondaryPreferred

Maybe the authSource option would be missing?

BTW, the TSL/SSL connection is ready, just need to release it. It'd be great to find the db connection bug before I do so...