Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Site can't be reached (ERR_NAME_NOT_RESOLVED) #175

Closed
rubenmoya opened this issue Sep 11, 2023 · 22 comments
Closed

[Bug]: Site can't be reached (ERR_NAME_NOT_RESOLVED) #175

rubenmoya opened this issue Sep 11, 2023 · 22 comments

Comments

@rubenmoya
Copy link

Operating system version

macOS Ventura 13.5.1

System architecture

ARM64 (M1, M2, etc)

Herd Version

1.2.0 (Build: 14)

PHP Version

PHP 8.2.10 (cli) (built: Sep 1 2023 00:12:21) (NTS)

Bug description

I'm new to all this PHP/Laravel/Herd world, so I don't really know how all this tools (valet/herd) work under the hood, please bear with me.

I installed Valet a while back, and used it for a little bit. Then when I read about Herd I uninstalled Valet and installed Herd, but somehow it still told me that "You have valet installed, let's migrate, etc".

Some services didn't start, but I restarted the computer and it worked.

Today I'm tried to use it again, but I keep getting the "Site can't be reached" error. I tried to upgrade to the latest Herd version, uninstall it, install it again, restart the computer, etc. And I still get the error, I'm not sure what I'm doing wrong.

I have checked the nginx, DNSMask and FPM-8.2 logs, and the only one with contents is the last one, this is the log:

image

The app itself looks like everything is "working":

image

I'm not sure where to look at, or what to try, so any help is appreciated.

Let me know if there is any more information that I can provide!

Steps to reproduce

No response

Relevant log output

No response

@Gandhi11
Copy link

I have the same problem on a Intel Mac

@jhgeluk
Copy link

jhgeluk commented Sep 14, 2023

Experiencing the same, also on Intel Mac

@mpociot
Copy link
Member

mpociot commented Sep 18, 2023

Could you please check if the following file exists: /etc/resolver/test?
If it does not, please create it with the following content:

nameserver 127.0.0.1

@mpociot mpociot closed this as completed Sep 18, 2023
@rubenmoya
Copy link
Author

Sorry to reopen this, I've just checked and it does exist:

image

Is there any information I can provide to debug it?

@sadhakbj
Copy link

I am also facing the same issue, valet was working perfectly fine, installing herd seems to be a problem for me.

@henryonsoftware
Copy link

henryonsoftware commented Jan 4, 2024

I got the same problem "This site can’t be reached", and yes on Intel Mac

@muba00
Copy link

muba00 commented Jan 5, 2024

I got the same problem "This site can’t be reached", and but on M1 Mac

@maxivassenko
Copy link

Same problem MBP on M3 Pro

@drlogout
Copy link

drlogout commented Mar 4, 2024

Same here.

@samueloshio
Copy link

Am facing same problem on windows 10. Is there any way to fix this please. I'm completely new to PHP Laravel and herd world. As matter of fact, this is my first bite using Laravel bootcamp chirper project 😉

As for my case, herd is serving from c:\users\user\Herd
Site in this directory like http://chirper.test says can't be reach

Any support to fix this will be appreciated 👍

@laurensgroeneveld
Copy link

In my case (on Mac) this was caused by having a NextDNS profile installed. When I disabled it I could access the site again (had to do a composer install first but not sure if that was related).

@joeyboli
Copy link

Solution : open your browser and change dns to default os dns

@phutd
Copy link

phutd commented Apr 24, 2024

In my case ( on Mac intel ), open GG Chrome settings and change DNS.
Example: GG public DNS - DNS Os

It works well for me.

@THUANDOVAN93
Copy link

Solution : open your browser and change dns to default os dns

In my case (on Mac Intel), open GG Chrome settings and change DNS (change to OS default)
It works well for me.

@andipyk
Copy link

andipyk commented May 6, 2024

chrome-capture

@superbolang
Copy link

Hello I encountered the same problem and above method didn't work

@clipsmm
Copy link

clipsmm commented Jul 2, 2024

Still experiencing the issue. It has been working the suddenly stopped working for all .test domains

ERR_TUNNEL_CONNECTION_FAILED

Screenshot 2024-07-02 at 13 38 04

MacBook Pro M3

image

But the .test domains are working well on other browsers: chrome, mozilla, safari

@hexlay
Copy link

hexlay commented Aug 5, 2024

None of the above helped on latest macos and latest herd (1.9.1) i still have ERR_NAME_NOT_RESOLVED and can't seem to fix it, also no logs are being written for that as well

@lancedouglas1
Copy link

Same issue, above solutions didn't help. Latest Herd and MacOs on M3

@mochadwi
Copy link

mochadwi commented Oct 9, 2024

the secure dns part on edge, solved my issue, thanks everyone suggesting

@jeffegiovani
Copy link

For me, in Windows, above solutions didn't help. Reinstalling Herd solved my problem.

@rvanbaalen
Copy link

Note to future self or others; for me, Little Snitch (network firewall) was routing all requests to a secure DNS server. Added a custom exception for the project.test domain and it worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests