Help setting up Valet correctly

Just in case someone has a problem with Valet you can try these suggestions by Adam Wathan (posted on Github):

Most common things to try:

Delete ~/.valet and re-run valet install

Log out of your OSX user account and back in, sometimes this is needed for the DNS resolver changes to get picked up

Look for errors in PHP FPM logs: cat /usr/local/opt/php70/var/log/php-fpm.log

Verify dnsmasq and php70 are running as root in brew services list

Make sure /usr/local/var/log exists so PHP FPM can write logs there

Verify PHP FPM is running by running ps aux | grep php and looking for a couple of FPM instances

Verify User and Group are set to your user name and the staff group in /usr/local/etc/php/7.0/php-fpm.d/www.conf, the installer should do this for you but worth double checking.

Just tried valet share for the first time and I'm getting these dial tcp [...] no such host errors also. I've done all the things @RichardMX suggested to no avail.

Will keep troubleshooting and working to figure it out, but bumping this in case anyone has other suggestions.

For those of you having trouble getting valet to install/work, I have a pretty great SO post here that helps me go step by step to make sure everything is working properly: https://stackoverflow.com/questions/37719851/pinging-test-dev-after-laravel-valet-install-returns-unknown-host

I have the same issue, but caddy don't start on port 80, when I check the port there's no caddy listening, I try everything, delete, remove, reinstall, check my mac, and nothing.. any help?

Did you try the process outlined in the answer to my SO post (linked above)? That process is what I use and it helps every time. More than that, I'm not sure.

Fixed my issue. I'm not sure how I was even able to see domain.localhost but when I pinged it it wouldn't resolve. That reminded me after reinstalling valet I had forgot to valet domain localhost. After running that command, I was ablet o ping domain.localhost again and at that point valet share ngrok domains started working.

@nateritter Thanks for the notice, but no success... must be something in my mac..

@vhguillen when you valet start and then sudo lsof -n -i:80 | grep LISTEN what do you see?

@nateritter is blank, nothing listening port 80, no caddy at that port.

@vhguillen and what are the results of brew services list?

@nateritter #brew services list

Name Status User Plist

dnsmasq started root /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist

mariadb stopped

php70 started root /Library/LaunchDaemons/homebrew.mxcl.php70.plist

I'm getting this in the logs mac console: 7/16/16 7:38:26.969 AM dnsmasq[16244]: failed to create listening socket for 127.0.0.1: Permission denied 7/16/16 7:38:26.969 AM dnsmasq[16244]: FAILED to start up

Thanks in advance

@vhguillen Try this: http://stackoverflow.com/questions/37172691/valet-laravel-dns-address-can-not-be-found/37174256?noredirect=1#answer-37174256 step by step ... one step at a time check each thing. Sounds like you've found the issue (dnsmasq).

@nateritter at this point I'm not ablet past this point:

• You may however need to tap brew/services first

• brew tap homebrew/services

• If it's not there, run

• brew install dnsmasq

• brew services start dnsmasq

brew install dnsmasq but. I did this and when I re-run brew tap homebrew/services it shows nothing. And still getting the error log, dnsmasp failed to startup.

What is in the last few lines of your /usr/local/etc/dnsmasq.conf file? If it's something like this: conf-file=/Users/YOURUSERNAME/.valet/dnsmasq.conf then what's the contents of that file?

@nateritter

1 - Yes the last few lines of /usr/local/etc/dnsmasq.conf is

conf-file=/Users/YOURUSERNAME/.valet/dnsmasq.conf

And the content of this file is: address=/.dev/127.0.0.1

Inside the directory /etc/resolver, there should be a file entitled dev with the following contents

nameserver 127.0.0.1

Is that true?

Yes, I was looking at this with no success:

http://superuser.com/questions/367754/wifi-conflict-with-dnsmasq-osx

Hmm.. well, I guess it's out of my league. Sorry. Wish I could help more.

Jeje, don't worry @nateritter your help were very welcome, I'm just keep searching and testing, I ran dnsmasq with root and eliminate the socket permission console error. But valet still don't work, If I find the solution I'll let you know.

@nateritter : I found something it is with caddy, I ran this command inside the project folder.

In this case ~/Sites/blog/

sudo ~/.composer/vendor/laravel/valet/bin/caddy --conf=/Users/{myuser}/.valet/Caddyfile

and it works.

Other wise it doesn't work.

I found the solution @nateritter, it was a mcafee antivirus installed, was blocking the LaunchDaemon service.

Now I have valet working perfectly.

Thanks for all the help.

Ah, I never would have guessed that one. :) Congrats on figuring it out!

Cheers.

I have the same problem :(

I don't have mcafee installed how can I test if my LaunchDaemon service is blocked?

Here is my system info

Mac osx Siera 10.12.4 (16E195) Laravel Valet 2.0.4 PHP 7.1 dnsmasq-2.76

Tried everything with no success, Could you please help