1
votes

I had to replace my router which in turn gave my dev box a new IP address and has since broken my local VirtualBox with a Homestead/Vagrant Laravel image. Here's the error that I'm getting when running vagrant up or restore or --provision:

==> default: Checking if box 'laravel/homestead' is up to date... ==> default: Clearing any previously set network interfaces... The specified host network collides with a non-hostonly network! This will cause your specified IP to be inaccessible. Please change the IP or name of your host only network so that it no longer matches that of a bridged or non-hostonly network.

Here's what I've tried so far:

  1. Changed router base IP address map from the factory assigned 192.168.1.1 to 192.168.10.1 to get back to the same map from previous router of 192.168.10.1.
  2. Reserved an IP address of 192.168.10.10 on my router and assigned it to my machine's mac address.

test results: same error of host network collision

  1. Changed router base IP address map to 10.10.10.1
  2. Reserved an IP address of 10.10.10.10 on my router and assigned it to my machine's mac address.
  3. Replaced all 192.168.10.10 IP addresses in my project (homestead.yaml, homestead.rb, etc.) with 10.10.10.10
  4. Updated my hosts file to point 10.10.10.10 to mysite.app

test results: same error of host network collision

  1. Time Machine restored my entire machine image to a week ago

test results: same error of host network collision

  1. Time Machine restored my entire machine image to today's backup
  2. Reset router and all project files back to 192.168.10.10
  3. Turned off Wifi (no network connection, no local IP address)
  4. Run vagrant up
  5. Confirmed host file maps 192.168.10.10 to mysite.app

test results: vagrant scripts run successfully, no error messages however I can only access the resulting local nginx site through http://192.168.10.10 and not http://mysite.app

  1. Turn wifi back on (assigned IP is now 192.168.10.10)

results: can't access local nginx site at all, either via http://192.168.10.10 or http://mysite.app

  1. Installed a fresh new laravel project and corresponding fresh new homestead box. Running vagrant up returns the same error message.

  2. Rebooted many times during this process, same problems.

  3. Deleted and reinstalled VirtualBox, same problem.

My initial diagnosis is that this has nothing to do with Laravel, nor homestead but is most likely caused by a VirtualBox setting or network connection.

Any suggestions are appreciated!

similar problem posted to laracast forum

same error message on SO

1
I have (and keep having) the same issue when I switch from VM between vmware and virtual box, usually restarting the OS (mac in my case) solves the issueFrederic Henri

1 Answers

0
votes

You've proven

vagrant up --provision

This recharges your yaml file

https://www.vagrantup.com/docs/cli/provision.html