Authorize and Unauthorize

Roon Core Machine

Windows 11 with 64GB and 2TB SSD (two identical machines)

Networking Gear & Setup Details

Cat.6 on Fritzbox, only ethernet, no VPN

Connected Audio Devices

Merging Nadac + Marantz NA6006 via Airplay + Merging Anubis

Number of Tracks in Library

20,036 tracks

Description of Issue

Hi. I have a question about “authorizing and unauthorizing” my core.

Having a license for only one core, I have to authorize each time the computer I use and “un-authorize” the one that is off.

Every time I do this, I get this error message about the core I authorize after “un-authorizing” the one I don’t use.

This error does not affect listening but simply the metadata and any albums added with the other core, are not updated. I have to close manually “roon server” and start it again, and the problem disappear. Can it be solved?

Thanks for your help!

You may have set up both your Windows 11 PCs to have a Roon Core present. I suggest that if this is the case, you decide which PC you want to have running the Core, and disconnect the Core running on the other PC (go to Settings > General and disconnect the Core that you want to remove).

Thank you Geoff.
But I have two PCs with two cores, one in my house in the city and one in the country house at 300km :smiley:
The problem arises precisely when I de-authorize one to listen to the other.

If you are switching regularly between two cores, this is common. You have to authorize the new core, then restart/reboot to enable the metadata service. Just continue following those steps. I would not count on that changing.

AJ

1 Like

Thank you too. But I have a friend who has the same situation but the two cores are on linux machines and this doesn’t happen to him. Maybe the problem is just in windows?

No, it can occur between two ROCK (RoonOS Linux) machines as well.

AJ

1 Like

Yep. We have two NUCs running ROCK, one at home and the other at our weekend apartment, and I have to restart the server software pretty much every time I authorise a different core.

Michael

1 Like

Oh thank you all. I hope the developers can fix this problem, without forcing to restart the server every time.

I have not had to do this when I have switched cores, one, rock one Linux. Admittedly I don’t do it often but I have never had to restart the server when doing so.

Yes. My friend, who has two cores on linux, confirms that he has no problem after the swap.
It really seems to only happen on core windows.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.