Tidal music won't play via Nucleus, possible network damage (ref#9T41DF)

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *All of my Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Only streaming* music is affected.

Please select the streaming service(s) with which you're encountering playback problems.

· TIDAL

Have you tried logging out and back in again to your streaming service in Roon Settings?

· Logging out and back in had no impact, the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· Thunderstorm was around 12:30 PM EDT, 7/3/25

What are the make and model of the affected audio device(s) and the connection type?

· Various playback devices showing similar problem.

Describe the issue

Music doesn't play when streaming music from Tidal using my Nucleus, to any of my network playback devices, including iPhone over WiFi. All devices connect to Tidal fine, and show album art, etc., and I can select an album and track to play, but it doesn't start. Roon app on my desktop is showing a blue line sliding back and forth across the track time bar after I hit Play. Nucleus-stored music library plays back fine. I may have incurred damage to the Nucleus network connector during a thunderstorm the other day. If this is so, can I replace the network connector on my Nucleus, or how otherwise can I get it repaired? Thanks!

Describe your network setup

Ubiquity router, Luxel network switches, playback devices include HP desktop, Cocktail Audio streamer/DAC, Onkyo reciever, iPhonesd, Sonos.

If you’re able to playback locally store music over your network, then it’s unlikely the Nucleus Ethernet port at fault.

Maybe detail how your audio equipment integrates with the Nucleus.

I’d try rebooting everything from the router to endpoint and everything in between. Allow for each item to come back on fully before rebooting the next.

Hello @Peter_Carlson.

The issue that you describe may be related to the DNS resolving 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.

  1. 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 Nucleus.
    • Note the IP address shown for the Nucleus.
  • Alternatively, use http://nucleus.local/ (on macOS or Windows with Bonjour installed).
  • Log into the Web Interface:
  1. 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.
  1. 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 Nucleus (make sure Roon Server is stopped) and let me know if you continue to experience stoppages when streaming

I have previously set up a static IP address for my Nucleus because I use ARC. I suspected I had a network problem after a bad thunderstorm the day the music died (!). Anyway, I bought and installed a new network switch today through which the Nucleus runs and viola! All good for now here. Thanks for your response!

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