Unable to update ROCK to 2.67 build 1661 on NUC (ref#8EPDS9)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· I’m stuck on 2.67 (build 1661)
I keep getting an error when trying to update ROCK trough ROON Windows
I tried different browsers
I tried reinstalling OS in web interface, which btw doesn’t reinstall
I tried restarting server

Running ROCK on a NUC with only ROCK installed

Tell us about your home network

· Everything is working fine, never had any trouble updating before.
Fiber in
Asus RT-AX86U router
Standard TP-Link non config Switch
No VPN
I have ADGUARD home, but tried disabling it as well
Have a Samsung Galaxybook 360 pro
so it is INTEL NIC

Hello @marz_adam

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!

I think I found it, uploading log files from Windows local :slight_smile:

Hey @marz_adam,

Our apologies for the confusion, we’re actually interested in the ROCK Roon Server logs, which you can still use the windows machine to gather.

  1. Using a Windows machine, open File Explorer and navigate to \ROCK\Data and use Guest as the username and password. You should then see the RoonServer folder.

Within the Roon Server folder, Find the folder called Logs

  1. This folder generally contains Roon_log.txt , Roon_log.01.txt, ect. or RoonServer_log.txt, RoonServer_log.01.txt, ect. (if making use of RoonServer)

  2. Zip up the entire Logs folder

    1. On macOS: Right Click -> choose Compress Logs
    2. On Windows, Right Click -> choose Send To -> Compressed Zipped Folder

Thank you!

Okay Benjamin, I have uploaded logs from **\\**rock\data\RoonServer, it’s a double dash to start..
And it just went straight in, without login…?

Hello @marz_adam

First, to reassure you: you did nothing wrong. \\rock\data\RoonServer with two backslashes is correct, and going straight in without a login prompt is expected. That share allows guest access, so Windows connects without asking. There is nothing to fix there.

The problem on our side is that we cannot find either of your uploads, the first one or the one from yesterday. So rather than have you wonder whether they arrived, please send them once more with a filename we can search for:

  1. Please name the zip file marz_adam-8EPDS9.zip, using your community name and the reference from this thread.
  2. Upload it to the File Uploader.
  3. Reply here with the exact time you uploaded it and your time zone, and the filename you used.

That gives us something to match against rather than searching by guesswork.

In parallel, there is something more likely to be the actual cause, and it is worth testing now rather than waiting on logs.

You mentioned you run AdGuard Home. That matters more than it might seem. Your ROCK gets its DNS server from your router, and if that points at AdGuard Home, then AdGuard is what your ROCK uses to look up our update servers. Turning AdGuard off does not remove it from the ROCK’s configuration, it just means the ROCK’s DNS server has stopped answering, so name lookups fail completely rather than being filtered. Either way, the ROCK cannot reach the update service, and that produces exactly what you are seeing: everything else on your network works because your other devices fall back or use different settings, while the ROCK does not.

So please do this:

  1. Open your Asus RT-AX86U settings and look at the DNS server it hands out under LAN, then DHCP Server. Please tell us what is listed there.
  2. Temporarily change it to 1.1.1.1 and 8.8.8.8, save, then reboot the ROCK so it picks up the new setting. A reboot is necessary; it will not take effect otherwise.
  3. Open the ROCK web interface and try the update again.

If it updates, we have our answer and you can then decide how to configure AdGuard so it does not block our update service.

One more thing we need. You said the OS reinstall in the web interface does not actually reinstall. Please run it once more and tell us exactly what it reports, including any status text or number such as exit code 43. That message is specific and tells us whether the reinstall is failing for the same reason or a different one.

Uploaded the file again “marz_adam-8EPDS9.zip” 14.10 Denmark, aug 19 2026

Tried changing DNS, didn’t do it. I have had AdGuard for quite some time, before that PiHole, never had a problem updating ROCK.

When I Press the update button, it shows the Update/Reinstall dialog, I press ok it flashes a prompt with the animation for a second than just closes, nothing else happens, no reports, nothing.

Hello @marz_adam

The upload arrived this time, thank you. The logs are clear.

The update has never started. Your ROCK stayed on 2.67 build 1661 for the whole nine days the logs cover. The check works and returns build 1683 every time, but the download then fails immediately, 24 times, always the same way:

While downloading update: System.Net.WebException:
Name or service not known (download.roonlabs.net:80)

That is a DNS failure. The ROCK could not turn that hostname into an address, so nothing was ever downloaded.

Those 24 are the only lookup failures in the entire log set. Everything else resolves without a miss, including updates.roonlabs.net on the same domain and api.roonlabs.net across 45,000 requests. A broken DNS server would break all of them. One name failing while the rest work means that name is being blocked.

Blocklists refresh themselves, so a name that was never touched before can start being blocked without you changing anything. That fits your point about running AdGuard for years with no trouble.

Why your DNS change had no effect. While the ROCK is on DHCP it takes DNS from your router and there is no way to override it on the ROCK itself. Your RT-AX86U also has DNS Director, called DNS Filter on older firmware, under LAN. When enabled it forces every client onto the DNS server named there and ignores what DHCP handed out. Please check whether it is on and what it points to.

Two things to do.

First, please open the AdGuard Home query log and search for download.roonlabs.net. That shows whether your ROCK asked for it and what AdGuard answered, including which filter blocked it. One screen settles this.

Second, please give the ROCK a static IP so it uses a DNS server of its own choosing:

  1. Open the ROCK web interface and go to the Networking section.
  2. Switch from DHCP to static, entering the ROCK’s current IP address, subnet mask and gateway. Your router’s DHCP lease list has these.
  3. Set the DNS servers to 1.1.1.1 and 1.0.0.1.
  4. Save, then stop Roon Server and reboot the ROCK.
  5. Try the update again.

The permanent fix, once confirmed. In AdGuard Home, under Filters then Custom filtering rules, please add:

@@||roonlabs.net^

That allows our domain whatever any blocklist says, and it is better than turning AdGuard off. You can then put the ROCK back on DHCP if you prefer.

If the query log shows AdGuard was never asked for that name, please tell us, because then the lookups are going somewhere else and we need to find where.

For me it was enough to change DNS server to 1.1.1.1 in ROCK web interface, Static IP was already enabled. a Quick Reboot and all was set and ROCK updated like a charm.

Thanks for the help :slight_smile: