· None of the above quite fits
· None of these quite match
· RoonServer on macOS loses outbound network connectivity after recent update
· Home network uses a TP-Link Deco M9 Plus mesh system as the primary router.
RoonServer runs on a Mac connected via stable local network (wired Ethernet to a Deco node).
No VPN is enabled on the RoonServer.
No custom firewall
The previous Roon version worked flawlessly on the same system and network. The issue started immediately after installing the latest update.
Qobuz and TIDAL pages fail to load (“Error loading page – please check your network connection”)
Roon Search fails with “Can’t connect to Roon Search”
The issue can be temporarily resolved by:
After doing this, everything works again for a while but the problem reappears.
Hello @VidarDK,
Thank you for the detailed report — that’s very helpful.
What you’re seeing is not specific to Roon alone. With macOS Sequoia, Apple introduced stricter and more opaque handling of Local Network permissions, and we’re seeing reports across multiple applications where macOS will randomly revoke or partially invalidate network access for apps that rely on local and outbound discovery.
This explains why:
Your workaround (re-toggling Local Network permissions and restarting RoonServer) aligns exactly with this macOS behavior.
Our engineering team is actively investigating ways to make Roon more resilient to these macOS permission resets. However, at the moment we don’t have a confirmed fix or a timeline to share, as this behavior is controlled at the OS level.
For now, the recommended steps remain:
We understand this is frustrating, and we appreciate your patience while we continue working with these macOS changes in mind. We’ll share updates as soon as we have more to report.
Thank you for the clarification.
Just to be clear, this setup was completely stable on the same macOS version prior to the latest Roon update, and the current behavior is quite frustrating in day-to-day use.
I’m happy to provide logs or assist with further testing if it helps move this investigation forward.
Hi @VidarDK,
Thank you for the clarification — and we completely understand how frustrating this is.
To address your main point directly: at this stage, there’s nothing further we need from you.
What’s happening here is consistent with a known macOS behavior where, after an application update, macOS can internally re-evaluate the app as “new” and silently restrict or partially invalidate its Local Network permissions. This is not specific to Roon and has been observed with other applications as well.
Our engineering team is already aware of this behavior and is actively investigating ways to improve resilience against these macOS permission resets.
For the time being, the workaround you’ve already found remains the recommended approach. We’ll share updates as soon as we have anything concrete to report.
Thank you for your patience and for offering to help — it’s appreciated.
This topic was automatically closed after 17 hours. New replies are no longer allowed.
