For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
Hello there
I have a Mac mini m1. I received my Mac mini m6. Roon is on m1 as a “server” and I want to use the m6 as a “client”, like a remote. M1 is on Tahoe 26.6.2 while m6 is on Golden Gate 27.0
I see a big banner but TMI for me…just at the end it says wait for a fix.
The issue: Roon on Mac mini m6 doesn’t seem to properly connect to m1, it says Connect…Initializing… but nothing is happening.
Is this the issue of the big banner at the top of the website?
macOS controls which apps are allowed to find other devices on your network, through a permission called Local Network access. Roon has been running into it since macOS 15.6, and macOS 27 has made it worse. That is why the M6 sits at Connecting and Initializing: it cannot see Roon Server on the M1.
Please work through this article on the M6. The steps are short and the screenshots show where to look:
Start with “Check Roon’s Local Network Permission”, then “If Roon Isn’t Listed Under Local Network”. If the M6 still cannot reach the M1 after a restart, use the “macOS 27: Try the Network Workaround” section further down.
Please check the same permission on the M1 as well, for Roon Server. Both ends need it.
The change is Apple’s, and we do not have a timeframe for a proper fix. The steps above should get you playing now.
I first followed the macOS 27 Local Network troubleshooting steps and applied the recommended local-network workaround on the Mac mini M6. Network connectivity itself was fine: the M6 could reach the M1 and connect to the Roon TCP ports.
The key clue came from the Roon Server logs, which showed:
“Possibly multiple Remotes with same/duplicated IDs”
The same Roon client ID was appearing from both the M1 locally (127.0.0.1) and the M6 (192.168.1.17), causing Roon Server to repeatedly kill one connection when the other appeared.
This appears to have been caused by Migration Assistant copying Roon client data from the M1 to the M6.
On the M6, I renamed ~/Library/Roon to ~/Library/Roon_old, reinstalled Roon, and reconnected it to the existing Roon Server on the M1 (192.168.1.45).
I then reset the M6 RAAT state by renaming ~/Library/RAATServer and the RAAT cache.
After that, the M6 connected normally, the Rotel A14 MKII became available again, and playback started working.
So the root cause appears to have been duplicated Roon/RAAT state after Migration Assistant rather than a basic LAN connectivity issue.
Thanks for your help.
This was redacted with the help of AI and troubleshooting was done also with the help of AI. I forgot we shouldn’t use Migraine Assistant (iPhone autocorrect, you don’t know how much I struggled with it yesterday) but use the restore/backup feature of Roon. Also the m1 is my Roon server and the m6 a client.