I have only ever had one machine – a Mac Mini – as my Roon Core.
For reasons I don’t understand, whenever Roon stores an upgrade, I have to remote into the Mac Mini to manually start Roon. Today when I started it, it asked me to login…it’s never asked me to do that.
Now all of my devices are reporting that I’m only authorized to run one Roon Core. Returning to the Mac Mini, it just freezes on “Looking for your Roon Core.” I’m reluctant to choose “Use this Mac” because of what it might do to my library. Restarting the app doesn’t help.
I have gotten pretty disappointed with Roon software quality. That I have to manually restart the app every time (which for me is tedious because I run it headless) has annoyed me for a while. Now I can’t even get it to run.
(just a user here) I have a hunch that your Mac Mini is running the standard Roon app that can operate as a Roon Core as well, rather than RoonServer which is what you should be using for a headless Roon Core. That might explain some of the behavior you have described.
That error suggest that Roon is detecting a second core somewhere. As you are no dioubt aware you can only run one Core per license but you cab have any number of Core/Library set ups and switch between them.
You haven’t got a laptop with a core on it maybe.
I would try @Fernando_Pereira suggestion and use the Server option rather than the GUI version and see if that helps.
The other option is that there is some networking glitch between the Core and your Router , maybe try restating all you kit from scratch starting at the modem/router. Wait until the router has fully connected before restarting the Core PC
After a long trip I tried to use Roon again. I was stuck with it reporting that my server was running “Production1x” and my client (locally on the server and on my main laptop) was running Stable. Attempting to look for upgrades failed so I couldn’t run Roon at all.
So I installed client and server from the MacMini that acts as my Roon server.
Now when I try to install Roon server it tells me it can’t run because it requires the newer version of MacOS (10.15) than my Mac Mini (late 2012) will run (10.12.6).