Some Mac users running Roon Server on macOS 27 are reporting a peculiar problem: Roon itself works, Remote apps can still connect to the Server, yet Roon Ready streamers and network speakers disappear from Settings > Audio.
Roon has acknowledged the issue and says it is related to how macOS 27 handles local network access. When Roon Server attempts to establish outbound connections to audio devices on the local network, those connections can be blocked by the operating system, producing No route to host errors in the logs.
The result is an unusual situation in which the Roon interface appears healthy while the network audio endpoints themselves vanish.
The Network Is Working, but Roon Cannot See the Devices
The problem can easily be mistaken for a streamer, router or network failure.
Users have reported cases where network audio devices disappear from Roon on a Mac running macOS 27 but immediately reappear when the same Roon Server is moved to another operating system.
In other cases, the same streamer continues to work through services such as TIDAL Connect while remaining unavailable in Roon.
USB DACs connected directly to the Mac may also continue to appear normally, further pointing to a problem with local network access rather than Roon’s audio engine as a whole.
Local Network Permission May Not Be Enough
macOS allows users to manage local network access under:
System Settings > Privacy & Security > Local Network
Normally, confirming that Roon and Roon Server have access here would be the obvious first step.
However, Roon says that toggling Local Network permissions or reinstalling the application may not fully reset the affected network state on macOS 27. In some cases, the permission appears to be enabled while outbound local network connections remain blocked.
Roon’s Temporary Workaround
Roon has published a temporary workaround that involves manually allowing the local network range through Terminal.
Users first need to identify the Mac’s IP address and local subnet, then add the relevant network range for the active Ethernet or Wi-Fi interface. Roon ARC users may also need to allow the multicast range 224.0.0.0/4.
After restarting the Mac, the missing network audio devices may reappear in Settings > Audio.
Roon stresses that this is a system-level change rather than a Roon-specific exception, so it should be regarded as a temporary workaround rather than a permanent fix.
Restarting RoonServer Directly Can Also Help
A simpler workaround has also been reported by users.
After quitting both Roon and Roon Server, users can navigate to:
Applications > Roon.app > Show Package Contents > Contents > RoonServer.app
Launching RoonServer.app directly and then reopening Roon has restored missing network devices in some systems.
This method has reportedly been useful in cases where the issue reappears after the Mac wakes from sleep.
It is not, however, a guaranteed fix for every configuration.
For Now, This Is a Workaround, Not a Resolution
The issue does not appear to be caused by a change to RAAT or the Roon Ready protocol itself. Instead, it concerns how macOS 27 allows Roon Server to reach audio endpoints on the local network.
That distinction matters for users who run Roon Server on a Mac mini or Mac Studio while using separate network streamers, DACs or active speakers. An operating-system update can effectively remove those endpoints from the playback chain even while Roon itself continues to operate normally.
Users who have not yet upgraded their Roon Server Mac to macOS 27 may want to wait for further guidance from Roon. Those already affected should check whether the issue matches this known macOS 27 behavior before resetting streamers, routers or other network hardware.
Roon says its development team is continuing to investigate a permanent solution.
