Roon Server on QNAP TS‑264 stopped working after update (build 1643/1653)

Audio Gear Talk HQ Player
1

Hi,
I would like to report an issue with Roon Server on my QNAP NAS.

Device: QNAP TS‑264
System: QTS 5.x
Roon Server version before update: 2.64 (build 1646)
Update offered: 2.65 (build 1653)
Result: Roon Server stops working immediately after the update.

After installing the latest Roon Server update, the application no longer starts on QNAP.
The App Center shows Status: Stopped, and restarting the NAS does not help.

The only way to restore functionality was to roll back the entire NAS to a previous snapshot.
After rollback, Roon Server 2.64 works normally again.

It seems that the new Roon Server build requires system libraries (GLIBCXX_3.4.21+) that are not available on QTS 5.x.
Please confirm if this is a known compatibility issue and whether a fix is planned for QNAP users.

Thank you.

1 Like
2
3

This was announced, as a general incompatibility between all currently available QTS versions, and Roon 2.65.

You have basically 2 options:

  • Stick with the last build of Roon 2.64 (B1646) and supress/refuse all updates in future
  • Run Roon 2.65 in a docker container, i.e. create your customized docker image and install it via Container Station on QNAP

I have a similarly powerful QNAP NAS and can confirm, the latter variant works well. It just requires some understanding how docker works, a strategy which folders you want to share, and troubleshooting regarding share/paths.

Article on Docker

4

Some warning to users would have been nice. I have a paid lifetime Roon account, but got no warning that Roon would stop working if I updated it. Container Station does not work on my QNAP. How to I restore functionality?

5

There was a notice on the forum at the start of the month plus a piece in the April newletter. Affected devices also had an in-app notification.

There is no alternative installer for your NAS. You should use the Docker image. The TS-264 is fully compatible with Container Station. What NAS are you using?

6

I just looked and the announcement was buried at the end of the newsletter, after a series of advertisement which I did not read (as might have been anticipated). I believe such an announcement needs to be before the ads, with special attention drawn to it, rather than buried where most of us will never see it.

My NAS is a QNAP TS-453Be. I got Container Station working by deleting it and its folders and reinstalling, and was able to get Roon running on it.

2 Likes
7

“Affected devices also had an in-app notification.” I did not see any notification.

8

Good to hear you’re running now. If you want Roon to hear about the [lack of] notification, please post in Feedback since Roon do not monitor this category.

9

The same has happened to me on my Qnap TVS-x72XT giving it a few days to see if I can get it up and running if not will not renew my subscription at the end of the month. Luckily for me I have been using more and more of the connect options ie Tidal connect etc and using more physical media. Overall not a happy customer.

10

As already pointed out, Roon staff do not read the Roon Software Discussion category, so you should post in Feedback if you want them to here your voice.

11

David, I think that giving it a few days won’t help. Roon’s update means that it won’t run again. But Roon Server can be installed in Container Station on your QNAP. There are instructions are here and in some other places:

It was easier than it sounds (although a QNAP glitch required me to delete and reinstall Container Station once), and only took a fairly short time. I agree though, the fact that Roon made a software installer that installs onto incompatible hardware, irreversibly, and with little effort to warn people, doesn’t fill me with confidence.

1 Like