Homestead installation issues

This looks like a problem with curl and your Win 7 installation. There are plenty of resources out there which will help you to solve this. Here are some:

http://stackoverflow.com/questions/9507353/steps-to-setup-curl-in-windows

http://guides.instructure.com/s/2204/m/4214/l/83393-how-do-i-install-and-use-curl-on-a-windows-machine

http://superuser.com/questions/134685/run-curl-commands-from-windows-console

http://www.confusedbycode.com/curl/

http://stackoverflow.com/questions/949959/why-do-64-bit-dlls-go-to-system32-and-32-bit-dlls-to-syswow64-on-64-bit-windows

Thanks, @pixelpeter I appreciate your help. I will re-install curl then.

I just have found a cool instruction of homestead. Please see here: http://www.sitepoint.com/quick-tip-get-homestead-vagrant-vm-running/

I have followed the instruction and worked fine on my machine. In this tutorial, they suggested that I should point to my localhost ip address (i.e: 127.0.0.1 myapp.com) instead of what Laravel documentation recommends (i.e: 192.168.10.10 myapp.com).

Surprisingly, it worked when I used the localhost ip address (127.0.0.1). Does anyone know why it works with this?

Thanks in advance.

@ryank30 Have you re-installed curl ?

In the hosts file you have to point to the ip address of your homestead machine that is defined in the Homestead.yaml file. Have a look at this file to see whats defined there. Maybe you have defined it as 127.0.0.1

@pixelpeter

Thanks. I will try it again after setting it up on hosts file.

@pixelpeter I re-installed it with ip address 192.168.10.10 this time. When I ran "vagrant up" I got an error message. Please see below.

The name of your virtual machine couldn't be set because VirtualBox is reporting another VM with that name already exists. Most of the time, this is because of an error with VirtualBox not cleaning up properly. To fix this, verify that no VMs with that name do exist (by opening the VirtualBox GUI). If they don't, then look at the folder in the error message from VirtualBox below and remove it if there isn't any information you need in there.

VirtualBox error:

VBoxManage.exe: error: Could not rename the directory 'C:\Users\ryan\VirtualBox VMs\settler_default_1434987271004_24349_1435110896707_56475' to 'C:\Users\ryan\V irtualBox VMs\homestead' to save the settings file (VERR_ALREADY_EXISTS) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachi ne, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: "SaveSettings()" at line 2788 of file VBoxManage ModifyVM.cpp

I am having the following issue "The name of your virtual machine couldn't be set because VirtualBox is reporting another VM with that name already exists. Most of the time, this is because of an error with VirtualBox not cleaning up properly. To fix this, verify that no VMs with that name do exist (by opening the VirtualBox GUI). If they don't, then look at the folder in the error message from VirtualBox below and remove it if there isn't any information you need in there." I have removed the VM in the VirtualBox GUI, but still I get the same error. How do I get to the folder to remove the line? is my basic question, I am wary of messing around too much in iTerm2. I am using a mac running Yosemite(10.10.4) and the newest version of VirtualBox(4.3.3), everything else - Laravel, Homestead was installed yesterday.

I had the same error, this install solved the problem for me, i encountered this issue on windows 7 and windows 10 https://www.microsoft.com/en-us/download/details.aspx?id=5555

More details here: https://github.com/mitchellh/vagrant/issues/7099

vagrant box add --insecure laravel/homestead

You are getting this because your certificate file cannot be located. You can set your certs up correctly and it will fix it or run the command above to download it without SSL.

In Win 10, I tried this link's bottom solution, https://github.com/mitchellh/vagrant/issues/6754

cp /mingw64/bin/curl.exe /c/HashiCorp/Vagrant/embedded/bin/curl.exe

and it worked!

There might be several things going on as part of this process. I'm on Win 8. I believe this will work for Win 10.

Make sure you have Git Bash installed.

Make sure virtualization is turned on in your BIOS. If you have Hyper-V installed you need to disable it, not just Disabled in Services:

Open CMD with Administrator privs.

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Reboot

To re-enable, change Disable-Feature to Enable-Feature. Reboot.

Ok, next, you need to make sure you have installed Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) at this URL:

https://www.microsoft.com/en-us/download/confirmation.aspx?id=8328

If you have it installed, reinstall it. If it says "repair" then do the repair.

Then make sure to create SSH keys in CMD > c:\users\data:

ssh-keygen -t rsa -C “[email protected]”

Just hit enter for everything

Go to your Homestead directory and open Homestead.yaml

authorize: ~/.ssh/id_rsa.pub

keys:

— ~/.ssh/id_rsa

folders:

— map: ~/Code

to: /home/vagrant/Code

sites:

— map: homestead.app

to: /home/vagrant/Code/Laravel/public

You don't have to change anything now, but if the vagrant build fails you may need to come back here and replace ~/ with the full path on where these directories are. Don't forget forward slashes and CASE MATTERS! Example of mine. NOTE: I created a new projects folder on my D: drive.

authorize: c:/users/data/.ssh/id_rsa.pub

keys: - c:/users/data/.ssh/id_rsa

folders: - map: d:/projects/homestead_projects to: /home/vagrant/Code

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

NEXT STEP:

Go into C:\Users\Data\Homestead\scripts\homestead.rb

Go to line 90 and comment it out, then replace with the following:

config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true

That's it for some major pain in the necks.