Sequel Pro SSH tunnel #38

sakanaproductions · 2015-02-12T20:42:36Z

I've started up scotch box without issue. But, when I go into sequel pro and try to get into the mysql through ssh I get the following error: "SSH connection failed, The SSH tunnel has unexpectedly closed." My connection settings are below.
Name: scotchbox
Mysql Host: 127.0.01
User: root
Password: root
SSH Host: 192.168.33.10
SSH user: vagrant
SSH password: vagrant

theJasonJones · 2015-02-17T02:28:32Z

I'm not sure if you have a typo, but the MySQL hostname should be
127.0.0.1

You have
127.0.01

sakanaproductions · 2015-02-17T16:06:19Z

Yeah, it was just a typo :)

Jamie Fishback
(323)393-3474
jamie@jamiefishback.com
http://www.jamiefishback.com

This e-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. Thank You.

On Mon, Feb 16, 2015 at 6:28 PM, Jason Jones notifications@github.com
wrote:

I'm not sure if you have a typo, but the MySQL hostname should be
127.0.0.1

You have
127.0.01

—
Reply to this email directly or view it on GitHub
#38 (comment).

whatnickcodes · 2015-02-17T16:07:41Z

So, are we good to to close this?

theJasonJones · 2015-02-17T16:08:50Z

I think we're good to go.

sakanaproductions · 2015-02-17T16:09:14Z

No, it was a typo on github not on sequel pro

Jamie Fishback
(323)393-3474
jamie@jamiefishback.com
http://www.jamiefishback.com

This e-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. Thank You.

On Tue, Feb 17, 2015 at 8:07 AM, Nicholas Cerminara <
notifications@github.com> wrote:

So, are we good to to close this?

—
Reply to this email directly or view it on GitHub
#38 (comment).

theJasonJones · 2015-02-17T16:27:21Z

I see, where is the typo so I can correct it? I seem to missing it when I look over the github docs.

Here is a image of the current settings:

sakanaproductions · 2015-02-17T16:31:42Z

The typo is in my bug report not in your documents.

Jamie Fishback
(323)393-3474
jamie@jamiefishback.com
http://www.jamiefishback.com

This e-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. Thank You.

On Tue, Feb 17, 2015 at 8:27 AM, Jason Jones notifications@github.com
wrote:

I see, where is the typo so I can correct it? I seem to missing it when I
look over the github docs.

Here is a image of the current settings:

[image: screen shot 2015-02-17 at 10 25 57 am]
https://cloud.githubusercontent.com/assets/1423384/6232088/82b4a3c6-b68f-11e4-91ec-85f327b84f0a.png

—
Reply to this email directly or view it on GitHub
#38 (comment).

floriandotpy · 2015-02-23T15:08:07Z

I've selected the private key generated by vagrant, the connection works for me.

EDIT: user / password combination works as well.

whatnickcodes · 2015-02-23T15:09:51Z

It could also be a network / firewall issue.

jazzdrive3 · 2015-03-01T07:39:37Z

I'm getting this error as well. "SSH connection failed, The SSH tunnel has unexpectedly closed."

Settings are correct. I can connect to my other vagrant boxes just fine through Sequel Pro SSH forwarding.

The final two lines in the Show Details message are "RSA host key for 192.168.33.10 has changed and you have requested strict checking.
Host key verification failed."

jazzdrive3 · 2015-03-02T02:35:06Z

Why was this closed?

whatnickcodes · 2015-03-02T02:37:38Z

Reopened. Are you still having problems?

jazzdrive3 · 2015-03-02T05:13:00Z

Yeah, the same issue as the original poster. I didn't see any solution in the thread other than using the vagrant key. Which is fine, but that would warrant an update to documentation, correct? Is that the recommended solution?

If I'm understanding correctly, @sakanaproductions had a typo just in his bug report, but he actually has the correct values in Sequel Pro. I have triple checked my values as well, and host key verification is failing.

See my comment at #38 (comment)

Thanks!

whatnickcodes · 2015-04-28T01:23:09Z

I'm going to close this, but use the key for now.

johnstephens · 2015-09-07T19:45:42Z

I have the same issue. Where can I find the vagrant key?

whatnickcodes · 2015-09-07T21:33:05Z

Type: vagrant ssh-config

johnstephens · 2015-09-08T01:10:41Z

Thank you! This worked for me:

Name: scotchBox
MySQL Host: 127.0.0.1
Username: root
Password: root
SSH Host: 127.0.0.1
SSH User: vagrant
SSH Password: {Select vagrant_private_key file}
SSH Port: 2222

m0lmk · 2015-09-20T15:43:33Z

I have this problem. I've tried using the vagrant_private_key file and it still gives the same error.

I've triple checked my settings and they are the same as the documentation.

Here is the error message

Used command: /usr/bin/ssh -v -N -o ControlMaster=no -o ExitOnForwardFailure=yes -o ConnectTimeout=10 -o NumberOfPasswordPrompts=3 -i /Users/matt/.vagrant.d/boxes/scotch-VAGRANTSLASH-box/2.0/virtualbox/vagrant_private_key -o TCPKeepAlive=no -o ServerAliveInterval=60 -o ServerAliveCountMax=1 -p 22 vagrant@192.168.33.10 -L 52259/127.0.0.1/3306

Bad local forwarding specification ' 52259/127.0.0.1/3306'

fakingfantastic · 2015-10-08T18:53:03Z

For anyone still having this issue, the answer might be pretty straight forward, as it was for me... once I saw the magic clue.

Host default
  HostName 127.0.0.1
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile [snip]
  IdentitiesOnly yes
  LogLevel FATAL

Port 2222!

Set the SSH port to 2222 in Sequel Pro, and I'm in!

Hope this helps!

Brendonwbrown · 2015-10-22T13:42:51Z

I had some strange formatting errors in my ssh 'known-hosts' file. Fixing these allowed me to ssh in without a problem. For those new to these issues, I recommend reading the 2.0 release announcement page here.

whatnickcodes · 2015-10-22T14:34:47Z

Thanks @Brendonwbrown

ablears · 2016-04-08T01:06:08Z

For me I needed to update the Sequel Pro client. This bug caused the issue:
sequelpro/sequelpro#2141

ghernagon · 2016-04-12T21:08:28Z

Agreed with @ablears, I was using an outdated version of SequelPro and after update, it worked like a charm.

Hope this help others.

whalesingswee · 2016-04-15T04:12:21Z

Thanks to @ablears, updated the SequelPro and everything is fine again.

cballenar · 2016-04-29T16:20:05Z

I had to use 127.0.0.1 for the SSH Host. Is this normal?

pendashteh · 2017-04-15T08:44:35Z

This is what worked for me:

I had to delete the old line from known_hosts. You can safely delete the file:

rm ~/.ssh/known_hosts

Note: I ran vagrant ssh-config and it gave me port 2222 and I put it in Sequel Pro but it didn't connect. It only worked when I removed 2222.

datajunkee · 2017-06-06T18:34:00Z

Thank you @pendashteh , deleting the old line form known_hosts was the key for me. I'm in!

Brendonwbrown · 2017-06-06T18:42:27Z

Note that if you use SSH key pairs for other connections, you will be deleting all of your known hosts. I like to shorten my ssh host names, so this is not something I would want to do. The alternative is to open known_hosts in a text editor and see if any obvious issues pop out.

iantearle · 2017-06-19T09:47:19Z

Just got Scotch Pro and this is still happening. Within Sequel Pro (latest version etc) all I get is:

SSH connection failed!
The SSH Tunnel has unexpectedly closed.

With either password or vagrant insecure key.

EDIT
So I edited the known_hosts - I had used scotch box before (non pro) so booting another vagrant I have created two SSH keys - had to uncomment the old one (i still want to run both scotch boxes).

avclark · 2017-09-08T03:39:16Z

I'm still having this issue. Clean Vagrant install with ScotchBox Pro 3.0. Tried with password and with SSH key and getting the same errors others have been reporting:

SSH connection failed!
The SSH Tunnel has unexpectedly closed.

Any ideas on how to fix?

whatnickcodes · 2017-09-08T03:40:15Z

Type vagrant ssh-config

Then just use the port forwarding settings

avclark · 2017-09-08T03:44:12Z

This is what that command spits out:

HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /Users/avclark/sites/.vagrant/machines/default/virtualbox/private_key
IdentitiesOnly yes
LogLevel FATAL

And here are my Sequel Pro settings:

MySQL Host: 127.0.0.1
Username: root
Password: root
SSH Host: 127.0.0.1
SSH User: vagrant
SSH Key: {private key}
SSH Port: 2222

What should I change based on ssh-config?

whatnickcodes · 2017-09-08T03:45:11Z

You on Mac or Windows?

avclark · 2017-09-08T03:45:18Z

Mac

avclark · 2017-09-08T03:45:31Z

El Cap

whatnickcodes · 2017-09-08T03:46:43Z

Okay can you try SSH into the box first.

No sequel pro

ssh vagrant@127.0.0.1 -p 2222

whatnickcodes · 2017-09-08T03:46:57Z

Password vagrant

avclark · 2017-09-08T03:47:52Z

Didn't even prompt for a password. Here's what I got (same as the errors Sequel Pro gives, btw):

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:s6TtuBDr5iBjWO9atbRydfyuY8+dAz45l408mEpfc04.
Please contact your system administrator.
Add correct host key in /Users/avclark/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/avclark/.ssh/known_hosts:39
ECDSA host key for [127.0.0.1]:2222 has changed and you have requested strict checking.
Host key verification failed.

whatnickcodes · 2017-09-08T03:49:56Z

Awesome. Getting there. Not a big deal. Just delete known_hosts

rm ~/.ssh/known_hosts

avclark · 2017-09-08T03:49:58Z

I checked my known_hosts file, but wasn't really sure what I was looking for. It was just a bunch of SSH keys for various servers and apps that I use, like Beanstalk, Github, etc...

whatnickcodes · 2017-09-08T03:50:45Z

I think you'd be okay deleting it and just starting over

avclark · 2017-09-08T03:51:01Z

ok, that worked. but did i just lose connection to all my other servers/apps?

avclark · 2017-09-08T03:51:11Z

thanks for the help, btw.

whatnickcodes · 2017-09-08T03:51:51Z

No you should be okay. Next time you SSH you'll just have to accept the connection again.

Can you now SSH into Vagrant?

How about Sequel Pro?

avclark · 2017-09-08T03:52:35Z

Yes to both. Cool. Thanks for the help.

whatnickcodes · 2017-09-08T03:53:17Z

Yep, no problem!

Brendonwbrown · 2017-09-08T15:05:40Z

I rather not delete the entire entry since I've established a lot of known hosts in the past. I remember there being some extra lines and formatting issues, which when cleaned up, allowed Vagrant to work.

philgyford · 2017-10-06T10:54:39Z

I'm on a Mac and I've tried all these individually and together:

Removing my ~/.ssh/known_hosts file.
Adding the private key mentioned in vagrant ssh-config as the SSH Key.
Adding either 2222 or 22 as the SSH Port.

I still get "The SSH Tunnel has unexpectedly closed."

whatnickcodes · 2017-10-06T14:08:05Z

Adding the private key mentioned in vagrant ssh-config as the SSH Key.

Don't do that

Can you try with just user/password auth:

vagrant
vagrant

philgyford · 2017-10-06T14:29:42Z

@whatnickcodes Sorry, yes I tried that first because it's in the documentation.

whatnickcodes closed this as completed Mar 2, 2015

whatnickcodes reopened this Mar 2, 2015

whatnickcodes mentioned this issue Mar 19, 2015

can't connect mysqlworkbench #51

Closed

whatnickcodes closed this as completed Apr 28, 2015

Sequel Pro SSH tunnel #38

Sequel Pro SSH tunnel #38

Comments

sakanaproductions commented Feb 12, 2015

theJasonJones commented Feb 17, 2015

sakanaproductions commented Feb 17, 2015

whatnickcodes commented Feb 17, 2015

theJasonJones commented Feb 17, 2015

sakanaproductions commented Feb 17, 2015

theJasonJones commented Feb 17, 2015

sakanaproductions commented Feb 17, 2015

floriandotpy commented Feb 23, 2015

whatnickcodes commented Feb 23, 2015

jazzdrive3 commented Mar 1, 2015

jazzdrive3 commented Mar 2, 2015

whatnickcodes commented Mar 2, 2015

jazzdrive3 commented Mar 2, 2015

whatnickcodes commented Apr 28, 2015

johnstephens commented Sep 7, 2015

whatnickcodes commented Sep 7, 2015

johnstephens commented Sep 8, 2015

m0lmk commented Sep 20, 2015

fakingfantastic commented Oct 8, 2015

Brendonwbrown commented Oct 22, 2015

whatnickcodes commented Oct 22, 2015

ablears commented Apr 8, 2016

ghernagon commented Apr 12, 2016

whalesingswee commented Apr 15, 2016

cballenar commented Apr 29, 2016

pendashteh commented Apr 15, 2017 • edited Loading

datajunkee commented Jun 6, 2017

Brendonwbrown commented Jun 6, 2017

iantearle commented Jun 19, 2017 • edited Loading

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

avclark commented Sep 8, 2017

whatnickcodes commented Sep 8, 2017

Brendonwbrown commented Sep 8, 2017

philgyford commented Oct 6, 2017 • edited Loading

whatnickcodes commented Oct 6, 2017

philgyford commented Oct 6, 2017

pendashteh commented Apr 15, 2017 •

edited

Loading

iantearle commented Jun 19, 2017 •

edited

Loading

philgyford commented Oct 6, 2017 •

edited

Loading