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 *WiFi*
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
· *Mesh networks*
You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.
· None of the above
Describe the issue
Roon on iOS or Windows not connecting to Roon on Synology NAS. Roon server is recognised and says Ready, but when pressing connect, it just hangs with the Roon animated icon on screen.
Everything is connected to a Deco mesh. Whole network system has been shutdown and restarted, but problem remains. Firewall has been disabled.
The same problem occurs from both iOS and Windows 11. The Roon logs show the connection to the NAS is made, but then after a long while and several memory related messages, it times out and disconnects, then reconnects. This repeats itself forever.
NAS is a Synology DS918+ with 8GB memory.
Describe your network setup
Plusnet broadband 80Mb/s in modem mode. Deco mesh nodes in each room. Connected by Ethernet to Plusnet router. NAS is connected by Ethernet to a mesh nodes, although the mesh to mesh node communication is over WiFi. No firewall enabled on NAS.
Thank you for the detailed report and for already taking the time to check your network, disable the firewall, and reinstall the remote apps.
Given your specific symptoms—hanging on the Roon logo, endless reconnect loops, and especially the “memory-related messages” in your logs—we know exactly what is happening here. Following our recent updates, Roon’s internal requirements for its operating environment have evolved. The legacy native Synology app package often struggles to keep up with these new requirements, which leads to it exhausting all available RAM (memory) on the NAS. When this happens, the Synology OS forcefully stops the Roon process, Roon tries to restart, and you get caught in this endless loop.
The official and most stable solution moving forward is to migrate your Roon Server from the old Synology package over to Docker (Container Manager). This creates an isolated environment that fully supports Roon’s modern architecture and prevents these memory crashes.
Because your database and music files are safely stored in your shared folders, you will not lose any data or settings. The Docker container will simply attach to your existing database and pick right up where you left off.
Here is how to make the transition:
Step 1: Stop the old server
Open your Synology DSM interface.
Go to Package Center > Installed, find RoonServer, and click Stop.
Step 2: Install Docker
In the Package Center, search for and install Container Manager (or Docker, depending on your exact DSM version).
Step 3: Deploy Roon via Docker We have built a tool to generate the exact setup code for you:
Select Synology, set your timezone, and correctly map the paths to your existing RoonServer database folder (e.g., /volume1/RoonServer) and your music folder.
If you are using DSM 7.2 with Container Manager, you can simply create a new “Project” inside the Container Manager app. Copy the docker-compose.yml text from our configurator, paste it into the project, and hit build/start. (Alternatively, you can use the docker run command via an SSH terminal if you prefer).
Please give this migration a try. If you get stuck on any of the steps or have questions about mapping your folders, just let us know—we are happy to help you get it running!
Thanks for this. Funnily enough my next step was to try the docker container, so thank you for the detailed instructions. I will do this and let you know the result.
Just checking in to see if you have had a chance to look into the Docker migration steps outlined above.
We know that setting up Container Manager for the first time can feel like a bit of a project, so please keep us posted on your progress! If you run into any hurdles or have any questions about mapping your specific folders along the way, just drop a reply here and we will be glad to assist you further.
I have spent the last few days redoing the setup. I installed a new separate SSD on my NAS, then installed Container Manager (docker) to that volume. I then setup Roon for docker. All seems to run okay on the NAS, but I still have the same problem connecting from iOS or Windows 11.
I get the same on screen. It shows the server as being Ready, but when I click Connect, it just sits on the Roon animated icon on screen.
Are there specific log files l can upload for you to investigate further? The server logs show the server is finding some roon ready devices, so it seems to be able to talk to my lan.
To understand why your Roon Remotes are getting stuck on the animated logo, we need to analyze the network handshake logs from both the server and client sides, as well as verify your container’s network configuration.
Please gather the following files and upload them to our secure log collector:
Your Docker Configuration File (docker-compose.yml)
If you deployed this via Container Manager > Projects, open your roonserver project and copy the YAML text from the configuration tab (or download the docker-compose.yml file directly from your RoonOnDocker folder via File Station). We need to verify that the container is strictly running in host networking mode.
2. Roon Server Logs from the Docker Container
Open Synology File Station.
Navigate to the shared folder you created for your Roon database (following the guide, this should be something like /volumeX/docker/RoonOnDocker/Roon/).
Inside that directory, go to RoonServer/Logs/ and grab the RoonServer_log.txt file. (If there are recent archived logs like RoonServer_log.01.txt, please grab those as well).
3. Roon Remote Logs from your Windows 11 PC
On your Windows machine, press Win + R to open the Run dialog.
Paste the following path and hit Enter: %localappdata%\Roon\Logs
Copy the Roon_log.txt file from that folder.
Once we have these logs, we will map out the timestamps to see exactly what happens at the network layer when your Windows/iOS apps attempt to authorize the connection, and why the TCP session is dropping.
Looking forward to your logs so we can get this sorted out!
