What happens if you press the "Select a different Roon Server" button?
· I don't see Roon Server.
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
Following the Roon update of 2026_04_27, neither my iPad Pro (M5) nor iPhone 17 Pro would connect to the nucleus on my QNAP TS-463U NAS, to which a Samsung SSD is connected. I couldn’t connect to Roon using my PC even though I hadn’t updated the Roon software there. I rebooted, then power cycled the QNAP; rebooted my UniFi Dream Machine Pro router, USW Pro Max 16 switches; and U7 Pro Max WAP. Except for the iPad and iPhone, everything in the Roon system is hard-wired. The software on all devices is up to date. I can connect to the QNAP NAS from my iPad, iPhone, and PC.
Thank you for your help!
Describe your network setup
UniFi Dream Machine Pro Router; two UniFi USW Pro Max 16 switches; and U7 Pro Max WAP. Comcast Gateway modem. All hardwired.
Hi, Thank you very much for your advice! I installed the RoonServer on my QNAP NAS with Docker per your instructions. This included creating a container on the NAS. When I then clicked on the Roon app, the screen displayed the correct Roon server and the option to connect. Unfortunately, the connection did not occur either on my PC or iPhone. I tried connecting again after restarting my QNAP NAS, and finally after deleting and re-installing the Roon App on my iPhone. Still no luck. I would very much appreciate your advice as to what do to next.
Thank you for the detailed breakdown of your network and the troubleshooting steps you’ve already taken. Since your UniFi setup is quite robust, we need to ensure the new Docker container is correctly integrated into your local network.
To help us investigate why your remotes are stuck on “Waiting for Roon Server,” could you please provide the following:
Container Status: Please share a screenshot of your Container Station dashboard showing the status of the Roon container.
Docker Compose File: Please paste the YAML code you used for the deployment. We specifically need to check if the network_mode is set to host.
Clean Installation: When you deployed the container, did you point it to new/empty folders for the /roon and /backups directories, or did you point it to existing ones?
Native App Check: Have you confirmed that the native Roon Server package in the QNAP App Center is completely stopped?.
I’m afraid I don’t know whether this is the YAML code. If it’s not, would you please tell me how to find it?
Roon: 2.65 (build 1653) production
00:00:00.002 Info: get lock file path: /tmp/.rnsgem0-
00:00:00.011 Info: GetLockFile, fd: 74
00:00:00.012 Info: GetLockFile, res: 0
00:00:00.013 Trace: Nope, we are the only one running
Initializing
Started
[Sentry] Initialized for RoonServer (appliance), release: roonserver@206501653+production
aac_fixed decoder found, checking libavcodec version…
has mp3float: 1, aac_fixed: 1
Running
Roon Docker image 1.0.6 starting.
Detected existing RoonServer install (branch: production).
Resolved ROON_INSTALL_BRANCH=‘production’.
Installed branch ‘production’ matches requested branch; no reinstall needed.
Image: 1.0.6
Branch: production
Roon: 2.65 (build 1653) production
00:00:00.007 Info: get lock file path: /tmp/.rnsgem0-
00:00:00.021 Info: GetLockFile, fd: 74
00:00:00.027 Info: GetLockFile, res: 0
00:00:00.035 Trace: Nope, we are the only one running
Initializing
Started
[Sentry] Initialized for RoonServer (appliance), release: roonserver@206501653+production
Not responding
aac_fixed decoder found, checking libavcodec version…
has mp3float: 1, aac_fixed: 1
Running
I don’t recall an option to point the container. Please let me know how to check and I will report back.
The Roon server was active in the App center. I stopped it, but that didn’t solve the issue on of not connecting to the Roon server on either my PC or iPhone.
Thanks for the update and screenshots! The root cause is not a network problem and not a firewall issue. The logs reveal a specific Roon account/licensing conflict triggered by the April 27 update.
Here’s exactly what happened:
On first startup after the update, Roon Server started with AccountStatus=NoAccountConfigured and MachineStatus=NeedsAccount — meaning it had lost its account linkage.
When you logged back in, Roon's servers returned "status":"NeedsBump" — meaning Roon's cloud sees two machines registered under the same name "NAS112F59":
Machine ID fda9354b (your current container)
Machine ID 2f91535b (a ghost/old registration from a previous install)
This is a licensing conflict. Roon requires a "bump" (manual deauthorization of the old machine) to proceed.
Because of this unresolved bump, the server never fully authenticated. The recurring EnsureAuthReady failed: NotLoggedIn warnings you see every hour for days are the direct consequence — Roon Server is running but is stuck in a perpetually unauthenticated state.
The incomplete receive errors from your PC (192.168.1.204) and iPhone (192.168.1.159) attempting to connect are a symptom, not the cause — clients are reaching the server fine over the network, but the server can't complete the handshake because it's not authorized.
See if this helps:
Step 1: Log in to your Roon account web portal
Go to
and sign in.
Step 2: Deauthorize the old/duplicate machine
Under your account’s “Login Sessions” section, you should see two entries for NAS112F59. Deauthorize/remove the old one (the one you’re not currently using — machine ID starting with 2f91535b).
Step 3: Restart the Roon Server container
In QNAP Container Station, stop and restart the roonserver container. On restart, it should successfully allocate the machine and log in cleanly.
Step 4: Sign in on a Remote
Open Roon on your iPad or iPhone, and use “Select a different Roon Server” → it should now appear and connect.
Thank you for your diagnosis and clear explanation!
When I used the link you provided, I was unable to sign into my account. When I signed into my account another way, I didn’t see a “Machines” or “Authorized Devices” section. I look forward to your advice.
As I mentioned, I cannot sign into account.roonlabs.com to change the machine authorization. The login form clears with no error. I have reset my password several times and have tried to login on my iPad and hard-wired PC. I tried Chrome and Safari on the iPad, and Chrome and Edge on the PC. I am not using VPN or an ad blocker. I would very much appreciate your help!
Thank you for your note. I have tried using Chrome and Safari on my iPad, and Chrome and Edge on my PC to log into the site whose link you provided so that I could delete the old machine. That’s where the login form clears per my previous message.
I will remove and re-install Roon from all of my devices (iPad, iPhone, and 2 PC’s). I had already on my iPad and, I believe, my iPhone.
When I uninstall Roon on my PC, do I uninstall the (1) application files or (2) settings and database files, or both?
I can log into the account that displays various kinds of information—eg, my subscription, payment method, email, etc.—but it does not display the machines in use.
I’m afraid I don’t know what you mean by the “login sessions” of my Roon account. In the account to which I have access (the one with my subscription, etc.), there is a record of logins.
I haven’t had access to Roon for a week and a half, and I would very much appreciate your resolving the issue.
I haven’t successfully connected to Roon since I installed the new software on 04/27. Per your instructions, I created a container for Roon and deactivated the native Roon server package in the QNAP app center. I understand I must eauthorize the old “machine” at account.roonlabs.com; however, I cannot access account.roonlabs.com even after resetting my password several times and trying various browsers (Safari, Chrome, and Edge) on my iPad and PC. I don’t use VPN or blockers. When I try to log on account.roonlabs.com, the login form clears with no error. I do, however, receive an email message from Roon stating there was a log on. Given the above, I think the logon issue is one that Roon has to resolve.
It sounds like you are very close to resolving this. The fact that your PC and iPhone can see the server and show the “Connect” button proves that your UniFi network and the Docker container are talking to each other perfectly—they are just being blocked at the “front door” by the licensing conflict Benjamin identified.
To get past the login and authorization hurdle, please try the following:
1. Accessing the Account Portal
If the login form is clearing without an error, it is almost certainly a browser cache or a security extension issue.
Try a Different Browser: Instead of clicking the link directly, try manually copying the address https://account.roonlabs.com/ and pasting it into a browser you haven’t used yet (like Firefox) or a fresh Incognito/Private window.
Check UniFi AdBlock: Even if you don’t have a traditional AdBlocker, UniFi’s “AdBlocking” or “Content Filtering” features (found in your UDM-Pro settings) can sometimes interfere with the authentication tokens on the Roon site. Try toggling those off for a moment.
2. Identifying the “Login Sessions”
The “record of logins” you see in your account is indeed the place we need. Under that section, you should see your QNAP NAS (NAS112F59) listed.
Look for the Duplicate: As Benjamin mentioned, there are two entries for the same NAS.
The Action: Click the option to “Sign Out” or “Terminate” the session for the entry that corresponds to your old native installation. Once that “ghost” session is gone, the cloud will allow your new Docker container to take the license. This should also be suggested during the new login process
3. PC Uninstallation Question
When you uninstall Roon on your PC, you should choose to uninstall both (1) the application files and (2) the settings and database files.
Why? Since your server’s identity (Machine ID) has changed because of the move to Docker, clearing the settings on your PC ensures that the Remote app doesn’t try to look for the “old” version of your NAS in its local cache. It forces the PC to look at the network with fresh eyes.
Summary of the plan:
Log into the portal via Incognito or Mobile Data.
Make sure that the default QNAP package is stopped.
Restart the Roon container in QNAP.
Perform a clean uninstall/reinstall on your PC.
Once you’ve cleared that old session, the “Waiting for Roon Server” screen should disappear almost instantly. Let us know if you manage to get into the portal!
On my PC, I was not able to log in using an incognito window in Edge after deleting all browsing history. I then downloaded Firefox to my PC to start from scratch. I was unable to logon in there; likewise trying Safari on my iPad.
In earlier messages, I may have been unclear regarding one point: although the login form clears without an error, I do receive an email security alert from Roon that says, “New sign in detected. A device from San Jose … just signed in to your Roon account. …”
Lastly, when I tried logging on for the first time using my guest network, I received the message, “There was an error logging in. InvalidRecaptcha.”
What kind of DNS are you using on your router? Since multiple remotes are failing, I wonder if this is an issue related to your local network, and DNS would be the first thing I recommend checking.
We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let us know if it helps?
Hi Noris, Thank you for your note. I change the DNS from auto to Primary server 8.8.8.8 and Secondary server 1.1.1.1. Unfortunately, the logon continues to clear without error. As noted previously, on one occasion, on my guest network, the logon cleared but there was the following message: “There was an error logging in. InvalidRecaptcha.”). I am not having difficulty logging into any other site.
I have also followed AI suggestions to the best of my ability. One of the AI’s suggested that’s perhaps Roon could
Hi, Noris, The logon cleared without error even when I turned off WiFi on my phone and used cellular. Since the cellular does not use my router, I don’t believe the issue is on my end. Thanks again!
