· I transferred 4TB of music from my old server (Rhein Z1Plus) which was deauthorized to the new server (Antipodes S4) which was authorized. After transfering Roon was working fine. After checking Roon was working I restored the Roonsettings from a backup of the old server, now Roon does no longer recognize my new server and connects to the old server which no longer exists with a trial account. It took 24 hours to transfer the library to my new server (an Antipodes S40). How do I authorize the new server and get rid of the virtual old server? I never expected this to happen, in the documentation Roon explains the settings ar for metadata etc. and not connectected to a specific server
Tell us about your home network
· Nothing wrong with the network, all is working fine, this is a Roon software problem
· I changed to a new server,when I login with the correct credentials I am logged in as a free trial user. I have a subscription but it cannot be used probably to login on my new server. There is one other server on my mac but I do not use it and I cannot delete it.
Do you see an Unauthorize button when you try to connect to the new server? Click it, which will remove the license from whatever Roon thinks to have been the previous server, and then you can select the new one.
You can stop it from running. Click its icon in the notification area on the Mac, unselect Launch at startup? and then click Quit
Thank you for the detailed explanation — I can see why this behavior was unexpected, so let me clarify what’s happening and how to get things back on track.
How Roon stores settings and metadata
Roon settings, metadata, and library information are stored inside the database on the Roon Server, and that database is associated with a specific Roon account. When you restore a backup, you’re restoring the entire server identity as it existed at the time of that backup — not just metadata.
Because of this, after a restore:
The server may present itself with the same identity and name as the old server
Roon Remotes may appear to “reconnect” to what looks like the old server, even though it’s now running on new hardware
Important question to confirm
After restoring the backup, are you logging in with the exact same Roon account that was used on the original Rhein Z1Plus?
If a different account is used, Roon will treat the restored server as a new, unlicensed server, which explains why it appears as a trial.
About the Mac server you’re seeing
The Roon Server instance on your Mac does not affect the Antipodes server in any way. It’s completely independent and can simply be stopped or ignored — it will not interfere with licensing or server selection on your network.
What to try next
Fully power off the old server (Rhein Z1Plus), if it is still present anywhere on the network
Launch Roon and make sure you are logged in using the same Roon account that owns the subscription
When prompted to select a server, choose the Antipodes S40
If you see an “Unauthorize” option, use it — this will free the license and allow it to attach to the correct server
Once logged in with the correct account, the restored server should correctly attach to your existing subscription.
We’ve not seen a response to this thread and diagnostics indicate that your Roon Server machine hasn’t pinged our servers since before you posted. Please let us know if we can clarify any of the suggestions @vadim shared above. We’ll watch for your reply. Thanks!
