jeudi 19 janvier 2017

Laravel Valet not working- as if it's missing a web server

I followed the instructions to install Valet and it worked fine the first 2 days with no problems at all. Then out of nowhere it stopped working and only seemed to get worse with time. First there were 404 errors on all laravel projects beyond their homepage and eventually the sites stopped working altogether as if there isn't a web server running.

Here are some details about my environment:

  • Running macOS Sierra, PHP 7.1, MariaDB

  • Composer works fine and is in path

  • Valet 2.0.3 (latest at the time of writing this)

  • Changed MAMP to default ports to free up ports 80 and 3306 before installing and running Valet the first time

  • Pinging something.dev returns 127.0.0.1 as it should

  • Running something.dev in browser does not work D if there is no web server running

After hours of searching, fiddling, uninstalling and reinstalling everything I am now at a very bizarre point. If MAMP is running on ports 80 and 3306 Valet will serve something.dev although I still get 404 beyond the homepage. How can this be? Isn't MAMP supposed to be on other ports to free up 80 and 3306 for Valet or not running at all? The other strange thing is that something.dev will return my webroot which is Valet parked and not the site something.dev which is under the webroot. I have searched high and low and I am at a loss as to how I can get things running the way they should be



from Newest questions tagged laravel-5 - Stack Overflow http://ift.tt/2iYALig
via IFTTT

Aucun commentaire:

Enregistrer un commentaire