I resolved this issue by hardcoding the path to the insecure_private_key file in the Vagrantfile, see my Stackoverflow <http://stackoverflow.com/questions/29673065/how-to-fix-vagrant-error-private-key-path-file-must-exist/30647046#30647046>post for more info.
Hope this is of use to anyone else who experiences the same issue. On Thursday, 4 June 2015 12:11:34 UTC+1, Saeed Bhuta wrote: > > Hi guys, > > Recently I have been getting the message: "* `private_key_path` file must > exist: P://.vagrant.d/insecure_private_key" whenever I try to spin up any > of my machines. Has anyone else experienced this? I've uninstalled Vagrant > and then installed it again but to no avail. I am using Puphpet to > configure the machines. My Vagrantfile can be found here > <http://pastebin.com/kcPRiniD>. I've never had this problem before. My > host machine is running on Windows 7. > > Appreciate any tips and advice, > > Saeed. > > -- 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.
