· QNAP TVS-871 Stopped working after latest update:
Tell us about your home network
· The latest update forced the Roon application running on the NAS to stop. After researching the Roon community board, I followed all the instructions to install the QNAP container app, create the Roon application and then proceed to run Roon. The container application says Roon is running, but when I go to load the application on a desktop or mobile device, upon connecting to Roon, I get the white ball that shows it loading, but nothing comes up after that. The Roon applications see the server and want to connect, but the connection never completes bring up the server application. I have done the install multiple time with the same results. I was even able to go through a restore of my previous backup, but Roon on any device I'm trying to use to connect always stops at the same screen after linking to the server.
An additional screen shot that's displayed before connecting to the server.
We’ve reviewed your logs and can see RoonServer starting up and running cleanly inside the container. The issue is that it never receives any connection requests from your remote clients. Cloud connectivity looks fine, but there’s no local traffic reaching the server at all.
With five local IP addresses on your QNAP, RoonServer may be binding to a virtual or container interface on startup rather than your main LAN adapter. To rule this out, we’d recommend disabling any unused virtual network interfaces in your QNAP network settings so the server has only one bindable interface.
It’s also worth checking whether a recent firmware update reset any QNAP firewall rules. Please confirm the following ports are open for RoonServer:
TCP 9330 — client/server control connections
TCP 9100–9200 — RAAT audio streaming
UDP 9003 — local network discovery
If you're unsure which is your primary LAN interface or how to remove the virtual ones, let us know your Container Station network mode (Bridge, Host, or NAT) and we can walk you through the next steps.
Hi Connor, I don’t have a firewall setup on my NAS and I do believe I turned off the other local IP ports on the NAS and only the 10GB port is connected to the network. Please see the attached pictures. That would be the only place I know to turn things off. Beyond that I’m not sure where to go to make additional changes and I dont have a clue what mode the Container Station is running in, I just installed the defaults and then followed the instructions on Roon to create the application. Also, the roon server in teh picture aboves IP address is pointing to the correct location. As far as I’m aware, nothing changed between the time of the update that failed and then my creating the oontainer and fllowing the docker application install.
This is exactly what I am experiencing, and tried to follow the steps above, but neither my org’s it guy nor I know what to do next. Waiting for Roon support to get back to me…Actually, rereading your post, you got further than I did…
Connor, I did uninstall everything and followed the same procedures outlined in the instructions reinstalling Container Manager, then creating the Docker Application using the parameters for the Docker YML code. The installation went fine without any errors and it says the server is up and running. But the outcome remains the same, even with the changes shown above. Where do we go from here? FYI - This time it’s a raw version by the way, meaning I have not yet tried to restore my previously backed up database. This is strictly a brand new install.
I don’t understand why there has not been a more urgent response to this issue as multiple people are dealing with the same problem. The fact that there was no warning that this update would take down users servers that were running on a NAS makes the delay in answering and coming up with a solution to fix this considerably more aggravating, especially as it appears Roon Labs new that would happen. Clearly better communication and follow-up is needed regarding this issue by Roon, and maybe a sense of urgency as well!
Connor and anyone else reading this post. PROBLEM RESOLVED. It appears you have to deauthorize your server and create a new server before the system will connect, even though the devices think they are seeing the new server. Once I did that, my devices immediately connected and it started rebuilding my library. I reconnected my Qobuz account and ran a restore from my backup which took a while, it’s a big library. The problem with the backup is that once I restored the backup, the server resorted to the previous issue in that my Roon Endpoints would no longer connect again. I had to delete everything and start over, minus doing a restore. This is a huge issue as I lost multiple playlist, tags, favorite album settings and bookmarks. Roon needs to have a way to restore these things when something like this happens. I have several criticisms of Roon including the issues related to an inability to restore ny backup successfully. A notification of this issue with upgrading NAS’s tied to this update should have been sent out to all users prior to the update being released, a more detailed and accurate install process should have been created and a link included in the update notification, and Roon support should have been much more responsive to these particular support issues. This was mostly trial and error to resolve with a lot of frustration when a little pre-planning could have minimized a lot of this. I certainly hop this helps others having this problem and beware of the issues you may encounter with the possibility that your backup won’t restore.
Thanks for the update and additional information! Your frustration is warranted, and I apologize for the delay in being able to respond to your thread and issues. That said, excellent work getting your system up and running!
I’d be curious to see if refreshing only your RAATServer database might help in this case. That way, you wouldn’t need to start completely fresh like you’ve mentioned in your above reply.
Instead of deleting the entire database, you can try resetting just the networking component.
First, perform a backup restore to restore your original database. Then, locate your Roon database folder on your NAS or PC.
Find the folder named RAATServer and rename it to RAATServer_old.
When you restart Roon, it will keep your library, playlists, and tags (from the database), but it will be forced to "rediscover" every audio endpoint from scratch as if it were a brand-new system. This often bypasses the connection loop.
Let me know if this is something you’d be interested in trying.
Hi Benjamin, and anyone else running into this situation related to their NAS not connecting.
Note: This was part two of the fix!
I did exactly as you said, at first it didn’t seem like it worked but after about 5 minutes it connected. My link to the file folder for my music for some reason was incorrect and I had to re-establish where they were located on the NAS server. Once that was done, it started the import process of the music again.
I checked and it appears my Playlist are there, Tags are there and so are the Bookmarks. There’s 14TB of music to re-import and that will take a while but it appears this was the right solution.
Thanks for the suggestion and instructions Benjamin, this was the miracle I was hoping for! I will follow-up once all the files are imported and I can test the Playlist and confirm to you it’s working correctly. Thankful that Roon support was able to come up with a solution that provided the final fix!!!
I want to step in quickly regarding the 14TB music re-import you mentioned. If Roon is currently treating that 14TB as a brand-new import rather than recognizing the existing files.
If you want to be absolutely sure your restored database perfectly links back to your music files without triggering a fresh import, there is a specific workaround you can use with your Docker mappings:
The “Empty Directory” Workaround This forces Roon to re-associate your files with the restored database paths manually.
Stop the Container: Go into Container Station and temporarily stop the Roon container so the current import pauses.
Create an empty folder: Create a completely empty folder on your QNAP (for example, /share/Public/EmptyMusic).
Edit your Container Station configuration: Change your default Music mapping to point to that empty folder, and mount your actual 14TB music directory as a new, secondary path. Your volume mappings should look something like this: - /share/Public/EmptyMusic:/Music- /share/YourActualMusicPath:/ActualMusic
Restart the Container: Save the configuration and start the Roon container again.
Restore the backup restore the backup over your current installation.
Re-link the Storage: Open Roon and go to Settings > Storage. Because Roon is now looking at the empty folder, your old storage location should show an error in red text (saying the files are missing). Click the three dots (⋮) next to that disabled folder, select Edit, and browse to the newly mapped /ActualMusic folder.
Roon will quickly scan the new location and instantly re-link all 14TB of tracks to their exact previous database entries, guaranteeing all your custom edits, play history, and deep metadata are preserved exactly as they were in the backup.
An additional screen shot that's displayed before connecting to the server.
