Thank you for your post. We’ve pulled additional logging to include the troubleshooting you’ve just performed.
We see request refusals (status code 403) returning from the KKBOX API, and other requests to Tidal and Qobuz fail or time out. At certain points, requests to Roon’s own metadata services fail because the RoonServer instance has no reliable path to the internet. All of these symptoms are intermittent. Among the failed requests to KKBOX’s API are the albums/tracks you’re missing in your screenshot and multiple login requests. Their servers aren’t allowing the requests to go through.
Do you have any antivirus security or VPNs on this computer? If so, test with those disabled. Ensure you’ve assigned a reliable DNS server in your router (we recommend Cloudflare, 1.1.1.1).
I would like to know where I can access the log information you mentioned, as well as what specific keywords in the log would indicate that KKBOX is rejecting requests—this would help me with debugging.
Also, how are you able to access or view my log information on your side?
For your reference, my Roon Server is installed on macOS. There is no antivirus software or VPN configured on the system.
Hi @stone07050,
Thanks for your questions — let me follow up on each one:
Your logs are stored locally on your server, and you can access them using the instructions found in this article.
If you search for status code: 403 in the logs, you’ll be able to spot the traces related to rejected requests. At the moment, I’m not seeing those 403 errors in your recent logs.
When we enable diagnostics on your account, your server automatically sends log data back to us, which allows us to take a closer look. This only happens after diagnostics are turned on from our end.
Lastly, were you able to test using Cloudflare (1.1.1.1) as your DNS server? As @connor mentioned, this can help with resolving connectivity issues to certain services like KKBOX. Let us know how that goes!
After changing the DNS to 1.1.1.1, I restarted the computer to avoid any issues related to DNS cache.
Then, I logged back into KKBOX, but the problem still seems to persist.
From what I see in the logs, most of the errors are related to the inability to find album metadata from Roon Labs.
Could it be an issue where the Roon database is missing some data?
Thanks for taking the time to run those tests. Debug traces related to metadata requests - whether they return 404 or unidentified - won’t prevent Roon from displaying an object entirely.
We see an exception after Roon attempts to match tracks from KKBOX storage (the collection of KKBOX object IDs stored in RoonServer for syncing) to the album requested from KKBOX’s servers. This isn’t normal behavior, and in the absence of any novel network setup, we need to escalate to development to ensure there’s not a broader underlying issue with KKBOX sync manifesting here.
Please stand by and we’ll respond as soon as possible with next steps, potential workarounds, and more information.
Thank you for your patience through the weekend. We’ve taken a closer look with our QA team and concluded this will most likely require a development fix on our end. Based on the available diagnostics, there’s an issue with Roon’s parsing of these particular KKBOX objects during synchronization.
We’ll follow up here as soon as we have an estimate of when this fix will be released - please feel free to ask any questions in the meantime. We’ll continue to investigate if there’s a workaround to force a proper sync in the meantime.