· My Mac Air works as Roon server. Play music on a Devialet Expert pro core. Expert Pro connected to network via Ethernet. Devices on same network. After updating to Golden Gate on MacAir I can't play my music on Roon, First I get message Waiting for Roon Sever. After reinstalling Roon I can log in but Roon can't see my Experts ethernet connection, Still can not play music. After restarting computer get message Waiting for Roon Server, Tried all things possible for two days bur can not find solution, What to do?
Tell us about your home network
· Its a standard telia network . All Equipment on 2.4.
What you describe is consistent with the macOS 27 update. Golden Gate tightened what applications are allowed to do on the local network, and Roon Server is caught by it, which is why your Expert Pro stopped being visible even though nothing changed on your network or on the Devialet.
Everything we know about this, and the steps to take, are in one place:
Thanks. I tried all steps you sugest but not the “workaround”. It is too complicated for me and not a sustainable meassure. Pls note you write: “Privacy & Security > Local Network and turn Roon and Roon Server off, then back on.” I can only see “Roon” but not “Roon Server”.
We recognize the steps involving the MacOS terminal application are quite tedious and intensive for what’s meant to be plug-and-play functionality.
However, the unfortunate reality in this case is that MacOS 27 Golden Gate has restricted RoonServer and Roon at a deep operating system level that you can only directly influence by entering these commands into the terminal. It’s the only way to get device discovery back on a Roon Remote using Golden Gate.
It’s not meant to be a sustainable measure. The team is working diligently on a solution that will prevent Golden Gate from falsely flagging Roon as a security threat moving forward. Ideally, you’ll only have to do this once or twice.
Please let us know if we can help. You can find the Terminal app itself in the MacOS Applications → Utilities folder.
Thanks for noting that the workaround is not a practical option for you.
Can you try updating to the latest macOS version? We have seen a handful of reports that this has fixed the issue. Otherwise, you can open the Roon app via the package contents, that workaround should still be applicable.