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
· *VPN* installed on RoonServer or Roon Remotes, *Antivirus* *software *installed on RoonServer _or _Roon Remotes
You mentioned a VPN. Have you tried disabling it?
· I tried disabling my VPN/proxy connection and Roon still won't connect
You mentioned antivirus software. Please select the specific Antivirus you have from the list below
· None of the above
Describe the issue
Everything has been working just fine. Small dialog box usually appears on my tablet/remote when Roon is open and I am listening to music. The dialogue says updates are available for one or more devices. I always ignore. Last night I clicked update all and I wound up not being able to reconnect to my Roon screen and since the tablet and my MAC both say "looking for Roon Server".
I disabled VPN and Antivirus I use through Aura, disconnected and reconnected network power, renamed Roon folder "Roon_old" and downloaded Roon to the MAC. Same response. The Roon server is on a QNAP NAS. Pretty frustrated!
Describe your network setup
My NAS is connected through ethernet directly to my Optimum cable box which is my router and modem. The Roon app is on my MAC desktop and Apple tablet that acts as my remote.
Hi @Eddie_Vializ, the QNAP package you were using is no longer the supported way to run Roon Server on that NAS, so the next step is to move to Container Station and the official Docker image.
Please use our guide here: Installing RoonServer on QNAP with Docker. It walks through opening Container Station, finding the image, downloading it, and starting the container on QNAP.
If you get stuck on a specific screen, send us a screenshot of what you see in Container Station and we can point you to the exact button to click.
OK, thanks I’m going to try this. But just for info sakes, is there an easier alternative if I choose to no longer use the NAS? What other viable options are available for the Roon Server to maximize listening quality? Thank you
My NAS has Roon Server on a solid state drive, a drive with ripped cd’s, and a back up drive along with a mirror drive all in a separate room away from my music equipment. I use Tidal so the cd’s are redundant. I am open to simplicity if it keeps the music clean.
So I went thru the steps, (not as bad as I expected) I stopped the old Roon in the QNAP apps. When I started Roon it showed my NAS name, green light button saying ready and a button “connect”. When I click connect on my tablet or desktop it stays searching but does not find the Roon Server. It did not ask me to select a different Roon.
Thanks for the update - although it’s unclear if you’ve moved over to running Roon Server via Docker. Were you able to successfully migrate?
If so, I would confirm:
All your Roon devices are running on the same local subnet
Try deleting and reinstalling the Roon remote app and see if you’re able to connect
Ensure all your Roon remotes are updated and running the latest version of Roon.
Your best bet here would be to ask this question over in our #RoonSoftwareDiscussion category on community. Many users would be able to offer suggestions and opinions on the matter.
Depending on the size of your library, you could consider looking into the Roon Nucleus One or Nucleus Titan. Here is more info on our Nucleus:
I reinstalled Roon For my Mac and tablet, they are still stuck in search mode not finding the Roon server my NAS. How can I check to see the migration was successful or not? is it possible the old Roon is still active and how can I check or disable? Everything went well step by step up to step 6 of the tutorial. At step 6, I clicked on Roon in the QNAP App Store and selected “stop” from the options. Was that the proper move? Thanks
It is a great sign that your remotes are seeing the NAS with a green light—it means the “discovery” phase is working! We just need to get the actual handshake between the remote and the new Docker server to lock in.
Since you’ve already stopped the old app, let’s take a few steps to clear any “ghost” connections and ensure the new container is communicating properly.
1. Force the Handshake (The Restart Trick)
Sometimes, after a migration, it takes a few attempts for the Docker container and your local network to properly bind the required ports.
Open Container Station, go to your Roon container, and click the Restart icon.
Do this 2 or 3 times, waiting about 30 seconds between each restart. This often forces the container to re-announce itself to your network and clears any stale data.
2. Verify “Host” Mode and Status
While you are in Container Station, let’s verify the “engine room” settings:
Ensure the container shows a green Running status.
Click on the container name and look at the Network section. It must say Host. If it says “Bridge,” your remotes will be able to see the server but will never be able to fully connect to it.
3. “Select a Different Roon Server”
Your Mac and tablet might still be trying to talk to the “identity” of the old native app.
On your tablet/Mac, if you are stuck on the “Searching” or “Connect” screen, look for a link that says “Select a different Roon Server” or “Disconnect.”
This should bring up a list of available servers. Choose the one that appears after your container restarts to establish a fresh connection.
4. Make the “Stop” Permanent
To ensure the old native app doesn’t interfere with the Docker container (especially after a NAS reboot):
In the QNAP App Center, find the old Roon Server app.
Instead of just stopping it, click the arrow/settings and select Disable. This ensures only the new Docker version is active on your network.
Next Steps: If you still can’t connect after these restarts, please take a screenshot of your Container Station overview screen (showing the container and its network mode) and share it here along with the container logs located in the RoonServer folder on your Qnap. We’ll be able to spot exactly what’s holding things up!
Gentlemen, my tablet and Mac found the server after numerous tries over two days. Vadim I followed your step by step, and removed the old Roon Server from the NAS. The music is sounding fabulous and I send to you all much appreciation and thanks for your assist. Peace
That is absolutely wonderful news! I am so glad to hear that everything finally clicked into place and that your system is sounding fabulous again. Removing that old native server completely is usually the final piece of the puzzle needed to clear up any lingering network confusion.
Thank you so much for your patience and for sticking with the troubleshooting steps over the past couple of days. We really appreciate your effort and cooperation in getting this sorted out.
Since everything is running smoothly, I will go ahead and close this thread. Please do not hesitate to open a new topic if you ever need assistance in the future.
