Can Local create a conflict with Laravel Valet?

I have Local and Laravel Valet installed on my computer. Apache can create an error with Laravel Valet where any page setup with Valet returns “It Works!” instead of the actual site. They both use .dev extensions so I’m not sure if there is a conflict.

If I try “apachectl stop” in the terminal I get this error “Could not find specified service”. Is Local running apache from a different location?

Local and Valet are on entirely VMs so none of their services should conflict.

However, if Valet is running some type of local DNS server to resolve .dev domains that may cause some trouble.

I honestly can’t think of any ways Local would interfere with Valet other than the /etc/hosts file somehow getting in the way of Valet’s host resolving.

Have you tried using non-.dev domains in Local by chance?

From Laravel Valet - Laravel 5.4 - The PHP Framework For Web Artisans

Laravel Valet configures your Mac to always run Nginx in the background when your machine starts. Then, using DnsMasq, Valet proxies all requests on the *.dev domain to point to sites installed on your local machine.

… so, yes, you’ll get an conflict

1 Like

It is, however, quite easy to change Valet’s domain suffix:
$ valet domain <suffix>

That should make Valet and Local live peacefully side by side.

1 Like

I changed the Local sites to have a different domain extension and it they both work now!

Thank you for your help :slight_smile:

1 Like