What happens if you press the "Select a different Roon Server" button?
· I see my Roon Server, but I still can't connect.
When you try to connect, what screen do you see?
· Just the Roon logo
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
· *Antivirus* *software *installed on RoonServer _or _Roon Remotes
You mentioned antivirus software. Please select the specific Antivirus you have from the list below
· None of the above
Describe the issue
Cannot Connect to Roon Server on QNAP NAS after Docker Installation. Roon Remote sees the server in the iOS, MacOS and Windows Apps, but hangs on the Roon logo screen. The NAS is a QNAP TS873X (AMD R-Series RX-421ND 4-core 2.1 GHz processor). The setup worked fine with the Roon Server prior to build 1653.
I tried restarting the container, but that didn’t help. I used the provided YAML code, except I changed the location of my music to /share/Multimedia/Music:
Thanks for the update and additional information! From a fresh Roon Server diagnostic report, we can see that your remote clients (likely your PC or Mac) are trying to connect using a cached broker ID from the previous Roon Server installation (pre-build 1653, before your Docker migration).
The new Docker-based server has a completely different broker ID. When the remote sends the old ID during the handshake, the server rejects it. This is exactly why you see the Roon logo and it hangs, the remote is stuck retrying with the wrong identity.
Some next troubleshooting steps for you to consider:
On each Windows Remote machine: Navigate to %AppData%\Local\Roon\Cache (note: this is the Remote app's cache, not the server), delete it, and relaunch Roon.
On iOS: Delete the Roon app completely, reinstall from the App Store, and connect fresh.
On macOS: Delete ~/Library/Roon/Cache and relaunch, or delete/reinstall the app.
When the remote opens, tap/click "Select a different Roon Server" — you should see PROART-P16 (your server's reported name). Select it.
You will be taken to a login screen. Sign in with your Roon account credentials. This activates the server.
If you had a previous Roon database backup (from before build 1653), you can restore it from Settings → Backups once logged in, which will recover your library, settings, and playlists.
Hello. Unfortunately that didn’t work. PROART-P16 actually isn’t the right server. I have deleted it, but I was trying to connect to QNAP-TS873 server (see attached image). It is still hanging after selecting this server and I did delete the cache on the Windows computer. I also deleted the app on my iPhone and reinstalled, but got the same result.
From a fresh Roon Server diganostic report from the QNAP, we can see the single most important finding, present consistently from the very start of the log (May 4) through today (May 8), is this repeating pattern every hour:
The server is running fine, it’s processing music, seeing other devices on the network, and accepting client connections, but it has no Roon account attached to it. Because of this, when a Remotes (Windows PC or iPhone) connect, the server accepts the TCP connection but then immediately gets into a broken loop.
This is the “hanging” behavior you see. The client keeps retrying because the server can’t authorize it (no account = no auth token to complete the handshake).
Are you able to open a browser on a computer on the same network and go to http://192.168.1.213:9330
to access your Roon Server web UI?
I’d also check that the QNAP firewall isn’t blocking ports for local network access.
It may help to clear any stale cache from your Roon Server database as well.
Hello. I am getting “This 192.168.1.213 page can’t be found No webpage was found for the web address: http://192.168.1.213:9330/”. This is after logging into the QNAP Webb UI. I can also access other Web UIs such as Twonky Server on this NAS.
Thank you for confirming that, and apologies for the confusion regarding the web UI link!
To clarify: the Docker container version of Roon Server does not actually have a web UI running, to stop the ron server you need to stop the container from the Container Station.
As Benjamin noted from the logs, your server is running perfectly on the backend but is essentially stuck saying, “I don’t have a Roon account logged in, so I can’t let anyone control me.” Normally, when you select the server in the Roon Remote app, it should immediately prompt you with a login screen or redirect you to a web browser to enter your Roon credentials to bind the server to your account.
Since that isn’t happening and the app is just hanging on the logo, we need to clear the path for that login prompt.
Stop the Old Native App (Crucial): Please double-check your QNAP App Center. Make absolutely sure the old, native QPKG version of Roon Server is completely Stopped or Uninstalled. If the old app is running in the background, it will fight with the Docker container for the network ports required to trigger that login screen.
The Login Behavior: When you open the Roon app on your iPhone or PC and click your QNAP-TS873 in the “Choose your Roon Server” list, does the screen attempt to open a web browser at all, or does it just freeze instantly on the Roon logo?
Please ensure the old App Center version is stopped, and let us know exactly what happens on the screen when you try to select the server. We will get that login prompt to trigger!
Hello. I uninstalled the QPKG version of Roon Server, but unfortunately it still freezes on the Roon logo. I tried on all of my operating systems - iOS, MacOS and Windows 11. Thanks.
Since the login prompt still isn’t appearing and the app continues to hang, we need to look “under the hood” of your Docker setup to see exactly where the handshake is failing.
To move forward, please provide the following three items:
Simply uninstalling the app via the Control Panel often leaves behind the database and cache folders that could be causing this loop. Please follow these steps:
Close Roon completely on your Windows PC.
Open File Explorer and paste the following into the address bar: %localappdata%
Locate and delete the following folders:
Roon
RoonServer (if present)
RAATServer
RoonGoer
Download and reinstall a fresh copy of the Roon Remote app from the Roon website.
Launch the app, select your QNAP server, and see if the login/browser redirect finally triggers.
Container Logs: In Container Station, click on your Roon Server container and navigate to the Logs tab. Please copy and paste the last 50–100 lines of the log here.
Container Station Screenshot: Please share a screenshot of your main Container Station dashboard that shows the status, resource usage, and network settings for your running containers.
Compose File (YAML): Please share the exact YAML code or docker-compose.yml file you used to deploy the container so we can verify the volume mappings and network configuration.
Once we have these diagnostics, we’ll be able to see if the container is throwing specific errors or if there’s a network conflict we missed. Standing by for your reply!
Hello. Unfortunately, deleting the folders and reinstalling Roon didn’t help. Attached are the screenshots of the Container Station Event Log and Dashboard and the docker-compose.yml file. The is nothing in the Log except for creating the container and restarting the application. The yml file is the same as the provided one except the location of the music files being changed for my setup.
Thank you for confirming that the old QPKG version is completely uninstalled. That rules out the most common port-conflict issue. Since the app is still hanging across all of your remotes (iOS, MacOS, and Windows), we need to look directly at the container’s output and map out the exact sequence of events you are experiencing.
To help us pinpoint where the handshake is dropping, please provide the following information:
1. Container Diagnostics
Container Status: Please share a screenshot of the container’s status page within Container Station showing its current state.
Server Logs: We need to see the actual Roon Server logs. You can find these inside the mapped data directory on your QNAP, specifically in the RoonServer/Logs folder. Please zip up the most recent text file in that folder and upload it here.
2. The Exact Sequence of Events
Please walk us through exactly what happens when you open the remote app by answering these questions:
The Freeze Point: At what exact step does the hanging Roon logo appear? Does it happen the millisecond you click “Connect” on the QNAP-TS873, or does it attempt to transition to another screen first?
“Select a Different Server”: When you launch the app, do you still see the option to “Select a different Roon Server”, or is it bypassing that and going straight to the freezing logo?
De-authorization: Have you ever seen a screen prompting you to “Unauthorize” your previous QNAP server license, or has that screen never appeared?
Database State: Did you restore the backup of your old database into the new Docker mapped folders, or is this container spinning up completely fresh with empty folders?
Once we can see those logs and understand the exact flow of the screens, we will be able to tell exactly why that login prompt is refusing to trigger. We are standing by!
I restarted the Roon Server application in Container Station and did get to the You’re Already Signed In - Unauthorize screen (see attached). I didn’t backup my old database to to the new Docker mapped folders. Should I Unauthorize the existing QNAP-TS873 server? Thanks.
That screenshot is exactly what we wanted to see! Getting to this screen means your new Docker container is running perfectly and properly communicating with your remote app.
Yes, you should absolutely click Unauthorize.
Why it is Safe:
Clicking “Unauthorize” does not delete any of your music, settings, or your old database. It simply tells Roon’s cloud servers to transfer your single active streaming license from the old QPKG installation over to this new Docker container.
Thanks. I got Roon Remote to launch, but it is showing no music. I get the indication that my music folder is empty when I go to Choose music storage folder, which it is not. Thanks again.
