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 Workaround
Please navigate to macOS System Settings > Privacy & Security > Local Network, and make sure Roon is allowed.
If it is already enabled, toggle the setting off and on again. Then reboot your Mac, and see if the same issue persists.
I hope it helps, if not please follow this link to provide specific details of your case to Technical Support.
We wanted to provide an update on the Local Network permissions issue described in this thread.
Over the past year, our team has spent considerable time investigating whether Roon could detect or automatically recover from the state where macOS revokes or invalidates Local Network access. Unfortunately, after extensive testing and review, we’ve confirmed that this permission state cannot currently be reset or repaired by Roon itself.
The Local Network permission system in newer versions of macOS is fully managed by the operating system. When macOS places an application into this state, there is no API or programmatic method available that allows an application like Roon to restore the permission. At present, only the user or a change from Apple to the macOS permission framework can resolve it.
The typical symptom of this state is that both network devices and locally controlled CoreAudio devices disappear from Roon. This happens because Roon relies on the system’s loopback networking to communicate with local audio devices, so when macOS blocks Local Network access, it can prevent both network endpoints and locally attached audio devices from appearing.
Because of this limitation, the workaround described in the original post remains the required solution: manually toggling Roon’s Local Network permission in macOS if you notice that your devices suddenly disappear.
We will continue monitoring changes to macOS in case Apple introduces a mechanism that would allow applications to recover from this state automatically. If that happens, we will absolutely revisit the issue and implement a fix on our side.
For now, if you encounter this behavior, please follow the steps outlined in the post above to reset the permission. If you continue to encounter issues, please create a tech support request here and our team will promptly investigate.