Thank you for your patience and our apologies for the lapse here.
Our diagnostics servers currently only see the old Roon Server instance installed on the QNAP itself as an application (not within Container Station). We need to ascertain why the Roon container would be running after a seemingly proper install but have no network access (either to the internet or your local network).
It looks like the Roonserver application itself doesn’t have an IP address assigned in the screenshot you shared.
So far, we’ve tried reinstalling the Container entirely to see if we can reset. The server still isn’t visible to our own diagnostic servers in the cloud or to your local Remotes and Linn streamer.
So, we want to check network connections next, at both the physical level and the level of network security.
When we were referring to the firewall above, we’re specifically inquiring whether you’ve installed QuFirewall (the native QNAP network security application), which would be accessible in the list of QNAP applications. Do you see QuFirewall listed anywhere in your QNAP settings or the list of installed apps? If so, let us know and we can share specific steps.
On your actual iOS devices you use as Roon Remotes, try navigating to Settings → Wifi and clicking on the WiFi Details page for your local network. Try setting the Private Wifi Address to “Fixed.”
How is this QNAP connected to the internet? Is it plugged into a switch, or a main router?
We’ll watch for your reply and proceed from there. Thank you!
We need to ensure that RoonServer is actually starting up, rather than just the container. The server so far hasn’t pinged our own diagnostic cloud servers, so we’re not confident that this Roon Server instance is yet discoverable on your network.
What do you see when you open Roon on another remote in this same environment, like a phone?
When you open the Container hosting roonserver in the QNAP Container Station interface, what do you see under the “logs” tab?
Another possibility is that the Roon Server container was created in a file location with insufficient space or permissions.
This would mean the docker would run, but would not be able to actually create the Roon folder housing your database. That sounds like the symptom you’re experiencing, and it would be unrelated to networking.
Open File Station on the QNAP:
Navigate to /share/Container/roon . The storage pool usage shows at the bottom of the left sidebar when you're in that share.
Right-click the roon folder → Properties
Check the Owner and Permissions there. It should be owned by root, otherwise it will fail silently.
Check the available space in this location. If it’s over 90% full, Roon probably can’t write the database
Additionally, there might be a Logs tab available. Do you see any failures listed there?
We’ll watch for your reply and proceed from there.
Thanks for taking the time to check. This confirms that the file location hosting the Docker doesn’t actually have sufficient room for Roon Server to install and run. Roon can’t write to its database, which is why it’s not coming up properly.
You have two options:
Option 1 — Free up space on the existing volume (quickest fix)
Open File Station and browse to /share/Container — look for anything bulky you can remove (old backups, unused app data, etc.)
In Container Station, go to the Images tab and delete any unused or old images sitting there — these can be surprisingly large
Once you’ve freed up a few GB, do a full restart:
docker-compose down
docker-compose up -d
If Roon comes up cleanly, you’re good for now.
Option 2 — Move Roon’s database to a larger volume (better long-term)
If that volume is just too small to be viable, you can point Roon at a different share with more headroom. In your docker-compose.yml, line 10 currently reads:
- /share/Container/roon:/Roon
Change the left side to a path on a larger share, e.g. /share/DataVol1/roon or wherever else you have space on this QNAP.
Before you do this: unless you have a reliable Backup of Roon still available, then copy your existing /share/Container/roon folder to the new location first. That folder contains your Roon database, library, settings, and machine identity. If you just update the path without copying the data over, Roon will start completely fresh and you’ll lose everything.
We’ll watch for your reply and proceed from there. Thank you again for your patience.
OK, I worked on this Sat and Sunday. I don’t believe it’s a disk storage space issue.
Docker system df Images 256.2 MB Containers 112.6MB Volumes 0
I did finally get it to connect somewhat. However my server now has a different name, I have a new Roon account, I think. I can’t get to locate my music and I lost all my info like favorites and such.
It looks like you have not restored a backup from your previous install (or copied the database folder to the location the containerized roon is using for this purpose). I know all this is complicated, and many users not familiar with the way QNAP is organizing things like volumes and share paths, as seen from the container, might be easily be getting frustrated.
Don´t loose hope, you are very near to a solution!
I assume you have used the default share paths in docker generator as seen in your screenshot in post 22days ago? If not, feel free to share screenshot. You might also want to take a look at the volume where /Container folder is mounted. You find this in general preferences > Shared Folders in QNAP QTS desktop, or by opening the volumes in File Stations. Is it the case this lives under DASH 32GB volume?
32GB is insufficient for hosting Container Station data, roon server application, roon database plus all backups. You need a bigger SSD volume for this purpose. Is /DataVol1, where your music is stored, a magnetic, spinning-disc volume? It looks like Container Station has written something in the folder /MinimServer folder which you have pointed at to share your music files.
Again, you are near a solution. You just have to define the correct paths for installing roon docker, and pointing it to your music and backups.
That is useless at best and may cause issues at worst. There is nothing to restore from a backup from another account (the DB is account bound). See also:
I only started a new account because it wouldn’t recognize my old one for some reason.
I was so tired by this time and somewhat punchy and giddy that is actually connected to the server that I believed that I needed to start a new account.
In hindsight I guess that was the wrong move.
I will probably pull the trigger on a different solution for a server from the Qnap tomorrow.
I’m really sorry for the frustration here. The transition to Docker-based deployment on QNAP has been rougher than we’d like for a number of users, and I completely understand how exhausting it is to spend time wrestling with container configuration just to listen to your music.
The Nucleus One or another headless server is a fantastic call. RoonOS is purpose-built to run Roon with no Docker, no NAS quirks, and no volume path headaches. Your network topology won’t be an obstacle, either. The Nucleus handles Roon updates seamlessly, so you’re not left chasing config changes every time something shifts under the hood.
If you haven’t pulled the trigger yet and have any questions before you do, feel free to ask here and I’m happy to help make the switch as smooth as possible.
Sorry again for the difficulties you’ve had so far. We’re watch for your reply to see which path forward you choose and support you from there. Thank you!
Before you do this: unless you have a reliable Backup of Roon still available, then copy your existing 