hmm. open virtualbox gui and see where it has halted

he's just starting really quick. virtualbox is saying that also. as i mentioned, my localhost website is accesible as soon as the first few errors appears, after that the errors keep going, but my website is running well. but i cant ssh into it and getting the errors as above.

strange. try updating your vagrant scripts. take a git pull from homestead repo, and also consider updating the box.

homestead: v3.0.2 = up to date

$ vagrant version
Installed Version: 1.8.4
Latest Version: 1.8.4

the last code of my post was allready the
vagrant box update command

i think everything is up to date?

try to delete .vagrant folder and rerun provision, you can also run vagrant ssh-config to have more information, the problem is with the private/public identification.

renamed the .vagrant.d folder, wich is it on my machine. rerun provision, everything up and running, new .vagrant.d file is made. but afster a vagrant down, i still get the problem with vagrant up...

my ssh, can you see whats wrong?

$ vagrant ssh-config
Host default
  HostName 127.0.0.1
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile C:/Users/Bart/Homestead/.vagrant/machines/default/virtualbox/private_key
  IdentitiesOnly yes
  LogLevel FATAL
  ForwardAgent yes

when renaming that .vagrant folder: C:/Users/Bart/Homestead/.vagrant

and running provision, i get:

$ vagrant reload --provision

==> default: VM not created. Moving on...

so i don't think that was the folder you meand?

Check that the private key for your user in the .ssh folder matches the one from the box, prolly that will solve it!

Basically make sure the output off ssh-keygen -y -f FOLDER/Homestead/.vagrant/machines/default/virtualbox/private_key > ~/id_rsa.pub Matches the id_rsa.pub key inside the homestead box, which your should be able to log in either vagrant ssh or ssh [email protected] -p 2222

one more think, that you could do is do a composer update.

maybe do vagrant box list and delete/destroy the box and bring it back up if the above does not solve it.