Chromium-based browsers blocked from accessing local network management interfaces on macOS 15+
Hello Apple Team,
I am an IT/network professional responsible for managing enterprise networking equipment (e.g., Aruba APs, switches, firewalls).
Since upgrading to macOS 15+, Chromium-based browsers (Chrome, Edge, Brave, etc.) are unable to access management interfaces on local IP addresses, even when these use non-standard HTTPS ports such as 4343 or 8443.
l
Symptoms:
- ERR_INVALID_REDIRECT or ERR_ADDRESS_UNREACHABLE when attempting to connect to https://<local-IP>:4343.
- Curl or low-level network tools can still reach the device → the block is enforced by the OS/browser, not the network.
- Safari can sometimes access these devices, but Chromium-based browsers are blocked due to macOS Private Network Access policies.
This change breaks real-world enterprise workflows:
- Network devices often only expose HTTPS on specific ports with no configurable DNS.
- IT professionals need to manage many devices across multiple sites with dynamic IP addresses.
- Importantly, this type of block does not improve security, since the same devices are fully accessible if they are on public IPs. Blocking local IPs in Chromium/macOS does not prevent actual threats; it only hinders professional network management.
- Security should be controlled by enterprise policies, firewalls, and internal security measures, not hardcoded OS restrictions.
Request:
- Provide a mechanism (flag, system preference, or enterprise policy) that allows IT professionals to disable this restriction for trusted local networks, or allow private network requests from Chromium-based browsers.
- Ensure that enterprise users can continue to manage their network devices on local IPs without workarounds such as VMs or port remapping.
Thank you for considering this. This change has a significant operational impact on enterprise IT teams.
Best regards,
Network and Security /IT Professional
[Edited by Moderator]
MacBook Air 15″, macOS 15.6
