I’ve created a post twice using the support form but it never shows up in the topic list.
My Roon Rock is setup for auto updates but has been stuck on build 2.47 for a couple weeks. Every time it tries to download gets the “error checking for update” message. Here’s what I’ve tried:
Starting and restarting the NUC that Roon runs on
Started and restarted Roon Server
Started and restarted Roon OS
Reinstalling Roon OS - when I do it looks to start the process and then nothing happens, no updates.
I’ve checked all the support threads but haven’t seen anything similar. Appreciate any help.
Thank you for your message. Can you please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
Thank you for taking the time to update logs - this greatly expedites our investigation.
We see RoonServer contacting the update server and receiving a notification that the most recent update is available. However, the request to the download server to actually begin the download fails due to name resolution errors.
In most cases, you can resolve these issues by changing the DNS server in your router (or whichever network hardware unit is providing DNS here) to a reliable server like Google (8.8.8.8), Cloudflare (1.1.1.1) or QuadNine (9.9.9.9).
If you’ve already taken this step or it fails to resolve the issue, then please elaborate on the network pathway serving ROCK, particularly any managed hardware (switches, second routers) or network security components. We need to pinpoint why some URL requests from the ROCK are selectively failing to resolve.
We’ll watch for a response and work from there. Thank you!
I’m also using PiHole for ad blocking in my network which blocks connections to ad networks. I turned off the ad blocking and tried the update and still didn’t work. However I got this error message and I’m thinking it might be related to the problem. Also, are their specific URLs that you could share for updating? I could try white listing them on the PiHole. I should add that with the exception of the managed switch, my network set up has been the same for a long time and I’ve had no problems with Roon updates. There also doesn’t seem to be a problem with any Roon client updates.
I’ve whitelisted the URLs but still didn’t work. I also been able to disable the filtering so not entirely surprised.
Where or how would I whitelist those executables? Running on a NUC based dedicated Roon Server. I don’t have type of firewall or other blocking in place.
I’ve also never had this problem before. Everything has working great for a couple of years with updates.
Since you are running ROCK, you are correct, you wouldn’t be able to specify specific executables.
I tried to enable diagnostics for your account and I notice that the log requests are not coming through, even though the machine is showing as recently online.
This further suggests that something is blocking the ROCK from communicating properly with various Roon servers. Have you tried to temporarily completely disable PiHole and check to see if the behavior is the same?
Hi - yes I can easily disable Pihole which just pass all requests rather than filtering out the ad servers and other blacklisted sites. Behavior is still the same.
Also, my Roon Arc hasn’t been working for a while, with neither a regular connection back to my Rock nor with Tailscale. Was thinking might be a relationship between that and the update problem or even perhaps why you can’t retrieve diagnostic data from my device. Checked my router and port forwarding for Rock was off by 1 digit. Good news - seemed to solve my Arc problem, at least in a quick test. Bad news - didn’t solve the updating problem.
Also, I got a notification for Mac Remote and updated just be clicking the upload button in Mac client. Not sure if it’s related to the Roon Server upgrade problem but just an FYI.
Thanks for sending those over! We did see the error trace when your ROCK attempts to update.
The core issue is that the system cannot resolve the domain name to an IP address. It’s a DNS failure; Roon can’t begin the HTTP request because it doesn’t know where to send it.
A simple test, after you disabled PiHole, did you reboot your router? This should clear DNS caches and reconnect your system to the network cleanly.
Ok problem solved and I kinda feel like an idiot here.
Went to the Rock WebUI to restart the server again and happened to look at the network settings below. I use a static IP address and realized that the DNS in those settings was incorrect. I recently upgraded to a new Raspberry Pi for Pihole but hadn’t changed the DNS in the network settings to point that new server. All makes sense now.
try to logout from Tailscale first, the perform a RoonOS reinstall. this worked for me. RoonOS performed the update to the most recent version. you may login to Tailscale after the update. to reboot the machine after update completion might also be helpful.
