Roon Remotes Not Able to Find Core on NAS

Hello, I powered down my NAS where Roon is installed while away for vacation. I returned to reboot and I can “see” my Roon Core on my NAS from a PC directly wired to the network. The Roon Remote on that PC and all other wifi Roon Remotes are unable to find the Roon Core. I’ve rebooted my NAS twice along with the Roon Control devices.

Through the system below, I can access my NAS files and Roon Core via my imac. But, again, none of my roon remotes connected to the same Google Home router says, “Waiting on Roon Core.”

  1. Operating System:

Roon Server - NAS Linux 4.4.59.

Roon Remote: iMac ethernet to network OS Monterey 12.6.3

  1. Firewall status: None

  2. Network connection

IP address via iMac to Google Home to nas synology server - home of roon core

Network configuration:

  1. Network hardware Google Home Router to switch, with both my remote (imac) and roon core (NAS) connected to the same switch. Zero change in hardware since before reboot of NAS.

I am not aware of any Fidelizer plugin on macOS being used.

I can access any log files to send for detail. It’s been YEARS since I’ve had an issue connecting to roon core that a rooboot of everytihng didn’t fix. I’m at a loss.

Thank you.

Try turning off everything including your routers and switches, and power on again starting with ISP router first, followed by switches etc.

Thank you for the reply. I performed a cold reboot in the sequence described and the result is the same.

I can still access files on Roon server over the network but am unable to get any of the Roon Remotes to connect to the Roon Server.

Thanks for trying this, @ROBERT_D_SMITH. I’m a fellow community member, and unfamiliar with Roon core on a NAS, so cannot offer further assistance. I’ll amend the thread title, as this may attract NAS users.

Roon support will pick this up in due course.

1 Like

Have you tried ‘Select a different Core’. I have two cores on two different QNAP NAS, each with their own license. So depending upon where I am, I get the same display you see and I have to ‘Select a different Core’ on my remote to display the core that is available and then I can connect to it by selecting ‘Connect’ on the remote.

Thanks, but I only have the one Core which has been working on the same network and NAS for years with no issues (even after power outages and other types of system reboots).

If you Select a different Core, it will show you what the core address is and you can select Connect.

1 Like

Okay, I’m a wimp. I started that path until I saw this.

Sorry that I forgot to mention that, but since you only have one Core, it will be fine. Once you click YES and then Connect, you will be all set.

@ROBERT_D_SMITH, there may be one other area to check. The latest Roon updates require that the Core and all Remotes be on the same version (Build) number. The current version for the production release is Build 1259. Given you have been offline for a month, your Core may be at an earlier version compared to any Remote trying to access the Core. Updates may be necessary on the Core and each Remote.

1 Like

Thank you. I was only offline for a few days. Given a lightening strike next to my home a few years back that took out random stuff in my house, I unplug critical (read expensive, ha) items if I’m out of town even for a few days.

How do I update the core if I can’t access it via a remote?

Thanks again.

Similar to what @mjw, I am a volunteer and do not have experience with a Core running on Linux or a Linux NAS. As a first step, you wrote:

Can your iMac Remote connect to your Core? If so, can you check the version of Roon on the Core and on your iMac?

Has the IP address of your NAS changed? My NAS has a static IP address, so accessibility doesn’t change after power cycling.

1 Like

@mjw No, sorry. I can connect to my NAS and Roon Core SSD drive from my iMac via ethernet. In other words, I can see all of the files on the NAS and Roon Core and even copy to and from those drives. They’re active. But, when I launch Roon Remote on that same iMac I get the “Waiting for Roon Core” screen.

I can also confirm the ability to see the NAS on the Google Home app on my iPhone.

@Stephen_Horvath, I have the NAS set to a static IP address. Could it have changed somehow during the reboot? I’m not sure. I can see its IP address via the Google Home network app, but I have no idea what the IP address was prior to the reboot.

Thanks.

First I would verify the Core and remote builds are the same as @ROBERT_F stated. If they are correct, I would try the Select a different a Core process, you won’t hurt anything.

1 Like

Here is some additional information to help troubleshoot.

  1. I was looking over the Roon RAAT log and the IP address of the NAS is unchanged (was able to find last IP address logged in RAAT files and it matches the NAS’s current IP address.

  2. I have six Roon Remotes through the house:

Wifi: macbook, iPhone, iPad
Ethernet: iMac and two Windows based machines.

None of the remotes connected to the same network can connect to the Roon Server. If there is a mismatch of software versions, I’d assume at last ONE of my remotes is on the same version as what’s on the Roon Core. I use Roon at least 3-4 days / week for 8-12 hours of music.

My NAS was only booted down for two days.

Just an obvious, possibly dumb question - is the Roon core service on your NAS running?

3 Likes

@Graeme_Finlayson , I had no idea what “Package Center” was let alone programs could be stopped and started.

Once Googled helped me link “Package Center” to my NAS OS, I opened it and found out Roon was, in fact, not running.

Thank you so very much! All is well with Roon and streaming. Whoot whoot!!!

2 Likes

Ah, that’s great news. I couldn’t imagine my life without Roon!

1 Like

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