After Power Outage Can't Find Roon Core

Support Nucleus Support
1

Roon Core Machine

Windows 11

System Model Vostro 3671
System Type x64-based PC
System SKU 0993
Processor Intel(R) Core™ i7-9700 CPU @ 3.00GHz, 3000 Mhz, 8 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.10.0, 3/18/2022
SMBIOS Version 3.1
Installed Physical Memory (RAM) 16.0 GB

Roon Nucleus
Starting Roon v2.0 (build 1211) production on windows

Networking Gear & Setup Details

AT&T Broadband → UpTone Audio Etherswitch - > Roon Nucleus → Wyred4Sound DAC2DSD SE Dac →

Connected Audio Devices

Roon Nucleus → Wyred4Sound DAC2DSD SE Dac → Wyred4Sound STP SE Preamp → PSAudio Stellar M1200

Number of Tracks in Library

18K+ Tracks in Library on a USB 8TB Drive locally attached to Nucleus

Description of Issue

After a Power Outage my Roon Nucleus could not be accessed. I’m able to ping it successfully but can’t access the core.

Microsoft Network Troubleshooting tool stated the device is refusing connection.

I disconnected power from the Nucleus and the Etherswitch and still couldn’t access the Roon Core. I then tried replacing the network cable and that made no difference. The logs last few lines stated the following:

02/23 18:56:37 Debug: [easyhttp] [13] POST to https://discovery.roonlabs.net/1/query returned after 156 ms, status code: 200, request body size: 140 B
02/23 18:56:38 Debug: [easyhttp] [15] POST to https://discovery.roonlabs.net/1/query returned after 368 ms, status code: 200, request body size: 74 B
02/23 18:56:52 Info: [stats] 5348mb Virtual, 224mb Physical, 32mb Managed, 1394 Handles, 59 Threads
02/23 18:57:01 Debug: [easyhttp] [16] POST to https://discovery.roonlabs.net/1/unregister returned after 157 ms, status code: 200, request body size: 61 B
02/23 18:57:01 Trace: [inetdiscovery] unregistered 1 devices
02/23 18:57:02 Trace: [upnp/service] canceling subscription, URI: http://192.168.86.1:5000/evt/IPConn

IP address 192.186.86.1 is the admin login for my Google Nest System not Roon.

I renamed the Roon and Ratserver directories to old to try to reload a new copy of the Roon Software and it didn’t work. The last lines of the log file stated the following:

02/24 10:22:32 Debug: [easyhttp] [103] POST to https://discovery.roonlabs.net/1/query returned after 159 ms, status code: 200, request body size: 74 B
02/24 10:22:46 Info: [stats] 5363mb Virtual, 52mb Physical, 32mb Managed, 1439 Handles, 59 Threads
02/24 10:23:01 Info: [stats] 5363mb Virtual, 52mb Physical, 33mb Managed, 1439 Handles, 59 Threads
02/24 10:23:01 Debug: [easyhttp] [104] POST to https://discovery.roonlabs.net/1/query returned after 391 ms, status code: 200, request body size: 140 B
02/24 10:23:02 Debug: [easyhttp] [105] POST to https://discovery.roonlabs.net/1/query returned after 121 ms, status code: 200, request body size: 74 B
02/24 10:23:06 Debug: [easyhttp] [106] POST to https://discovery.roonlabs.net/1/unregister returned after 157 ms, status code: 200, request body size: 61 B
02/24 10:23:06 Trace: [inetdiscovery] unregistered 1 devices
02/24 10:23:06 Trace: [upnp/service] canceling subscription, URI: http://192.168.86.1:5000/evt/IPConn

Any help would be appreciated.

John Lee

2

Hi John. Just another user here. Can’t assist with your issue, but would recommend that you remove your email address from your post as it is not recommended.
Anyone that can assist will reply direct to your post which will then get notified to you. Cheers.

2 Likes
3

Does the browser find the admin web interface using http://ip-address-like-you-use-in-ping ?

4

I received a refused to connect message the same as the Microsoft Network Troubleshooting found.

5

ERR_CONNECTION_REFUSED? Site can’t be reached? Are we sure the IP is correct?

6

This might sound silly but have you tried restarting the network one piece at a time?
Sometimes a clean sequential reboot starting at the ISP end (modem->router->switches->devices) helps.
Especially when a network/device was shut down unexpectedly, they don’t always “let go” of previous IPs and need a fresh start to negotiate a good connection.

7

Turned off and disconnected all network devices going to Roon. Turned them back on in the following order:

AT&T Broadband → UpTone Audio Etherswitch → Roon Nucleus.

Roon Core still could not be found.

I was able to select the local PC as my Roon Core which first prompted me to unauthorize the Roon Nucleus.

I had to Unauthorize the Roon Nucleus to set the Roon Core on my Local PC. I then unauthorized the local PC with the expectation Roon setup software would be able to now find the Roon Nucleus to be able to reload the core there. Again, find the Roon Core didn’t find the Roon Nucleus.

I don’t want to use my PC as the Roon Core as it is not setup to interface with my Stereo System.

8

I did an arp-a to list all my IP’s on my home network and the IP address for the Roon Nucleus was there.

I then went to the AT&T Broadband Modem and had list out the home devices

A device entitled Rock was using the address for the Roon Nucleus I’ve always used for it. I’m assuming Rock stands for Roon Nucleus.

9

I am surprised. ROCK stands for Roon Optimized Core Kit and is the self-install Roon OS version for regular NUCs. It identifies as “rock” on the local name service. E.g., the web admin page is http://rock and the internal storage is accessible as smb://rock.

In contrast, the web admin page for a Nucleus by default is http://nucleus and the the internal storage smb://nucleus, so clearly it is known as “nucleus” on the name service, e.g.,

image
image1214×650 57.8 KB

The name as such should not matter but I am surprised that yours identifies itself as “rock”.

10

Unrelated side note: people will click on anything …

image
image1429×164 30.2 KB

11

No and I know I’m using the right IP address. I can ping the address for the Nucleus successfully. When I remove the lan connection from the Nucleus the destination is unreachable until I plug the lan cable in.

12

Sorry for the distraction, please ignore the last post. I was just laughing because 3 people had clicked on the example address from my earlier post

To the point
I am still more intrigued by your Nucleus identifying as “rock” on your router. Can you navigate to http://rock in your browser, or http://nucleus, or neither?

13

I can’t open the Core what is accessing data storage going to do, if I can’t even open the core?

14

My point is that it seems unusual that your Nucleus identifies as “rock” on your router because all the documentation says that it should identify as “nucleus”. The screenshots from the documentation I posted were intended to demonstrate this. I thought my words had made this clear, apologies if not.

As the router knows it as “rock”, it should normally be accessible with http://rock in a browser. Therefore my question if you can you maybe navigate to http://rock in your browser, or http://nucleus, or neither?

May be pointless questions, but something is wrong and nobody knows what, so trying a few things may give us more hints. (Unless you want to do it on your own and not be bothered, in this case please let me know and I will stop trying to help and leave)

15

Same result I would get by just using the IP address

This site can’t be reached

nucleus’s server IP address could not be found.

Try:

ERR_NAME_NOT_RESOLVED

Same result for rock

16

Sorry, we have to be precise here:

When using http://nucleus, you get ERR_NAME_NOT_RESOLVED as per your screenshot. This means the router does not know the “nucleus” device name in its name service.

It remains weird that your Nucleus does not identify as “nucleus”, but we will have to accept this for now. As you wrote above, “a device entitled Rock was using the address for the Roon Nucleus I’ve always used for it”, and as that’s what it is, it is not surprising that “nucleus” is not known to the router.

However, when you use http://rock, do you really get the “same result for rock”, i.e. ERR_NAME_NOT_RESOLVED, or do you get ERR_CONNECTION_REFUSED or something else?

Another question: What is the IP address that you use for pinging the Nucleus?

17

This site can’t be reached

rock took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

The IP is 192.168.1.66

18

This site can’t be reached

192.168.1.66 refused to connect.

Try:

ERR_CONNECTION_REFUSED

19

OK, two different errors for this one, ERR_CONNECTION_TIMED_OUT in the first post and ERR_CONNECTION_REFUSED in the second. Also a bit weird but oh well, not sure what to do with this for now.

I find the IP address more interesting, 192.168.1.66, while your Google Nest admin login is 192.168.86.1

This may be fine or not, so another question: Is it intended that the Nest and the Roon core are on different subnets, i.e., 192.168.86 vs 192.168.1 ?
It may well be intended, but I’d like to rule out that different devices unintentionally ended up on different subnets because in this case this could affect connecting to Roon if it’s not on the subnet you expect it on

20

Google Nest Is accessed through Wifi, Roon is on Ethernet.