Hi @Mike_Rife,
Thanks for the quick response. Feel free to migrate to the other RoonServer machine in the meantime - we’ll enable diagnostics for that unit as well.
I will let you know when it is completed. Thank you. Seriously.
OK, I have moved to the “other” 2018 mini. All my zones are up — except for a Bridge that this device hosted — and running fine on a mini that had no earlier Roon server attached to it. It is running on wi-fi.
Playing fine. Question. Should I set up a Bridge on the other, original mini? Or just wait and see? It is currently on my desk. I can set it up, or wait.
One thing. In the mysterious “Local Network” section it shows “Roon.” The other showed “Roon” and “Roon Server” as two separate items. Is there anything to this?
Connor, I can’t thank you guys enough for working with this Old Man to get my favorite thing working correctly.
MIKE
1 Like
Connected the OG mini where the replacement used to sit. Downloaded a Roon Bridge and opened it. Says it is running. My audio zones do not show it though it appears in my Local Network section of the mini.
Hey @Mike_Rife,
Glad to hear you’ve sorted out most of your issue!
Apologies for my confusion here - are you planning to use this Mini as a remote device? If so, there’s no need to run Roon Bridge on the device.
Perhaps a reboot of Roon and Roon Server may help? Can you confirm the Mini is on the same local subnet as your other Roon devices?
I’d also double check any Mac firewall settings with the Mini running bridge or your Roon Server - see if temporarily disabling them may help. 
I replaced the mini (1) I was using as my core with the mini (2) I was using in my office. It (2) is up and running fine so far. I deleted every iteration of Roon from the device I replaced (1).It will take the place of the (2) I moved from my office. I installed a Roon Bridge app on (2) that will be my office computer and made sure both (1) and (2) were runnng on my network.
So far, (2) does not see (1). (2) does see my soundbar on the same network. I have no firewalls enabled on either.
Bridge shows up in the “About” section but not in the network area of my audio setup.
So, today’s chapter. This am Apple pushed a Sequoia update to my minis. Before I started my latest quest, I took the upgrades, knowing that gift had taken my zones away before.
I reinstalled a new Roon Server on the mini that served me well before the conflict. Then I cleaned up the office mini and installed a Roon Bridge.
As of now all six of my zones are up and playing. I did have to remove power to my core device at one point, and my zones disappeared again. I did the sliders trick which restored them.
Oh, and somewhere in the process I lost Bluetooth to my keyboard and trackpad. Another problem I had to track and solve.
Tomorrow, I may have to access the sliders again, maybe every day.
Better than yesterday.
Hey @Mike_Rife,
Thanks for the update!
Based on your admin in Roon, we do see a few Macs, but they’re running the latest version of Seqouia, not Sonoma. Did you recently update them again to latest macOS?
If so, there are some known fixes Apple pushed around Apple’s handling of Coreaudio, that very likely helped you with your issue. Most Roon users didn’t have to re-enable local network access after the update. I’m hoping this will be the case for you as well!
We’ll leave this thread open over the next few days just to make sure things have smoothed out for you! 
My mistake, Sequoia it is.
2 Likes
Hi @Mike_Rife,
Thanks for confirming that for us!
Everything is stable so far. My playlist played fine as does my iPad, Sonos stream and Office Bridge. Six successful days in, but I will still be wary of all upgrades going forward.
Thanks to all who helped despite my rants and disappointments through this small nightmare,
1 Like
This has been an ongoing problem since macOS 15 in September, there are probably a hundred threads about it. Where have you been? 
However, the vast majority of people seem to have reported that it got fixed with 15.3, so the main tracking thread was closed and Roon Labs asked for people who are still affected to open new support tickets
I opened a ticket 17 days ago and received advice to correct the problem. I struggled through multiple attempts to get where I am now.
So far,so good
I know, I think it was I who recommended it.
My post was in response to @David_Snyder because he didn’t seem to be aware of the issue.
I was not aware because I follow my own advice and run Roon Server on a ROCK build.
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.