What is the operating system of your Roon Server host machine?
· MacOS
What kind of device are you using to perform the login?
· Mac
Where are you trying to login?
· I can't log into TIDAL, KKBox or nugs
Have you been redirected to the Tidal/KKBOX/nugs login page in your browser?
· Yes
Please try clearing the browser cache and cookies for the [l](https://account.roon.app/)ogin page where you have been redirected
· No, the issue remains the same
Content / Popup Blockers
· No, the issue remains the same
Temporarily try to use a different browser
· No, the issue remains the same
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
· 17:50 NZ standard time (UTC+12) Sunday 3 May 2026
Describe the issue
After recent Roon updates (currently both server and remote are on 2.65 1653) I can no longer log into Tidal. This has been working fine for years but isn't any longer. I can log into Tidal without issue on the Tidal app and website, but when attempting to login from Roon, after the Tidal login successful redirect in the login flow I get the 'Waiting for Tidal login' in Roon with the spinner until it times out.
Not sure if it's related, but I also get a timeout when the server checks for an update ('There was an error checking for an update') and 'Can't connect to Roon search' after timeout when searching in Roon.
My server is macOS 14.8.5 on an M1 Mac mini.
Describe your network setup
ISP is Spark NZ with a router supplied by them, with TP Link Deco mesh network into which the Mac mini is plugged in via ethernet. This is very unlikely to be the issue as there were no issues for many years until a few weeks ago when I updated Roon apps and it broke.
The diagnostic logs indicate that your Roon Server is currently experiencing routing issues and timing out when attempting to communicate with our cloud servers (api.roonlabs.net).
Because of this connection failure, your Roon Server is unable to validate or refresh its authentication, which has caused your Tidal token to expire. This same network block is also the direct cause of the update check errors and search timeouts you are experiencing.
To resolve this routing issue, please change the DNS server settings on either your Mac mini or your TP-Link Deco router to a reliable public DNS service like Cloudflare (1.1.1.1) or Google (8.8.8.8 and 8.8.4.4).
How to change DNS on your Mac mini (macOS 14):
Open the Apple menu and select System Settings.
Click on Network in the sidebar.
Click on your active Ethernet connection, then click the Details… button.
Select the DNS tab on the left.
Click the + (plus) button under the DNS Servers list.
Enter 1.1.1.1 or 8.8.8.8 (click “+” again to add 8.8.4.4 if using Google).
Click OK to save the changes.
Alternatively, how to change DNS on your TP-Link Deco:
Open the Deco app on your mobile device.
Tap More at the bottom, then select Advanced.
Tap IPv4, then tap your Internet Connection Type.
Toggle off the Obtain DNS Automatically switch.
Enter 1.1.1.1 or 8.8.8.8 in the Primary DNS field.
Tap Save in the top right corner.
After updating your DNS configuration, reboot your Mac mini and attempt to log in to Tidal again.
Thanks, Vadim! I did try other DNS including Cloudflare and Google to no avail. However, you are right that it’s a network-dependent issue as I switched the Mac mini to another wifi network and now I can login to Tidal without issue, check for updates, etc.
So all is good for now. But unfortunately this doesn’t explain why it suddenly stopped being able to reach Roon’s servers after years of being able to do so on the original network without issue. I didn’t make any network config changes, it just stopped working, immediately after I did a Roon Server update. Perhaps just a coincidence but very strange. Anyway, I’m happy it’s sorted itself out somehow! Thanks again for your help.
Glad to hear it sorted itself out on the alternate network. It’s still unusual that the original network stopped reaching our servers without any obvious configuration change, especially right after the Roon Server update.
For now, we’re glad it’s working again. Enjoy the music, and we’ll go ahead and close this one out.
