Nucleus One becomes unresponsive, requiring power cycle to regain access (ref#VCYXCR)

Select your Nucleus model from the list below

· Nucleus One

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices

Describe the issue

A couple of minutes ago music stopped playing on my Naim Uniti Atom. The Roon App on my iPad could no longer connect to Roon Server (running on Nucleus One). The web interface (http://nucleusone.local/) was no longer accessible. Ping did work. I had power cycle the Nucleus One in order to get it back up. Unfortunately this was not the first time this happened. Any hints what to do in order to avoid this in the future?

Hi @Oliver_Stettner

Thank you for reaching Roon support. We have enabled the diagnostic mode on your account.

After reviewing your logs, we can confirm what happened: the Roon Server process ran into a memory pressure situation caused by a large metadata processing task that ran in the background while playback was active, eventually making Roon completely unresponsive — while the network stack (and ping) continued to work normally, since that runs at the OS level.

This is a known issue that our engineering team is actively working on. A fix is targeted for an upcoming release.

In the meantime, if this happens again, please try the following steps in order:

  1. Reboot the Nucleus One — power it off, wait 10 seconds, and power it back on.
  2. Reboot your network devices — router and any switches, then let everything reconnect.
  3. Restart your Roon Remote apps — close and reopen Roon on your iPad and any other remotes.

If the remotes still fail to connect after that:

  1. Uninstall and reinstall Roon on one of your remotes (e.g. the iPad), then try connecting again. This clears any stale session state on the client side.

We apologize for the inconvenience and appreciate your patience while we work on the permanent fix.

Thanks Vadim. I will wait for the next release.