Level 65
Started from fresh again? Names will get stored in the vagrant configuration so make sure you get rid of those too.
1 like
Dec 4, 2014
4
Level 3
Homestead 2.0 up problem
I get this error every time I try to resume my homestead box using homestead up:
A VirtualBox machine with the name 'homestead' already exists.
Please use another name or delete the machine with the existing
name, and try again.
Then I have to open VirtualBox and delete everything and then try again. But on my other PC everything works. Any clues?
Level 3
Where is the vagrant configuration?
Level 65
.vagrant or .vagrant.d I think depends what OS. I'm on OS X but I'm not sure on Windows.
1 like
Level 3
Ok, I have uninstalled vagrant, virtualbox, homestead and deleted .homestead and .vagrant.d folders. Then I had some problems with network adapter drivers ... somehow I fixed that.
Then I installed vagrant, virtualbox and homestead.
Running vagrant from command line worked, but when I typed homestead up or homestead edit I got vagrant is not recognized as an internal or external command.
Then I read on https://laracasts.com/discuss/channels/general-discussion/im-unable-to-run-homestead-up that there is a problem with homestead 2.0.8, so I installed 2.0.7:
composer global require laravel/homestead:v2.0.7
Now it seems that everything is working.
Please or to participate in this conversation.