For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
I had been running RoonServer from my QNAP NAS for many years until the most recent update rendered it inoperable. I followed Roon's article "Installing RoonServer on QNAP with Docker" and still have not been able to get it working again. When I open Roon Remote, my NAS does show up and offer to connect but when I click connect nothing happens. When I log in to my NAS and open up Roon Server in the app center, I see that the status is "stopped". I am thinking the problem could be that I had been running my Roon Server from an SSD that is plugged into the QNAP via USB. During the process of installing Container Station, I did not see any way to account for the USB drive. That is, I believe I made an error with the storage mapping, but I am unsure how to fix it.
I understand the transition to the new Docker-based setup can be confusing, especially when external USB storage is involved.
To clarify how the new setup works: the Docker container should be treated as a completely brand-new, clean installation. If the old native app is stopped and you used the default paths from the guide, you should be able to connect to the new Roon Server, click Login, and authorize it as a new core. Once you are successfully logged in, you can then restore your historic database from a previous Roon backup.
Here are the immediate steps to take:
Disable the Old App: Ensure the old Roon Server application in the QNAP App Center is completely Stopped or disabled. If it is trying to run in the background, it will conflict with the new Docker container and prevent your Remote from connecting.
Fresh Start: Do not attempt to map the Docker container directly to your old database files right away. It needs to start clean first.
USB Mapping: If you want the new Docker container to store its fresh database on your Samsung Portable SSD, the volume paths in your configuration must explicitly point to that external drive’s mount point in QTS, rather than the default container folders.
To help us correct your storage mapping for the USB drive, could you please share the exact Docker Compose (YAML) file or the configuration settings you used when setting up the container?
Thank you. The problem was the storage mapping. I think it may be helpful for the instructions in the “How to Install…” article to include some more details about storage mapping instructions for QNAP. Reading in the forums here, I gather I am not the only person who was struggling with that step.
