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

Sequoia seems to randomly block local IP addresses

spaceballl

spaceballl

macrumors 68030
Original poster
Nov 2, 2003
2,937
362
San Francisco, CA
Has anyone else seen this? Specifically, here's the issue.

  1. I boot up the Mac, and everything works great. I can use Firefox and navigate via IP address to all of my local IP addresses.
  2. At some point, the local IPs don't work. I think my server is messed up. I go to the closet to reboot it. And then I still can't access it... I open up my phone, open the Plex app, and I can stream off the server... Hmmm. It's up.
  3. I reboot the Mac. I can log into my servers again.
  4. Repeat.
Anyone else seeing this strange behavior?
 
I am not surprised. If using Wi-Fi, try setting "Private Wi-Fi address" to OFF.

The new default is "Rotating" so that the interface's MAC address is frequently changed which a) may force a DHCP request for new IP address, and b) invalidates what is in the ARP cache on other devices.
 
  • Like
Reactions: Alameda
The same thing happens to me after every MacOS Sequioa update (ERR_ADDRESS_UNREACHABLE from web browser). I have been on Sequoia since developer beta 4.

Once I do an additional system restart after the update completes the local server web interface works. I have confirmed that access the web interface on another device also works for me while the Mac is throwing errors.

I was hopeful the Private Wi-Fi address option above would fix it, but it did not. I also turned off limit IP tracking as well.
 
I suspect it too, strange logs of network disconnections at random times, noted with both securityspy and plex. I'm waiting for 15.1 to attempt a clean installation.
 
Last edited:
I'm seeing the same thing, even after doing the things mentioned in this thread. This is using 15.1 RC and has been the same since the start of the 15.0 betas
 
I have been seeing a similar issue with Chrome and Firefox after an update from Sonoma to Sequoia on one of my user machines.

We have local websites we use on our LAN and local DNS server to provide domain names using old school UDP over port 53. I can open the sites in Safari and use the terminal to ping/dig/nslookup/curl the websites no issue, but anytime I try and use these two browsers it fails to load the websites w/ ERR_ADDRESS_UNREACHABLE.

I have explored multiple routes: turning off DNS over HTTPS, ensuring iCloud Priviate IP relay is off, ensuring no proxies are turned on, turning off the application firewall, removal and re-adding network interfaces, flushing DNS caches, uninstall and reinstall of programs. Nothing has moved the needle.

The local websites work for all my other users running a variety of OS's: Windows 11/Server, Mac Sonoma, various Linux flavors.

It seems crazy to me that these web browsers and breaking basic networking features.

Anyone else made any progress on cracking this nut?
 
  • Like
Reactions: flowsy
1729882115544.png


After a lot of chasing, we found that turning on these settings for our browsers solved our LAN resolution issues.
 
  • Like
Reactions: icanhazmac and flowsy
do you have the macOS firewall enabled? I've noticed some quirks there. also are you somehow using wifi6e? I've had to go to network settings on my MacBook Air and disable the wifi6e option so it wouldn't try to use it since it would randomly kill my network IP traffic while seeming to still be "online".
 
My server kept showing errors, so I proceeded to cleanly reinstall the system.

The 'classic' method (creating USB stick with Installer sequoia) failed because when I erased Macintosh HD the stick then saw the disk but did not proceed with the installation on it.

Only solution (DFU didn't work either): create a USB stick with Installer Sonoma, install sonoma and THEN install sequoia... unfortunately by doing so the network problems remained. (So installing sequoia even if on a clean installation of sonoma is not enough)

The solution was then to proceed with an installation by putting the Mac in DFU (at this point it worked) and starting out 100% clean (sequoia 15.0.1), the network problems no longer occurred.

(Firewall enabled)
 
Last edited:
I just started having this issue with my Chrome browser. What is interesting, is it only seems to affect local webpages on the same subnet. I have some other web pages on a separate routable vlan that I can still get too. I can turn off/on the local network privacy setting, but that doesn't fix the problem. If i quit and reopen chrome, everything works again. This only seems to have started impacting me after updating to 15.3, and is still around in 15.3.1. When I got my Mini M4 a month ago, it was on 15.0 (or 15.1), and never had the issue.
 
For me, using Firefox, this issue has been fixed for a while now (I'm on the dev beta track).

To fix it at the time (until I installed the next beta), I'd go into Privacy & Security, Local Network and toggle access OFF for Firefox and then back on again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back