For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· Roon Server is on, but I'm still having trouble connecting.
What do you see on your screen?
· I see something else
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
· None of the above
Describe the issue
After reinstalling the server on my QNAP according to the new procedure (Docker/Container), the server is not reachable from any of my remote controllers (Windows, IOS, Android). The server is reported as running in the NAS. It is also normally seen from the remote controllers, but when you click to connect, a white window appears the the roon logo in the middle. And everything remains stuck. And this happens from any kind of remote. Please assist and try to help me recover confidence in Roon customer care, which is now quite low... thanks
Describe your network setup
Router TIM Hub +; NAS QNAP TS 464 ethernet connected; iPhones, iPads, tablet Fire connected via wifis,
Thanks for writing in and for sharing your report! Based on your description, this sounds like a Docker/Container deployment networking issue. The “stuck on Roon logo” symptom with a server that’s visible but won’t complete connection almost always points to the container not being on host networking mode, which Roon Server requires to communicate with remotes.
Here are the next troubleshooting steps:
1. Verify the container is using host networking, not bridge:
Roon Server requires host network mode in Docker/Container Station. Bridge mode lets the container start (so the NAS reports it “running” and remotes can discover it), but the data ports needed to complete the connection get blocked, producing exactly the white-window-with-logo hang.
In QNAP Container Station, check the container's network setting and confirm it's set to Host, not Bridge or NAT. If it's wrong, recreate/redeploy the container with host mode.
2. Confirm the data directory was mounted persistently
If the container can't reach a writable, persistent database location it can stall on connect.
Verify the volume mapping points to a real share on the NAS and that the path has correct read/write permissions for the container.
3. Check that the container is actually bound to the NAS's LAN IP
With host mode, the server should answer on the QNAP's Ethernet IP. -
From a remote, try connecting by entering the server's IP and port directly (the "Help"/manual connect option in the remote) rather than relying on auto-discovery.
4. Rule out leftover database conflicts
If this is a fresh install but you pointed it at an old database folder, a version mismatch can cause it to hang. Confirm whether you migrated an existing database or started clean.
This thread has been reopened as per your request. When you have a chance to let us know the outcome of the above steps, please let us know, and we can continue from there, thank you!
