Endpoints missing after updating iMac to Mac OS 27 public beta (ref#DCL9SJ)

[John_Tullis]

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Network Zones* are affected.

How is the affected Zone connected to your RoonServer machine?

· Network - WiFi

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· I have a *mesh network* with devices connected to multiples points

Your local network might need some re-arranging to support Roon.

· None of the suggestions have helped me. I'd like to submit a support request.

Do you have an approximate timestamp of when the issue last occurred?

· from 1800 15 July and current

What are the make and model of the affected audio device(s) and the connection type?

· KEF LS50 wireless Wifi or ethernet from access point. Mano Mk3 streamer Ethernet from Access point. 3 iPod mini from wifi

Describe the issue

Problem appear to arise after iMac used as Roon Server was updated to Mac os27 public beta Endpoints no longer appear on audio option of Roon app on iMac

Describe your network setup

Asus mesh router 2 units ZEN WIFI PRO XT12

[Suedkiez (Just a fellow user like you)]

Did you try this known issue? It’s usually necessary to do this after updates

Roon Server Can’t Find Audio Zones / macOS Sequoia Network Connectivity Issue Workaround

The Issue macOS Sequoia (version 15), has tighter (and more obfuscated) network security settings than preceding macOS versions. This is causing problems during Roon updates; despite being previously enabled during the Roon installation MacOS, after an update MacOS is denying access to the network (yet retains displaying all is well). Roon Status Roon support and product team are aware and are working a fix, which I understand is quite involved (I have no timeline for that, sorry). The Workar…

[benjamin]

Hi @John_Tullis,

Thanks for writing in! I believe @Suedkiez is likely correct with the above reply. Since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.

Please try the following steps:

1. Open macOS System Settings → Privacy & Security → Local Network
2. Make sure Roon and Roon Server are both enabled
3. Even if they are already enabled, please toggle them off and back on
4. Fully quit Roon Server from the macOS menu bar / task bar
5. Reboot your Mac
6. After reboot, launch Roon again and check if the devices is avaliable again.

Once these permissions are refreshed and the system restarted, your audio devices should reappear.

Please let us know if the issue persists after these steps, and we’ll continue from there.

[John_Tullis]

Thanks for reply

Under System Settings-Privacy & Security-Local Network there is only an entry for Roon. No entry for Roon Server.

Since the update to OS 27 Beta when I turn on iMac and Roon app starts up I now get message that server cannot be found and have to select option to use iMac as server. That was not happening previously. Maybe that is an indicator of the underlying change/problem?

Regards

[vadim]

Hello @John_Tullis

Thanks for checking, and that’s a good, specific detail, only “Roon” showing under Local Network with no “Roon Server” entry at all points to the permission never being (re)registered for the server component under this beta.

Before we go further, could you please confirm you’ve completed the rest of the steps from our earlier reply: toggling the Local Network permission for Roon off and back on, fully quitting Roon Server from the menu bar, and rebooting the Mac? You mentioned what you found in System Settings, but not whether you did those remaining steps, so we want to make sure we’re not troubleshooting past something that might already resolve it.

Separately, and worth knowing since you’re already on a beta OS: this general issue (macOS silently dropping or failing to register an app’s Local Network permission after an update) is a known, longstanding bug on Apple’s side, not something Roon can detect or fix from our end, since that permission lives inside Apple’s own privacy framework. We’ve dealt with this exact pattern before and normally the toggle workaround is the only fix. That said, our latest Early Access build (2.71, build 1674) appears to trigger a fresh permission prompt on macOS, which may resolve the missing “Roon Server” entry you’re seeing. If the reboot and toggle steps above don’t fix it, you’re welcome to try that build: EarlyAccess: Roon 2.71 Build 1674 and ARC 1.81 Build 422 are Live!

Please let us know how it goes either way.

[John_Tullis]

Thanks Vadim

I did toggle permission for Roon off and on and still had my same problem.

I applied the Early Access build you linked and Roon Server appeared in Local Network options and access points are now accessible again

Your assistance is appreciated

[connor]

Hi @John_Tullis,

Thank you for confirming. This Early Access build will roll out in a public Roon update next, so you’ll be able to switch back to the main production track once you see a new release available. Instructions for migrating between EA and Production are listed here.

Please let us know if you encounter any issues.