Can't play any track from qobuz

[Renato_Candia]

I’ve correctly signed into my Qobuz account (premium tier, trial) but every time I try to play a track I always get a “track currently not available” error from Roon.
I live in Italy and I can listen correctly every track through the Qobuz app.
I can play correctly either my local files or Tidal tracks through Roon.
My setup
Roon Core 1.6 build 401 on Audiophile Linux 64 bit kernel rt 4.9
running on a Beelink AP34 mini pc (Celeron N3450)
Pro-ject DAC BOX DS2 Ultra connected via USB
Roon App on Windows 10 and Android (Samsung Galaxy S8)
as control App
Thanks

[noris]

Hello @Renato_Candia,

Thanks for contacting us regarding this issue, can you please perform this test?

1. Are you able to play (Assume Form by James Blake) on the Qobuz web player until the track has concluded? Link to track is as follows: (https://play.qobuz.com/album/i6yfb3qats3rc ). We’ve confirmed this album should be streamable in every country except Poland and if you are only able to play 30 seconds of this track, please see Mike’s post here:
   (Qobuz errors: too many failures, playback stopped )

2. Are you able to play the same track (Assume Form by James Blake) in Roon all the way until completion using Qobuz integration? If you are not able to do so, please provide the exact local time in your country for the playback attempt (ex: 1:36PM on 2/25/19)

3. If you have a TIDAL subscription as well, are you able to play back the TIDAL version of that track and does it work as expected until completion? If you are not able to do so, please provide the exact local time in your country for the playback attempt (ex: 1:36PM on 2/25/19)

4. Does logging out and back into Qobuz help resolve the playback issue?

5. Can you post a screenshot of your Signal Path while the track is playing? You can use these instructions to upload screenshots to Community.

Thanks,
Noris

[Renato_Candia]

Thanks for your fast and exhaustive reply.
Using your advice I realized that on the machine running Roon Core there was an incorrect system time. Once fixed all play nice.
Consider my call closed and again many thanks for your support.
Renato Candia

[noris]

Hello @Renato_Candia,

Glad to hear that the issue is solved with the system clock change! It is certainly a bit strange that the system clock could cause such issues in a Linux box but thanks for letting me know.

– Noris