Trouble with SSH tunnel

2,656 views
Skip to first unread message

tykho

unread,
Jan 4, 2011, 9:57:06 AM1/4/11
to Sequel Pro
Hello,

I'm experiencing some problems connecting to a mysql server using ssh
tunnel. It's very strange and it works on and off kinda.

Most of the times I get an error, but every now and then it just
works. Sometimes after removing the favorite password and entering it
again.


I've tried using the terminal to connect to the server and it works
just fine, and I've used Sequel Pro before to connect to another
server using ssh, and it worked just fine. So what am I doing wrong?
I can see the error messages, but I'm not really sure what to do about
them, especially since it just works not and then.


Last part of the log:
/.../
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/jw/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/jw/.ssh/identity
debug1: Trying private key: /Users/jw/.ssh/id_dsa
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
2011-01-04 15:48:12.430 SequelProTunnelAssistant[23955:903] SSH
Tunnel: specified keychain password not found
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
2011-01-04 15:48:12.519 SequelProTunnelAssistant[23956:903] SSH
Tunnel: specified keychain password not found
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
2011-01-04 15:48:12.572 SequelProTunnelAssistant[23957:903] SSH
Tunnel: specified keychain password not found
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).




I also changed the password of the user I'm sshing with on the host,
and I could connect once. I disconnect and I reconnect again and I get
another error:

/.../
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/jw/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/jw/.ssh/identity
debug1: Trying private key: /Users/jw/.ssh/id_dsa
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).


Anyone that can help?

Rowan Beentje

unread,
Jan 4, 2011, 10:10:52 AM1/4/11
to seque...@googlegroups.com
Hi tykho,

Interesting log - it looks like the root cause of the issue is that the favourite has a password associated (and stored in the keychain), but for some reason the tunnel assistant can't access that password. You can see it trying but failing: "SequelProTunnelAssistant[23955:903] SSH Tunnel: specified keychain password not found".

This might occur if the tunnel assistant has been denied access to the password in the past, or if the keychain item itself has been corrupted in some way. I'm not sure what else could be causing it if the connection interface is displaying password blobs (••••).

The failure to then prompt you for a password is probably related - it's error-ing rather than falling back to a prompt, which we'll fix.

When you've removed the favourite's password and reentered it in the past, has that been in prefs, or only (temporarily) on the connection screen? It might be worth managing favourites in the prefs, removing the password, closing prefs, and then going back and adding it again - that should recreate the keychain item, and hopefully fix the issue...

Rowan

> --
> You received this message because you are subscribed to the Google Groups "Sequel Pro" group.
> To post to this group, send email to seque...@googlegroups.com.
> To unsubscribe from this group, send email to sequel-pro+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sequel-pro?hl=en.
>

tykho

unread,
Jan 4, 2011, 10:26:04 AM1/4/11
to Sequel Pro
Hello, and thank you for the quick reply.

Seems it works if I remove the password from the password field in the
temporary connection screen and choose to connect, and then enter the
password in the popup window.
Tried opening preferences, removing password, closing prefs, opening
it again and adding it, close prefs and then connect - but I then I
get the error. Also tried to remove it in prefs, save prefs, connect
and enter in popup - but it just gave me the error again.

What about removing the related entries in keychain access?

Rowan Beentje

unread,
Jan 4, 2011, 10:42:23 AM1/4/11
to seque...@googlegroups.com
Yes, do try removing the related entry in keychain access; the first part of the name should be easy to search for, in the form "Sequel Pro SSHTunnel: [favourite name] ".

Does the favourite name have any non-latin characters in it? That could also be a potential source of issues, come to think of it, as the name gets passed into the tunnel assistant as an environment variable...

--Rowan

Message has been deleted

tykho

unread,
Jan 4, 2011, 11:17:00 AM1/4/11
to Sequel Pro
ops, removed message

Aye, had an "ä" in the favourite name, edited it and now it works
fine... kind of strange how it worked sometimes though, right?
Thanks for the help!

Rowan Beentje

unread,
Jan 4, 2011, 11:20:03 AM1/4/11
to seque...@googlegroups.com
*Very* weird that it worked sometimes.

Thanks for the pointer on the ä - I've replicated that, so we'll get that fixed for the next version :)

Reply all
Reply to author
Forward
0 new messages