Hi Patrick, Really sorry that I didn't read your entire message fully. It's a long message. Lol.
So, what I can suggest is, if you can SSH to remote hosts. Then try to SSH to the Virtualbox machine. So for instance, when the machine is coming up, you'll notice a host port number, as you mentioned, port 2222. So you should be able to reach the VM with the command: ssh -i insecure_private_key -P 2222 [email protected] See if you already have the SSH host key stored in ~/.ssh/known_hosts. I presume you're using PuTTy so it will be a known_hosts somewhere in PuTTy. If it's already there, maybe delete it. Try to establish the connection again, it should prompt you to save the host key again. Say yes and it should attempt to login. If it fails login (you'll need to check the private_key you're using). ssh -vvv -i insecure_private_key -P 2222 [email protected] will produce output for your attempt to login. Post the output here. If you get a password prompt, the password for vagrant boxes is "vagrant". Dennis -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9d2dd2d5-ca6c-4f8e-b19b-06333c082062%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
