[Bug]: Sites are unreachable

[Shahinyanm]

Platform

macOS

Operating system version

macOs Sonoma 14.5

System architecture

Intel (x86)

Herd Version

1.9.1

PHP Version

No response

Bug description

Problem Details

1.  After Upgrading to Laravel Herd 1.9.1:
•   All previously working sites are no longer accessible.
•   herd links and herd parked commands show that the sites are linked and parked correctly.
2.  Reinstallation Attempts:
•   I tried uninstalling and reinstalling Laravel Herd, but the issue persists.
3.  DNS Configuration:
•   The DNS settings are default for macOS.
•   The nameserver is set correctly.
4.  Firewall:
•   The firewall is disabled, but there is no change in behavior.
5.  Logs:
•   There are no relevant entries in the logs indicating any issues.

Steps to reproduce

Relevant log output

No response

[mechelon]

Can you try to force quit all services (hold the option key while the Herd menubar is open) and share your Nginx/DNSMasq error logs?

[Shahinyanm]

Dnsmasq now is using as i have installed localy , before there weren't any errors

[indrapalijama]

any updates on this one?

[Shahinyanm]

any updates on this one?

Yup, I have fixed, The first link was working automatically, but after the upgrade, it need to add 127.0.0.1 site.test to /etc/hosts

After that everything working correctly

[mechelon]

When I understand that correctly, you have installed another instance DNSMasq in parallel to Laravel Herd? It only supports using the instance that comes with it, then you also don't have to modify the hosts file.

[Shahinyanm]

When I understand that correctly, you have installed another instance DNSMasq in parallel to Laravel Herd? It only supports using the instance that comes with it, then you also don't have to modify the hosts file.

Nope, i didn't I only upgrade Laravel herd from 1.4.1 - to 1.9.1 , restart macos, and then no sites was reached

After ton of manipulations , delete and install, tried to write manually site in hosts , and it works,

[sschlein]

There's definitely something running on the same port that dnsmasq uses and so Herd can't start the version that's shipping with it. If you can solve this and stop the other program from blocking it, you'll be good with Herd

[indrapalijama]

There's definitely something running on the same port that dnsmasq uses and so Herd can't start the version that's shipping with it. If you can solve this and stop the other program from blocking it, you'll be good with Herd

yes, i noticed that my dnscrypt-proxy is using the host (127.0.0.1) as dnsmasq so it's not working, do you have any idea how to run it side by side?

[sschlein]

You can't – that's not supported by Herd nor the proxy, they both need the same port.

[Shahinyanm]

There's definitely something running on the same port that dnsmasq uses and so Herd can't start the version that's shipping with it. If you can solve this and stop the other program from blocking it, you'll be good with Herd

I have checked , there is only one process for dnsmasq and it's started by herd,

[victor-falcon]

I had the same problem.

Now it's working after adding 127.0.0.1 site.test to my /etc/hosts but I think there is something wrong with DNSMasq, don't know why is this issue closed.

[ataldev]

I had the same problem.

Now it's working after adding 127.0.0.1 site.test to my /etc/hosts but I think there is something wrong with DNSMasq, don't know why is this issue closed.

But this is not the solution! it's supposed to work without this. Herd should handle this by itself.

[mechelon]

The initial issue was closed because Herd does not support parallel use of two Dnsmasq instances. Feel free to open another issue with your specific problem. (Modifying your hosts file should not be necessary.)