It looks like you're getting somewhere! The connection reset by peer is you trying to establish a connection. That's good.
I would suggest you access the console through VirtualBox and get a prompt. Remember, vagrant:vagrant (is the username/password). And then maybe restart SSH service. At this point, you'll need to observe logs to see why it's resetting. You can check to see if the SSH process is tied to a particular interface? You can check with the command (on Linux) netstat -tlpn | grep 22 It *should* be bound to any port, i..e 0.0.0.0/22. Oh, another thing, sometimes, permissions on the private_key can prevent connection. If the private_key is a DSA key, then the new OpenSSH rejects these keys. You may want to access /etc/ssh/sshd_config and review the configuration for SSH. One more thing, 'vagrant ssh' still fails? Dennis P.s. Another thought, sorry I'm mostly guessing here, perhaps when you spun up the machine, you asked vagrant to generate a new SSH key? If your vagrant file doesn't have any ssh configurations then it should use the insecure_private_key. -- 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/b35d2bc5-e7d4-4bb0-94c5-f11e2d828714%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
