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 tried to update Roon but I think my QNAP (TS-453D) NAS drive, which hosts the Roon server, may have been turned off during the update process, or the internet connection may have been lost. Roon software now can't find the Roon server. I have backed up the Roon database and re-installed the Roon software to my Windows laptop but the Roon software still can't find the Roon server. Is it possible to update / re-install the Roon server software, without the Roon app working (i.e. not showing the Settings page) and without losing any of my library data (playlists etc.)?
Describe your network setup
The Q-NAP (TS-453D) NAS drive is connected to a BT Smart Hub 2 router via ethernet cable. My Windows laptop and iphone are connected to the network wirelessly.
Please check on your NAS if Roon Server is running there.
How if you can’t access Roon?
Sure why not? Roon Server not running is the situation everyone faces before installing Roon. If you have a Roon backup you should be able to restore lost content if necessary.
Note: If you ran the RoonServer package in the past, this is now defunct. Please switch to the official Docker installation instead. See also:
Thanks for your advice. I renamed the Roon, RoonServer and RAATServer folders to Roon (Old), RoonServer (Old) and RAAT Server (Old), then I reinstalled the Roon Software to my laptop. I now have new Roon, RoonServer and RAATServer folders. I believed this process was backing up the Roon database but apologies if this is not the case.
Thanks also for the info on Docker. That looks really complicated and I’m nervous about trying this. Maybe the Support Technician can hand-hold me through the process? It’s good to know I can (in theory) reinstall the server software without losing anything however.
Thank you for reaching out. First, please do not worry—your QNAP update did not fail due to a power loss or an internet drop. The recent Roon update introduced new system requirements, meaning the old native QNAP Roon app can simply no longer run. Transitioning to Docker is the required next step for everyone using a NAS.
I do want to gently clarify the folder renaming you performed. Because your Roon Server runs on your QNAP, your actual Roon database lives on the NAS, not on your Windows laptop. Renaming those folders on your laptop only resets your remote application; it does not back up your core database. Did you previously set up automatic Roon backups (via Settings > Backups) to a shared folder on your NAS or to a service like Dropbox? If so, your library and playlists are perfectly safe.
I completely understand that Docker looks complicated and intimidating at first glance! Please rest assured that it is actually much simpler than it seems. The official guide is a step-by-step walkthrough with pictures, and we are absolutely here to hold your hand through the entire process.
Take it one step at a time. Start by following the guide to create the required folders on your QNAP. If you get stuck, feel unsure, or just want us to double-check something, simply stop, take a screenshot, and reply to this thread. We will tell you exactly what to do next. You’ve got this!
I followed the instructions but when I reopened the Roon app, the only Roon server that was showing, which was marked as ready, appears to be my previous server as it has the same name (MusicNASRoon) as the previous one. During the process I completed, I I gave the server a new name (roon-server). When I try to connect to the MusicNASRoon server, I input my log in details but it keeps returning to the log in page (below). I initially got a message stating that I was already logged in to a server and could not therefore log into a second server. When I try to log in, it keeps returning to the following page:
Also, whilst I thought my database was backed up automatically, if I press ‘restore a back up’ on the Roon app log in page, the RoonBackups folder is empty. I’m not absolutely sure that this is the correct backup folder.
Whilst I thought I’d followed the process correctly, I can’t get past this stage and I suspect I’m trying to connect to the old server. I also fear that my library is not backed up (or the back-up files are located elsewhere).
Do you have any suggestions as to what to do next?
Welcome back! It sounds like you are very close to getting this finished. The behavior you are describing is actually quite common when moving from the old native app to the new Docker setup.
Here is what is happening and how we can get you past this login screen.
The “Two Servers” and the Login Loop
The reason you see your old server name (MusicNASRoon) and get a message saying you are “already logged in” is because your account currently sees two separate Roon “brains.” One is the old native app, and the other is your new Docker container.
The Solution: When you see the message stating you are already logged in to another server, you should see an option to “Un-authorize.” * Don’t worry: Clicking “Un-authorize” does not delete your music or your database. It simply tells Roon, “Please move my license from the old app to this new Docker container.” Once you click that, the login loop should break, and you will be able to proceed.
Confirm the Old App is Stopped
If the old server name is still appearing as “Ready,” it is very likely that the old QPKG app is still running in the background.
Go to your QNAP App Center.
Find the old Roon Server (the one with the Roon logo).
Ensure it is Stopped or, better yet, Uninstalled. This ensures it isn’t “fighting” the Docker container for control of your network.
The “Missing” Backups
If the RoonBackups folder appears empty when you click “Restore,” it usually means one of two things:
Volume Mapping: Your Docker container might be looking at a “new” empty folder rather than the one where your old backups were stored.
The “Old” Location: Since you renamed folders on your laptop previously, the actual backups might be sitting in a different shared folder on your NAS that wasn’t linked to the Docker container yet.
To help you further, could you please provide a screenshot of:
The “Choose your Roon Server” screen where you see the different names.
Your Container Station dashboard showing the running roon-server.
Once you “Un-authorize” the old server, we can help you point Roon to the correct folder to find those backups! You are doing great—we’ll get this sorted.
Thanks for your response. I was unable t complete step 1 because I no longer get the message that I’m already logged on or the option to unauthorize. I have tried to log in several times but I got that message only once. Now all I see when I open the Roon app is this screen:
I do hope it was ok to go ahead with step 2 even though I couldn’t complete step 1.
On the backups, I haven’t done anything on that front yet but I’m pretty sure my library was set to create automatic back-ups so hopefully I’ll be able to find them with your help.
Unless I’ve misunderstood, it sounds like you may be all set to go - if you’re no longer running into login issues and no longer see the screen to unauthorize your previous server, you should be all set to go moving forward.
Let me know if things are now running smoothly for you, or if you’re still hitting login issues.
The log in screen (above) is showing only the old server (MusicNASRoon), not the new one (roon_server) and when I click on Connect, I just get this page:
Ah you have my apologies there @Chris_Russell1! I completely misunderstood your prior reply.
The good news is from a fresh Roon Server diagnostic report, your Roon Server running via Docker is completely healthy and operating normally.
The problem is purely on the account/authorization side, not with the server itself.
The Roon app on your Windows laptop is only showing the old server name (MusicNASRoon) because that name is still registered to your Roon account in the cloud. The new Docker container hasn’t been claimed under your account yet.
Two quick things to check:
It may be worth temporarily disabling your PC’s firewall to see if you’re able to see your new Roon instance.
I’d also triple-check that your NAS and PC are functioning on the same local subnet within your local network.
If neither help, on your windows 11, I’d be curious to see what happens if you perform a Roon app refresh. Steps are below:
Apologies that my previous message was unclear and thanks for the suggestions.
I turned off my Avast firewall and still Roon only showed the old server. My NAS and laptop are both on the same subnet, at least the first 7 digits of the IP addresses are identical. I believe that confirms they’re on the same subnet?
Thank you for sticking with this, and please, no apologies needed—Docker networking can be quite a puzzle!
There is a very specific behavior we need to check regarding that server name. You mentioned earlier that you were looking for your backups. Did you, at any point during this new Docker setup, manage to hit a “Restore a Backup” button and successfully point it to a folder?
Here is why I ask: If a database backup was successfully restored into the new Docker container, the container will instantly inherit the name of the old server (MusicNASRoon). The database essentially overrides the roon_server name you gave the container. Therefore, you might actually be looking at your new Docker container on that screen right now, just wearing the old name!
To figure out exactly what machine is broadcasting that name, let’s run a definitive test by temporarily deleting the container:
1. Delete the Docker Container
Open your QNAP interface and go to Container Station > Applications.
Stop the roon-server application, and then completely Delete (Remove) it. (Don’t worry, we have your YAML code and can spin it back up in just a few seconds later).
2. Check the Roon Remote
Once Container Station shows that the application is completely gone, open the Roon app on your Windows laptop again.
Look at the “Choose your Roon Server” screen.
The Results:
If MusicNASRoon disappears: That confirms your Docker container was the one broadcasting it, meaning it successfully inherited your old database name. We will then know exactly what we are dealing with.
If MusicNASRoon STILL shows up: It means something else on your network (perhaps the old native app didn’t uninstall cleanly, or it’s installed on another device) is still running a Roon Server and causing a major conflict.
Please let us know what happens to that screen once the container is deleted!
For clarity, before I deleted Docker Container, Roon showed the MusicNASRoon server but when I clicked on it, nothing happened. I just got the Roon logo icon indicating that it was searching for something but not finding it.
Also, in case this is helpful, previously I did try to Restore a Back-up, which took me to a folder structure (I’m not sure whether this was on the NAS or my Windows laptop) but the folder entitled Back-up appeared empty. At this point I’m pretty sure I didn’t press ‘restore’, I just navigated back to the previous page.
It feels like we (i.e. you) are getting close to finding a solution. I hope so as I.m really missing my music.
Thanks for your help Vadim, I’d be lost without it.
Excellent work! That test was a massive success and tells us exactly what is going on.
Because MusicNASRoon disappeared when you deleted the container, it confirms that your new Docker setup was indeed looking at your old database files.
First, we need to spin up a completely clean container. We will worry about your backup in the very next step—right now, we just want to get you successfully logged into a fresh, working Roon screen.
Here is how to deploy a clean slate:
Step 1: Clear the Database Path
Open File Station on your QNAP.
Navigate to the folder you set up for your Docker container’s database (usually inside the Container shared folder).
Rename that existing database folder to something like RoonServer_Old.
Create a brand new, empty folder in that exact same location and give it the original name (so your Docker YAML code can find it).
Step 2: Re-Deploy the Container
Go back into Container Station > Applications.
Create a new application, paste the exact same YAML code you used previously, and click Create to spin it up.
Step 3: Connect and Log In
Open the Roon app on your Windows laptop.
You should now see a fresh Roon Server appear. Click Connect.
Crucial: When you get to the login screen, do not click “Restore a backup”. Just enter your email and password and log in as if it is a brand-new setup.
Once you are successfully logged in and looking at a blank Roon interface, stop and let me know! From there, I will give you the exact steps to safely locate and restore your backup so you can get your music back. We are on the home stretch!
Am I trying to rename the correct folder and if so, any idea why it won’t change the name of the folder? If you can confirm that this is the correct folder, I can try to rename it with a different name.
At step 1.4 (create new folder), what do you mean by “the original name”? Do you mean name the newly created blank folder as the original name of the folder that I (should) have just renamed (i.e. name the new folder ‘database’)?
At step 2.2 (create new application), I will input ‘roon-server’ as the application name (as I did last time) but where can I obtain the exact same YAML code I used previously? I still have the Docker Configuration Generator page open from when I did this last time. Is the code I used last time provided on this screen?
It looks like the reason you are receiving a “Failed to rename” error is that the Roon container is currently running, which locks the files inside the database folder.
However, there is one more possibility to keep in mind if stopping the container doesn’t immediately fix the rename error: File Permissions.
1. Stop the Container
First, ensure the container is fully stopped in QNAP Container Station. If it’s running, the system will actively protect those files and prevent any renaming.
2. Check for Permission Conflicts
If you stop the container and still cannot rename the folder, it is likely a permissions issue. On QNAP, even if you are an administrator, the folder might be “owned” by the docker user or root, preventing your specific user account from modifying it.
The Shared Folder Workaround: Instead of using File Station, go to Control Panel > Shared Folders.
Select the shared folder where your Roon data resides.
Click Edit.
Go to the Permissions tab.
Ensure that your username has RW (Read/Write) access explicitly checked for the “Roon” folder and its subfolders.
If you see an “Apply changes to this folder, subfolders and files” checkbox, make sure it is ticked.After saving these changes, go back to File Station, and you should now have the necessary permissions to rename the database folder.
3. Creating the New Folder
Once you successfully rename the old one, create a new folder and name it exactly database. This provides the empty, clean space Roon needs to initialize.
4. The YAML Code
Yes, you have it right! If you still have the Docker Configuration Generator page open, that is the exact YAML code you used. You can safely copy that again.
One final note: When you recreate the container, please ensure that the “Environment Variables” and “Volume Mappings” in your configuration match your previous setup exactly. If the folder path in the YAML doesn’t match the location of your newly created database folder, the container won’t be able to “see” it, and it will fail to start.
Try stopping the container first, and if the error persists, check those permissions—let us know if you get stuck on the command line!strong text
Hello and thanks for the guidance. However, despite spending a lot of time on this, I haven’t been able to make much progress. I’m way out of my depth here and have managed to complete only some of the steps you suggested, as follows:
Step 1 (Stop the Container): The container was definitely fully stopped when I originally completed this step prior to your last response.
Step 2 (Check Permissions Conflicts): Within the permissions tab, the only shared folder that has my username listed is the ‘Music’ folder and read/write permissions for my username are confirmed by a tick in the corresponding box:
Step 3 (Creating New Folder): Your instructions don’t state which old folder you would like me to rename or where you would like me to create a new folder - so I haven’t been able to complete this step.
Step 4 (YAML Code): on the Docker Configuration Generator, which I still have open, I don’t know which is the YAML code. Also, I don’t know how to recreate the Container or how to ensure hat the “Environment Variables” and “Volume Mappings” in my configuration match your previous setup exactly. I don’t understand the final part of your guidance at all.
It’s over a month now since I lost access to Roon and I’m more confused now than I was before you guided me through all of the above steps. Woud it be possible to guide me through the remaining steps using screen sharing software please, so you can view my screen and show me what to do, step by step? I’m really lost off now and don’t know what to do next. If we are able to share screens and if you can provide hands-on guidance on what to do, I’d be extremely grateful.
