Level 23
Try running valet link from inside the directory of your project. If error still persists, maybe try running valet stop && valet start?
3 likes
Dec 27, 2017
11
Level 1
Valet is not working (site cannot be reached)
Hi,
I install valet reading the documentation, then use the park command in the sites folder and then use the command laravel new blog. But when I access any of the link below it appears site cannot be reached.
https://blog.dev/
https://blog.test/
http://blog.dev/
http://blog.test/
Do you know how to debug this error better? I already read some discussions about none fixed the issue.
The command brew services list shows:
Name Status User
php71 started root
nginx started root
mysql started dennk
The command valet path shows:
"/users/dennk/sites
Ping to localhost works but ping to blog.dev or blog.test dont.
Level 1
Thanks..but get the same issue.
Level 1
ping blog.test or ping blog.dev shows: cannot resolve blog.test/blog.dev: unknown host.
Level 19
Looks like you are missing, dnsmasq. Have you ensured that it also installed and running? From the list that you provided of brew services, you don't have it installed.
Also by default Valet's domain should be .dev; However, using chrome you may need to change that to .test. or something else.
valet domain should output what the domain is set to. valet domain test will change it to .test.
You also can't access your local sites with valet on https:// unless you have set them up to be accessed that way. valet secure domain
2 likes
Level 53
Read this article about not using dev for development any longer.
https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd
2 likes
Level 1
Thanks for the answers. valet domain shows "test". But the issue continues, also using valet secure domain it appears the same issue site cannot be reached accessing https://blog.test.
Level 23
The dnsmasq service should have been installed with Valet. You should try removing valet and installing it again, or try to run valet star as root.
2 likes
Level 1
After head banging a little while, this bit helped. dnsmasq was indeed not installed at least in my case. So, had to stop valet, and restart valet. Then valet domain test revealed that the dnsmasq was not installed and started downloading from home-brew and that fixed it. Was able to launch http://blog.test.Thanks
Level 1
I faced the same issue, after searching a lot, I found the solution. Go to the root and run: valet domain test . This test here is the domain you want to use. you can use any (test, me, app) etc.
This will definitely work, try it. :)
Level 6
Update 27.03.2022, For me worked: valet domain test, and then: valet use [email protected] --force
2 likes
Level 1
Just a follow-up on this that may be relevant for anyone coming at it new (like me) using macOS 13 Ventura (and on Apple Silicon, if that matters):
The solution from @mkrebseberth worked for me. It's probably also worth noting that at the valet domain test command, I got this prompt:
Using a custom TLD is no longer officially supported and may lead to unexpected behavior. Do you wish to proceed? [y/N]
I'm guessing that the fact that this is no longer supported is why it wasn't working automatically! But it explains why pinging a .test domain wasn't working for me, even though I was positive that dnsmasq was installed.
1 like
Please or to participate in this conversation.