Qobuz pages not loading properly on client PC with server on Linux (ref#0GOO2T)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· Qobuz related pages are not working properly on client PC, they are freezed, loading and loading. The local albums look Ok, connection in Services Roon menu to Qobuz is alive, Qobuz app works. I have a feeling that smth wrong with Roon server connection to Qobuz. Can I check it somehow? Server installed on Linux machine. As an example: Qobuz Grand Selection screen freezed.

Tell us about your home network

· VPN is not used. I'm using TP-Link Omada infrastructure - no changes were made, the problem appeared few days ago.

There is an error in server log, which more or less appears at the same time as there is a problem with pages loading. I’ve found out that also Live Radio is not visible, just loading and loading…

01/17 22:11:28 Info: [stats] 10018mb Virtual, 1093mb Physical, 581mb Managed, 512mb estimated Unmanaged, 358 Handles, 71 Threads, 0.71% of runtime in GC pauses, 58ms last GC pause duration
01/17 22:11:43 Trace: GetImageData[Remote](id=1776 spec=4by3_2048 key=iqcaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030303132313238/photo/4by3_2048.jpg) => fetched in 199ms status=200 size=0 overalltime=300201ms
01/17 22:11:43 Trace: [remoting/brokerserver] Failed to get image data due to IOException (attempt 3/3)
01/17 22:11:43 Warn: [remoting/brokerserver] Failed to get image data after 3 attempts: Failed while reading web response stream
01/17 22:11:43 Warn: [broker/httpserver] While Serving Image: Failed while reading web response stream
01/17 22:11:43 Info: [stats] 10026mb Virtual, 1093mb Physical, 587mb Managed, 506mb estimated Unmanaged, 357 Handles, 72 Threads, 0.71% of runtime in GC pauses, 58ms last GC pause duration
01/17 22:11:44 Trace: GetImageData[Remote](id=1775 spec=1by1_1024 key=hqcaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030303132313238/avatar/1by1_1024.jpg) => fetched in 204ms status=200 size=0 overalltime=300211ms
01/17 22:11:44 Trace: [remoting/brokerserver] Failed to get image data due to IOException (attempt 3/3)
01/17 22:11:44 Warn: [remoting/brokerserver] Failed to get image data after 3 attempts: Failed while reading web response stream
01/17 22:11:44 Warn: [broker/httpserver] While Serving Image: Failed while reading web response stream
01/17 22:11:58 Info: [stats] 10026mb Virtual, 1093mb Physical, 588mb Managed, 505mb estimated Unmanaged, 353 Handles, 70 Threads, 0.71% of runtime in GC pauses, 58ms last GC pause duration

…Maybe, smth is blocked from provider side.

Hello @AllanB,

Based on the symptoms you’re describing — Qobuz pages and Live Radio loading indefinitely while local content works — this points to traffic being blocked or interfered with at the ISP or network level.

Roon relies on uninterrupted access to external services (Qobuz APIs, image and radio endpoints). ISP-level filtering, DPI, or partial blocking can result in exactly this behavior, where services appear connected but content fails to load.

Please note that ISP-level blocking or filtering is not officially supported by Roon. We recommend checking with your internet provider or testing temporarily via a different network connection to confirm.

Once unrestricted access is restored, Qobuz pages and Live Radio should load normally.

Vadim, thank you. Qobuz app works properly from my PC, no issues. I made internal check through another network - Roon became alive. Looks it is really ISP issue in some extra package filtering. Just contacted my ISP provider, they promised to check trace from my Roon server to the final package destination. Kind regards.

1 Like

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