Roon on QNAP no longer showing up on my network

[Sevenfeet]

I recently updated Roon on my QNAP TVS-h1688x to the latest early access build (a routine update I’ve done countless times) but now all Roon clients (Mac, iOS/iPadOS) on my network can no longer find the server. The RoonOnNas.log.txt file seems routine with no errors. Listed are the first lines of the log file.

22.03.26-21:34:03 — Starting RoonServer …
22.03.26-21:34:03 — ROON_DATABASE_DIR: /share/RoonServer/RoonOnNAS - [available]
22.03.26-21:34:03 — ROON_DATABASE_DIR_FS: zfs
22.03.26-21:34:03 — ROON_ID_DIR: /share/ZFS530_DATA/.qpkg/RoonServer/id - [available]
22.03.26-21:34:03 — Free Inodes: 800.3M
22.03.26-21:34:03 — ROON_DIR: /share/ZFS530_DATA/.qpkg/RoonServer
22.03.26-21:34:03 — Model: TVS-h1688X
22.03.26-21:34:03 — QNAP Serial: Q213I06993T
22.03.26-21:34:03 — Architecture: x86_64
22.03.26-21:34:03 — Total Memory: 98733068
22.03.26-21:34:03 — Available Memory: 43986384
22.03.26-21:34:03 — QTS Version: 5.2.9 - Build: 20260214
22.03.26-21:34:03 — PKG Version: 2023-03-07

The last version the RoonServer_log.txt talks about the update being successful (2.62 build 1642 earlyaccess) to (2.63 build 1643 early access), but this is the last version of the file to be written back on 3/19 when the update happened. No log files have been written since.

Any ideas on what to troubleshoot here?

[BlackJack]

Move away from Early Access to Production release please.
You can (currently) not run new .NET10 based Roon Server on a NAS (missing components). See also:

[Ticket In] B1643: Roon Server on QNAP stopped starting up after update

Immediately after update to B1643 Roon Server stopped starting up. Several restarts of QNAP RoonOnNas app and whole NAS didn’t help. QNAP app reports: Status : Stopped Version : 2.63 (build 1643) earlyaccess

[Ticket in] B1643 Will not run on NAS (Synology DS918)

Not sure if this is the right place, but I run the Early Access builds and the latest update (build 1643) won’t run. Not complaining, I chose to run the Early Access and this is the first time something like this has happened in almost 2 years. Anyway, the roon log file doesn’t appear to have anything in it except the device and build information. Curious if anyone else is having issues and if there’s some instructions somewhere on rolling back.

And from there:

[Ticket in] B1643 Will not run on NAS (Synology DS918)

Hi, @Eric_Lynch, @Ricardo_Ramos, we sent a ticket to our dev team, they are looking into this problem. Hopefully, we’ll have a solution soon. As workaround, I can suggest moving your servers back to production by following this article. Thanks! – Ivan

[Sevenfeet]

Thanks for the prompt reply. Oh well, I guess it’s back to Production until this is worked out. Now I have to figure out how to download the production version again…

[Suedkiez (Just a fellow user like you)]

@Sevenfeet

Now I have to figure out how to download the production version again…

Same as switching to EA, get the production version from here

Roon on NAS

Compare

Roon Early Access Program

[Sevenfeet]

OK, I downloaded the production version from Roon on NAS (RoonServer_2023-03-07x86_64.qkpg) and did a manual install. RoonServer still has its status as stopped and still indicating the EarlyAccess 2.6.3 version. So I’m clearly doing something wrong. Any ideas?

[Suedkiez (Just a fellow user like you)]

Someone a QNAP will show up to help

[Arindal]

@Sevenfeet

So I’m clearly doing something wrong. Any ideas?

Do a full deinstall of roon server app on the QNAP, and subsequently install the roon server app from QNAP´s designated App Center > Entertainment. That is for sure production version. Make sure, automatic update for all devices including all remotes, is deactivated. I remember my Mac on which I run roon as the main remote, was still running EA, so tried to force EA update on the QNAP with production app as well.

[Sevenfeet]

Sorry for not following up but uninstalling and reinstalling the app was pretty straightforward and the reinstalled app found the old database and outside of having to resync Tidal, everything worked immediately.

I guess now we have to wait for the for the Docker version of Roon.