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
· *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
My QNAP NAS knocked itself offline after a week away in Barcelona, and no matter my troubleshooting, the Roon Remotes won't reconnect to the server after a restart.
So far, I've tried stopping and restarting the Roon Server app on my NAS, uninstalling and reinstalling it with a new server, allowing the ports to be open on my QNAP's firewall, and re-installing the Roon Remote apps on both my Windows PC and Android phone.
Very confused, as the same thing doesn't happen when Plex needs to reload. A simple stop and start solves the issue...am I missing something obvious?
Describe your network setup
The NAS is connected to my Virgin Media Superhub 5.0 router via Ethernet.
Do you have a second router in this setup, or a consumer VPN?
Roon Server will latch onto whichever network interface has the best connection on startup. You’ll want to ensure this network interface is on the same VLAN/subnet as your Roon devices. According to diagnostics, this QNAP has multiple available network interfaces, some of which are likely separate VLANs.
We’ll watch for your response and proceed from there. Thank you!
The odd thing is that it was working fine when I was away in Barcelona using Roon Arc, although since I’ve returned, the NAS was knocked offline and it won’t reconnect to Roon - that’s the crux of the issue. The server is being ‘seen’ by Roon Remote on my phone or my Mac, but it just won’t connect to it..
I want to make sure I fully understand your current setup and how you are trying to access the server so we can get to the bottom of this.
Could you please clarify a few quick details for us?
Your Location & Network: Are you currently back home and connected to the same local Wi-Fi/network as your Virgin Media router, or are you trying to connect to the NAS remotely from another city?
The App: Are you using the standard “Roon” remote app on your Android and PC, or are you trying to use the mobile “Roon ARC” app?
Installation Method: How exactly is Roon installed on your QNAP NAS? Are you using the native package (often the one provided by Christopher Rieke in the App Center), or is Roon running inside a Docker container via Container Station?
While we wait for those details, a highly effective troubleshooting step for a remote that hangs on the logo or the “Waiting for your Roon Server” screen is to clear the server’s temporary cache. Sometimes old, corrupted network state data gets stuck there after a NAS knocks itself offline.
How to clear the Roon Server Cache:
Stop the Roon Server app on your QNAP NAS.
Open File Station on your QNAP and locate the shared folder where you chose to store your Roon database.
Navigate into that folder to find RoonServer/Cache.
Select all the contents inside the /Cache folder and move them elsewhere (like a temporary folder on your PC/NAS).
Restart the Roon Server app on the NAS.
Open the Roon Remote app on your phone or PC and check if it successfully connects.
Would you be able to give that cache clear a try and let us know how the system behaves afterward, along with those setup details?
Using the standard Roon remote app, rather than Roon Arc.
It’s installed with the native package, and the most recent one I could find.
I’ve just tried clearing the cache (moving the files/folders to another temporary location on my NAS) and the server shows as ‘Ready’ in the Roon Remote app, before the never ending Roon logo loading screen…so still very confused.
Let’s try to force Roon’s systems to completely release and re-authenticate your NAS. We can do this by temporarily using your Windows PC (or a Mac) to “steal” the active Roon authorization.
Here is how to trigger the reset:
Open the Roon app on your computer.
When prompted to choose a server, select the option to set up that specific computer as the Roon Server (instead of connecting to the QNAP).
Log in with your Roon credentials. You will see a prompt warning you that your account is already in use on the QNAP.
Click the Unauthorize button next to your NAS. This is the crucial step that forces the cloud to break the stuck session.
Once Roon loads the main interface on your computer, navigate to Settings > General and click Disconnect (or Log Out).
Now, restart the Roon Server app on your QNAP NAS one more time.
Open your Roon Remote app, select the QNAP NAS, and log back in.
Forcing this fresh authentication handshake usually clears out that infinite loading loop. Let us know if this gets you back into your library!
I’ve just tried this using my Mac, and it unfortunately hasn’t worked, so when connecting to my NAS, I’m still getting the Roon logo loading screen virtually permanently. Setting up my Mac as the server went straight in, so there’s an issue on the server side.
Thank you for your patience. We still see the NAS reporting multiple network interfaces: the first on the network/subnet shared by the rest of your devices, and then three private network interfaces in the range common for dockers/virtualization containers. We see critical log errors that suggest Roon can’t bind to discovery sockets.
Just to confirm, do you have dockers/VMs installed on this QNAP? Please try running Roon in Host mode within your Container network settings, if so.
What is the make/model of mesh network you have setup here?
Thank you for your patience! We have been digging through the diagnostic logs from your QNAP NAS, and we found a couple of very interesting things.
First, we can see that your NAS is successfully operating as a Roon Server. Just today, it successfully streamed Genesis to your MacBook Pro Speakers! Since the Mac is able to connect and play music, the database itself is healthy and functioning.
However, we are also seeing repeated instances of a specific network error: System.Net.Sockets.SocketException (98): Address already in use.
This error means that Roon is trying to use a specific networking port to communicate, but your router or NAS is telling Roon that another application (or another device) is already hogging that port. This kind of IP or port conflict is exactly what causes the “infinite loading logo” on certain remotes, while others might slip through and connect.
To help us clear this conflict, could you please check your Virgin Media Superhub router settings?
Look at your connected devices list and ensure there are no IP address conflicts (two devices accidentally assigned the exact same IP address).
Could you also confirm if your Android phone is still stuck on the loading screen, or if it managed to connect at the same time as your Mac?
My server had to restart to install a software update, and it seems like it fixed itself….so all back working on my Mac now. I seem to be having issues with the server being available on Roon Arc, as logging into the app states that the server needs to be turned on and configured for remote access.
Thank you for confirming that the local access issue is resolved.
Regarding Roon ARC, please navigate to the Roon ARC settings on your Mac while connected to the NAS’s Roon Server and test the connection there.
Once the test is complete, please share a screenshot of the results so we can analyze it and help determine the underlying problem.
Please also let us know if Roon ARC worked for you in the past, prior to your trip to Barcelona, and confirm if you have at home a router provided by your ISP ?
Hi, I had to restart my NAS due to another firmware update from QNAP, and it’s put me right back to the beginning I’m afraid. A simple restart worked before, although it hasn’t helped in this instance, and I’m not sure why.
I would next review your router settings, and disable all but a single local subnet within your network - then reboot your devices to ensure all your Roon devices are functioning within the same local subnet. This is required for connection.
