Devices unable to connect to Roon Server (ref#LR1T4E)

[Chuck_Nelson]

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· I see something else

When you try to connect, what screen do you see?

· Just the Roon logo

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

· *Mesh networks*

You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.

· None of the above

Describe the issue

Any device won't connect to Roon Server. Used to be no problem.

Describe your network setup

Asus Mesh Router. Hardwired Mac mini as Roon server.

[connor]

Hi @Chuck_Nelson,

First, retoggle local network permissions for Roon in MacOS System Settings → Privacy & Security → Local Network.

Is the Mac hardwired to the main router or to a mesh node? If you’re still having issues, please try enabling multicast forwarding in your Asus mesh network router settings page.

This setting is intertwined with IPTV on Asus routers. Go to Advanced Settings → LAN and open the IPTV tab.

What do you have configured for IGMP snooping and multicast routing/IGMP proxy?

We’ll watch for your reply. Thank you.

[Chuck_Nelson]

I recall doing the “Privacy & Security –> Local Network before so I tried that first. Toggling the loan network permissions didn’t do anything until I restarted the Mac mini (I recall having to do that before). Then when I opened the Roon app on the Mac mini, it asks if I want to connect to my MacBookPro or “Setup a Roon Server on this Mac”. So it seems it’s lost the Roon server on the Mac mini. However, in the Mac mini “Activity Monitor” app, I see “Roon” running and consuming about 10% of the Mac mini CPU. Should I press the violet “Use this Mac” button to set it back up?
I haven’t tried the other router things you mentioned although the Mac mini is hardwired to a network switch that is connected to the Asus mesh base unit.

[benjamin]

Hey @Chuck_Nelson,

Thanks for the update!

@Chuck_Nelson

Should I press the violet “Use this Mac” button to set it back up?

If your mac mini is usually your server, then yes, press ‘Use this Mac’ and you’ll be all set.

[Chuck_Nelson]

When I pushed “Use this Mac” and then login, it says, “You’re already signed in”, and at the bottom of the screen asks if I want to “unauthorize” my Mac-mini instance (so it still thinks one is out there). Should I go ahead and unauthorized?

[vadim]

Hello @Chuck_Nelson,

Yes, it is absolutely safe to click “Unauthorize”.

Doing this simply transfers your active Roon license to the current Roon Server you are trying to access. It will not delete your database, music files, playlists, or any of your settings. It is just our system’s way of confirming which server should be actively using your account right now.

Please go ahead and click it, and let us know if your devices are able to connect successfully afterward!

[Chuck_Nelson]

After unauthorizing, rebooting the Mac mini twice, and toggling the Local Network settings for the Roon server a few times, I was able to get the Roon Server with all the network audio devices working again (all sources had disappeared and needed to be renamed but the music library was intact).

Then there appeared to be an update that came through (2.6.2 Build 1641) and things still working after that. Thanks!

[vadim]

Hello @Chuck_Nelson,

That is fantastic news! We are thrilled to hear that you got everything back up and running, and that the system remained stable through the recent update to build 1641.

Just to give you a bit of context on why you had to jump through those hoops: macOS has a known quirk regarding its Local Network privacy permissions. Sometimes, when an app like Roon Server is updated, macOS gets a little confused and silently blocks those network permissions in the background—even if the toggle in System Settings still looks like it is turned “on.”

Toggling that Local Network setting off and back on, along with the reboots, forces macOS to properly re-register the permission. That is exactly why your Roon Server was finally able to see the network and communicate with all your audio devices again.

If you ever notice your devices suddenly dropping off the radar immediately following a Roon or macOS update in the future, toggling that Local Network permission is a great first step to try.

Happy listening, and please don’t hesitate to reach out if you need help with anything else!