Skip to content

SSH SQL connection after update to Ubuntu 14 #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lkwdwrd opened this issue May 22, 2014 · 3 comments
Closed

SSH SQL connection after update to Ubuntu 14 #365

lkwdwrd opened this issue May 22, 2014 · 3 comments
Labels
for:documentation
Milestone
1.2 Release

Comments

@lkwdwrd
Copy link
Contributor

lkwdwrd commented May 22, 2014

Just wanted to note that I had a slight issue connecting to the MySQL database with Sequel Pro after I updated to the newest build.

The fix was removing the IP from the known hosts file at ~/.ssh/known_hosts. After removing it I reconnected and re-added it as a trusted host and everything is humming along fine.
@lkwdwrd lkwdwrd closed this as completed May 22, 2014
@JJJ
Copy link
Contributor

JJJ commented May 22, 2014

I originally noted this here, but failed to make a separate issue:

#340 (comment)

Thanks for making this.

@jeremyfelt
Copy link
Member

Ahh, good call. I missed @johnjamesjacoby's note earlier.

I'm going to reopen so that we can document this for 1.2 release.

@jeremyfelt jeremyfelt reopened this May 22, 2014
@jeremyfelt jeremyfelt added this to the 1.2 Release milestone May 22, 2014
jeremyfelt added a commit that referenced this issue Nov 13, 2014
@jeremyfelt
Document need to clear key from known_hosts for VM
8be0e06 
Fixes #365
@jeremyfelt jeremyfelt mentioned this issue Nov 13, 2014
Merged
@jeremyfelt jeremyfelt mentioned this issue Dec 11, 2014
Closed
jb510 pushed a commit to jb510/VVV that referenced this issue Feb 28, 2016
@jeremyfelt @jb510
Document need to clear key from known_hosts for VM
4de54be 
Fixes Varying-Vagrant-Vagrants#365
@lock
Copy link

lock bot commented Feb 23, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
for:documentation
Projects
None yet
Milestone
1.2 Release
Development

No branches or pull requests
3 participants
@JJJ @jeremyfelt @lkwdwrd