MacOS updates restrict Roon's Local Network access (ref#0J0V8A)

[Powered_Two_Wheeler]

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Looking for your Roon Server"

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *MacOS*

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

It's back! MacOS updates prevent permissions for Roon to access Local Network. Toggle On/Off resolves the issue every time. Roon S/W levels are latest. MacOS latest 26.4.1 (25E253)

Describe your network setup

Unchanged

[Suedkiez (Just a fellow user like you)]

Note this recent update in the pinned support topic about this macOS behavior:

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

Hi everyone, 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 v…

[Powered_Two_Wheeler]

Oh I missed that. Ah well it’s not the end of the world. But still mildly annoying.

[Suedkiez (Just a fellow user like you)]

Yeah I didn’t see this for a long time either, and it definitely is annoying.

[vadim]

Hello @Powered_Two_Wheeler,

It’s definitely frustrating to feel like you’re playing “Groundhog Day” with your permissions every time a macOS update rolls out.

As @Suedkiez pointed out, our engineering team has spent a significant amount of time under the hood of macOS trying to find a way to “force” this permission to stay active or to repair it automatically.

Unfortunately, the Local Network permission is part of Apple’s TCC (Transparency, Consent, and Control) framework. It is a “black box” that third-party applications like Roon are strictly forbidden from touching. When macOS updates and decides to “forget” or invalidate that permission, Roon has no way to toggle it back on programmatically—only the user has that key.

Since you’ve already found that the Toggle On/Off dance resolves it, you are currently using the only known fix.

At this stage, because the issue lies entirely within how macOS manages its privacy database during updates, the most impactful thing you can do is submit a bug report or feedback to Apple. The more users they hear from regarding how these updates break local network handshakes for a lot of apps, the more likely they are to refine that framework in future versions of the OS.

Since we’ve confirmed this is an OS-level limitation and you have the functional workaround, I’ll go ahead and close this thread.

Thank you for your patience with this macOS quirk. Happy listening!

[Suedkiez (Just a fellow user like you)]

@vadim

When macOS updates and decides to “forget” or invalidate that permission, Roon has no way to toggle it back on programmatically—only the user has that key.

Maybe stupid question, but shouldn’t the app at least be able to pop up the message asking for the permission again? Other apps seem to do this for me, at least the HP print spooler for my old Laserjet (and this is much older than these macOS changes), which asks AFAICT after every macOS update.

I feel the main problem is that Roon fails silently and the user has to know they have to go to the permissions and toggle it.

[Powered_Two_Wheeler]

@vadim

ocal Network permission is part of Apple’s TCC (Transparency, Consent, and Control) framework. It is a “black box” that third-party applications like Roon are strictly forbidden from touching. When macOS updates and decides to “forget” or invalidate that permission, Roon has no way to toggle it back on programmatically—only the user has that key.

Done! Feedback submitted. Don’t hold your breadth! I think the pop up as suggested by @Suedkiez is valid.