· Since the last update, I haven't been able to play tracks from Tidal or Qobuz. The Tidal login succeeds, but then Roon gets stuck on "Waiting for Tidal Login." I’ve restarted the Nucleus One several times—and even reinstalled it—but nothing helps. I had the same issue a few weeks ago, but managed to get it working again after several attempts to log in. This time, however, I can't get Tidal running in Roon at all. To try and work around this, I signed up for a Qobuz account. That login works, but Roon won't display the content. Could someone please look into this urgently? That would be greatly appreciated. Thanks in advance.
Tell us about your home network
· The modem is from a Dutch provider (Ziggo), and the router and access points are from TP-Link. No changes have been made to this configuration, and everything is working fine.
Hi @Dennis_Meijer, thanks for the detail, and for laying out what you had already tried.
What stands out is the version. Your Nucleus One is on Roon 2.71 build 1683. Current production is 2.73 build 1694, and it carries several fixes to how Roon syncs with streaming services, including one where a service reports itself as logged in while media requests quietly fail behind it.
Please update the Nucleus One and try both services again, then let us know how it goes. If Tidal still sits at “Waiting for Tidal Login” afterwards, we will pull a fresh set of logs and look at the connection itself.
Hi Vadim, thanks for the reply. I checked again this morning and had to log back into Roon; after that, Tidal and Qobuz turned out to be working fine. What’s strange is that I always install updates whenever Roon prompts me to. I even reinstalled the software over the weekend. I can’t explain the version discrepancy. I had the same issue with a previous update, though back then I eventually managed to get Tidal working after several attempts.
Just an extra detail: I ran an update after Roon prompted me to do so, and that’s when this problem started. It looks like the update didn’t happen or didn’t complete properly. Is that possible?
Hi @Vadim, it turned out the software wasn’t on version 2.73 (build 1694) yet. I performed the update, and now I’m experiencing the same issue I had over the weekend. Neither Tidal nor Qobuz is working. Qobuz shows the same red error, and Tidal just keeps waiting at the login screen, even though I’ve already logged in. This morning, everything worked after logging into Roon again, and both Roon and Qobuz logged in automatically. I look forward to hearing from you; thanks in advance.
I logged out of Roon, but now I am unable to log back in. I can select the account via the web interface, but after that, the ‘logging in’ process just spins indefinitely. I would appreciate knowing the solution to this. Thanks in advance.
Your system is working again as of 29 September, and we can see why it broke. It was neither Tidal nor Qobuz.
Your Nucleus could not reliably look up or reach our servers. Over 26, 27 and 28 September it recorded 6,607, 4,949 and 1,906 network timeouts. Among them, every attempt to sign in to your Roon account timed out: 165 attempts, 165 failures, none successful. That is exactly the spinning login you described. It also answers your question about the version, because Roon checks for and downloads updates over the same connections, so the update could not complete either.
The cause is the DNS server your Nucleus is using. It is set to an address out on the internet (89.101.251.229) rather than anything on your own network. When that server is slow or unreachable, everything in Roon that needs the internet stops while your local network keeps working normally, which is why nothing else in the house looked wrong.
Please change it as follows. Your current values are already filled in below, so you can copy them as they are.
Open a web browser on a device on the same network and go to http://192.168.68.57
(If that does not load, open the Roon app and go to Settings > Setup > Find Nucleus to confirm the address.)
Scroll down to the Networking section and click Configure.
The Nucleus is on DHCP at the moment, and DNS cannot be edited there, so please switch it to a static address and enter:
IP address: 192.168.68.57
Subnet mask: 255.255.252.0
Gateway: 192.168.68.1
DNS: 1.1.1.1 and 1.0.0.1
Click Save to apply.
Stop Roon Server from the same page, then restart the Nucleus.
Please let us know once that is done. Things are working at the moment, but the setting behind the failure is still in place, so we would expect it to come back otherwise.
Hi @Vadim, I followed your instructions. For DNS, I kept 1.1.1.1 since I only have one field. However, I had never changed that setting since the Nucleus One arrived. Was it incorrect from the start, back when I moved the server from the Mac to the Nucleus? In any case, it works now—thanks. Best regards, Dennis
Great to hear it’s working again, and thanks for confirming the DNS change did the trick. Please note, if you ever can’t reach the Nucleus due to the static IP and you switch to a different router/subnet, you can reset the network settings by following this guide:
In any case, hope you enjoy the music, and we’ll go ahead and mark this one for closure.
