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
Roon was working normally, then I installed the 26/04/26 update today & since then Roon server will not start. Installed on QNAP NAS TS-253D on seperate dual 1TB SSD drives. I have restarted the NAS a number of times and started & stopped Roon but server will not start. I then uninstalled the Roon app and re-installed, still the app will not start.
Describe your network setup
QNAP TS-235D NAS with 16GB memory, running dual 4TB SATA drives, with Roon server running on dual 1TB SSD.
Wow, thanks for the update, I have installed the Docker with container station and Roon Server starts. Unfortunately now when I try to restore a backup, it doesn’t allow me to navigate to the folder on the NAS containing the files. Any ideas?
There should be a path setup for backups. Copy your backups in that path or change the path in the container setup to match your actual path or add an additional path to your container setup.
Thanks for your help! Now working after moving backup files from original location to new container location. The problem is now that the my music collection is located on different drives in the NAS & Roon will not allow me to navigate there, unlike in the past. I have tried adding a new netrwork share folder but it will not apply the changes. Any thoughts?
It’s great that you’ve got the Roon Server up and running in Docker!
Since the container operates in an isolated environment, it can only access folders that have been specifically “mounted” during the setup. If your music library is spread across multiple drives on your QNAP, you’ll need to add each of those paths to the container configuration.
To help you get everything visible in Roon, could you please provide:
Your Docker Compose file: Please paste the YAML code you used for the installation. This will show us which volumes are currently being mapped to the container.
Music Locations: Where exactly is your music stored on the NAS? For example, is it on /share/<folder>/Music or spread across different volumes like /share/ExternalDrive?
Tip for adding more folders: If you look at our Docker Configuration Generator, you can use the “+” button in the Volumes section (as shown in the screenshot below) to add as many additional paths as you need. Each path on your NAS can be mapped to a folder inside the container so that Roon can scan it.
Hi! Thanks for your detailled response, this change is starting to make sense now. The main music folder path is \NASLOCHBD\Multimedia\MusicRoonServer. There are a couple of other locations I may need, but these could be added later once I understand how to add folders.
I cannot find how to get the non-windows folder path, sorry!
Here is a new copy of the yaml from the github site as I am not sure how to copy the original from the container:
Please don’t close the thread yet, I still can’t map the music location. The previous response was that if I provide the required information, you could then show me what code to include.
I also have discovered that the container can only be installed on the primary storage, ie SATA instead of SSD. My old installation had the Roon server on SSD for speed and all data on SATA.
With the container and data all located on the SATA drives, this goes against the preferred Roon setup?
Hi @vadim, I have detailed the information you need above, can you please assist with the correct lines to add to my setup?
Also, I also have discovered that the container can only be installed on the primary storage volume, ie SATA instead of SSD. My old installation had the Roon server on SSD volume for speed and all data on SATA volume.
With the container and data all located on the SATA drives, this goes against the preferred Roon setup?
Apologies for the confusion there—it looks like we jumped the gun on closing this! Finding the absolute path using PuTTY was the hardest part, but you still need to apply that path to your Docker configuration to actually get Roon to see your music.
Here is how to update your yaml configuration to link that specific folder:
1. Update the Music Path
Open Container Station and edit your Roon Server application.
Locate the volumes: section in your yaml code.
You need to replace the generic music path with the absolute path you just found.
Change this line: - /share/Music:/Music
To this exactly: - /share/CACHEDEV1_DATA/Multimedia/MusicRoonServer:/Music
Save the changes and recreate or restart the Roon container so the new configuration applies.
It should be automatically added as your watched folder. If not, open your Roon Remote app, navigate to Settings > Storage > Add Folder, and select the folder simply named /Music.
Because of the mapping you just created, Roon will look inside that /Music container folder and see everything inside your QNAP’s Multimedia/MusicRoonServer directory.
2. Performance Tip: Moving the Database to your SSDs I noticed you mentioned having dual 1TB SSDs for your Roon Server. If your current Docker database folder (/share/Container/roon) was accidentally created on your mechanical HDDs during the initial Container Station setup, you can easily migrate it to the SSDs for significantly better performance.
To do this:
Stop the Roon Server container in Container Station.
Open the QNAP File Station app.
Locate your roon database folder and move it completely from the HDD volume to a shared folder on your SSD volume.
Go back to your yaml configuration in Container Station.
Update the left side of the database mapping (- /share/Container/roon:/Roon) to match the new absolute path on your SSD volume.
Start the container. Roon will boot up using the fast SSD storage.
I hope this gets your library scanning successfully and ensures your database runs at top speed.
Hi @vadim, while waiting for a response I think I stumbled across the same solution as what you are suggesting!
I had to create a new folder within the SSD for the installation of the Container. I then removed the Container and data from the primary volume & ensured a fully clean install of the Container on the SSD.
Then using Putty ensured I had the correct drive/folder paths and created the new YML below:
I was able to start Roon, login and load a copy of the last save from backups.
Since then no problems until the next update.
I hesitantly ran the update hoping all would be good.
It took longer than normal to restart the server & unfortunately it broke the Tidal account link.
I could not log out and back in to rectify, so had to go into the Container in QNAP, restart the app and the Container, wait for a restart, then restart the Roon app.
Once Roon restarted, I logged back in and all good.
