-
Notifications
You must be signed in to change notification settings - Fork 631
ssh login vm #29
Comments
user and password are by default "vagrant" (without the quotes) |
Just a note, you can easily ssh into your VM(s) with |
@jtreminio maybe adding a hint in "Step Ω" at the bottom of the page would ease things because I suppose PuPHPHet users will be vagrant newbies most of the time.. |
... and/or and additional link to the vagrant ssh documentation: http://docs-v1.vagrantup.com/v1/docs/getting-started/ssh.html |
nit: I whink the correct url would be http://docs.vagrantup.com/v2/getting-started/index.html |
The default SSH logins aren't working for me, using vagrant 1.6.2 |
in your db tool (mysql workbench, or Sequel Pro, whatever) connect via ssh On Fri, May 16, 2014 at 2:17 PM, philsbury notifications@github.com wrote:
|
Yup tried that and connection was denied. I tested an ssh connection using vagrant@xxx.xxx.xx.xxx but that also failed. I can update the password by using vagrant ssh and then passwd, but that isn't ideal if it's not me using a provisioned vm. |
Use the private key generated at puphpet/files/dot/ssh/id_rsa, username |
Worked like a charm, thank you! |
This issue has come up again with a new box. When attempting to log in with Sequel Pro, the error "The SSH Tunnel has unexpectedly closed." is presented (using the private key). When booting the box, it also says: I notice there's SSH settings in the config.yaml, does this need updating in any way? |
Fixed the above, on my Mac, it had remembered the old key in /Users//.ssh/know_hosts Deleting that and reconnecting fixed the problem! |
Hey jtreminio, Cheers ! |
...Solved this for me! |
I'm able to ssh using private key, but what is the default passwd for vagrant user? |
whats the default username + password to login to the VM via SSH?
The text was updated successfully, but these errors were encountered: