I can login to ARC and it sees my Roon Core but when I connect to the core, it gets stuck on the Syncing with Core for the first time. I do this with my phone connected to my home's wifi. Roon settings page shows ARC to be ready, and it also shows with a green circle in Roon ARC. I also verified I can indeed connect to the ARC port from outside my home (using telnet).
Describe your network setup
I have NetGEAR Wifi Mesh setup as my router. My Roon core is connected with ethernet to one of the satellites. Roon operation itself is seamless and has no issues.
Thank you for your post. Diagnostics show that the session layer for ARC has lost authorization - we have work that will soon be released to prevent this sudden unauthorized condition from occurring, but I recommend reinstalling the app and attempting onboarding once more on your local WiFi.
Please also note that sync can take up to 5 minutes or more with a larger library. If sync failures continue to occur after re-authorizing the session, please let us know and we’ll investigate logs to learn more.
I did try uninstall/re-install over local wifi, but the problem continues. I realized after several minutes it drops out of the sync and goes back to the previous Roon Core selection page.
Rename the “RoonServer” folder to “RoonServer_old”
Restart the RoonServer in the WebUI to generate a new Roon database folder
On the Roon Remotes, press “Use another Roon Server” and connect to the new database
Before restoring your backup, see if you’re able to connect and sync with Arc, or if you run into the same issue. We’ll be monitoring for your reply. Thank you!
If the empty library syncs but the Backup still fails to sync with ARC, then there are two possibilities:
The first possibility is that the library size (specifically, the object count, not the actual storage volume) is too large for the framework to process.
To test this, let’s verify how if ARC every completes syncing. How long has it remained on “Syncing” so far? If it’s any longer than 10 minutes, this is an indication that the sync has already failed (it should only take about 5-10 minutes at the longest).
The next step here would be to disable Qobuz in Roon before reinstalling ARC, to see if a portion of the library can sync.
The second possibility here is that a specific Backup alone contains a corrupt piece of data that can’t sync with ARC. You can test this easily by attempting to restore a second Backup from another date, even just the day before/after.
We’ll watch for your response and take action accordingly. Thank you again.
My library was roughly around the same size and I could connect to it so not sure if this is size related. Also note that I have tried several times to reduce my library size in Roon but this fails as I reported here: Roon Slow; Deleted Qobuz Albums, but they get Re-Added
If there is an upper limit to the size of library Roon can handle, then it should just set a hard threshold for that and refuse adding anything beyond that. It’s just really annoying that any issue people report is blamed on library size (which usually isn’t, there is often a bug that gets fixed), while there is also currently no way of reducing the library size.
I am not going to do any further tests like this. It’s your job to fix it, so please do.
We completely understand your frustration. However, our intention with these diagnostic tests is simply to pinpoint the cause of the issue, so we can either restore functionality immediately or develop a fix as quickly as possible.
The theoretical maximum album size for Roon itself depends on a combination of processing power, storage capacity, and the structure of your library. This is also true for ARC, where cloud data transfer (Roon’s metadata services, Google, etc.) also plays a role. We’ve seen libraries larger than yours sync successfully on similar hardware, so this isn’t necessarily a hard limit. Instead, we’re focused on understanding why you’re encountering this specific syncing issue.
We know this is preventing you from using the app and we’re escalating accordingly. No problem if you don’t want to participate further - we’ll update you as soon as we have meaningful insights. When responding, we’d appreciate a quick confirmation on whether the symptoms persist or have changed.
