Unable to connect to Roon with remote or desktop version (ref#XK6WT8)

Support
1

Hi! What’s not quite right with Roon?

· Roon is slow, freezing or won’t start

Roon is slow, freezing or won’t start

· Roon won’t start up at all

Tell us what's going on

· I cannot connect to Roon with either a remote or the desktop version of Roon. I can see the Roon Server at RAATServer (\\DESKTOP-05LGLE4\Users\geoff\AppData\Local)(Y:) but a connection is never made.

Tell us about your home network

· Router is a Fritz!box 7530AX. (192.168.178.1)
There are network switches at 192.168.178.32 & 192.168.178.48

2

Hi @Geoff,

What are you using as your Roon Remote? Is this affecting multiple Remotes, or just one in particular? For example, is a PC able to connect?

3

Hello Noris,
Thank you for the reply which is appreciated. I regularly have used my smart phone to connect to Roon but did have the option to use my networked PC. Neither now connect.
However I found yesterday that the network extender probably used by my phone has developed a fault. I shall be setting up some other form of access for the smart phone over the weekend and will get back to you.
Regards,

Geoff

4

Hello again,
I have been investigating and it seems the network extender that previously worked is now defective. I have an ethernet connection to the Nucleus and I should be able to use this with the Roon desktop version. However i have been encountering problems removing Roon remote (aka Roon desktop).
I have now attempted to test the Roon connection and here are the results:

  1. I am trying to connect to the Nucleus via a network switch which shows only one green light on the ethernet socket. The incoming long distance ethernet cable (17m to the switch) is showing two green lights and has been tested multiple times with an ethernet tester. An App called Advanced Network Tester tells me my Nucleus is dead but it has been tested and run by the Meridian agent who sold it to me.
  2. For now my only option to connect to the Nucleus is with Roon Desktop (aka Roon Remote Server) and this I have downloaded . When I try to install Roon desktop, as normal or as administrator I repeatedly get told to remove all instances of Roon server.
    3. Is there any advice on removing a previous version of Roon desktop or Roon remote?
5

I need to add that I have spent considerable time trying unsuccessfully to remove an old version of Roon desktop. I get told that first I must remove Roon itself from my PC.
Roon desktop and Roon do not exist as far as I can determine on my PC.
What should I do?

6

@Geoff ,

If you want to move your Roon Server to your Windows machine please make sure first to confirm Nucleus’s state.

Please connect it directly to the router without intermediary switch and check if you can connect to it like that.

If it is unreachable then please remove it and proceed to PC cleanup.

In this article you can see what folders are used on windows machine for Roon Installation.

please make sure to clean them up and then download Roon and install from here :

.

Let us know please if it runs afterwards.

Thanks.

7

Thanks alex, I believe I have successfully followed your advice and this is what I came upon.

8

Hi Alex, I have followed your instructions. Here is what I found at the point where you want me to “proceed to PC clean up”. Bearing in mind that all that you see is on my PC C:/ drive which should I delete and which should I clean up? I am proceeding to run Roon Nucleus Plus from hopefully my PC but otherwise my mobile.

image
image374×190 4.75 KB

9

Hello again Alex, I do not primarily wish to run Roon from my PC (though this could be a fall back) and have established that the main reason I am unable to connect to my Nucleus Plus is the failure of a network extender. I do need to clean up my PC hard drive, install the replacement network extenders that are in the post and hopefully resume playing music.
Please can you provide detail on cleaning up my PC.

Regards,

Geoff

10

Hello Alex, I primarily wish to run Roon from my mobile, the PC was just a temporary fall back that has previously worked but now does not.

I have now installed new network extenders for connection to the Nucleus Plus but cannot connect to it with my mobile. On the screen shot of my C: drive above you can see Roon, RoonGoer and Roon Server. Please can you advise what actions I should take to clean up my C: drive.

Regards,

Geoff

11

Hello Alex,

image
image596×410 9.47 KB

12

Hello, I have downloaded Roon for Windows with the Nucleus connected to the router. I tried to get it to run with windows but there was no response.

Regards,

Geoff

13

Hello,
I am using a Pixel mobile as my remote. It has worked numerous times previously.

Regards,

Geoff

14

Hello @Geoff,

Thank you for the updates and for providing those screenshots. Network issues can be a real puzzle to untangle, but let’s get your system back on track. Looking at your setup and the images provided, there are a few things we need to correct to get you connected again.

1. The Network Extender

First, regarding the faulty network extender: we strongly advise against using Wi-Fi extenders with Roon. They frequently block the specific multicast traffic Roon relies on to discover devices, or they place devices on a different subnet entirely. For a stable system, your Roon Nucleus must be connected directly to your main Fritz!box router using an Ethernet cable.

2. The Mapped Network Drive

I also need to clear up a misconception regarding the screenshots you shared. Seeing the RAATServer (\\DESKTOP-05LGLE4\Users\geoff\AppData\Local)(Y:) drive does not mean you have successfully connected to your Roon Server.

That image merely shows that you have mapped a local Windows folder from a PC on your network as a network drive. Roon’s architecture does not operate through mapped Windows folders like this, so this connection isn’t actually talking to your Nucleus.

Next Steps: Testing the Nucleus

To figure out why your remotes cannot find the Core, we need to verify that your Nucleus is actually booting up properly and receiving an IP address from the Fritz!box.

Please try these two steps:

  1. The HDMI Test: The most definitive way to see what the Nucleus is doing is to plug it directly into a TV or computer monitor using an HDMI cable. Turn the Nucleus on and let it boot. Please take a clear photo of the text that appears on the screen and post it here. This will immediately tell us its IP and operating status.
  2. The Web UI: If you know the previous IP address of your Nucleus, try typing that address directly into a web browser on a device connected to your main router. Does the Roon Web Administration page load, or do you get an error?

We will watch for your reply with the HDMI photo!

15

Hello Vadim,

Thank you for a most useful reply. I have tested the Nucleus plus connected directly to the main house router. I have taken photos of the Nucleus on test as you requested connected by HDMI cable to the main and only router. Here is a link showing general arrangements of the test setup as well as an IP scan of our home network and a shot of the network page of our router.=> https://photos.app.goo.gl/u2Ki15JC71mz64DAA

There seems to be something very wrong. The Nucleus output, both HDMI A & B, is connected to a screen by an HDMI cable as you can see. You can also see (Light on) that the Nucleus was powered on with its normal 19V DC power supply. The screen connected shows no signal is being received. This is most strange as I sent the Nucleus to the company from which I bought it for test. The company is Audio Images in Sheffield UK. The owner, Rick, tells me that it worked fine, so I am really mystified. During test, the Nucleus was connected to the main router alone, with an HDMI cable. I have verified that I was logged on to Roon Labs.

In response to your various points:

  1. I do not and never have used Wi-Fi for signal delivery to the Nucleus. As I write the Nucleus is now re-connected directly to the router using a well screened Cat 6A 4pr F/FTP cable. Wi-fi does not work in this building because of the thickness of the old stone walls. The reason for Wi-Fi is to connect my phone to the network for controlling Roon (I used to use an iPad), connecting to Google door bells and finally connecting via ethernet and possibly to a Google TV streamer. The connection from the Nucleus to the stereo amplifier is via a Meridian 218 zone controller over ethernet.

2. The faulty network extender (we have three in total) has been replaced because we need such devices as described above. I could make sure it is not on the same ethernet extension as any Wi-Fi device or remove it altogether.

3. I note what you say about Wi-Fi devices. Are you saying that I must remove them altogether, if only for test purposes? They are already on separate ethernet extensions. It would be helpful to know under what conditions Wi-Fi is permissible. Importantly, it is a fact that people all over the world make frequent use of Wi-Fi devices of many different types and designs. If Roon equipment cannot live with this then you have a problem!!! Perhaps you can propose an alternative. My near term intention is to change this network to optical fibre and this may deliver an improvement.

4. I have scanned my network and can see an allegedly dead Nucleus Plus. You should be able to see this on the router network scan I also have uploaded.

5. You asked for old IP Nucleus locations. You will find a further scan uploaded showing our network in the above folder. I shall be visiting these and all other Nucleus locations I am able to recollect and will advise the outcome. Our router does record such locations, but how exhaustively I don’t know.

Very Best wishes and thanks again,

Geoff Owens

16

Hello Vadim,

I have just searched my PC using the string 192.168.178.52. This is where my advanced IP scanner thinks my Nucleus lives. I scrolled the right hand window to the bbottom so you could see the latest status. This is what I got:

image
image1144×823 63.6 KB

17

Hello Vadim,

I believe I have found the IP address of my Nucleus which is 192.168.178.52 by scanning my PC. I checked this by connecting to the 192.168.178.52 IP address with file explorer in Windows. If you look at the previous screen shot I sent it is in the top right hand corner.

The Nucleus is still connected directly to our router where I plan to leave it. What is the next step?

Regards,
Geoff

18

Hello Support,
i ama ble to connect to hte

19

Hello Support,
Here is the latest log from my Nucleus Plus. I am unable to get it to boot up.

04/23 18:18:46 Info: Starting RAATServer v2.64 (build 1646) production on windows
04/23 18:18:46 Info: Local time is 23/04/2026 18:18:46, UTC time is 23/04/2026 17:18:46
04/23 18:18:46 Trace: \[bits\] myinfo: {“os”:“Windows 11”,“platform”:“windows”,“machineversion”:206401646,“branch”:“production”,“appmodifier”:“”,“appname”:“RAATServer”}
04/23 18:18:46 Debug: \[easyhttp\] \[1\] POST to https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery.,roon.raatserver. returned after 455 ms, status code: 200, request body size: 129 B
04/23 18:18:46 Trace: \[bits\] updated bits, in 482ms
04/23 18:18:46 Info: \[RAATServer\] creating RAAT__manager
04/23 18:18:46 Info: \[RAATServer\]     appdata_dir  = C:\\Users\\geoff\\AppData\\Local\\RAATServer
04/23 18:18:46 Info: \[RAATServer\]     unique_id    = 479fe974-bc84-48b4-b3c2-c67bf620ac9d
04/23 18:18:46 Info: \[RAATServer\]     machine_id   = d7f04eb6-3412-8d04-117a-2312aba1bcbb
04/23 18:18:46 Info: \[RAATServer\]     machine_name = DESKTOP-05LGLE4
04/23 18:18:46 Info: \[RAATServer\]     os_version   = Windows 11
04/23 18:18:46 Info: \[RAATServer\]     vendor       =
04/23 18:18:46 Info: \[RAATServer\]     model        =
04/23 18:18:46 Info: \[RAATServer\]     service_id   = d7634b85-8190-470f-aa51-6cb5538dc1b9
04/23 18:18:46 Info: \[RAATServer\]     is_dev       = False
04/23 18:18:46 Trace: \[raatmanager\] starting
04/23 18:18:46 Info: \[raatmanager\] added codesigning key keypair_name=Roon public_key=9bb28e4e9e34ed4ff75c6a35339497cbdd3420713c941f5468571afc03555bf7
04/23 18:18:46 Trace: \[raatmanager\] \[System Output\] loaded config from C:\\Users\\geoff\\AppData\\Local\\RAATServer\\Settings\\device_9b961fc2035f3dd343e04f8f136e7682.json
04/23 18:18:46 Trace: \[raatmanager/windows\] FOUND type=wasapi id={0.0.0.00000000}.{e6e72a4f-3449-4f83-9280-965dda1441c3} usb_id=
04/23 18:18:46 Trace: \[raatmanager/windows\]       name=Realtek(R) Audio               output_name=Speakers
04/23 18:18:46 Trace: \[raatmanager/windows\] FOUND type=asio   id={A80362FF-CE76-4DD9-874A-704C57BF0D6A} usb_id=
04/23 18:18:46 Trace: \[raatmanager/windows\]       name=Realtek ASIO                   output_name=
04/23 18:18:46 Trace: \[raatmanager\] \[Realtek(R) Audio\] loaded config from C:\\Users\\geoff\\AppData\\Local\\RAATServer\\Settings\\device_d66310b54dc230bd66fac55c08019f18.json
04/23 18:18:46 Trace: \[raatmanager\] \[Realtek ASIO\] loaded config from C:\\Users\\geoff\\AppData\\Local\\RAATServer\\Settings\\device_b70c925ce84267f9ff112e2a832ce419.json
04/23 18:18:46 Trace: \[raatmanager\] initialized
04/23 18:18:46 Info: \[RAATServer\] running RAAT__manager
04/23 18:18:46 Warn: \[raatmanager\] update_bits, json string: {}
04/23 18:18:46 Trace: \[raatmanager\] starting discovery
04/23 18:18:46 Trace: \[discovery\] starting
04/23 18:18:46 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:18:46 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:60136
04/23 18:18:46 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:18:46 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:60137
04/23 18:18:46 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:18:46 Trace: \[raatmanager\] starting server
04/23 18:18:46 Info: \[jsonserver\] listening on port 9200
04/23 18:18:46 Trace: \[raatmanager\] announcing
04/23 18:18:46 Debug: \[discovery\] broadcast op is complete
04/23 18:18:47 Trace: \[servicemanager\] added device raatserver/479fe974-bc84-48b4-b3c2-c67bf620ac9d in addr:**ADDR**
04/23 18:18:47 Trace: \[servicemanager\] added service com.roonlabs.raatserver.tcp for device raatserver/479fe974-bc84-48b4-b3c2-c67bf620ac9d
04/23 18:18:52 Trace: \[ipaddresses\] enumerating addresses
04/23 18:18:52 Trace: \[ipaddresses\]    FOUND   Ethernet 192.168.178.58
04/23 18:18:52 Trace: \[ipaddresses\]    SKIPPED Wi-Fi: not up
04/23 18:18:52 Trace: \[ipaddresses\]    SKIPPED Local Area Connection\* 8: not up
04/23 18:18:52 Trace: \[ipaddresses\]    SKIPPED Bluetooth Network Connection: not up
04/23 18:18:52 Trace: \[ipaddresses\]    FOUND   Loopback Pseudo-Interface 1 127.0.0.1
04/23 18:18:52 Trace: \[ipaddresses\]    SKIPPED Teredo Tunneling Pseudo-Interface: no ipv4
04/23 18:18:52 Debug: \[easyhttp\] \[2\] POST to https://discovery.roonlabs.net/1/register returned after 324 ms, status code: 200, request body size: 528 B
04/23 18:18:52 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:18:57 Trace: \[RAATServer\] refreshing @ 10s
04/23 18:18:57 Debug: \[discovery\] broadcast op is complete
04/23 18:19:01 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:19:01 Trace: \[raatmanager\] updating network interfaces
04/23 18:19:01 Trace: \[discovery\] stopping
04/23 18:19:01 Trace: closing multicast
04/23 18:19:01 Trace: \[discovery\] closing unicast send socket
04/23 18:19:01 Trace: \[discovery\] closing unicast recv socket
04/23 18:19:01 Trace: \[discovery\] starting
04/23 18:19:01 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:19:01 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:63987
04/23 18:19:01 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:19:01 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:63988
04/23 18:19:01 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:19:01 Debug: \[discovery\] broadcast op is complete
04/23 18:19:06 Debug: \[easyhttp\] \[3\] POST to https://discovery.roonlabs.net/1/register returned after 96 ms, status code: 200, request body size: 528 B
04/23 18:19:06 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:19:38 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:19:38 Trace: \[raatmanager\] updating network interfaces
04/23 18:19:38 Trace: \[discovery\] stopping
04/23 18:19:38 Trace: closing multicast
04/23 18:19:38 Trace: \[discovery\] closing unicast send socket
04/23 18:19:38 Trace: \[discovery\] closing unicast recv socket
04/23 18:19:38 Trace: \[discovery\] starting
04/23 18:19:38 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:19:38 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:57550
04/23 18:19:38 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:19:38 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:57551
04/23 18:19:38 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:19:38 Debug: \[discovery\] broadcast op is complete
04/23 18:19:43 Debug: \[easyhttp\] \[4\] POST to https://discovery.roonlabs.net/1/register returned after 311 ms, status code: 200, request body size: 528 B
04/23 18:19:43 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:20:41 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:20:41 Trace: \[raatmanager\] updating network interfaces
04/23 18:20:41 Trace: \[discovery\] stopping
04/23 18:20:41 Trace: closing multicast
04/23 18:20:41 Trace: \[discovery\] closing unicast send socket
04/23 18:20:41 Trace: \[discovery\] closing unicast recv socket
04/23 18:20:41 Trace: \[discovery\] starting
04/23 18:20:41 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:20:41 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:62499
04/23 18:20:41 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:20:41 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:62500
04/23 18:20:41 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:20:41 Debug: \[discovery\] broadcast op is complete
04/23 18:20:46 Debug: \[easyhttp\] \[5\] POST to https://discovery.roonlabs.net/1/register returned after 306 ms, status code: 200, request body size: 528 B
04/23 18:20:46 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:21:47 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:21:47 Trace: \[raatmanager\] updating network interfaces
04/23 18:21:47 Trace: \[discovery\] stopping
04/23 18:21:47 Trace: closing multicast
04/23 18:21:47 Trace: \[discovery\] closing unicast send socket
04/23 18:21:47 Trace: \[discovery\] closing unicast recv socket
04/23 18:21:47 Trace: \[discovery\] starting
04/23 18:21:47 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:21:47 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:50715
04/23 18:21:47 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:21:47 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:50716
04/23 18:21:47 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:21:48 Debug: \[discovery\] broadcast op is complete
04/23 18:21:53 Debug: \[easyhttp\] \[6\] POST to https://discovery.roonlabs.net/1/register returned after 306 ms, status code: 200, request body size: 528 B
04/23 18:21:53 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:22:51 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:22:51 Trace: \[raatmanager\] updating network interfaces
04/23 18:22:51 Trace: \[discovery\] stopping
04/23 18:22:51 Trace: closing multicast
04/23 18:22:51 Trace: \[discovery\] closing unicast send socket
04/23 18:22:51 Trace: \[discovery\] closing unicast recv socket
04/23 18:22:51 Trace: \[discovery\] starting
04/23 18:22:51 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:22:51 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:64416
04/23 18:22:51 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:22:51 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:64417
04/23 18:22:51 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:22:51 Debug: \[discovery\] broadcast op is complete
04/23 18:22:56 Debug: \[easyhttp\] \[7\] POST to https://discovery.roonlabs.net/1/register returned after 302 ms, status code: 200, request body size: 528 B
04/23 18:22:56 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:25:24 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:25:24 Trace: \[raatmanager\] updating network interfaces
04/23 18:25:24 Trace: \[discovery\] stopping
04/23 18:25:24 Trace: closing multicast
04/23 18:25:24 Trace: \[discovery\] closing unicast send socket
04/23 18:25:24 Trace: \[discovery\] closing unicast recv socket
04/23 18:25:24 Trace: \[discovery\] starting
04/23 18:25:24 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:25:24 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:63122
04/23 18:25:24 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:25:24 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:63123
04/23 18:25:24 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:25:24 Debug: \[discovery\] broadcast op is complete
04/23 18:25:29 Debug: \[easyhttp\] \[8\] POST to https://discovery.roonlabs.net/1/register returned after 317 ms, status code: 200, request body size: 528 B
04/23 18:25:29 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:26:26 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:26:26 Trace: \[raatmanager\] updating network interfaces
04/23 18:26:26 Trace: \[discovery\] stopping
04/23 18:26:26 Trace: closing multicast
04/23 18:26:26 Trace: \[discovery\] closing unicast send socket
04/23 18:26:26 Trace: \[discovery\] closing unicast recv socket
04/23 18:26:26 Trace: \[discovery\] starting
04/23 18:26:26 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:26:26 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:59183
04/23 18:26:26 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:26:26 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:59184
04/23 18:26:26 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:26:27 Debug: \[discovery\] broadcast op is complete
04/23 18:26:36 Debug: \[easyhttp\] \[9\] POST to https://discovery.roonlabs.net/1/register returned after 4506 ms, status code: 200, request body size: 528 B
04/23 18:26:36 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:32:08 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:32:08 Trace: \[raatmanager\] updating network interfaces
04/23 18:32:08 Trace: \[discovery\] stopping
04/23 18:32:08 Trace: closing multicast
04/23 18:32:08 Trace: \[discovery\] closing unicast send socket
04/23 18:32:08 Trace: \[discovery\] closing unicast recv socket
04/23 18:32:08 Trace: \[discovery\] starting
04/23 18:32:08 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:32:08 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:49959
04/23 18:32:08 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:32:08 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:49960
04/23 18:32:08 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:32:08 Debug: \[discovery\] broadcast op is complete
04/23 18:32:13 Debug: \[easyhttp\] \[10\] POST to https://discovery.roonlabs.net/1/register returned after 323 ms, status code: 200, request body size: 528 B
04/23 18:32:13 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:33:11 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:33:11 Trace: \[raatmanager\] updating network interfaces
04/23 18:33:11 Trace: \[discovery\] stopping
04/23 18:33:11 Trace: closing multicast
04/23 18:33:11 Trace: \[discovery\] closing unicast send socket
04/23 18:33:11 Trace: \[discovery\] closing unicast recv socket
04/23 18:33:11 Trace: \[discovery\] starting
04/23 18:33:11 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:33:11 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:60771
04/23 18:33:11 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:33:11 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:60772
04/23 18:33:11 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:33:11 Debug: \[discovery\] broadcast op is complete
04/23 18:33:16 Debug: \[easyhttp\] \[11\] POST to https://discovery.roonlabs.net/1/register returned after 303 ms, status code: 200, request body size: 528 B
04/23 18:33:16 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:37:25 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:37:25 Trace: \[raatmanager\] updating network interfaces
04/23 18:37:25 Trace: \[discovery\] stopping
04/23 18:37:25 Trace: closing multicast
04/23 18:37:25 Trace: \[discovery\] closing unicast send socket
04/23 18:37:25 Trace: \[discovery\] closing unicast recv socket
04/23 18:37:25 Trace: \[discovery\] starting
04/23 18:37:25 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:37:25 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:53864
04/23 18:37:25 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:37:25 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:53865
04/23 18:37:25 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:37:25 Debug: \[discovery\] broadcast op is complete
04/23 18:37:30 Debug: \[easyhttp\] \[12\] POST to https://discovery.roonlabs.net/1/register returned after 316 ms, status code: 200, request body size: 528 B
04/23 18:37:30 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:38:30 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:38:30 Trace: \[raatmanager\] updating network interfaces
04/23 18:38:30 Trace: \[discovery\] stopping
04/23 18:38:30 Trace: closing multicast
04/23 18:38:30 Trace: \[discovery\] closing unicast send socket
04/23 18:38:30 Trace: \[discovery\] closing unicast recv socket
04/23 18:38:30 Trace: \[discovery\] starting
04/23 18:38:30 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:38:30 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:50883
04/23 18:38:30 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:38:30 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:50884
04/23 18:38:30 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:38:31 Debug: \[discovery\] broadcast op is complete
04/23 18:38:36 Debug: \[easyhttp\] \[13\] POST to https://discovery.roonlabs.net/1/register returned after 305 ms, status code: 200, request body size: 528 B
04/23 18:38:36 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:40:21 Trace: \[jsonserver\] \[127.0.0.1:56128\] accepted connection
04/23 18:40:21 Trace: \[jsonserver\] \[127.0.0.1:56128\] GOT\[LL\] \[1\] {“request”:“enumerate_devices”,“subscription_id”:“0”}
04/23 18:40:21 Trace: \[jsonserver\] \[127.0.0.1:56128\] SENT \[1\] \[nonfinal\] {“status”: “Success”, “devices”: \[{“name”: “System Output”, “type”: “wasapi”, “device_id”: “default”, “is_system_output”: true, “config”: {“external_config”: {“product_override”: null}, “output”: {“name”:
04/23 18:40:36 Trace: \[jsonserver\] \[127.0.0.1:56128\] read: eof
04/23 18:40:36 Trace: \[jsonserver\] \[127.0.0.1:56128\] destroying client
04/23 18:44:29 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:44:29 Trace: \[raatmanager\] updating network interfaces
04/23 18:44:29 Trace: \[discovery\] stopping
04/23 18:44:29 Trace: closing multicast
04/23 18:44:29 Trace: \[discovery\] closing unicast send socket
04/23 18:44:29 Trace: \[discovery\] closing unicast recv socket
04/23 18:44:29 Trace: \[discovery\] starting
04/23 18:44:29 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:44:29 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:56416
04/23 18:44:29 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:44:29 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:56417
04/23 18:44:29 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:44:29 Debug: \[discovery\] broadcast op is complete
04/23 18:44:35 Debug: \[easyhttp\] \[14\] POST to https://discovery.roonlabs.net/1/register returned after 301 ms, status code: 200, request body size: 528 B
04/23 18:44:35 Trace: \[servicemanager\] registered 1 devices, 1 services
04/23 18:45:32 Trace: \[RAATServer\] network reachability changed, refreshing discovery
04/23 18:45:32 Trace: \[raatmanager\] updating network interfaces
04/23 18:45:32 Trace: \[discovery\] stopping
04/23 18:45:32 Trace: closing multicast
04/23 18:45:32 Trace: \[discovery\] closing unicast send socket
04/23 18:45:32 Trace: \[discovery\] closing unicast recv socket
04/23 18:45:32 Trace: \[discovery\] starting
04/23 18:45:32 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:45:32 Info: \[discovery\] \[iface:Ethernet:192.168.178.58\] multicast send socket is bound to 0.0.0.0:51229
04/23 18:45:32 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast recv socket is bound to 0.0.0.0:9003
04/23 18:45:32 Info: \[discovery\] \[iface:Loopback Pseudo-Interface 1:127.0.0.1\] multicast send socket is bound to 0.0.0.0:51230
04/23 18:45:32 Info: \[discovery\] unicast socket is bound to 0.0.0.0:9003
04/23 18:45:32 Debug: \[discovery\] broadcast op is complete
04/23 18:45:37 Debug: \[easyhttp\] \[15\] POST to https://discovery.roonlabs.net/1/register returned after 297 ms, status code: 200, request body size: 528 B
04/23 18:45:37 Trace: \[servicemanager\] registered 1 devices, 1 services

Where do I go from here???
Regards,

Geoff

20

Hello @Geoff ,

Apologies for the delayed reply here, and thanks for sticking with us for your current troubleshooting you’ve done so far. The big issue here, before we get into the network aspects of it, is that your Nucleus doesn’t seem to be booting up properly.

If you’re getting no HDMI output (and you’ve checked the basics - correct input, working HDMI cable, Nucleus has power + power button is pressed), then this would indicate a hardware issue.

Are you able to get HDMI output with nothing connected to the Ethernet port? Does the Nucleus power button glow after being pressed? Please let us know these details and we can proceed from there.