Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

waqaspuri

macrumors newbie
Original poster
Aug 29, 2022
2
1
Hello, I have installed some software, possibly Laravel Valet, but I'm not exactly sure what I did wrong. The problem is that I'm unable to open the domain name anything. app, while the rest of the domain names resolve without any issues. Could there be a port conflict, or is there another issue? How can I find out what is conflicting? I'm using macOS Sonoma. the site works great on mobile devices connected via the same internet connection.

dns cache flushed
restarted.
apache2 stop
mysql stop
but still not working.
 
It might have modified /private/etc/hosts.
cat /private/etc/hosts should return:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
 
  • Like
Reactions: gilby101
To access the app through the hostname, you need to make sure it points to your localhost. The simplest way to do this is to add an entry to the /etc/hosts file.

Just map the hostname to 127.0.0.1 in that file. That should take care of it.
 
possibly Laravel Valet
I know nothing (until this moment) about Laravel Valet, but I do see from https://laravel.com/docs/11.x/valet that it installs dnsmasq on your Mac and configures that to modify DNS requests for .test domain. That should not affect other domains, but I suggest you look carefully at your dnsmasq configuration.

This is in addition to 1) anything odd in your /private/etc/hosts and 2) changes in your macOS DNS settings.
 
I know nothing (until this moment) about Laravel Valet, but I do see from https://laravel.com/docs/11.x/valet that it installs dnsmasq on your Mac and configures that to modify DNS requests for .test domain. That should not affect other domains, but I suggest you look carefully at your dnsmasq configuration.

This is in addition to 1) anything odd in your /private/etc/hosts and 2) changes in your macOS DNS settings.
I was able to resolve it with that, installed it again, with dsnmaqs then --force to terminate entire list of valet parked domain names. Now am able to resolve .app domain names. It was conflicting with dnsmasq somewhere.
 
  • Like
Reactions: gilby101
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.