Qobuz login and playback issue on Roon Nucleus (ref#1HKKQM)

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *All of my Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Only streaming* music is affected.

Please select the streaming service(s) with which you're encountering playback problems.

· Qobuz

Have you tried logging out and back in again to your streaming service in Roon Settings?

· Logging out and back in had no impact, the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· Last occurred today around 6:45 PM local time. The issue has also happened multiple times since yesterday. Most recent symptom was Qobuz login failure / NotLoggedIn message when trying to access Qobuz in Roon.

What are the make and model of the affected audio device(s) and the connection type?

· Main router: Linksys MX5300. Roon Nucleus is connected by Ethernet through a Lynksys 8-port Gigabit switch. Control devices connect over Wi-Fi through the Linksys network. Stable connection, no recent network changes.

Describe the issue

I am using a Roon Nucleus. Local music files stored on the Nucleus play normally.

The issue only affects Qobuz streaming through Roon. This started yesterday after previously working normally. Qobuz login often fails and I receive messages such as “Qobuz login failed” and “NotLoggedIn”. Sometimes tracks do not start or playback fails.

Qobuz works normally in the native Qobuz app using the same account, so the issue appears to be specific to Roon integration.

I have already tried logging out of Qobuz in Roon Settings > Services and logging back in, restarting Roon, and rebooting the Nucleus, but the issue remains.

Please advise on the next steps or any logs/settings you would like me to check.

Describe your network setup

Roon Nucleus connected to home router via Ethernet cable. Control devices connect over Wi-Fi. Stable internet connection. No recent network changes.

Hello @Abhilash_Krishna,

Thanks for your patience.

We reviewed the latest diagnostics from your Nucleus. From what we can see, the Qobuz login/authentication side now appears to be working successfully, and Roon is able to sync your Qobuz library/favorites.

However, we can still see Qobuz playback failures later in the logs. Around 12:31 PM local time on April 27, Roon attempted to retrieve the playback URL from Qobuz, but the request timed out after about 100 seconds. This resulted in an UnexpectedError / timeout and playback stopped unexpectedly.

This suggests that the original NotLoggedIn/login issue may have recovered, but there is still an active connectivity issue between your Nucleus and Qobuz’s streaming/CDN service.

As the next step, please try changing the DNS servers on your router to either Google DNS or Cloudflare DNS, then reboot both your router and Nucleus:

Google DNS:

8.8.8.8

8.8.4.4

Cloudflare DNS:

1.1.1.1

1.0.0.1

After that, please test Qobuz playback again and let us know the exact local time if it fails.

Thanks.

Hello Alex,

Thank you for the guidance.

I changed the DNS settings to Cloudflare (1.1.1.1 / 1.0.0.1), restarted the network device and rebooted the Nucleus.

I have been testing Qobuz playback in Roon since then, and so far playback has been stable with no errors or unexpected stops.

I will continue testing and update you if the issue returns.

Thank you.

Abhilash.

Hi @Abhilash_Krishna,

Thank you for the update and we’re glad to hear the DNS service change has improved reliability in the meantime.

If the network can’t resolve the hostname for Qobuz’s authentication servers, Roon can only retry a certain number of times before the connection attempts fail entirely. The requests simply never reach Qobuz at all. This is likely what precipitated your original symptom here. The DNS change will, hopefully, ensure that Qobuz hostnames resolve correctly to their IP addresses moving forward.