Homestead: Homestead settings file not found after update

[doncadavona]

Can't start homestead upon successful update via $ vagrant box update then $ git pull origin master. Afterwards, the command $ vagrant up can't find the Homestead settings file.

Versions

• Vagrant: 1.9.1
• Provider: Virtualbox 5.1.14
• Homestead: (Can't see) homestead: command not found with the issue. I guess 0.4.4 based on:

$ vagrant box list
laravel/homestead (virtualbox, 0.4.4)
laravel/homestead (virtualbox, 2.0.0)

Host operating system

macOS 10.12.3

Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/Code
      to: /home/vagrant/Code
      type: nfs

sites:
    - map: laravel.app
      to: /home/vagrant/Code/laravel/public


databases:
    - homestead

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 50000
#       to: 5000
#     - send: 7777
#       to: 777
#       protocol: udp

Vagrant up output

Homestead settings file not found in /Users/doncadavona/Homestead
Homestead settings file not found in /Users/doncadavona/Homestead

Expected behavior

The homestead app should run.

Actual behavior

$ vagrant up outputs:
Homestead settings file not found in /Users/doncadavona/Homestead
Homestead settings file not found in /Users/doncadavona/Homestead

Steps to reproduce

1. Update homestead: $ vagrant box update
2. Cancel the update by hitting CTRL + C while the update is downloading.
3. Retry update: $ vagrant box update (let it finish)
4. Run $ vagrant up, vagrant reload --provision or vagrant box add laravel/homestead.

References

[doncadavona]

Anyways, got my Homestead back via git checkout v3.0.1 coming from v3.0.2. But still want to know why the Homestead settings file is not in v3.0.2.

[svpernova09]

After you vagrant box update you always want to vagrant box destroy. No idea why you were seeing Homestead settings file not found in /Users/doncadavona/Homestead

Would have to know what branch / version of this repo you were using. There is no v3.0.2 version of the repo.

[roberto-aguilar]

@doncadavona the Homestead settings file not found in /Users/doncadavona/Homestead error message is thrown by the Vagrantfile and that is surely because you still have your Homestead.yaml in your ~/.homestead directory. In Homestead v5, the Homestead.yaml file must be in your homestead repository directory (in this case /Users/doncadavona/Homestead).

/cc @svpernova09

[throttlehead]

I think they might of made it easier to run multiple versions of Homestead by looking for it in the repo directory instead. I simply copied my Homestead.yaml from my windows user directory right into where I cloned a new copy of laravel/homestead repo and viola!

[doncadavona]

Thanks guys! Good to know, the Homestead.yaml is now in the ~/Homestead directory instead of ~/.homestead.

[0Sarah0Al]

Hi
I went through a huge mess after I updated my VirtualBox two days ago.
I got the error:
"default: Failed to restart php7.0-fpm.service: Unit php7.0-fpm.service not found." when I ran the command: vagrant up.
And all my websites stopped working and first got: bad gateway and then 500 errors.
So here is what I did:
1- I made a back-up of Homestead.yaml
2- I removed homestead globally using the command:
"composer global remove laravel/homestead"
I also realized there was a bad quotation mark in my 'composer.json' in the ".composer" directory, so I fixed it.
3- I removed laravel/homestead box and then re-installed it.
4- installed homestead again through composer global command.
5- I cloned the recent version of homestead from this repository into a directory I called "Homestead."
6- Since I made a back-up of homestead.yaml, I copied it back in the ~/Homestead directory.

Now, everything works like it used to before the VirtualBox update.
Thanks to everybody in this thread.

Hope this would help anyone who went through this massive headache. :(

[mpathy]

Now I have an:

....... in os_friendly_id': undefined methodgsub' for nil:NilClass (NoMethodError)

because it told me to remove the virtualbox machine in order to creat it new.. :(

[Beaudinn]

@mpathy same here

[andyscraven]

@Sarahphp1 Thank you. I was just at the point where I thought "f**k it" and starting from scratch then I saw your post. So I did exactly the same. Removed everything and started again with Homestead. All fine now.