Roon and Qobuz issues with Innuos server causing playback and connectivity failures (ref#8ODOCV)

Support
1

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Looking for your Roon Server"

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *Prebuilt Branded Roon Server* (SonicTransporter, Innous, Merging...)

Select any of the following components that are present in your local network setup

· *Mesh networks*

You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.

· Orbi

Click below for next steps with an Orbi mesh network.

· I still need help.

Describe the issue

Roon + Qobuzz only played songs for 4 seconds, I tried to log in and out of my Innuos Roon Server. Cannot connect any more.
Qbuzz and Bluesound still work. Roon only shows logo.

Describe your network setup

Worked in this config until recent. Did not change anything. Innuos mini MKIII server on ethernet, NAD C368 incl dig Bluesound streamer mod + NAD Pulsesestreamer on ethernetnet to

2

Hello @Gerard_van_der_Poel,

Welcome back to the community! I am sorry to hear you are dealing with these playback and connectivity failures.

To give you some context on what is happening: tracks skipping or stopping after 4 seconds typically indicates that the server is struggling to maintain a stable connection to Qobuz to buffer the rest of the file. However, the fact that you are now completely stuck on the Roon logo (“Looking for your Roon Server”) after attempting to log out means the Roon Server background process on your Innuos Mini MKIII has likely crashed or hung at the system level.

Here is the best path forward to get this resolved:

Step 1: The Full Hardware Reboot

Sometimes a system-level hang just needs a hard reset to clear the network cache and reboot the background services.

  1. Completely power down your Innuos server, your Orbi router (and any satellite mesh nodes), and your NAD/Bluesound endpoints.
  2. Unplug them from power for about 2 minutes.
  3. Plug the Orbi router back in first and let the network fully establish.
  4. Power on the Innuos server, and finally, turn on your audio endpoints.

Step 2: Contact Innuos Support

If Roon still hangs on the “Looking for your Roon Server” screen after a full physical reboot, it means the Roon service within the Innuos operating system is still failing to initialize.

Because Innuos uses a custom, proprietary operating system to manage the Roon Core alongside their own Innuos Sense software, Roon Labs does not have direct access to troubleshoot their OS-level services or permissions. You will need to reach out directly to Innuos support. They have the internal tools to check the system logs on your Mini MKIII and can determine exactly why the Roon process is refusing to start on their hardware.

Please let us know how the reboot goes and what the Innuos team suggests!

3

Many thnx for the quick and effective help Vadim!

The hard reset seems to work. It reastablished the connection to my Roon Server.

For now I can only play music via Airplay, and not via Raat, but that’s something I solved myself in the past..

Happy to have my music playing again!

All the best,

Gerard