As mentioned before, I tried to play some music using my iPad as my Roon interface. My player is a Devialet 140, I have Roon Server installed on a dedicated solid state disk in my QNAP TS-453 a, set up which up until now functioned quite OK. When opening the iOS Roon App, I was informed that there were updates available for one or more devices. I hit :"Udate all". I waited patiently and tried again. The message "Waiting for your Roon Server still appeared. I checked all wired connections, they appear to be OK.
Then I decided to check in the app center of my QNAP to see if Roon was running at all. It looked that way but when I opened the Roon application it indicated (in red) that Roon was stopped. This certainly was not my doing, at least I never instructed the application to stop running. I restarted the aplication. Nothing changed. Same message. Roon had been, or was stopped.
Then I rebooted my QNAP. Nothing changed. I tried to get the latest build of Roon Server via the app on my QNAP. It looked like it downloaded, seemed to be running, but I still only find that "Roon server was stopped". This error seems to persist. I am not a computer man at all, so by now I have run out of options I think....
Reinstalling Roon Server with Docker (?) looks very terrifying to me..... The terminolgy used sends shivers down my spine..... Could you help me out?
Tell us about your home network
· I use a Fritzbox 4040 router/switch, my QNAP is connected to that via a Netgear GS 308BE switch and so is my Devialet 140. So far I have hardly had any network issues.
Thanks for the screenshot and the details about your QNAP setup. Since the Roon Server package no longer works on QNAP, we need to move to the official Docker image instead.
We’ve received your request to re-open this topic thread and we’re eager to assist further.
Our diagnostics servers show that your QNAP server is currently online, running the latest build, so we’re assuming you’ve correctly migrated to the docker-based version of the server.
You mentioned that you’re not able to locate your Roon library. We can see several hundred local tracks were scanned by Roon in the latest library sync; can you please elaborate on what’s missing, or perhaps share a screenshot illustrating the current problem?
We also noticed that some of your Roon Remotes are running outdated versions of the app. Please ensure you’ve updated to the latest Roon version across your devices. You might need to re-safelist Roon in the respective firewalls on your machines (Microsoft Defender, QuFirewall, etc.).
Thank you very much for getting back to me. With the aid of community members and Arindal, I managed to solve the problem (in the end…..).
What I do wish bring to your attention is this:
I think it would have been wise if Roon had thought better about the implications of putting RoonServer in a Container. From my experience as a high end audio sales person I know that perhaps 75% of the more senior streaming audio listeners only have very basic knowledge of the highly comuterized systems they are using. Let alone “the modern way of doing things” in this digitqal world. I think it would have been nice if some effort had been put in in advance to take these Roon users by the hand. I would have appreciated that……
Thank you for your candid and very important feedback. I completely understand your frustration; moving from a “one-click” application to a container-based system is a significant shift, especially when you simply want to enjoy your high-end audio setup without needing to become a system administrator.
I would like to offer some context as to why this was necessary: as Roon continues to evolve, our software requires modern, secure system libraries that the older, native QNAP package architecture could no longer provide or reliably update. Moving to Docker was a forced but necessary evolution to ensure we can keep developing new features and maintain the performance standards of our product.
We have worked hard to make the Docker migration as seamless as possible by creating detailed, step-by-step guides that rely almost entirely on “copy-paste” configurations. However, I hear you loud and clear—for many of our users, the terminology itself is intimidating and the process is far from “basic.” We are constantly looking at how we can improve our documentation to be more accessible, and your perspective as someone working in high-end audio is incredibly valuable for that effort.
We sincerely apologize for the stress and inconvenience this transition caused you. We are very glad that you were able to get everything back up and running with the help of the community.
Thank you again for your patience. We hope you can now get back to enjoying your music—happy listening!
