Chromium based browser repeatedly shows: ERR_ADDRESS_UNREACHABLE

Question

Level 1

4 points

Chromium based browser repeatedly shows: ERR_ADDRESS_UNREACHABLE

Hi, Edge is unable to access websites on the local network, showing the error: ERR_ADDRESS_UNREACHABLE.

It used to work, and the issue first appeared after the Sequoia update. Back then, applying certain tricks resolved it, but since the latest update (macOS 26.0.1), those old methods no longer work. Safari still works fine on the same machine, as do other non-Mac computers on the same network.

[Edited by Moderator]

MacBook Pro (M1, 2020)

Posted on Oct 3, 2025 5:05 AM

Reply

Answer 1

Top-ranking reply

Akairo Author

Level 1

4 points

Oct 4, 2025 6:18 AM in response to Akairo

I managed to get it working. I had tried before by entering the address

but that didn’t help.

What finally worked:

Even though my server doesn’t communicate via HTTPS, I entered the address in the form. At that point, macOS prompted me to allow Edge to access the local network, even though it had already been granted permission. And lo and behold, it’s been working ever since. Something must’ve been stuck, I’m not sure, but now it’s working again.

[Edited by Moderator]

Reply

Answer 2

Oct 3, 2025 8:58 AM in response to Akairo

Akairo wrote:

Hi, Edge is unable to access websites on the local network, showing the error: ERR_ADDRESS_UNREACHABLE.

It used to work, and the issue first appeared after the Sequoia update. Back then, applying certain tricks resolved it, but since the latest update (macOS 26.0.1), those old methods no longer work.

Safari still works fine on the same machine, as do other non-Mac computers on the same network.

[Edited by Moderator]

Try a different browser and compare your results...

if that works it points to your third party app—if in doubt search the developers website or contact their: Support/Help/FAQ/Known issues/compatibility/updates…

Contact a third-party vendor - Apple Support

Reply

Answer 3

Akairo Author

Level 1

4 points

Oct 4, 2025 5:57 AM in response to Akairo

However, the issue reappeared today (after I restarted the Mac, since it had only been in sleep mode since yesterday), and once again macOS asked whether I want to allow Edge to access the local network. So it seems the bug might actually be in macOS.

Reply