What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
What kind of device are you using to perform the login?
· iOS
Where are you trying to login?
· I can't log into Roon
Please try to restart your Roon Server by closing the Roon Server app in the taskbar (MacOS), task manager (Windows) or rebooting your Roon Server machine.
· No, the issue remains the same
Different device
· I am able to switch to the diffrent device
Are you still facing the issue on the different device
· No, the issue remains the same
Record the timestamp
· 6-6-2026 at 21:29
Describe the issue
The login to my Roon Rock will not finish. I have the Roon app on my Iphone IOS 18, Ipad OS15, Windows 11 and windows 10 PC. I can connect to my Roon, can select my Roon Optimized Core Kit. Get a green indicator with ready. RoonOS 2.1. I select connect, then login, Message Roon wants to use roonlabs.com to sign in. I press Continue. I get popup acccount.roon.app. Select my account to login. Then it stays in the login screen for a moment and I'm back one step. Same on all my devices. I have a NUC for the Roon Rock. Just installed the latest image from your website. I can login to my account in a brouwser.
Describe your network setup
TPlink router, TPlink switch, wires to NUC an PC, WiFi to the rest
Welcome to the forum! Since the issue happens across multiple devices, I wonder if this could be a DNS issue with the ROCK getting a proper response.
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?
If it does not, can you please use these instructions to access your ROCK logs, upload a set to the link below and let us know once uploaded? Thanks!
Since it worked after switching off the ISP DNS, we do not need the ISP DNS specifically, and Google, Cloudflare, or Quad9 should all work the same as the ISP, but with better reliability.
If your router is behind your provider’s router, that extra detail helps explain the setup. Please let us know how it behaves from here.
I seem to be working better but connecting with Tidal did not finish. I got the screen with the message ROON + TIDAL connected but in Roon it was in a loop to get connected. I already tried it several times.
Then I started over again. Reset database, reinstall OS, add the ffmpeg file, I replaced the BITS file. Not nottint is working any more.
I get also the message that if I did not downloaded Roon from the webside i should not loggin. But on my Iphone I have to use the app store?
I believe it is solved. Everything is working again.
Reinstalled image Rock again en put the settings back. Then I changed settings in my router. Setting: router to access point. This because it is behind my providers router. I think this was the solution.
Why the issue with the connection happend? There was an update in my router 2 weeks ago, maybe this was the reason? There where no issues with other network devices. Maybe a pint to solve in the Roon.
I’m happy to have the Roon back. Thanks for the support.
I am thrilled to hear that everything is back up and running! You did an excellent job troubleshooting, and changing your TP-Link to Access Point (AP) mode was exactly the right move to permanently resolve this.
To answer your question about why this happened and why Roon was affected while your other devices were fine, it comes down to a network concept called Double NAT.
When you have a second router (your TP-Link) plugged into your ISP’s router, and both are acting as standard routers, they create two separate, isolated networks.
Other Devices: Standard internet traffic (like web browsing, checking email, or watching Netflix) only needs to reach out to the internet. Double NAT doesn’t usually bother these apps, which is why your other network devices seemed perfectly fine.
Roon: Roon relies heavily on local multicast traffic to instantly discover your remotes, audio zones, and handle internal authorization handshakes (like linking to TIDAL). When your network is split into two separate routed segments, that local traffic hits a wall and cannot pass through, causing those endless login loops and failed connections.
You mentioned the TP-Link router updated two weeks ago. It is incredibly common for firmware updates to reset certain network rules, default the router back to strict routing mode, or tighten internal firewalls. That update likely closed whatever small loophole Roon was previously using to communicate across the two routers.
We’re going to allow this thread to close out since the issue is resolved, but please reach out here if you have any further questions or require additional troubleshooting in the future.
