Media Loading Slowly After 2.52 Update on Synology NAS (ref#C99BHW)

[sdas (Subhankar Das)]

What’s happening?

· Other

How can we help?

· I am experiencing freezes or crashes

Other options

· Other

Describe the issue

As soon as I updated to 2.52 (build 1538), Roon is showing 'media is slowly loading or network issue'. I confirm no network issue. Core is on a Synology NAS and I use multiple end points incl streamers etc and control via iPad or phones. this problem has started as soon as the latest update was done on21st June2025 onwards and has effected every single of my end points. Please advice

Describe your network setup

Netgear Orbi 40 mesh system with 3 satellites , fiber optic network provider

[DDPS]

There are some known issues with Tidal right now that Roon is sorting out.

[sdas (Subhankar Das)]

Thanks for letting me know.

[vadim]

Hello @sdas,

Thank you for contacting Roon Support.

We reviewed the diagnostic data enabled on your account and it have a lot of errors :

[easyhttp] [1928] GET to https://api.roonlabs.net/tidal/1/featured/new/tracks?offset=0&count=30&c=tidal-us&tidal=max returned after 3682 ms, status code: 403

This indicates that Roon tried to communicate with the TIDAL API but received a 403 Forbidden response. This usually means that Roon does not have proper authorization or there is a mismatch related to your TIDAL account or region settings.

---

Recommended Troubleshooting Steps

1. Log Out and Log Back Into TIDAL in Roon Please open Roon on your Synology NAS or connected client and:

• Go to Settings → Services → TIDAL
• Click Logout
• Then log in again with your TIDAL credentials. This refreshes your authentication token and often resolves such issues.

2. Verify Your TIDAL Account Status

• Visit [url=https://tidal.com]tidal.com[/url] and log in with the same account.
• Confirm that your subscription is active and you can stream full tracks (not limited to previews).
• Ensure your account region matches your actual location or VPN settings.

3. Restart Roon Server on Synology NAS Restart the Roon server service via the Synology DSM interface or reboot the NAS to refresh all connections.
4. Check DNS Settings on Synology NAS Sometimes DNS resolution problems interfere with Roon’s access to TIDAL. We recommend using reliable DNS servers such as:

• Primary DNS: 8.8.8.8 (Google DNS)
• Secondary DNS: 1.1.1.1 (Cloudflare DNS)

You can configure this in Synology DSM → Control Panel → Network → General → DNS Server settings. After updating, reboot the NAS.

[sdas (Subhankar Das)]

Hi Vadim,

I have done exactly as you suggested. I am attaching the screenshots for you. I still have the same problem.

1. I have logged out of tidal and qobuz (multiple times) and signed back in. Tidal credentials are perfect.

2. Changed the DNS settings as instructed and restarted the NAS more than once.

3. Since I am using Synology DSM6, I have updated the Roon Core as well on the NAS (from your Chris Rieke! section)

No change in results. I still have the same problem from any client (end point) I use. I have several endpoints.

Pl advice

Some additional info:

1. This problem has started since the past two weeks. Prior to that I have been using this Nas setup for roon for the past several years without any issues.

2. As far as Tidal and Qobuz is concerned and my credentials on login, these are the other ways I login to these services:

a. Tidal App and Qobuz App (on mac, ipad, android etc)

b. I have signed in Tidal and Qobuz on my Eversolo A-8 and my Hifirose RS 150 B (in their respective apps)

c. Using Tidal and Qobuz connect on my Lumin U1 mini, even on the Lumin app.

d. Audirvana studio (tidal and qobuz both signed in)

3. I have several ways to access tidal and qobuz built into my system (redundancy at its peak, i don’t really need so many). I just did it to compare. Anyway, every single other method works in my system except for roon.

4. I have checked my local files on my Synology NAS. I faced the same problem only once on one random track. I have listened to my local files on my NAS for a few hours now, no such issues except that once. Ignoring this for now.

Regards,

Subhankar Das

[daniel]

Hi @sdas,

Thanks for the update! I took a look at the latest diagnostics from your server, and it’s great to see that the 403 status code is no longer appearing. That’s definitely a step in the right direction.

To help us investigate further, could you share an example of a track that experienced slow loading? Also, it looks like your post didn’t include any screenshots. Were you having any trouble uploading them? Let us know, and we’ll be happy to assist.

[sdas (Subhankar Das)]

Sorry about the screen shots. Sending them now. The track is seen. This is just one example. Every single album has this issues. That includes my local files. I will ask my internet provider to come over and physically check my entire network to see if there is any physical issue with cables, routers etc. Just trying to rule them out. I will let you know how that goes. Not that I am expecting anything, since everything else is working, but you never know.

Regards,
Subhankar

[benjamin]

Hey @sdas,

Thanks for the screenshots and additional info!

We can see the following errors occur, which then lead to playback stopping:

Trace: [Morpheus] [raatclient] GOT [7] {"samples":22050,"status":"Dropout"}
Trace: [Morpheus] [raatclient] GOT [7] {"samples":17640,"status":"Dropout"}
Trace: [Morpheus] [raatclient] GOT [7] {"samples":6201,"status":"Dropout"}
Warn: [Sonnet Morpheus] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
Trace: [Sonnet Morpheus] [zoneplayer/raat] too many dropouts. stopping stream

However, we see that the track had fully buffered before experiencing the issue:

Trace: [Sonnet Morpheus] [Lossless, 16/44 MQA TIDAL FLAC => 24/44 MQA] [100% buf] [PLAYING @ 0:00] Deuteronomy: [Moderated] - Meshell Ndegeocello

So the playback issue is likely more related to the network connection between your router, server, and endpoints. I’d make sure you are signed out of all other Tidal logins across your various devices.

Does this occur no matter the endpoint you play content from? What if you try playing audio from the system output of your mobile device - does the same failure occur?

See if you can simplify your network connections, and reboot your router (if you haven’t yet ) and we’ll be on standby for your reply!

[sdas (Subhankar Das)]

I have planned a visit for my ISP to come and inspect my entire network physically. I also feel that the problem is with my network. I will let you know once they finish their work.
Regards,
Subhankar

[benjamin]

Sounds good @sdas, we’ll be monitoring for your response and reply!

[sdas (Subhankar Das)]

Hi,
To begin with, I am very happy to report that my problem has been solved. Only this time, I am very embarrassed to say that the cause was a faulty CAT6 cable from the ISP to my Netgear Orbi router. Changed the cable and everything is back to normal. I should have looked at my networking system as a start point. Sorry for all the trouble. My apologies. And thanks for handholding me thru the entire process. Without your timely responses I would have never thought of looking at the network, since everything else was working. So, for now, all’s well. Until next time! Have a great day, guys.

Regards,
Subhankar
Mumbai, India

[vadim]

Hello @sdas,

Thank you for the update, and we are glad to hear that the issue is resolved! Enjoy your music.