What is the operating system of your Roon Server host machine?
· Linux Server (Ubuntu, Fedora, ArcLinux...)
What kind of device are you using to perform the login?
· Windows
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
· 15:22 BST
Describe the issue
The browser window indicates my Roon and Tidal accounts have been connected. (Tried this with both Windows and iPhone clients and this bit works fine.) But Roon is stuck on "Attempting login" and the "Failed to reconnect." and "There was an error authorizing with TIDAL: Unauthorised. Please try again." Or, "We couldn't verify your account in time". I can use TIDAL direct without any issue and local music works fine in Roon. I just updated Roon Server with the latest version but not sure if this is related.
Describe your network setup
RoonServer is hardwired. I can see it is making multiple calls to 104.20.47.62 on TCP/443
Please first reboot Roon Server entirely. If you have any consumer VPNs, try changing the network pathway or disabling them.
Please also verify that a reliable DNS service is assigned in your router settings. Sometimes repeated resolution failures will result in an authorization timeout with the Tidal API. We commonly find that assigning Cloudlfare (1.1.1.1) or QuadNine (9.9.9.9) as the default DNS server will prevent this from happening.
We’ll watch for your reply and proceed from there. Thank you!
I tried rebooting the Roon Server but that made no difference.
I am not clear why DNS might be the problem given that the oauth part worked fine everytime.
The issue seemed to be solely with the Roon Server being able to use the oauth token (that was obtained without issue many times by my client systems). My client systems and the Roon Server are using the same DNS configuration. Are you able to provide any more detail regarding this, so I can try to identify a suitable solution?
As an aside, the Tidal auth in Roon Server did “fix” itself at some point after I raised this ticket but I have seen others raise very similar issues, so would like to find a proper fix rather than just accept that the problem went away by itself.
Thanks for the update. We enabled diagnostics, and we found is that your Roon account was also having trouble refreshing the login token at the same time, which points to a broader connection issue rather than something isolated to TIDAL, though it’s hard to say why the timeout happened. Please let us know if you see this again. We’ll keep an eye out for similar reports.