· Roon app shows only “Ready to switch?” with no continue/switch/confirm button.
This happens on both the macOS Roon app and the iPhone Roon app.
I use one Roon account in two different locations: office and studio. Each location has a different Roon Server.
My office system is currently working normally with the same Roon account. I can use Roon and play music there without any issue.
The problem only happens when trying to connect to the studio system / Roon Optimized Core Kit / ROCK at 192.168.1.12.
Roon Server at the studio: - Roon Optimized Core Kit / ROCK - IP: 192.168.1.12 - RoonOS: 2.1 build 271 - Roon Server: 2.67 build 1661 - Status: Ready / OK
The Roon Server web UI shows: - Operating System: OK - Roon Server Software: OK - Roon Database & Settings: OK
Client: - macOS 26.5.1 - Roon app reinstalled - Local RoonGoer and RoonServer folders renamed - Mac-side RoonServer stopped - Same issue occurs on iPhone Roon app
Studio audio setup: - SOtM Eunhasu: V0.6.4 - SOtM mode: Roon is active - USB DAC connected to SOtM: SOULNOTE D-2 Ver.2
Issue: After clicking Connect to the studio Roon Optimized Core Kit, the app shows only:
“Ready to switch?”
There is no continue, switch, unauthorize, or confirm button.
SOtM Support replied that a similar issue has not been reported to them before. They also suggested that this should be reported directly to the Roon team, and they will ask Roon for further support as well.
A Roon Community moderator also suggested that this looks like a Roon issue related to the new process to transfer a license between Roon Servers, and not related to SOtM.
This seems to be related to Roon Server authorization / switching between two different Roon Servers, because the office Roon Server works normally with the same account, but switching to the studio ROCK gets stuck on the “Ready to switch?” screen.
Related Roon Community thread: https://community.roonlabs.com/t/roon-shows-only-ready-to-switch-with-no-continue-button/321914/2
Tell us about your home network
· Studio network:
- Roon Server / ROCK is connected by Ethernet. - Roon Server IP: 192.168.1.12 - Gateway / router IP: 192.168.1.1 - The macOS Roon app and iPhone Roon app are on the same local network. - The ROCK web UI is reachable from the browser. - The ROCK web UI shows Roon Server Software OK and Database OK. - No VPN is used for this connection. - The issue happens before selecting any audio output device. - The Roon app can see the studio ROCK server, but after clicking Connect it gets stuck on “Ready to switch?” with no button.
Thank you for the detailed report. We have escalated this to our R&D team for investigation.
In the meantime, to get you back up and running, you can reset the ROCK database with the following steps:
Stop RoonServer from the [url=https://kb.roonlabs.com/Nucleus_Web_Administration_Interface]ROCK Web UI[/url]
Navigate to your [url=https://kb.roonlabs.com/Database_Location]ROCK's Database Location[/url]
Find the folder named "RoonServer" and rename it to "RoonServer_old"
Restart RoonServer from the Web UI to generate a fresh database
On your Roon remote, tap "Go back" and connect to the new database
If you have a previous backup from this ROCK or from another server, you can restore it at step 4 instead of starting fresh - just choose to restore from backup when prompted.
Please let us know if you need help with any of these steps!
Thank you for your reply and for escalating this to your R&D team.
I understand the suggested steps:
stop RoonServer from the ROCK Web UI
rename the “RoonServer” folder to “RoonServer_old”
restart RoonServer
then try connecting to the new database
I am not near the studio system today, so I will try this tomorrow when I am on-site.
Before doing this, I will confirm that I have a valid Roon backup available.
Just to confirm: is this procedure mainly intended as a diagnostic / recovery step to rule out a corrupted local RoonServer database or authorization state?
If the new database resolves the “Ready to switch?” issue, should I then restore from my previous backup, or should I first report the result before restoring?
Yes, please let us know how the process goes. If the new database resolves the issue, you can restore from the backup and keep using the install after that, assuming there are no issues. We’ll keep you posted on when we hear back from R&D (most likley sometime next week) and please let us know once you’ve had a chance to try the reinstall.
renamed the existing “RoonServer” folder to “RoonServer_old”
started RoonServer again to create a fresh database
connected to the ROCK successfully
restored my previous backup
After creating the fresh database, the “Ready to switch?” screen displayed the correct “Switch to Roon Optimized Core Kit” button. I was then able to switch the license to the studio ROCK successfully.
After restoring the backup, I also restarted/activated Roon Ready on the SOtM Eunhasu side, and Roon now sees the endpoint as “SOtM → SOULNOTE D-2”. Playback is working normally now.
So the problem appears to have been related to the previous RoonServer database / authorization state.
We’re reopening this ticket because we wanted to inform you that we’ve identified the underlying cause.
There is now a ticket in the development pipeline to prevent this stale “Ready to Switch” condition from recurring. We’ll track this work in this topic thread so we can inform you when it’s been included in an Early Access release and subsequent Production release of Roon.
Thank you for your patience and for confirming. We will close this thread for now - please keep an eye on the Software Release Notes for updates when the fix is included in an upcoming release.
This ticket is progressing through the pipeline, and while it wasn’t included in the latest update, we expect an upcoming update to resolve this problem.
We don’t have a precise timeline but we’ll share that information here as soon as it’s available. Thank you again for your patience.
Thank you for confirming that the workaround has things working again. We’re glad to hear you can keep using it for now. We appreciate your patience as the proper fix makes its way through the development queue.
Development is testing/finalizing the fix; I don’t have an exact timeline to release yet and can’t guarantee it will be included in the next EA build, but we’ll be sure to ping you here once we have confirmation. Thanks again.
