· This isn't just an ARC issue but a slew of them. Basically: I wanted to move my core from one computer on my network to another. managed to do that, but the old server must have created an artifact that I cannot remove. I even resurrected (and renewed my subscription) on a second Roon account that I had been using to test Qobuz vs. TIDAL—same issue. in a nutshell: no matter which Roon account I use, I "see" servers but they are advertised under different names (my phone shows "Mac Media," which is the name of a server I had on a Mac that I completely erased), even though the IP addresses are the same. The name of the computer actually hosting my server is not actually advertised at all. Roon works locally from there; doesn't work on remotes—usually it will ofer me two versions of the same server with teh same name but a hyphen between words, and neither will stay connected. Have removed files from the ~Library folders on my Mac, reinstalled app, tried different accounts (as I said)—nothing works. Help?
Tell us about your home network
· Eero 6+, four APs, all with ethernet backhaul. no issues. used to work flawlessly!
Thanks for taking the time to write in and share your report!
Before anything else, each time you run into this issue on a new Roon Server instance, are you restoring from a saved Roon backup?
If so, its likely the prior server name is imported onto your new machine. You can easily chance this name by accessing your Roon Settings> Setup > Roon Server name.
With that, since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.
Please try the following steps:
Open macOS System Settings → Privacy & Security → Local Network
Make sure Roon and Roon Server are both enabled
Even if they are already enabled, please toggle them off and back on
Fully quit Roon Server from the macOS menu bar / task bar
Reboot your Mac
After reboot, launch Roon again and check if the devices is avaliable again.
Once these permissions are refreshed and the system restarted, your devices should reappear.
Please let us know if the issue persists after these steps, and we’ll continue from there.
benjamin: thanks for the tip. unfortunately, it didn’t work–something else seems to be afoot. for what it’s worth, I didn’t restore from a backup when I started this time; I literally signed out of my account entirely and signed into a different Roon account hoping to start fresh. no such luck. any other ideas?
I can start the server, things appear to be fine, none of it is visible to my endpoints or ARC. When I try to enable ARC I do get diagnostic info that seems to be suggesting there’s a UPnP problem with my router (which would explain ARC issues, but maybe not endpoint problems (not sure about that), but UPnP has always been on and used to be no problem at all.
If it’s helpful, the server issue does seem to be resolved in this state. it’s running, and will play to my system outputs, but only those.
You are correct here - the ARC error code will be separate from any endpoint related issues. Feel free to copy and paste the specific error code here.
For your endpoints - can you confirm they’re all on the same local subnet? From a fresh diagnostic report, it looks like you may have a few active subnets within your local network.
For example, your server could be on the IP scheme: 192.168.7.yyy
While your endpoints could be on: 192.168.4.zzz
You’ll want all your Roon devices to fall on the same subnet for proper playback. Let me know if this makes sense and if you need additional help here.
I actually wound up wiping that computer entirely–the nuclear option. i’m going to start again fresh. is there anything I need to know about removing old server instances from my account before I rebuild?
You’ll need to ensure you fully delete the server itself, rather than just the GUI. This will erase your Roon library and play history, along with any customizations you’ve made in Settings. It will also erase your MUSE settings, including custom DSP and any Zone settings you’ve changed in Device Setup. Restoring a Backup would, of course, restore these settings as they were when the Backup was created.
A full refresh is identical to the steps @vadim shared above, except you’ll target and delete the RoonServer folder rather than the Roon folder.
Exit out of RoonServer/Roon
Navigate to your Roon [url=https://kb.roonlabs.com/Database_Location]Database Location[/url]
Find the folder that says “RoonServer” and delete it
Reinstall the Roon App from our [url=https://roonlabs.com/downloads]Downloads Page[/url] to generate a new RoonServer instance
Verify if the issue persists on a fresh database before restoring a Backup as desired
Thanks @connor. Like I said: I wiped the whole machine. Sold it, actually, which is just a weird coincidence. When I start again am I going to be able to start fresh or will there somehow be a server stil linked to my account on the Roon side? I’m worried that logging in with my account will somehow trigger that I alreay have one linked to me.
To answer your question directly: your Roon account does still remember the old server, but none of the old data, settings, or names will transfer over to your new setup.
A standard Roon license allows for one active server at a time, so our cloud systems just keep track of which machine is currently authorized. Here is what will happen when you set up your new computer:
When you install Roon and log in, the app will notice that your license is still assigned to the old machine.
Roon will display a screen showing your previous server with an Unauthorize button next to it.
Simply click Unauthorize.
This will immediately detach the old server from your account and assign your license to the new machine. It’s just a quick administrative step on our end.
Would you like us to keep this thread open for a few days so you can let us know how the new installation goes?
