What kind of performance/speed issue are you experiencing?
· Can't connect to search or search takes a long time to complete
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
Timestamp of issue occurrences
· Oct. 31st, 2025 at 3:30PM.
Describe the issue
Sometime between either the update to 1582 or 1583 Roon stopped connecting to Tidal and is extremely slow to load anything server side, search stopped working and doesn't display artist info or metadata. It became and local-only offline player (albeit a very expensive one at that). Trying to reconnect Tidal works authenticating but Roon never leaves the "Waiting for Tidal Login" dialog. Even Settings > About times out while checking for updates and goes "There was an error checking for an update".
Describe your network setup
Fiber optic router, cat6 cabled to a passive switch, cat6 cabled to the ROCK machine. Nothing changed on the network config or setup side.
Please try to log out of TIDAL in Roon and then log back in. After doing so, try to reproduce the issue once more.
When the problem occurs again, please take a screenshot of what you see on your screen and note the exact timestamp (date and time) when it happens.
Once you have this information, please share it here so we can check our server logs for further details.
This happened every single time I tried for a few days now, the latest right now at Nov. 3rd, 8:05am.
I do firmly believe this is just a side effect of the problem. I noticed that while Qobuz is still connected, I cannot play anything via streaming, only files stored locally.
To recap: nothing changed in my network physical or config setup, I can still access Rock’s storage perfectly fine, such as to add a few albums bought last friday. And to go to \ROCK\data\reinstall to place roon-production.bin in order to reinstall into production edition to see if it solves it. It didn’t. Search doesn’t work. Streaming doesn’t work (even with Qobuz, apparently still linked). Can’t link Tidal. Live portions of the home screen doesn’t refresh anymore (Roon mixes and such). Settings > About times out while looking for an update.
The only variable between Roon working and my current state was a dreadful 1583 update.
I just had to: re-download ROCK again, balena-flash to a usb drive again, re-install it, then “software” reinstall it for the server to update, put ffmpeg on ./Codecs, reconnect using a remote, restore yesterday’s backup (good thing I have a daily schedule backup routine set to an attached drive), de-authorize the old now non-existent ROCK, and wait for the remotes to refresh.
Everything’s back to normal, Tidal now links again, search works, live home screen is back, update dialog doesn’t time out. All it took was a few days of irritation plus some hours today I’d rather had spent listening to music.
Roon is unbelievably ungracious when it comes to restoring itself from any sort of crash or unexpected condition. If there’s a power outage, after powering back on it always needs to have the server software restarted so the remotes can access the library (it comes back with crazy uptimes of 250000 hours or something). Every now and then you have to restore a backup for it to work, plus now this early access 1583 update completely borked the install so bad I had to re-flash it. Incredible.
Every June when it’s time to refresh the annual subscription I make a pro/cons list of… should I get lifetime? And stuff like this ALWAYS drags me down to a resounding naaah. Seriously, guys.
