Trouble Installing Laravel on Windows 7 with Vagrant / Virtual Box

Open VirtualBox and see if it's actually on?

Homestead_default virtual machine is Running. After vagrant up gives up, I run it again and see

C:\laravel_code\Homestead>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: VirtualBox VM is already running.

But when I try to connect to learn.app:8000 the page can't be found.

What's the actual error for the page? Name not resolved or time out etc?

Did you edit you etc\hosts file? 127.0.0.1 learn.app

"The connection to learn.app was interrupted." http://i.imgur.com/qinkCe8.png

@fraserk I have this line already added to the end of etc\hosts: 127.0.0.1 learn.app

What happens when you view or ping the IP?

Looks good to me

C:\laravel_code\Homestead>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

127.0.0.1 will always work, it's your local.

Try > ping 192.168.10.10

small note: in /etc/hosts you must point to vm ip

192.168.10.10 learn.app

EDIT:

In windows hosts file is windows/system32/something

VirtualBox has two adapters set up in File > Preferences > Network > Host-only Networks.

The first has IPV4 of 192.168.56.1 and the second has 192.168.10.1

Do one of these need changed to 192.168.10.10?

EDIT:

hosts is located in C:\Windows\System32\drivers\etc for future reference

@Shwheelz my host-only networks is setup similar to yours. None is pointing to 192.168.10.10 so I wouldn't change that.

Just a note, pinging both of the IPv4 addresses I mentioned above work, 192.168.10.10 obviously does not. @fraserk is your hosts file using either of those IPv4 addresses?

Mines are 22.1 and 10.1

https://www.dropbox.com/s/0kc02l0f4act3fh/Screenshot%202014-10-01%2012.47.21.png?dl=0

https://www.dropbox.com/s/vlvjegin3kqnmoz/Screenshot%202014-10-01%2012.47.12.png?dl=0

@fraserk but are you referencing them in /etc/hosts like @keevitaja is suggesting?

no. im only referencing 127.0.0.1 in the hosts file..

what happens when you go to http://localhost:8000/

You've set the IP as

ip: "192.168.10.10"

Thanks @bashy, I'm sure that was one of the problems. Still no dice though. @fraserk, http://localhost:8000/ leaves me the same "Webpage not found" error as mentioned earlier. Which IP do you set at the top of your host file? Adapter 1 or 2?

I'm using 127.0.0.1 in my host file and ip: "192.168.10.10" in Homestead file . I'm stump.. The only other thing I can think of is the network setting on the VM network to Nat?

For my Homestead VM, I have Adapter 1 as NAT and Adapter 2 as Host-only Adapter. The NAT adapter is where all of the forwarding ports are set, so if you don't have a NAT adapter, things won't work.

We need to figure out why you don't have a NAT adapter, let me take a closer look at my Homestead environment and get back to you. I'd say just change it manually, but we probably won't get the port forwarding right, and it's better to figure out why the auto-provisioning isn't working.

I took some screenshots of Virtual Box that might be helpful

VM is running, general specs: http://i.imgur.com/K14votU.png

Settings, Adapter 1: http://i.imgur.com/rTeMAhK.png

Settings, Adapter 2: http://i.imgur.com/YvsAZN0.png

My VM, Host-only network list: http://i.imgur.com/f6WzZzR.png

VirtualBox Host-only Ethernet Adapter #2: http://imgur.com/mLrjHPn

VirtualBox Host-only Ethernet Adapter: http://imgur.com/IDeadyZ

try to uninstall virtualbox then install VirtualBox-4.3.12.

this solves my problem, and the problem was exactly the same.

In my case I put 127.0.0.1 and it works for my hosts file.

I had problems with the VirtualBox version and needed to install the test version.

Maybe you can find here some information:

https://www.virtualbox.org/ticket/13187

Hope it helps you.

@zzzcollapsar I tried your suggestion, but now Vagrant can't detect VirtualBox at all. Is there something else I need to configure?

C:\laravel_code\Homestead>vagrant up
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.

Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.

did you reboot your system? if so, probably redo the whole git Homestead, edit yaml, vagrant up process? if that still not working, check if your CPU supports vt-x?

Did you enable Virtualization option in your BIOS?

@ratiw I got the virtual machine to run, but the connection times out with Vagrant. See my post above with screenshots

http://i.imgur.com/K14votU.png

@zzzcollapsar I'm back where I was with 4.3.16. Still fails to connect even though the virtual machine turns on.

It is running but it's not responding. I think I used to have the same problem of getting 'Connection timeout' repeatedly, until I recheck my computer BIOS and found out that I didn't enable the Virtualization option.

Please see this:

https://gist.github.com/ratiw/1428d432877d745aa49d

Also, using 127.0.0.1 in hosts file seems to be better than 192.168.10.10, otherwise, you will have problem with your VM when your notebook resume from sleep or hibernation. With 127.0.0.1 you will not have such problem.

I've had the same issue on my mac today. Deleted the homestead box, downloaded it again and it worked. No idea what caused this or if the issue will return.

Worth mentioning is the fact that I also did a clean install if virtualbox, vagrant and homestead on my Windows 8.1 work laptop yesterday with no issues at all, not a single timeout.

@ratiw I'll check that next time I turn on my computer, but I've successfully used virtual machines on this computer in the past with VMWarePlayer, so I'm skeptical that the problem lies in BIOS.

@jehad I downloaded everything for the first time yesterday. Today, I uninstalled VB 4.3.16 and installed 4.3.12. I also deleted Homestead and re-cloned it.