· No, Roon Server is not running.
· I can't turn on Roon Server, I need help.
The Roon Server stopped / QNAP
QNAP NAS (8TB RAM) is connected via Ehternet to my device. Since yesterday, after I clicked on UPDATE ALL DEVICES, nothing is working.
The Roon Server package no longer works, please switch to the official Docker image to run Roon Server on your NAS. See also:
HI Thanks. Now it can see the server, but it prevents me from using it because it says that my license can connect to one server only. I deleted Roon Server App from my NAS, trying to login - same issue. First the message that I have connected one server already, and if I try again, it is a white screen with never ending loading animation.
On the screen that tells about your license you are presented with an option to revoke that license – an option you should take.
I don’t have any next step for you regarding the non-connect issue you face. Many others ran into a similar issue some somehow resolved it themself, without providing clear steps on how to that I can recollect, or are still in the very same situation as you. I hope official support (or another user) will tackle this issue and come up with a solution. In the mean time, while you wait, you can search the forum - maybe you can make sense out of other users cases that somehow resolved that issue and repeat it. If you do, please share clear instructions or a link to the solution you found here for the benefit of others.
Hello @Vladimir_Grayvoronsk
Thank you for the update and the screenshot. The “eternal loading” screen usually points to one of two things: either a network port conflict (where two Roon Servers are running simultaneously and fighting for the same connection) or a database permissions issue (where the new container is struggling to read data from the old installation).
To help us untangle this and get you past the loading screen, could you please clarify a few details about your setup process?
/Roon volume to a completely new and empty folder on your NAS, or did you point it directly to the existing folder where your old native database was stored? (Note: Pointing the new container directly to the old database folder without using the official “Restore from backup” method is the most common cause of the infinite loading loop).Once we have a clearer picture of how the folders and apps are currently interacting, we can provide the exact steps to clear the conflict and get you logged in. Standing by for your reply!
Hi, thank you for your quick reply. Here are the answers: 1) The native App was uninstalled and deleted after mounting the new one via Docker 2) I do not understand anything in this, I just left all as is (as suggested in the instruction to the Docker Installation). Here is the text I obtained for the app: {
AppArmorProfile:“unconfined”
Args:
Config:{}
Created:“2026-04-29T09:11:50.774930529Z”
Driver:“overlay2”
GraphDriver:{}
HostConfig:{}
HostnamePath:“/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/containers/c9c07bcf385909b71699bc5ee403e11c899f5f2013375eb47862ebd8857c1957/hostname”
HostsPath:“/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/containers/c9c07bcf385909b71699bc5ee403e11c899f5f2013375eb47862ebd8857c1957/hosts”
Id:“c9c07bcf385909b71699bc5ee403e11c899f5f2013375eb47862ebd8857c1957”
Image:“sha256:9099e5a231d8a7765f97fbba06dd8521845bcc297f74a776da8abce2e4aa0dda”
LogPath:“”
MountLabel:“”
Mounts:
Name:“/roonserver”
NetworkSettings:{}
Path:“/entrypoint.sh”
Platform:“linux”
ProcessLabel:“”
ResolvConfPath:“/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/containers/c9c07bcf385909b71699bc5ee403e11c899f5f2013375eb47862ebd8857c1957/resolv.conf”
RestartCount:0
State:{} 3) The native was stopped and not working already. I deleted the native app after the installation via Docker 4). Running. No issues. I restarted it again, it is running.
Thanks for the update! A fresh Roon Server diagnostic report shows us that when you switched from the native QNAP Roon Server app to Docker, Roon’s licensing server saw two different machine IDs claiming to be the same server “Nordic”.
The logs show the Docker server hitting NeedsBump status on every startup — meaning Roon’s cloud sees a conflict and won’t license the new machine until the old one is bumped off. The good news: this eventually did resolve itself (the logs confirm MachineStatus=Licensed was achieved), meaning the server itself is actually running fine and licensed.
The problem you’re experiencing, the infinite loading screen when connecting, is a separate client-side issue, most likely caused by the Roon remote app (on your PC/phone) still trying to connect with stale session data from the old native app instance.
Let’s first fully remove Roon from your remote devices. For windows:
If you’re still stuck at loading, lets try deauthorizing via the Roon web account portal.
2c17bbde...)
Diagnostics show an active RoonServer that appears to be containerized. Are we correct in assuming this issue is now resolved?
Hi, all. Since I do not know anything in networks or other tech words you were using I asked CLAUDE CODE to inspect and correct your Docker app and it did it. Now everything works. I do not know how, but works…
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.