Qobuz not streaming after 1.7 upgrade

Core Machine (Operating system/System info/Roon build number)
ROCK Version 1.0 (build 183) stable
Server Version 1.7 (build 505) stable

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
All gigabit hardwired to Comcast Internet 150 down / 20 up
Network gear is Ubiquity Unifi Switch and EdgeRouter

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
All

Description Of Issue
Since upgrade to 1.7 Qobuz has been unable to stream. This is consistent. The track, any track, fails to start. I get the Knight Rider light back and forth on the status. Local files and Tidal tracks play as expected.

Did some troubleshooting tonight:
Logged out / Logged back into Qobuz from Roon
Restarted the Server (the server itself from the “power” drop-down on the ROCK settings page)
Double checked that DNS was properly resolving Qobuz addresses.
Still have problem.

Have the following error in my log every time I try to play a track from Qobuz:

12/16 03:30:16 Warn: [streamingmediafile] caching https://streaming2.qobuz.com/file failed: System.Net.WebException: The operation has timed out.
12/16 03:30:16 Warn: [streamingmediafile] caching https://streaming2.qobuz.com/file failed: System.Net.WebException: The operation has timed out.
12/16 03:30:16 Error: [seekableurimediafile] while determining length: System.IO.IOException: streaming media failed due to network
12/16 03:30:16 Error: [seekableurimediafile] while determining length: System.IO.IOException: streaming media failed due to network
*12/16 03:30:16 Error: [zoneplayer] Unexpected Failure While Opening Sound: https://streaming2.qobuz.com/file?<stuffremoved>: UnknownFailure
12/16 03:30:16 Info: [dac] [zoneplayer]     Open Result (Playing):Result[Status=UnexpectedError]
12/16 03:30:16 Info: [dac] [zoneplayer] Open result (Queueing): Result[Status=UnexpectedError]
12/16 03:30:27 Info: [stats] 22350mb Virtual, 921mb Physical, 414mb Managed, 320 Handles, 102 Threads
12/16 03:30:29 Trace: [streamingmediafile] retrying request due to The operation has timed out.

Interesting to note: If I take the URL from *, in the log above, and paste it directly into a browser of a machine on the same network (same subnet, network path, DNS, etc.) as ROCK then the track plays fine and without any hesitation. Qobuz player works fine as well. Also note:

12/16 03:28:49 Debug: [easyhttp] GET to https://www.qobuz.com/api.json/0.2/track/getFileUrl?<truncated> returned after 843 ms, status code: 200

So Roon is able to get the file details it’s just not reading the file.

Need help troubleshooting further as I cannot login to ROCK directly and I think that’s the next step.

Thank you much.

Hi @ipeverywhere,

Just to confirm — Local content is playing okay? It’s only Qobuz playback? And this is happening for all endpoints?

Have you tried using Google DNS? Does that result in any changes?

That is correct.

Local, Tidal, Internet Radio… all works as expected except for Qobuz.

Additional troubleshooting:

  • Tried again tonight without change, fail.
  • HUP’d my local DNS server, rebooted ROCK, fail.
  • Set ROCK to use 8.8.8.8 SUCCESS

WhaHuh?
DNS results from my local server and 8.8.8.8

$ nslookup streaming2.qobuz.com
Server: 10.xxx.yyy.aaa
Address: 10.xxx.yyy.aaa#53

Non-authoritative answer:
streaming2.qobuz.com canonical name = d3ukpcl6kuujlx.cloudfront.net.
Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.43

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.63

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.86

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.10

$ nslookup streaming2.qobuz.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
streaming2.qobuz.com canonical name = d3ukpcl6kuujlx.cloudfront.net.
Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.86

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.10

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.63

Name: d3ukpcl6kuujlx.cloudfront.net
Address: 13.224.2.43

I’d rather not use Google DNS but will leave it this way for a bit. Is this a Roon issue or Cloudfront issue?

Hi @ipeverywhere,

Glad to hear that the DNS change helped with the issue!

You can try using Cloudflare (1.1.1.1) if you prefer not to use Google DNS.

I tried pinging streaming2.qobuz.com and I see the same cloudfront.net replies. I’m thinking that this is a proxy/load-balancer and expected behavior.

What I actually suspect was the case here was that for some reason the ISP-provided DNS servers were not properly resolving the Qobuz streams, and changing your DNS to Google allowed proper resolution.

If you’d like to try Cloudflare or any other DNS servers, do let us know how it goes.

interesting, hit the same wall, I will give this a try.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.