· ROCK Update Error: “There was an error checking for an update” on NUC8i7 after the recent 2.60 update My end points and Roon bridge appliances all did update but the server did not. Because of this I cannot play any music on the endpoints that were updated although I can still use them as remote. My Roon Bridge appliances can not be enabled. Note that I did reboot my router and my NUC running ROCK but no change. Help!
Try using the Web Administration Interface of your ROCK/NUC and choose “Reinstall” of the Operating System. The reinstallation will preserve your database and settings.
My internet connection is working fine and I can play music from Roon to my Devialet Expert Pro via RAAT. Just can’t update Roon Server on my NUC from v 2.58. Just FYI… the error popped up very quickly. Like the failed update, it seems it just can’t find what it needs to download.
Of course I can’t rule out that this is somehow related to Roon’s cloud issues, but on the other hand they seem resolved at least for other aspects.
The exit code 10 happened a few times before, and in these past cases it was network related and resolved by one of or a combination of these:
Rebooting the router and then, once the router is back up, the ROCK.
Configuring the router to use a known good DNS server (e.g., Google DNS, Cloudflare).
In one case, setting a static IP on the ROCK (probably suggesting that there had been some kind of local IP assignment problem, so I guess this doesn’t apply to you)
Hmm, OK looks like you already did all this. Maybe grasping at straws, but are you sure you can add two DNS servers with comma separation into the DNS Server field? The documentation doesn’t say either way but only shows screenshots with one IP.
Other than that, I’m out of ideas. Over to the support team…
I would not be unusual to have comma separated lists of IPs, so I wouldn’t be surprised if it’s just fine. I suppose if it prevented DNS from working, then nothing would have ever worked at all. I was just grasping at straws after all
Though one would wish that the documentation would be more explicit about it.
I would love to know if the problem was something you guys resolved or if it was something to do with my network (of course, never seen this before until now and I’ve been using Roon since 2015). @alex_h - @Suedkiez raised a good question… I use a static IP and had 1.1.1.1, 8.8.8.8 in the DNS entry. Any reason to think that might not work? I would think for a static IP, you’d want to be able to specific a secondary DNS address since I don’t believe static configs will fall back to the router configuration if there is a DNS failure. Just wondering if that is documented somewhere. Thanks!
As suspected, we experienced some infrastructure instability recently, which is the most likely culprit for the update failures and the inability to reinstall (causing the “Exit Code 10”).
However, regarding your network configuration, I wanted to add a note about DNS:
It is generally not best practice to mix DNS servers from different providers (e.g., using Cloudflare’s DNS for the primary and Google for the secondary). This can lead to inconsistent resolution behavior, which can stall updates.
We strongly recommend setting your Router (or ROCK’s network settings) to use exclusively one reliable provider:
Google:8.8.8.8 and 8.8.4.4
OR Cloudflare:1.1.1.1 and 1.0.0.1
Please update your DNS settings to use just one of these sets, reboot the ROCK.
@vadim - great to know about using the same provider when specifying DNS on a static config. I had not heard that before but it makes sense. I’ll update my DNS settings accordingly. And thanks for letting me know that the issue I was having was likely due to some infrastructure instability.
Using a single DNS provider ensures that if a record is cached or resolved differently between providers, your device doesn’t get conflicting information.
I’m glad we could clarify that for you. I’ll go ahead and close this topic now.
