[BUG] After upgrade

Question

[BUG] After upgrade

racso051 opened this issue 10 years ago · 22 comments

Hi, I'm having problems with the last update. Now I can't connect to to my databases. When I try to open a database occurs an error "Failed to connect to target host" and sometimes also an Unauthorized.

Thanks.

Answer 1 · 2014-06-11T18:26:46.000Z

I'm also having this problem now, even after removing and re-adding a connection.

I also tried downgrading, which gave me corrupt errors. I then removed all related files using AppZapper, and tried the latest version again, but it still isn't working, giving me a "Failed to connect to target host" error.

Answer 2 · 2014-06-11T20:56:10.000Z

Ah I'm sorry, I see a bug about choosing the beta/release channel... And yes, there is a problem to downgrade since I increased the database version (the database to save the connection information).

Sorry about that

Answer 3 · 2014-06-11T22:27:39.000Z

can you give more information on how you connect to your server? with ssh? with replicaset? a public server?
You can contact me by email on my pseudo on mac.com

Answer 4 · 2014-06-11T22:38:10.000Z

Public servers for me.

Answer 5 · 2014-06-11T22:38:48.000Z

Can you give me more info on how to reproduce this bug?

Answer 6 · 2014-06-12T00:03:43.000Z

you should be able to downgrade to 2.6.2 now. But I still need your help to fix this bug.

https://mongohub.s3.amazonaws.com/MongoHub-2.6.2.zip

Answer 7 · 2014-06-12T00:05:25.000Z

which public server?

Answer 8 · 2014-06-12T12:52:29.000Z

I'm trying to connect to mongohq database.. only works for local databases.

Answer 9 · 2014-06-12T12:56:46.000Z

Are you able to go back to 2.6.2, at least?

Answer 10 · 2014-06-12T12:58:39.000Z

With the 2.6.2 version works fine again.

Answer 11 · 2014-06-12T12:59:19.000Z

ok cool. So I will take my time to fix on the beta version

Answer 12 · 2014-06-12T13:00:54.000Z

Perfect. Thanks for your help :)

Answer 13 · 2014-06-12T16:21:54.000Z

Great, I can reproduce the bug, I will be able to fix it.

Answer 14 · 2014-06-13T14:12:04.000Z

Should be fixed in beta 3

Answer 15 · 2014-07-17T14:04:28.000Z

I have this problem with mongolab database in beta 3.

Version 2.6.2 does not work either.

Version 2.6 works with mongolab without problems.

Answer 16 · 2014-07-18T12:44:40.000Z

What do you have in the console? Anything useful? Can you tell me what information you put in the connexion window?

Answer 17 · 2014-07-19T10:49:02.000Z

No I don't have anything useful in the console.

In the connection window I have just name, address, port, user, password and database. Anything else is as default. But one thing I noticed is that it change the port to -12536. Eg. if I set port to 53000 it change the port to -12536 after save. Maybe there is too small integer for port?

Answer 18 · 2014-07-19T13:12:19.000Z

Yes, you were right. That was the problem (I introduced it recently). It should be fixed in beta 5

Answer 19 · 2014-07-20T17:33:32.000Z

Thanks. Now it doesn't change the port value anymore but it still doesn't work with my mongolab databases. I can't get any error but it doesn't show my collections in database. Same databases still work in version 2.6 so something has changed but I can't say what. I also created new test database to mongolab but it doesn't work either. Can you connect to mongolab (there is possibility to create free development databases) databases?

Answer 20 · 2014-07-21T12:54:31.000Z

I found SSL was activated all the time (this is an issue with MongoLab that doesn't support ssl). I was able to use 2.7b6 with MongoLab. Let me know if it works for you too.

Answer 21 · 2014-07-21T13:07:42.000Z

Thanks, now it works with 2.7b6.

Btw. Old saved connections didn't work because it changed the ports to something like -12536 (too small integer while converting settings?) and I had to fix those manually, but after that it worked.

Answer 22 · 2014-07-21T13:09:44.000Z

Yes, sorry about this bug... I made a mistake by switching to int16 (I forgot about the signed limit)...