· None of the above quite fits
· None of these quite match
· Login to TIDAL does not work
· Fritz 7690
image moderated [email removed]
Hi @lobopanic,
Thanks for writing in and for sharing your report! Based on your account admin, it looks like you’re both properly signed into Tidal and have Tidal tracks synced to your library.
Are you still having issues?
Hi benjamin,
that is the problem. The website says “Login successful”, but login does not work.
See screenshots.
In the meantime, I uninstalled and re-installed Roon and had the same issue. All of a sudden, today it worked and I started to set up everything. Then, after shutting down the computer for a while, I am receiving the message shown in the screenshot. It all worked really well up to now, but this is a new experience with Roon to me. All this while internet connection is flawless and TIDAL works with no issues.
Hello @lobopanic
Since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.
Please try the following steps:
Once these permissions are refreshed and the system restarted, your Roon Server should reappear.
Please let us know if the issue persists after these steps, and we’ll continue from there.
Hello @vadim
thank you for your response. I already managed to solve the “Waiting for Roon Server …” “issue”.
Roon is also running again on my system, but I identified an uncommon behaviour.
Roon Server NOT running : Tidal app starts and can be used immediately after it is loaded.
Roon Server running : Tidal app starts but states “internet connection not available”.
In this case, Roon cannot log in to Tidal, which is probably expected. Waiting for a few minutes after booting the computer and then starting Tidal works as well. Then Roon logs in and works after clicking on “Retry” in the error pop up window, but it never starts without this red pop up.
My system :
MacBook Pro 2021
macOS Sequoia 15.7.5
This MacBook is Remote and Server.
Hey @lobopanic,
Thanks for the update! This specific retry dance suggests a temporary bottleneck or a conflict in how macOS handles network requests during the initial startup sequence.
I’d go through the steps @vadim mentioned above if you haven’t already:
If that doesn’t help, Private Relay can occasionally mask the network status from apps, leading Tidal to believe there is “no internet” because it can’t establish a direct handshake immediately.
If neither help, let’s see if clearing the Tidal cache improves the behavior:
/Library/RoonServer/Cache/Cache folder elsewhere, like your desktopWe’ll be monitoring for your reply and results 
Hi @lobopanic,
We don’t see any recent Tidal sync with your account in our diagnostic servers so we’re not confident this is resolved.
Another suggestion would be to change the DNS server assigned in your router to a known, reliable service. This would be under a dedicated DNS tab (usually) in your router settings admin page. We recommend assigning Cloudflare (1.1.1.1) or Google (8.8.8.8).
Please let us know if we can assist further and we’ll watch for your response. Thank you!
Hi @connor ,
thank you. Unfortunately, none of the above approaches changed the behaviour. Private Relay is a feature that is included in iCloud+, which I don´t have.
No problem, I got it running on my system again. I just have to wait several minutes after booting the system before starting Roon.
Hi @lobopanic,
We wanted to circle back here before this thread closes. Have you been able to login to Tidal via Roon? Please see @benjamin’s reply above if not and let us know if it helps.
This thread is now auto-closing, but you can reactivate the topic thread here if you have future login issues or any other problem with Roon.