What happens if you press the "Select a different Roon Server" button?
· I don't see Roon Server.
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· Roon on a *NAS* (Synology, QNAP, ASUSTOR)
Select any of the following components that are present in your local network setup
· *VPN* installed on RoonServer or Roon Remotes
You mentioned a VPN. Have you tried disabling it?
· I tried disabling my VPN/proxy connection and Roon still won't connect
Describe the issue
The connection issue both via VPN and within my home network appears since the ROON server updated itself today. It worked well before. As already indicated the ROON server is installed on a QNAP NAS
Thank you for reaching out. We are sorry to hear that the latest update has caused connectivity issues with your QNAP NAS.
The reason you are seeing “Waiting for Roon Server” is that the native Roon Server app for QNAP has reached its technical limits due to outdated libraries within the QNAP operating system. To ensure a stable and modern experience, we have transitioned to an official Docker-based installation for QNAP.
To get your system back up and running, you will need to switch to the Docker version of Roon Server.
Stop the native app: Before deploying the Docker container, make sure to stop the old Roon Server app in the QNAP App Center.
Restore your database: Once the Docker container is running, you can restore your settings and library from a recent backup.
Why Docker? This move allows Roon to run in its own isolated environment with all the necessary up-to-date libraries, bypassing the compatibility issues that affected the native QNAP package.
Please give the Docker installation a try using the guide above. If you run into any trouble during the setup, let us know and we’ll be happy to help!
Currently on my QNAP Nas the Server App (now the docker) is on a different disk as the music library. How can I specify my music library correctly? I fear /share/Music is not correct.
To find the correct path for your music library on your QNAP NAS, you need to know how QNAP structures its shared folders.
QNAP shared folder paths follow this pattern:
/share/CACHEDEV1_DATA/Music
# or
/share/MD0_DATA/Music
# or
/share/YOUR_VOLUME_NAME/Music
The generic /share/Music is actually a symlink that QNAP creates, so it might work, but it’s not reliable, especially when the folder is on a different volume than the app.
How to find the exact path:
SSH into your QNAP and run:
ls -la /share/ | grep -i music
This shows what /share/Music actually points to.
Or check the real path directly:
readlink -f /share/Music
This will return the actual full path like /share/CACHEDEV1_DATA/Music.
Alternatively, in File Station → right-click your Music folder → Properties → look for the volume/path info.
For Docker specifically:
In your Docker container configuration (via Container Station or docker-compose.yml), you need to mount the host path correctly. Use the resolved real path, for example:
volumes:
- /share/CACHEDEV1_DATA/Music:/music
rather than the symlink path. Then point your music server app to /music (the container-side mount point).
The most common volume names on QNAP are CACHEDEV1_DATA, CACHEDEV2_DATA, or MD0_DATA depending on your storage pool setup. Running readlink -f /share/Music via SSH will give you the definitive answer.