Roon Server stopped on NAS after update to build 1653 (ref#SFRJML)

Support
1

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

· Roon stopped working on my NAS server, Roon Server
Status : Stopped Version : 2.65 (build 1653) production QPKG-Version : 2023-03-07

Tell us about your home network

· Cisco

2

Hello @Dariusz_Znamirowski and welcome to the forum.-

The Roon Server package no longer works, please switch to the official Docker image to run Roon Server on your NAS. See also:

3

Hello @Dariusz_Znamirowski , and welcome to the Roon community!

Thank you for reaching out. A big thanks to BlackJack for stepping in quickly with the correct information!

As mentioned above, the recent Roon update introduced new minimum system requirements. Because the native QNAP operating system relies on older software libraries that Roon can no longer support, the standard Roon Server package will no longer run and shows as “Stopped.”

To get your system back up and running, you will need to transition your Roon Server to our new, official Docker-based installation. Docker allows Roon to run in an isolated environment with all the modern libraries it requires, ensuring stability and performance on your NAS.

Here is our step-by-step guide to walk you through the migration process: Installing RoonServer on QNAP with Docker

A quick tip for your migration: You do not have to start from scratch! Before setting up the Docker container, make sure you know where your previous Roon backups are stored on your NAS. Once the new Docker container is up and running, simply click the “Restore from backup” link on the initial Roon login screen to bring back all your playlists, metadata, and settings exactly as they were.

Please take a look at the guide, and let us know if you have any questions or run into any trouble during the setup. We are here to help!