search

vieten / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Cannot connect to MySQL database via SSH on Media Temple Grid Service. #1232

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Steps to reproduce the problem:

1. Attempt to connect using instructions found at 
http://kb.mediatemple.net/questions/1796/Connect+to+MySQL+on+the+%28gs%29+Grid-S
ervice+using+Sequel+Pro

Expected to establish a connection, instead received this error:

OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to s97121.gridserver.com [205.186.187.151] port 22.
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /Users/rob/.ssh/id_rsa type -1
debug1: identity file /Users/rob/.ssh/id_rsa-cert type -1
debug1: identity file /Users/rob/.ssh/id_dsa type -1
debug1: identity file /Users/rob/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3p2 
Debian-5~bpo.1
debug1: match: OpenSSH_4.3p2 Debian-5~bpo.1 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 's97121.gridserver.com' is known and matches the RSA host key.
debug1: Found key in /Users/rob/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/rob/.ssh/id_rsa
debug1: Trying private key: /Users/rob/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: read_passphrase: can't open /dev/tty: Device not configured
debug1: permanently_drop_suid: 501
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
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,keyboard-interactive
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,keyboard-interactive
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,keyboard-interactive
debug1: No more authentication methods to try.
Permission denied (publickey,password,keyboard-interactive).

Using Sequel Pro 0.9.9.1 Build 3408

*I've triple-checked verifying the password I'm using is correct.

Original issue reported on code.google.com by robmars...@hotmail.com on 23 Nov 2011 at 6:01

GoogleCodeExporter commented 9 years ago 
Hi Rob,

If you establish an SSH connection in the terminal with the same connection 
details, I assume that works?

Original comment by rowanb@gmail.com on 23 Nov 2011 at 10:36

GoogleCodeExporter commented 9 years ago 
Yes, I used the instructions Media Temple provides at 
http://kb.mediatemple.net/questions/1599/Using+SSH+in+Terminal.app+%28Mac+OSX%29
 and was able to connect just fine. Thanks for following up so quickly!

Original comment by robmars...@hotmail.com on 23 Nov 2011 at 5:19

GoogleCodeExporter commented 9 years ago 
I'm bitten by this, too. SSH login works fine if I use a key in authorized_keys 
on the server

Original comment by erikcede...@gmail.com on 15 May 2012 at 11:02

GoogleCodeExporter commented 9 years ago 
What build of Sequel Pro are you using?
Does this also happen on other Macs or with another user account?

Original comment by schlabbe...@gmail.com on 16 May 2012 at 6:28

GoogleCodeExporter commented 9 years ago 
Closing after no further feedback.

Original comment by stuart02 on 7 Jul 2012 at 9:26

GoogleCodeExporter commented 9 years ago 
I'm experiencing exactly the same. Any fix yet?

Original comment by barcl...@gmail.com on 7 Oct 2013 at 1:55