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
Few weeks ago I added 2 drives to my Asustor AS5340T nas. I backed up music and movies to an external HD so I could add the drives. After loading music and movies back to nas then the apps including Roon Server and Emby Server. I made a shared folder for the music and configured Roon server for that. No matter what I do now I cannot connect to my server on any device which includes ipad, windows laptop or ARC on my phone. I have tried using docker and portainer, checking network and un and reinstalling app. Both ipad and laptop see that server is running but do not connect. I have tried the go back feature because it states I have new server but that does'nt connect either
Thank you for reaching out and providing those details. It sounds like the transition of adding new drives to your Asustor NAS has caused a configuration mismatch in how Roon identifies your database.
Based on your description, there are two likely culprits here:
Virtualization Systems (Docker/Portainer)
I noticed you mentioned trying to use Docker and Portainer. It is important to note that Roon does not officially support running the Roon Server within virtualization or containerized environments like Docker. While many users in the community do this, these setups often create complex networking layers (NAT/Bridging) that prevent Roon Remotes on your iPad or laptop from properly “shaking hands” with the Core.
For the best stability, we strongly recommend using the native Asustor ADM Roon Server app rather than a Docker container.
Database Corruption or Path Mismatch
When you added the new drives and moved your music and movies back, the internal identifiers for your previous Roon database likely became “stale” or the folder permissions changed. Since your Remotes see the server but can’t finish the connection, the database is likely stuck in a loop.
To give Roon a fresh start on your NAS, please try the following:
Stop the Roon Server app in your Asustor App Central.
Using the Asustor File Explorer, navigate to the volume where Roon was installed.
Locate the folder named RoonServer.
Rename this folder to RoonServer_old (or delete it if you have a fresh backup elsewhere).
Reinstall the Roon app.
This will force Roon to create a 100% fresh database. At this point, your iPad and laptop should be able to “see” a new Core. You can then sign in and either start fresh or restore your database from the backup you made on your external HD.
Please try renaming that folder first and let us know if the Roon logo finally gives way to the login screen!
Thanks for the update, I’m glad to hear things reconnected for you!
Before diving into deep settings, let’s see if Windows can talk to the NAS at all when it isn’t relying on discovery protocols.
Open a web browser on your laptop.
Type the IP address of your NAS directly into the URL bar and hit enter.
If the Asustor login page appears, the network connection is fine, and we just need to fix Windows "Discovery."
With that, if Windows accidentally flagged your home network as "Public" instead of "Private" (which can happen after router reboots or updates), it will aggressively block network discovery to protect you.
Go to Windows Settings > Network & internet.
Click on Wi-Fi or Ethernet (whichever you are currently using).
Click on your connected network properties.
Ensure the Network profile type is set to Private. If it is set to Public, change it to Private.
Additionally, If the profile is Private but it still isn't showing up, the specific discovery toggle might be off.
Open the classic Control Panel (search for it in the Windows taskbar).
Go to Network and Sharing Center > Change advanced sharing settings (on the left sidebar).
Under the Private network section, make sure both Turn on network discovery and Turn on file and printer sharing are selected.
Save changes.
Let me know if either of the above help, thank you Mark! 🙌