The IP in your homestead.yaml and your hosts file must match. Try changing it to 192.168.10.10 in your hosts file.
I am having the same issue and I mentioned here - http://laravel.io/forum/11-29-2014-homestead-20-unable-to-create-laravel-project-directory It's not host file issue. Please help
Try this. Ssh in homestead, then cd into your projects public folder and run pwd. You will get real path, copy that in Homestead.yaml in sites section. After that destroy homestead and up it again. Hope this helps you.
Nop, still not working. This is my output for homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Setting the name of the VM: homestead
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 80 => 8000 (adapter 1)
default: 443 => 44300 (adapter 1)
default: 3306 => 33060 (adapter 1)
default: 5432 => 54320 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => /Users/uzairjawed/.composer/vendor/laravel/homestead
default: /home/vagrant/Projects => /Users/uzairjawed/Desktop/Projects
==> default: Running provisioner: file...
==> default: Running provisioner: shell...
default: Running: inline script
==> default: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCjUXY9qzMvqMZ8CrapzlRMk8MB2x7fQoRGkYzBNauvLJVcVpiwUYYpA3OekF2kBGuCd1FIE2VJes//sSjLOTdrxLI+JzdsXvgLMZJYfmewZLxAl/213QrFAXrvkHg+CAMnl5jfdvN79+PASEknz7lG4LFMKxsGcEIk4idLqNNCIiwHL4qXkEixeCoufdJbdk9XxmisGCKxM7YoSIxMYqKkDga22VpqCOrAWbj6YfwPOQrSeY+oAcFclcmcl1scj6oqZhyJPpIqXNCwB5fU4wm83KB/E5Z9XFebR6QUBXjDhR+knR5goZ0+RGCuctPLJwxqX8ly6k++fkoIW8HN8JAJ you@homestead
==> default: Running provisioner: shell...
default: Running: inline script
==> default: Running provisioner: shell...
default: Running: inline script
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 1959
==> default: Running provisioner: shell...
default: Running: /var/folders/lz/r6r1rkr17qjf3k4w6fnlbb3h0000gn/T/vagrant-shell20141130-7508-19mv1fo.sh
==> default: Warning: Using a password on the command line interface can be insecure.
==> default: Warning: Using a password on the command line interface can be insecure.
==> default: Running provisioner: shell...
default: Running: /var/folders/lz/r6r1rkr17qjf3k4w6fnlbb3h0000gn/T/vagrant-shell20141130-7508-6n26ze.sh
==> default: NOTICE: database "propertybook" does not exist, skipping
==> default: Running provisioner: shell...
default: Running: inline script
==> default: Running provisioner: shell...
default: Running: inline script
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2101
==> default: Running provisioner: shell...
default: Running: inline script
==> default: You are already using composer version b23a3cd36870ff0eefc161a4638d9fcf49d998ba.
==> default: Running provisioner: shell...
default: Running: /var/folders/lz/r6r1rkr17qjf3k4w6fnlbb3h0000gn/T/vagrant-shell20141130-7508-12a27is.sh
Run the Homestead 'serve' command from your SSH session and see if that helps:
$ serve myawesomeproject.app /home/vagrant/projects/myawesomeproject/public
Just in case anyone else stumbles upon this in the near future, I had the same exact thing as OP. After many trials I got it fixed by using "vagrant provision" command
I can't use Vagrant provision says "A Vagrant environment or target machine is required to run this command. " etc etc
Verified, running the provision command in vagrant fixed this for me.
@aligajani the message you are seeing is reported when not Vagrantfile is found. Make sure your working directory is where your homestead files are which will contain the Vagrantfile.
I was able to fix this issue by defining absolute, instead of relative, paths when running:
serve homestead.app /home/vagrant/Code/public
Also, all the path variable might be case-sensitive but I haven't tested this.
Hope this helps.
@aligajani You can access the homestead id to run provision with.
vagrant global-status
id name provider state directory
-----------------------------------------------------------------------------------
f826aec default virtualbox running /Users/home/.composer/vendor/laravel/homestead
Then run provision with the id.
vagrant provision f826aec
No reason to be in the directory then.
Thats funny. You get vagrant so it is easier to run laravel and then you just spend time fixing vagrant. What a waste of time.
@Goddard: You're totally right, learning new things is ridiculous, we should all give up and dig ditches, or install toilets and clean septic tanks. What was I thinking? I hate learning stuff! /facetiousness
did anyone find out the solution of this problem yet please ? i was fine on wamp i installed homestead just to make use of RAM caching systems
I have the same/similar issue.
Vagrant came up no problem (I've used it in the past with puppet).
The issue I am having specifically is the redirecting of 192.168.10.10 to 127.0.0.1:8000
I have always used Vagrant on port 8000 -- and it has and does work fine (it shows up with Laravel when I do it.
How do I get the redirect to work?
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community