If it is an older box I'd wager it was initially setup with vagrant ssh using the vagrant private key to access the root user's credentials directly. If you have upgraded Vagrant to version 1.7.x or higher they now regenerate the private key for the vagrant user so that not everyone is using the same key (because strange people are using this HUGELY insecure key in production).
Your steps to recovery are to find the insecure vagrant key (probably in the Github), put it somewhere locally (probably in the .vagrant directory next to the Vagrantfile) add "config.ssh.insert_key = false" and that should get you back up and running. It appears that project also injects keys on your behalf so if Vagrant has updated the key, you need to copy their private key/pub into the file that project suggests for your keys. On Saturday, June 6, 2015 at 4:40:30 PM UTC-5, Jacopo Nardiello wrote: > > Hi all, > after over a year of using a vagrant machine for personal dev I've started > to experience some really weird behaviour and I pretty much ran out of > options. > > Basically, whenever I run vagrant up I get this really weird error: > http://pastebin.com/jWU6EyZK > > My whole vagrant setup is the following: > https://github.com/jnardiello/jjbox > > To me, it looks like that on boot vagrant is trying to ssh into the > machine as root. How is that even possible? > Note that I experience this error not on initial provisioning (which is > successful and without problems) but AFTER running vagrant halt for the > first time. > > Any help would be MUCH appreciated, I'm probably missing something. > Thanks > Jacopo > -- 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]. For more options, visit https://groups.google.com/d/optout.
