Issues accessing Tidal

Core Machine (Operating system/System info/Roon build number)
Linux - build 667

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
WiFi

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

Description Of Issue
I am having issues accessing tidal content. Roon is showing that it logged in. However I cannot see any tidal albums listed when I look at an artist page.

There are some 403 errors in the log:

10/24 11:54:09 Debug: [easyhttp] [17] GET to https://tidal.roonlabs.net/1/featured/top/albums?offset=0&count=30&c=tidal-au returned after 1149 ms, status code: 403
10/24 11:54:09 Debug: [easyhttp] [16] GET to https://tidal.roonlabs.net/1/featured/new/albums?offset=0&count=30&c=tidal-au returned after 1153 ms, status code: 403

I have restarted the core which has made no difference.

Note: I can play music on tidal if it is already in my library. I just cannot see albums that are not in my library.

Hi @David_Radnell,

What is the model/manufacturer of all your networking gear?
Is there any change in behavior if you try to use Ethernet?

Which flavor of Linux are you using? Have you configured the Linux firewall properly?

My setup has been running for a couple of years so there should be no issues with firewall.
I beleive I have issues with the dayabase. I have not been able to back it up, backups fail. Any suggestions how to rescue my database?

Hi @David_Radnell,

Can you please use these instructions to send me a copy of your Roon logs?

Also please let me know which flavor of Linux are you using, thanks!

Hi Noris,

I took the opportunity to upgrade the server that Roon is running on, so I re-installed Roon on the new server and restored the database from an old backup. It is working fine with no issues accessing Tidal.

I suspect my issues on the old server were due to a corrupted database.

1 Like

Hi @David_Radnell,

Happy to hear that the new server is working as expected!

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