· None of the above quite fits
· None of these quite match
· After update I can no longer connect to my NAS.
· QNAP TVS-471, AmpliFi Alien Router v- 4.0.8, no VPN
The usual Roon Server package no longer works after the Roon update to version 2.65 released on April 27. (It has some increased requirements and it turned out that QNAP hasn’t updated certain operating system libraries in 10 years).
Please switch to the new official Docker image to run Roon Server on your NAS. See also:
Hello @Kanye_Hemi_Talkin,
Thank you for reaching out. I know it’s frustrating to have your library go offline right after an update, especially when everything was stable before.
A big thank you to @Suedkiez for jumping in with the correct information!
What happened: The recent Roon updates (Version 2.65 and newer) introduced new underlying system and security requirements. Unfortunately, the native QPKG environment on many QNAP models—including your TVS-471—lacks the modern software libraries required to support these changes. This causes the Roon Server process to fail to launch, which is why your remotes can no longer find the NAS.
The Solution: To get back up and running, you will need to transition your Roon Server to Container Station (which uses Docker). By running Roon in a container, it creates a self-contained environment that has all the necessary modern libraries it needs to run flawlessly, regardless of the underlying QNAP OS age.
Next Steps: Please follow our official guide for setting this up: Installing RoonServer on QNAP with Docker
If you hit any roadblocks during the Container Station setup or need help with the volume mapping, just let us know—we’re here to help!
Thanks Suedkiez,
So, I followed the Docker and Container Station procedures as outlined in the links, apparently successfully, but Roon still won’t connect. Actually did it a second time after the first one did not work (Roon still failed to connect).
Whenever I select my NAS (below)
I get is this
I’m confused by this because part of the instructions for setting up Docker was to remove Roon Server from the NAS, which I did. So… I click DONE. and get this.
I also tried reinstalling Roon Server, in QNAP, but that did not change anything. Currently, I’ve removed Roon Server from Qnap.
I’m not an IT or a very experienced NAS user. Just want to listen to and maintain my audio library which is stored on the NAS so I can archive and listen to it in various places with ease of use (at least, that’s the idea). Hopefully, you or someone can glean what I’m doing wrong from these screenshots so I can get back to doing that again. Thanks.
I think we want to wait for @vadim to make suggestions for next steps, but some things seem strange here:
In the first screenshot, I am not sure if there should be “roonserver” and “roonserver-1” running.
In the third screenshot, after you select your NAS, it is “Searching for Roon OS Server”, but “Roon OS” is a Nucleus or ROCK, and I think this screen should only appear if you previously click “Search for Roon OS”, not when you click Connect for the NAS. So I don’t know what’s going on there.
Right. I mentioned that I had attempted a second time after the first attempt failed so that’s why there are two roonserver entries. I’ve, alternately, tried turning each off/on to no avail. I took the screenshot when both were turned on. I know I must’ve done something wrong but don’t know where I went wrong. Likewise, the Roon OS line also confused me as I don’t have a Rock or Nucleus. Hopefully @vadim can straighten me out. Thanks.
Thank you for providing the screenshot! It completely explains why you are having trouble connecting. It looks like things got a bit tangled up during the setup attempts.
Looking at your Container Station, there are a few critical issues we need to fix:
roonserver and roonserver-1). They are likely fighting over the same network ports and database files.Roon (whose details are shown at the bottom) is actually running a completely unrelated Docker image (registry:2.8.1), not Roon Server. Furthermore, it is running in “Bridge” mode (showing IP 10.0.3.2 and port forwarding) instead of “Host” mode. Roon must be in Host mode, or it will be invisible to your remotes and audio devices.
Roon, roonserver, and roonserver-1, click Actions, and completely Stop and Remove (Delete) all three of them. Don’t worry, your actual music files won’t be deleted.host.Before starting the new one, you can share your YAML file from the compose generator page, and we will review it together.
Let us know once you have cleared out those duplicates and spun up a single, fresh container in Host mode!
Okay, I figured out to remove the docker-compose entry by removing the application.
Here’s the yaml file: (please note: the image line keeps changing itself to “Package roonserver GitHub” within this reply window. the yaml file line actually reads “image: ghcr.io/roonlabs/roonserver:latest”)
services:
roonserver:
image: Package roonserver · GitHub
container_name: roonserver
network_mode: host
environment:
- ROON_INSTALL_BRANCH=production
- TZ=America/Denver
volumes:
- /share/Container/roon:/Roon
- /share/Media/Music:/Music
- /share/Container/roon-backups:/RoonBackups
restart: unless-stopped
logging:
driver: local
Hello @Kanye_Hemi_Talkin,
Fantastic job figuring out how to remove that stuck application stack! Deleting the overall “Application” container entry from Container Station is exactly the right way to wipe out a Docker Compose environment. You’ve cleared the clutter perfectly.
Your YAML file looks absolutely excellent. You have correctly configured the network mode to host, picked the right timezone, and the image path (ghcr.io/roonlabs/roonserver:latest) is exactly what we want.
Before you click “Create” to deploy this file, we just need to double-check two last critical details to ensure a perfectly smooth launch.
If the old Roon Server app is still running in the background, it will block the new Docker container from using the necessary network ports.
Take a close look at line 12 of your configuration: - /share/Media/Music:/Music
This line tells Roon: “Look inside the QNAP folder named Media and the sub-folder named Music to find the audio files.” Since you mentioned you are not an experienced NAS user, we want to make 100% sure that is the exact name of your folder. On QNAP devices, the default system multimedia folder is usually named Multimedia (capital M) rather than Media.
Media: Your YAML file is perfect. Do not change a thing!Multimedia: Change that line in your YAML file to: - /share/Multimedia/Music:/MusicOnce the old app is stopped and you’ve confirmed that path name, go ahead and paste your YAML file into the Container Station create screen and deploy it via the create application.
After the container starts running, give it about 60 seconds to fire up the background libraries. Then, grab your phone or tablet, open the Roon app, and click Connect next to your NAS. It will immediately see the fresh, clean container in host mode, log you right into your account, and get your music playing again!
Let us know how the deployment goes!
Okay thanks. The path is correct (Media, not Multimedia) but when I paste the yml text into the Create Container I get “Failed to Retrieve Image Data. A timeout occurred while retrieving image data from the registry. Check the entered value and check network connection.” the network connection checked.
Okay, so for a day Roon seemed to have found the Qnap NAS, as it began importing my music files and repopulating the playlist image files, etc. as it’s supposed to but, now it has returned to its previous state of the perpetual speaker icon and nothing else. I tried restarting (several times) but still the speaker icon just pulses. I can’t access settings or other menu commands except, Quit. What gives?
Hey @Kanye_Hemi_Talkin,
Thanks for the reply! The current Roon Server log shows the server is up and stable, but the last client connection (from 192.168.114.224) dropped on May 28 with a history buffer overflow. The server is not crashing, the Roon remote app simply isn’t finding or staying connected to it. This is almost certainly a SSDP/mDNS discovery issue on the local network rather than a server failure. The AmpliFi Alien router can sometimes suppress multicast traffic between devices, which is how Roon remotes discover the server.
Can you confirm that you confirm your Roon Remotes are all functioning within the same local subnet in your network?
It may be helpful to assign a static IP to both your server and remotes to see if that helps maintain connection.
We also saw a few crashes earlier on:
roonserver container has a memory limit set. If there's a limit below ~2GB, increase it or remove it.
Thank you, @Kanye_Hemi_Talkin! 
Thanks Benjamin. Sorry for the slow response back.
My network is up and running (always has been except when I’ve restarted several times). All Amplifi routers are on the same local network. Here’s a screenshot of current Container Station overview. Roon is currently running in the non-functioning state described in my previous post (just the pulsing speaker icon) with “Quit Roon” as the only functional menu item so… I can’t access Settings. I’ve not had connectivity issues with the routers previously.
Thanks
Update: I just clicked on menu item “About Roon” and am now getting this (below). I’m missing something fundamental here. Network settings seem normal and firewall is disabled. I just seem to be going in the same spiral after the update. FileVault was on. Might that be a problem? I tried decrypting but still no joy. Should I “Select a different server again”?
OKAY! After restarting, for the umpteenth time Roon, once again populated itself with my music library on the NAS although without any of my playlists and favorites, etc. Like starting from scratch. At least on the host end, that is. One client is still not functioning but that’s a separate issue, I think. I’ve got music in my main listening room now so that’s much better than the few weeks prior, anyway.
Thanks for the update!
Apologies if this has been glazed over, but do you have a backup you’d be able to restore from?
That way, you’d be able to access your prior playlists and saved settings.
Outside of that, how are things running? Which remote device are you still having issues with? We’d be happy to take another look. Thanks, Kanye!
