July 21, 2009
Hi Team,
Meerkat 1.2.1 can't automatic reconnect to my ssh server.
They just showup a window and let me click "Retry" to reconnect.
How do I fix it?
screenshot:
http://img218.imageshack.us/img218/1508/screencapturecfl.png
July 22, 2009
#2
Hi Justin,
I managed to link
Hi Justin,
I managed to link with server, but the problem I have here is that once the connection breaks off, the software will NOT automatically re-establish the connection by itself...
Is there anyway I can enable the software to reconnect automatically?
Thanks,
July 22, 2009
#3
Ah, for that, some
Ah, for that, some functionality is coming in Meerkat. Right now, it will try to automatically reconnect after network or sleep/wake changes, but as for retrying a failed connection, it does not -- yet. I apologize for the confusion there.
July 22, 2009
#4
Thanks for your reply. I am
Thanks for your reply. I am looking forward to next version that can overcome this issue.
August 17, 2009
#5
Reconnect: modal dialog is not a good ui solution
Hi!
I've been evaluating Meerkat a while, and the reconnect feature is very, very annoying. I'd be happy to buy the licence, but this is definetely a showstopper for me.
The main problem is that Meerkat explicitly asks from the user whether he/she wants to reconnect or cancel. This is done with a confirmation dialog box, which often gets buried underneath other windows. No reconnect attempt from the Menu bar item works, if a single reconnect dialog is open. In the menu bar, there is no indication of any open dialog boxes. And worse still, if Meerkat is run outside of the Dock, the dialogs hidden underneath other windows are very difficult to find (especially when using Spaces). And if the user has several tunnels that need reconnecting, the dialogs stack and have to be all acknowledged before Meerkat starts to respond properly.
I'm a user interface designer, and I can guarantee that no user (except nerds, which should not be considered when designing user interface especially for the Mac) wants to answer the "reconnect? cancel/retry" question. Heck, I'm a nerd too and I hate it. :) Meerkat should simply try to reconnect automatically at regular intervals. The user is only interested in the fact the tunnel works. Retrying to connect the tunnel under the hood doesn't hurt the user.
Please get rid of the dialog and replace it with an automatic reconnect. If you think that reconnecting automatically is somehow harmful, make it an option in the preferences - but make sure it's checked on by default, since it's the most sensible default for most users.
September 20, 2009
#6
kplaakso speaks my mind...
I
kplaakso speaks my mind...
I have the exact same issue and i have payed for my licence already...
So as a valid customer I demand "Get rid off that $%& dialog box" and i will be a happy customer again...
;-)
Thank you for your support.
Cheers
Lars
September 20, 2009
#7
This is definitely in the
This is definitely in the pipeline :-)
September 20, 2009
#8
Oh look
I just came to post on this, and it was discussed and updated just today.
+1 on the popup killing--I just want the growl, please!
Still loving it anyway :)
September 22, 2009
#9
Cheers
Could you say how long that pipeline is? It is really killing me...
September 23, 2009
#10
I don't have a hard estimate,
I don't have a hard estimate, but it is coming soon. Wish I could be more specific.
To help me understand your situation a bit better, what is causing the reconnection prompts? Do your tunnels time out or is there some other situation that's causing it?
September 23, 2009
#11
Waking up from sleep
When I wake up from sleep, I've very often moved my computer. I have, for example, spent the last few weeks in a hotel which requires me to open a browser window and do a silly login to gain connectivity.
Meerkat attempts to connect as soon as I wake up, bringing up the popup, meaning i cant right click on the menu bar icon when I am ready to reconnect.
September 23, 2009
#12
That's a good use case. The
That's a good use case. The feature I'm working on should get around that, trying silently in the background in ever-increasing intervals.
September 24, 2009
#13
That would be perfect
That's just what I'd like it to be. It connects, mentions quietly that it failed or not, and I still have control over 'right now' with the menu bar icon. And meerkat never bounces at me :)
Want to join the forums? Create an account or login.
Hi Stephen,
First off, I apologize for the problem.
Debugging SSH connections varies widely based on the server setup, so the easiest thing to do is probably to right-click the tunnel in question, select "Copy Command", and paste that into the Terminal to see how it works there. That may shed some light.