Looks like 3.0 broke SSH tunneling

[morcmarc]

Just installed the new update and I can't get onto any of my remote servers using SSH tunnels. When I open a connection it connects to my local Mongo instance instead. Tried re-adding my existing connections to no avail. Has anyone else got the same?

[jeromelebel]

What is your setup?

[morcmarc]

OS X Mavericks if that's what you meant. As for the ssh config, I can send a screenshot later when I'm at my Mac.

[jeromelebel]

The screenshot would be great.

[EricJahn]

It is the same for me (except I am not using SSH), I just updated to the latest version (from 2.6) and all my connection settings are reset to localhost. However when I add them again, I can not connect to any of my remote databases.

[jeromelebel]

@EricJahn can you explain me which information you put in the connection panel?

[EricJahn]

Just the usual stuff (Server, Port, Database Name, Username and Password). It seems to work with the new update (3.0.1).

[jeromelebel]

Do you have a database password with some characters like @: ?

[EricJahn]

No, only a-z and 0-9.

[jeromelebel]

Very weird. I didn't change anything related to ssh. Or maybe if there is some kind of url characters in the default database or the replica set name, that could explain.
In the log window, you should see an url mongodb://xxxx if there is now a % encoding. That would be the reason. Otherwise, I don't know. But at least it's working for you.

[samuellow]

Just updated to 3.0.1 and experiencing the same issue. The logs seem to indicate that the SSH tunnel is successful but the client seems like it's not using the tunnel and is instead trying to connect locally to my computer.

2014-10-20 04:13:30 +0000 somewhere.url debug mongodb://127.0.0.1/?

[rlaferla]

I'm seeing this exact same problem and it's a DEAL BREAKER. Please fix it. I can no longer use the app.

[rlaferla]

Even worse, I can't revert to 2.5 because it's complaining:

Persistent store migration failed, missing source managed object model.

[rlaferla]

Here's the log:

2014-10-20 04:23:56 +0000 mongoc.cluster info Client initialized in direct mode.
2014-10-20 04:23:56 +0000 mongoc.client info Using custom stream initiator.
2014-10-20 04:23:56 +0000 mongoc.client warning Failed to connect to: 127.0.0.1:27017, error: 61, Connection refused
2014-10-20 04:23:56 +0000 mongoc.client warning Failed to connect to: 127.0.0.1:27017, error: 61, Connection refused

[rlaferla]

If you need to revert to 2.5, delete the folder ~/Library/Application Support/MongoHub. You will need to recreate all your connection meta data though. I also deleted the preferences with defaults delete com.fotonauts.MongoHub

[jeromelebel]

I need the content of the log window of one of you.

[jeromelebel]

Maybe fixed in 3.0.2 (if it is the case, you can close this issue, otherwise, I really need more information)

[samuellow]

Update 3.0.2 has fixed the problem, thanks.

[morcmarc]

Indeed, it's working now! Thanks very much!

[jeromelebel]

So the fact you had no ip at all for the server was the issue.

I'm glad it's working for you again!

[nover]

Working here as well, also had SSH connection issues after the 3.0.1 upgrade, 3.0.2 and I can connect again :)

Just thought you should know...

[rlaferla]

Works for me. THANK YOU!