Roon won't play certain tracks from Qobuz, gets stuck on progress bar (ref#K9XYO0) [Partially Resolved, Qobuz Backend Issue]

Hi @sme019, it’s a known issue, Roon are working with Qobuz to resolve. I’ve merged you two support topics to this track topic so all the history is together.

Unfortunately 2.64 has not fixed the issue. My log analysis:

Title: Intermittent Qobuz stream failures — 0 bytes received from CDN (v2.62 → v2.64, persists)

Describe the issue:

Qobuz streams intermittently fail with “unrecoverable error” during track transitions. The currently playing track finishes fine (buffered), but Roon can’t fetch the next track from the Qobuz CDN. After 3 retries, playback stops. Skipping to a different track sometimes works, sometimes doesn’t.

This started on v2.62 (build 1641) and persists after updating to v2.64 (build 1646). Logging out and back into Qobuz doesn’t resolve the issue — failures continue intermittently.

What’s happening in the logs:

Roon connects to the Qobuz CDN (streaming-qobuz-std.akamaized.net) and gets a response in ~42–47ms, but receives 0 bytes of audio data. After 3 retries, it gives up:

10:00:24 Info: FTMSI-B-OE qo/E14F92EA rid:1 response took 43ms
10:00:24 Debug: FTMSI-B-OE qo/E14F92EA rid:1 request ended – first block: 0 blocks read: 0 download speed: -256kbps response time: 43ms
10:00:24 Warn: FTMSI-B qo/E14F92EA block 0: no data received, retry 2/3 (error: Timeout)
10:00:24 Info: FTMSI-B-OE qo/E14F92EA rid:2 response took 47ms
10:00:24 Debug: FTMSI-B-OE qo/E14F92EA rid:2 request ended – first block: 0 blocks read: 0 download speed: -256kbps response time: 47ms
10:00:24 Info: FTMSI-B-OE qo/E14F92EA rid:3 response took 42ms
10:00:24 Debug: FTMSI-B-OE qo/E14F92EA rid:3 request ended – first block: 0 blocks read: 0 download speed: -256kbps response time: 42ms
10:00:24 Error: FTMSI-B qo/E14F92EA block 0: stream received no data after 3 retries (error: Timeout)
10:00:24 Warn: FTMSI-B qo/E14F92EA: unrecoverable error
10:00:25 Error: \[zoneplayer\] Unexpected Failure While Opening Sound: https://streaming-qobuz-std.akamaized.net/file?…: IoFailure

The key detail: the CDN responds quickly (42–47ms), but the response body is empty. Meanwhile, other streams on the same session work fine — some download at 7–14 Mbps:

10:00:09 Debug: FTMSI-B-OE qo/B367A97A rid:1 request ended – download speed: 9147kbps
10:00:24 Debug: FTMSI-B-OE qo/B367A97A rid:2 request ended – download speed: 14773kbps

So it’s not a general internet or bandwidth issue — specific stream URLs fail while others succeed.

Additional observation (new with 2.64):

After updating to 2.64, I’m also seeing repeated rnet/RnetJsonClient connection failures that weren’t present on 2.62:

09:57:10 Warn: \[rnet/RnetJsonClient\] failed to connect Connection reset by peer
09:57:11 Warn: \[rnet/RnetJsonClient\] failed to connect Connection refused
09:57:48 Warn: \[rnet/RnetJsonClient\] failed to connect Host is down

These appear around the same time as the Qobuz failures and may be related.

Pre-2.64 evidence (same Qobuz issue on v2.62):

04:24:50 Warn: FTMSI-B qo/19CBC3CE: unrecoverable error
04:24:50 Error: \[zoneplayer\] Unexpected Failure While Opening Sound: https://streaming-qobuz-std.akamaized.net/file?…: IoFailure

What I’ve tried:

  • Restarted Roon Server
  • Updated from v2.62 to v2.64
  • Logged out and back into Qobuz
  • Verified internet connectivity (Qobuz CDN reachable in 42ms, no packet loss to any device)

Setup:

  • Core: macOS (Darwin), RoonServer v2.64 (build 1646)
  • Streaming service: Qobuz
  • Affected zone: Dining Room Move + Kitchen (Sonos group), but likely affects all zones
  • Network: Wired Ethernet (primary) + Wi-Fi, both stable

Everyone, please read the release notes, or the content of this thread, including updates from Roon staff.

The latest update did not include a fix since the issue is upstream from Roon, i.e., the fix will come from Qobuz. The update allows Roon to gracefully skip a track when the Qobuz API returns an empty stream.

This issue is specifically related to certain tracks. Something about the source file is preventing playback. Certain tracks regardless if randomly selected via the radio algorithm or directly chosen will not play. Here are several that fail to play via the Roon UI. Perhaps something in the metadata can be analyzed. FYI, every one of these tracks plays without issue when using the Qobuz app directly. Only when selected via Roon UI does it hang. Thank you for your attention to this issue.
Example problem tracks:
Bill Frisell - Here It Is - Bird on the Wire
Tord Gustavsen Trio - The Other Side - The Tunnel
Brad Mehldau Trio - Seymour Reads the Constitution - Spiral
Brad Mehldau Trio - Blues and Ballads - Since I Fell for You
Stan Getz - Live at Cafe Au Go Go - One Note Samba

Yes, it’s a known issue with certain Qobuz tracks and is affecting many if not all Roon/Qobuz users.

Roon are aware and working with Qobuz to resolve.

They will post updates here in this tracking topic.

In the Qobuz thread on audiophile style is david craff active from qobuz, he replyed on some questions yesterday. may be useful info;

I can play (in Roon) The Tunnel and Since I Fell for You, but the rest (and others) I have the same problem. Hope for a fix very soon.

Same goes here for me. When playing existing playlist that include Qobuz streaming service randomly tracks are skipped over that once played perfectly fine. I was going crazy and started looking at my network equipment and all settings. Glad I came across this thread so I would stop wasting my time. Roon and Qobuz has been very solid in my system and I have had very little problems. Hoping this gets resolved ASAP.

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· As with many other people my Roon rock is having problems. It is very slow and routinely can't access Qobuz. It sometimes times out with this message:

Tell us about your home network

· Sorry, I didn't read the to step make a line break instruction.
It most recently gave this message when it eventually timed out:
Unexpected error loading album. Please try again later. (NetworkTimeout)

Here also the same problem some tracks won’t play in Roon.

Track: from Fink Memorise your senses.

If I go to Qobuz , it plays perfectly.

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· I'm seeing a huge increase in the number of songs [and full albums] that no longer play when I hit the play button. Music that is on Qobuz and will play from that app but will not play from Roon, even though it shows up on Roon. I get no error message other than "nothing is playing" and the play button is grayed out. In another instance, it says "too many failures". I've rebooted my Roon Server [Small Green Computer - Sonic Transporter i5] and it has the latest software. This issue has not occurred [that I can recall] to music I have ripped - only to streamed content - but not all of it.

Tell us about your home network

· The router is an Araknis as are the switches. I have no clue on the model number. Not using a VPN

I meant to add that I have also rebooted the modem, router and switches. Didn’t help. And while the issue is mostly “permanent”, one of the songs did work, then I went back and tried again and it quit working.

There is a known, ongoing issue with Qobuz that leads to unplayable tracks. Qobuz and Roon are working on this. The relevant official tracking thread for this issue is pinned to the top of the Support category and the latest update is this:

Previously, the issue also made Roon unresponsive because it couldn’t recover if it encountered such an unplayable track. This part was fixed in a recent Roon update. Make sure to update to the latest Roon version:

Thank you for your response. I assume there is no “will be fixed by” date!

Maybe it’s time to for me to switch to Tidal?? This really is incredibly, incredibly annoying.

Switching to Tidal and losing all play counts, tags, and any other personal metadata would be much more annoying. (These are tied to specific albums versions and won’t come along if you switch).

They are working on it and making progress, hang tight and in the meantime enjoy local music that you may have neglected :wink:

Having this same issue on a number of random tracks via Qobuz on Roon. It’s frustrating because it can be a single track off an album so no clear rhyme or reason. Hoping for a fix soon!

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Streaming tracks greyed out or unavailable

Tell us what's going on

· I've noticed some Qobuz tracks skip when played in Roon, but not when played in the Qobuz app. Two such tracks are "Sherpa" and "Tamebsz" by Angine de Poitrine on the album "Vol 1". The Roon logs show the following:
logs containing errors when attempting to play the track "Sherpa":

04/06 00:35:24 Warn: FTMSI-B qo/24CA3499 block 0: no data received, retry 1/3 (error: Timeout)
04/06 00:35:25 Warn: FTMSI-B qo/24CA3499 block 0: no data received, retry 2/3 (error: Timeout)
04/06 00:35:25 Error: FTMSI-B qo/24CA3499 block 0: stream received no data after 3 retries (error: Timeout)
04/06 00:35:25 Warn: FTMSI-B qo/24CA3499: unrecoverable error
04/06 00:35:25 Error: [cachingseekableurimediafile] while reading: System.IO.IOException: FTMSI-B: unrecoverable error
04/06 00:35:25 Warn: [zoneplayer] couldn't play URL https://streaming-qobuz-std.akamaized.net/file?uid=1199254&eid=270133496&fmt=7&profile=raw&app_id=188245549&cid=1442450&etsp=1775453724&hmac=VrLEONNpDrk7E-gOlvAjQLTClug: other error
04/06 00:35:29 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "DeviceChanged", "device": {"device_id": "{A015AC06-F052-A181-A21C-A9F2802F083C}", "type": "asio", "name": "ZenGo SC ASIO Driver", "error_message": "DeviceOpenFailed", "config": {"unique_id": "28cd2c00-89f6-bf2a-bc81-06fddd88cfe4", "output": {"name": "ZenGo SC ASIO Driver", "dsd_mode": "none", "device": "{A015AC06-F052-A181-A21C-A9F2802F083C}", "type": "asio"}, "external_config": {}}}}


logs containing errors when attempting to play the track "Tamebsz":

04/06 00:35:57 Warn: FTMSI-B qo/0D5441F5 block 0: no data received, retry 1/3 (error: Timeout)
04/06 00:35:57 Warn: FTMSI-B qo/0D5441F5 block 0: no data received, retry 2/3 (error: Timeout)
04/06 00:35:57 Error: FTMSI-B qo/0D5441F5 block 0: stream received no data after 3 retries (error: Timeout)
04/06 00:35:57 Warn: FTMSI-B qo/0D5441F5: unrecoverable error
04/06 00:35:57 Error: [cachingseekableurimediafile] while reading: System.IO.IOException: FTMSI-B: unrecoverable error
04/06 00:35:57 Warn: [zoneplayer] couldn't play URL https://streaming-qobuz-std.akamaized.net/file?uid=1199254&eid=270133498&fmt=7&profile=raw&app_id=188245549&cid=1442450&etsp=1775453757&hmac=vUjapccd_hY-LUrwjC8Rbs6gWdQ: other error

Tell us about your home network

· Orbi Wifi and Verizon Fios ISP.

@adam_tuxbury - this is a known issue and Qobuz and Roon Labs are working on a fix for it. I’ve merged your post into the main tracking thread.

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Streaming tracks greyed out or unavailable

Tell us what's going on

· Qobuz-Tracks won't play

Tell us about your home network

· Router has no impact ... since RoonARC shows the same behaviour...