ERR_CONNECTION_TIMED_OUT Chrome with Valet

laravel / valet

A more enjoyable local development experience for Mac.

https://laravel.com/docs/valet

MIT License

2.52k stars 698 forks source link

ERR_CONNECTION_TIMED_OUT Chrome with Valet #611

Closed hocine87 closed 6 years ago

hocine87 commented 6 years ago

Hi,

I configure Valet for my project, but when i go to adresse i have a chrome error.

DNS_PROBE_FINISHED_NXDOMAIN

PHP version : PHP 7.2.8

drbyte commented 6 years ago

NXDOMAIN stands for "non-existent domain"

Basically in the case of Valet it means your dnsmasq service is probably not running, or is not configured to resolve domains ending in the TLD you've used for your project.

Perhaps you haven't configured Valet using valet park to specify directories to use for your projects. Perhaps you haven't configured Valet using valet domain for the TLD you're trying to use. It defaults to .test which is what you really should be using if you don't want to clash with other real TLDs.

You didn't indicate the domain/tld you were attempting, nor whether this problem is occurring for all projects or just a specific one.

drbyte commented 6 years ago

I think your dnsmasq is still not active. When you ping project.test it should resolve to 127.0.0.1 not 192.168.x.x (the ping request may still timeout since the internal firewall may not be set to respond to pings, but the IP address should show as your localhost)

It suggests to me that dnsmasq isn't running. What does brew services list show? When did you last reboot? What does brew services list show after the reboot?

In your Mac's System Preferences->Networking->DNS page, what do you have listed for DNS IPs?

You may find my custom configuration for dnsmasq beneficial, as posted in comments in these related issues: https://github.com/laravel/valet/issues/299#issuecomment-274177318 https://github.com/laravel/valet/issues/115#issuecomment-241275816

drbyte commented 6 years ago

dnsmasq needs your Mac's DNS pointed to localhost, like this:

drbyte commented 6 years ago

You could also enable logging in the dnsmasq config file and then review the logs to see what it's saying. I'm guessing you'll find nothing in it since I think your Mac is still not sending requests thru dnsmasq.

I don't think this is valet-specific. You may find stackoverflow and dnsmasq troubleshooting sites (be sure to specify Mac) to be helpful in sorting out your issue.

adamwathan commented 6 years ago

Closing this as not an issue with Valet itself since there's no code we can add to the project that is going to solve this for you. Feel free to continue the discussion to try and troubleshoot your problem though!

vladimir-xaro commented 3 years ago

I had the same problem, Chrome was showing this error and FireFox was working fine. The solution was to change dns in Chrome settings:

mkwsra commented 2 years ago

My issue was the same as @vladimir-xaro , however, I was using Google's DNS instead of Cloudflare, which caused the problem, so boys please stick with "With your current service provider"

sawirricardo commented 2 years ago

@vladimir-xaro @mkwsra Are there other ways? I need to still use dns in my chrome though.