· I’m having a Tidal problem again on my ROCK Roon server. Tidal loads slowly and constantly skips to the next track in the middle of playback. I get the familiar error message saying that there is a network problem. My Roon server is connected via LAN, and I also have a RoPieee bridge in the kitchen. The router is fine. I have good network throughput and the internet connection runs at 150 Mbit. I have the impression that these problems are related to the latest update?! Can anyone help me?
Tell us about your home network
· FRITZ!Box 6690 cable ; no vpn; connection to the Rock Server via LAN
Here’s a step-by-step on how to change the DNS settings on your Nucleus:
Open a web browser on a device connected to the same network as your Nucleus.
Enter the IP address of your Nucleus in the address bar.
If you don’t know the IP address:
Open the Roon app.
Go to Settings > Setup > Find Roon OS.
Note the IP address shown for the ROCK.
Alternatively, use http://ROCK.local/ (on macOS or Windows with Bonjour installed).
Log into the Web Interface:
Once the web page loads, you’ll see the Nucleus web administration interface.
Change the DNS Settings:
Scroll down to the Networking section.
If the Nucleus is using DHCP:
Note that you cannot directly edit DNS settings under DHCP. You will need to switch to a static IP to specify custom DNS servers.
Switch to a Static IP:
Click on the Configure or Edit option under networking.
Enter the current network settings for your Nucleus (IP address, subnet mask, gateway) manually. These can often be found in your router’s settings or your current DHCP lease information.
Specify Custom DNS Servers:
Add DNS servers in the relevant fields. Common choices:
Google DNS: 8.8.8.8 and 8.8.4.4
Cloudflare DNS: 1.1.1.1 and 1.0.0.1
OpenDNS: 208.67.222.222 and 208.67.220.220
Save and Apply Changes:
Click Save or Apply to confirm your new settings.
Restart the ROCK (make sure Roon Server is stopped) and let me know if you continue to experience stoppages when streaming
Same here - sometimes. Changing DNS from cloudflare to google to Provider (vodafone) always helps, but only for a while. I have done that DNS circle several times now, it is quite interesting that changing one to the other of the above immediately helps to listen music for the day or even some days. But sooner or later the Tidal problem comes up again. Location is near Cologne, Provider is Vodafone (ex Unitymedia) and I am sure that I don’t have in house network problems. Problem has to do with DNS somehow.
Thanks for the additional context — this is helpful.
Based on similar cases and what we typically observe in diagnostics, this behavior is very unlikely to be caused by DNS itself.
The fact that switching DNS providers (Cloudflare → Google → ISP) temporarily improves playback is a strong indicator of a CDN routing issue, not name resolution:
DNS changes can cause your connection to be routed to a different TIDAL CDN edge.
Depending on how your ISP (in this case Vodafone / ex-Unitymedia) handles routing and peering, some CDN paths can be unstable, congested, or intermittently unreachable.
When Roon encounters packet loss, high latency, or stalled HTTP responses from the CDN, playback may stall and skip with a generic “network error,” even though local bandwidth and LAN connectivity are fine.
This also explains why:
Local network tests look healthy
Internet speed is sufficient
The issue appears and disappears without any local changes
DNS changes help only temporarily
In short: DNS is just influencing which CDN endpoint you hit — it is not the root cause.
The underlying issue is most likely how the ISP is routing traffic to TIDAL’s CDN at a given time.
We don’t see anything in this report that points to a ROCK issue or a regression introduced by the recent Roon update.
If the issue resurfaces consistently, the most effective long-term resolution usually comes from the ISP side (routing/peering), not from repeated DNS changes.
We’ll keep monitoring for patterns on our end, but at this point there’s nothing further to adjust within Roon itself.
Thank You for the explanation, well understood I think… So clearly, if the Problem keeps ongoing, either the ISP (Provider) has to be changed (which is no possible option for me unfortunately) or to cancel roon and to listen via Tidal connect or Spotify connect directly. Both doesn’t satisfy me, I’ll keep watching the issue for a few month from now, but if the problem still occurs in future my options are limited.
Unfortunately, it’s exactly the same for me. I’m with the same provider, Vodafone (formerly Unitymedia), here in Hessen. It’s really unfortunate because these issues keep happening over and over again
Hi all, I have exactly the same problem and tried all the measures mentioned in this thread, with the same dissatisfying results. Provider is as well Vodafone Cable (1Gbit) in Cologne, Germany. Not happy to hear that nothing can be really done about it.
Cheers, Frank
Thanks for the detailed report - we’ve reviewed the information you shared and the context of the discussion here.
Based on similar cases we’re seeing, this behavior is not caused by ROCK itself or by a recent Roon update. Your local network setup and available bandwidth appear to be sufficient, and there’s no indication of a hardware or Core performance limitation.
What’s most likely happening is an intermittent connectivity issue between your ISP and TIDAL’s CDN endpoints. When this occurs, Roon may temporarily lose access to the stream, which can result in skipping or “network error” messages during playback.
You may notice that changing DNS servers (for example, to Google or Cloudflare) can sometimes improve the situation. This doesn’t fix the root cause, but it can result in your connection being routed to a different TIDAL CDN node, which may be more stable. For this reason, DNS changes can appear to help temporarily.
At this point, we recommend:
Continuing to monitor whether the issue is consistent or intermittent
Testing playback at different times of day
We are also keeping an eye on similar reports to see if any broader patterns emerge.
Thanks for your patience, and please let us know if anything changes or if you can capture logs during a failed playback attempt - that can help us confirm the behavior.
During the last few weeks there have been several threads asking for delays and track drop downs with TIDAL in this forum. Behaviour of roon sounds very similar to what we have here, but many of the users are in other countries and certainly not customers of Vodafone / Unitymedia Germany. So, just guessing: It could also be server issue of Tidal CDN itself? In this case only option for end users might also be “wait and see” . But there might be more hope that Tidal / Roon can fix it than I have with Vodafone as ISP to work on this topic.
I have Wappen Tidal against Qobuz (Test Abonnement) now and no Problems at all with the otherwise Seminar Setup. So clearly, this is a Tidal/Roon Problem. Hope they will fix it soon.
Vodafone has recently had performance and routing problems all over Germany. Just FYI. You might consider opening a case with Vodafone and have them test your connection.
Thanks for the info. But I never have any playback issues with Tidal Connect or any movie streaming service. Just the combination of Roon and Tidal.currently listening to a playlist. Almost every second track is aborted and it jumps to the next. Not a pleasure to listen to…the files from the NAS play flawlessly.
I can try with Vodafone, but I guess it will be fruitless. As all other apps have no issue, they will disregard my request.
If this will not be resolved, I have to cancel my subscription to Roon, although I like it a lot otherwise.
Now I have to correct some things. Currently Tidal has the same problems with Connect and playing from the BluOS App. So It looks like a Tidal problem. I also found a thread on Reddit where users complain that around since a month they see these issues with Tidal.
I am now testing Qobuz in Roon. Not a single dropout. Let’s see what happens.
Same here. After experiencing Vodafone/Tidal routing issues (which is most likely the cause of the problem) for weeks, I have now started a Qobuz trial subscription without any problems so far. Appears to be a reasonable workaround.
I did some more research and found two issues that might have caused the whole situation.
In another thread I read an issue with BluOS that I checked as well (I have the Nad C658 and a Pulse Mini). In BluOs I still had a NAS registered for my media library that I don’t have anymore. According to the other Thread this can cause disruptions as the BluOS devices try to sync with that NAS but can’t find it anymore. I deleted the entry.
In Roon I had set the re-indexing of the current NAS to 4 hours, which is not necessary, as I add new files only two to three times a year. I have set it to the longest interval, which is 24h.
After applying these two things the system runs totally smooth independent whether it’s Tidal or any other source. If it stays that way, I am happy. So it seems in my case it was not a Vodafone/ Tidal issue.
I just was surprised how complex these things are.
Maybe check these things as well with your system and it’s fine then.
Cheers,
Frank
