Valet v1.1.2 Update: Just keep getting the 'It Works'

@simondavies try the 1.1.3 one that just released. FYI, what I have been doing is doing a uninstall and a install on each major update. Just in case they keep making changes to the underlying driver. So far nothing has broken for me on all my sites.

@noeldiaz thanks but no luck still get the 'it works' page for all, seems like tis goinf else where like mac installed apache set up etc...

@simondavies Oh I see, you mean it is seeing another web server landing page. I think the "It Works" one is from Nginx. So it wouldn't be valet at all. Do you still have a VM running somewhere? Maybe Homestead? Check your VirtualBox GUI too.

@noeldiaz nope not had my HS on since trying this the other day, it was only since the version 1.1.2 update i had the issue.

Its seems i am getting somewhere as one of my .devs are working now, i stopped apache apachectl stopthen valet installthen valet restart

Then re-added my bespoke driver for this, basically changing the call to public folder to html folder (MT set up)

This then worked.

But

And that seems to have kicked in that site. But with the test laravel site does not wok and gives me the following error, which seems to be the call to that 'html' where as it should be 'public' with this one, so issue with drivers??

     Warning: chdir(): No such file or directory (errno 2) in /Users/USERNAME/.composer/vendor/laravel/valet/server.php on line 104

     Warning: require(/Users/USERNAME/Desktop/Sites/imasite/html/index.php): failed to open stream: No such file or directory in /Users/USERNAME/.composer/vendor/laravel/valet/server.php on line 106

   Fatal error: require(): Failed opening required '/Users/USERNAME/Desktop/Sites/imasite/html/index.php' (include_path='.:') in /Users/USERNAME/.composer/vendor/laravel/valet/server.php on line 106

I even added another laravel site, but the same. Looks like its now using JUST my mediatempleValetDriver.php file

To test this i simply renamed the laravl test site public folder to html and it popped in.

So this whole things seems to be a driver issue??? Knowledge is limited :-)

ignore that now, i been looking at the drivers and mine in particular to the one i saved locally and forgot a /, now all seems to be working.

So the process I had to fix the issues seems to be:

• remove valet completely (some reason valet uninstall does nothing) so to get the latest version (v1.1.3 at the time)
• stop apache (apachectl stop)
• composer global require laravel/valet
• valet install
• valet restart

Besides my custom driver the above seems to have fixed the issue...

UPDATE

As a request, I will also add to mention that with some others it might be a good option to try and simply turn off your locally running Apache, as this as others might find is only the issue that fixes it, as @greatwitenorth has mentioned

I had this same issue with a fresh install of Valet. I had to (apachectl stop) and then (valet restart). Once I did that it resolved my sites properly.

I had the same issue, did thesudo apachectl stop and valet restart which got me to 502 bad gateway. Then I found this question which said to do:

brew uninstall php70
brew install php70 --with-fpm

and that worked.

For me it was apache that was already running. Turned it off and Valet started serving sites. Strange that Valet said it started successfully with another application already bound to port 80 though.

@simondavies , if you can update your answer to include @greatwitenorth 's method that'd be helpful cause for me either all it took was turning of apache

@greatwitenorth , Big Thanks

sudo apachectl stop //Stop apache 
valet restart //now you are good to go

Might be silly but make sure after running the command to stop apache and restart valet to do a hard refresh... my browser had cached the old 'It works' page

For me it turned out that nginx and fpm were not running so I had to run:

sudo brew services start nginx

and

sudo brew services start php-fpm

Just ran into this after trying to follow a tutorial to get something unrelated working. One of the steps was to restart apache.

My mistake for following that blindly, but turning it back off made Valet work again.

sudo apachectl stop

just stopping apachectl worked for me too!

I had a different problem where i stopped nginx and then started it manualy, "it works" now. lol

sudo nginx -s stop

sudo nginx

For anyone having this issue using Xdebug Toggler for OSX you need to pass the flag --no-server-restart