Roon cannot connect to Core

[Adam_Herbert]

Roon Core Machine

Microsoft Windows 10 Pro
Intel J3455B-ITX
16.0 GB RAM

Networking Gear & Setup Details

All Ethernet Cat 5e
Netgear GS716TV3 Layer 3 switch
pfsense firewall appliance

Connected Audio Devices

Core uses a Topping E30 DAC via USB

Number of Tracks in Library

7,841 tracks in the library

Description of Issue

Everything was working perfectly yesterday but today when I start Roon it just spins on the Connecting to Core startup screen. Nothing in my system or network has changed.

I have reinstalled ROON and restarted both my PC and the server. I have plugged just the PC and server into another unmanaged switch to remove the network from the equation and the same thing happens.
No idea where to go from here.

[Adam_Herbert]

Update: I have installed Roon remote on another PC and I cannot connect to Roon Core from it either. On my main PC I have converted the Roon install to a core install. The odd thing is I can control the Topping USB device connected to the Roon Core and play music though it. I cannot connect to the Roon Core from any remote app anymore.

[Adam_Herbert]

Hi,

I saw this and it made me laugh. How do I change the core settings if I can’t connect remotely to it in the first place?
Hopefully someone from Roon will chime in soon with some advice because it’s not like this software is free.
This is starting to sound a lot like I now need to have both Roon core and Roon app installed on my server? This was not the case up until now so it seems like a massive architectural change.

[Adam_Herbert]

So I assume this is related to release 952 where they have overhauled the Core/Remote connection system? I am going to roll everything back to previous release and see if that resolves this seeing as there is not any support from Roon appearing in a timely fashion.

[Adam_Herbert]

Some more screenshots from a complete clean install. Same issue.

[Marin_Weigel (Bram Stoker's Cappuccino)]

@Adam_Herbert

Intel J3455B-ITX

A little under spec but should not be the cause.

@Adam_Herbert

I have plugged just the PC and server into another unmanaged switch to remove the network from the equation

Roon needs an internet connection every once in a while on startup to verify subscription or life license.

@Adam_Herbert

I have converted the Roon install to a core install.

You mean a Roon Server install?
That would be the one without a GUI.
Perfectly fine to have that and the full Roon install coexist, just remember to make the server install “the core”.

@Adam_Herbert

This was not the case up until now so it seems like a massive architectural change.

No, there had not been a change in architecture.

And how did you get the screen shot searching for Roon OS devices?
Anyway, that only makes sense if you’ve got a Roon Nucleus or a NUC with Rock, as it says at the bottom of that screen shot, and you’re running Windows here.

That said, make your full Roon install the core by selecting “use this…” and try from there while being connected to the internet… good luck.

[Adam_Herbert]

Let me be very clear, my Roon system was working perfectly for over 18 months and then 2 days ago it stopped working for no reason. Nothing has changed, I have always had a Roon core installed on my server and remotes every where else. Now all I get is this from the remotes:

Nothing has changed in quite sometime. I have done all the troubleshooting that makes sense and nothing makes any difference. I have gone as far as putting only the server and one PC on a switch with internet access and I get the same issue.

[Adam_Herbert]

Here is the tail of the logs if that is of any use, seems to be looping through this query and not recovering:

06/09 19:01:11 Debug: [appupdater] Update not needed
06/09 19:01:11 Debug: [easyhttp] [10] POST to https://discovery.roonlabs.net/1/query returned after 490 ms, status code: 200
06/09 19:01:25 Info: [stats] 5310mb Virtual, 188mb Physical, 28mb Managed, 1340 Handles, 68 Threads
06/09 19:01:40 Info: [stats] 5298mb Virtual, 189mb Physical, 28mb Managed, 1340 Handles, 65 Threads
06/09 19:01:41 Debug: [easyhttp] [12] POST to https://discovery.roonlabs.net/1/query returned after 478 ms, status code: 200
06/09 19:01:41 Debug: [easyhttp] [13] POST to https://discovery.roonlabs.net/1/query returned after 451 ms, status code: 200
06/09 19:01:56 Info: [stats] 5294mb Virtual, 189mb Physical, 32mb Managed, 1339 Handles, 64 Threads
06/09 19:02:11 Info: [stats] 5298mb Virtual, 189mb Physical, 32mb Managed, 1344 Handles, 65 Threads
06/09 19:02:11 Debug: [easyhttp] [14] POST to https://discovery.roonlabs.net/1/query returned after 503 ms, status code: 200
06/09 19:02:11 Debug: [easyhttp] [15] POST to https://discovery.roonlabs.net/1/query returned after 451 ms, status code: 200
06/09 19:02:26 Info: [stats] 5298mb Virtual, 189mb Physical, 29mb Managed, 1346 Handles, 65 Threads
06/09 19:02:41 Info: [stats] 5294mb Virtual, 189mb Physical, 30mb Managed, 1341 Handles, 64 Threads
06/09 19:02:41 Debug: [easyhttp] [16] POST to https://discovery.roonlabs.net/1/query returned after 454 ms, status code: 200
06/09 19:02:41 Debug: [easyhttp] [17] POST to https://discovery.roonlabs.net/1/query returned after 491 ms, status code: 200
06/09 19:02:56 Info: [stats] 5286mb Virtual, 189mb Physical, 29mb Managed, 1340 Handles, 62 Threads
06/09 19:03:11 Info: [stats] 5290mb Virtual, 189mb Physical, 29mb Managed, 1335 Handles, 63 Threads
06/09 19:03:11 Debug: [easyhttp] [18] POST to https://discovery.roonlabs.net/1/query returned after 449 ms, status code: 200
06/09 19:03:11 Debug: [easyhttp] [19] POST to https://discovery.roonlabs.net/1/query returned after 449 ms, status code: 200
06/09 19:03:26 Info: [stats] 5294mb Virtual, 189mb Physical, 33mb Managed, 1340 Handles, 64 Threads

[Auron_Lim]

Hmm…please double check again your router setting, make sure the associated network components are on the same gateway. Eg . 192.168.1.xxx or 192.168.2.xxx . Usually i would set a fixed IP or IP reserved for Roon Core and streamer to avoid IP address changed.

[Adam_Herbert]

This is not a basic network issue. These machines are all on the same vlan, DHCP on pfsense issues ip’s, this is not the problem. Like i said nothing has changed in quite some time. The server IP is reserved anyway but that is completely irrelevant with regards to hostname lookups on local DNS. It is clearly able to find the Roon core server, it is hanging when trying to establish the connection.

[Adam_Herbert]

Here is the logfile entry from my Roon remote PC showing it locating the Roon Core server.

06/09 19:00:41 Trace: [remoting/remotebrokerv2] [WOTISAYSERVER] [init WOTISAYSERVER@10.27.27.41:9332] Connected
06/09 19:00:41 Info: [remoting/distributedbroker] FOUND BROKER WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720)

[Marin_Weigel (Bram Stoker's Cappuccino)]

@Adam_Herbert

These machines are all on the same vlan

I’m not a network wiz, don’t run VLANs myself, and it wouldn’t explain that it worked until recently, but Roon and VLANs seem to be a ticket to frustration for many - so I’m tagging @support who will hopefully get to your help request sooner than later while working through their pile-up…

[Adam_Herbert]

I have dug up some more logs which @support may find useful (Roon Remote to Roon Core):

06/10 11:30:28 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:28 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:33 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:33 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:38 Info: [stats] 33559992mb Virtual, 441mb Physical, 38mb Managed, 1479 Handles, 81 Threads
06/10 11:30:38 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:38 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:43 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:44 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:49 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:49 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:53 Info: [stats] 33559996mb Virtual, 441mb Physical, 36mb Managed, 1479 Handles, 82 Threads
06/10 11:30:53 Debug: [easyhttp] [13] POST to https://discovery.roonlabs.net/1/query returned after 231 ms, status code: 200
06/10 11:30:54 Debug: [easyhttp] [14] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/10 11:30:54 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:30:54 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:30:59 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:00 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:05 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:05 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:08 Info: [stats] 33560012mb Virtual, 441mb Physical, 41mb Managed, 1520 Handles, 86 Threads
06/10 11:31:10 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:10 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:16 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:16 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:21 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:21 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:23 Info: [stats] 33559996mb Virtual, 441mb Physical, 39mb Managed, 1508 Handles, 82 Threads
06/10 11:31:23 Debug: [easyhttp] [15] POST to https://discovery.roonlabs.net/1/query returned after 237 ms, status code: 200
06/10 11:31:24 Debug: [easyhttp] [16] POST to https://discovery.roonlabs.net/1/query returned after 235 ms, status code: 200
06/10 11:31:26 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:26 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:31 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:32 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:37 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:37 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:38 Info: [stats] 33559984mb Virtual, 440mb Physical, 37mb Managed, 1512 Handles, 79 Threads
06/10 11:31:42 Trace: [remoting/remotebrokerv1] connect timeout
06/10 11:31:42 Trace: [remoting/remotebrokerv1] connecting to WOTISAYSERVER (8deb1cba-3718-4023-a164-f91cdbcda720) @ 10.27.27.41:9331 (attempt 1/6)
06/10 11:31:47 Debug: [easyhttp] [17] POST to https://discovery.roonlabs.net/1/unregister returned after 231 ms, status code: 200
06/10 11:31:47 Trace: [inetdiscovery] unregistered 1 devices

[jamie]

Hey @Adam_Herbert,

Sorry to hear that you’ve had some issues with connecting to your Core. In. checking your diagnostics it looks like you could be up and running again. Can you please update on your current status?

If you’re still having issues please hard reboot your router and core, power down, unplug them, wait several minutes, plug in and restart. Please power down your remote devices as well.

Power up your devices in this sequence: Router, Core, Remotes. Please let us know if this helps.

[Adam_Herbert]

Hi Jamie,
Full reboots all round and no difference, Roon remote is still hanging on the the “Choose your Roon Core” screen.

[Adam_Herbert]

Jamie,
Looking at the logs again your app seems to be doing a lot of queries to https://discovery.roonlabs.net, it now seems to be in another loop:

06/13 08:25:46 Trace: [broker/accounts] [heartbeat] now=12/06/2022 10:25:47 PM nextauthrefresh=12/06/2022 11:20:47 PM nextmachineallocate=13/06/2022 2:20:47 AM
06/13 08:25:47 Debug: [easyhttp] [29] POST to https://discovery.roonlabs.net/1/query returned after 232 ms, status code: 200
06/13 08:25:47 Info: [stats] 5279mb Virtual, 187mb Physical, 31mb Managed, 1353 Handles, 60 Threads
06/13 08:25:48 Debug: [easyhttp] [30] POST to https://discovery.roonlabs.net/1/query returned after 895 ms, status code: 200
06/13 08:26:02 Info: [stats] 5279mb Virtual, 188mb Physical, 29mb Managed, 1364 Handles, 60 Threads
06/13 08:26:17 Debug: [easyhttp] [31] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:26:17 Info: [stats] 5283mb Virtual, 188mb Physical, 28mb Managed, 1365 Handles, 61 Threads
06/13 08:26:17 Debug: [easyhttp] [32] POST to https://discovery.roonlabs.net/1/query returned after 231 ms, status code: 200
06/13 08:26:32 Info: [stats] 5279mb Virtual, 188mb Physical, 32mb Managed, 1365 Handles, 60 Threads
06/13 08:26:47 Debug: [easyhttp] [33] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:26:47 Info: [stats] 5283mb Virtual, 187mb Physical, 28mb Managed, 1366 Handles, 61 Threads
06/13 08:26:47 Debug: [easyhttp] [34] POST to https://discovery.roonlabs.net/1/query returned after 238 ms, status code: 200
06/13 08:27:02 Info: [stats] 5283mb Virtual, 187mb Physical, 32mb Managed, 1366 Handles, 61 Threads
06/13 08:27:17 Debug: [easyhttp] [35] POST to https://discovery.roonlabs.net/1/query returned after 232 ms, status code: 200
06/13 08:27:17 Info: [stats] 5283mb Virtual, 187mb Physical, 29mb Managed, 1366 Handles, 61 Threads
06/13 08:27:17 Debug: [easyhttp] [36] POST to https://discovery.roonlabs.net/1/query returned after 226 ms, status code: 200
06/13 08:27:32 Info: [stats] 5279mb Virtual, 187mb Physical, 27mb Managed, 1370 Handles, 60 Threads
06/13 08:27:47 Debug: [easyhttp] [37] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:27:47 Info: [stats] 5279mb Virtual, 187mb Physical, 31mb Managed, 1370 Handles, 60 Threads
06/13 08:27:47 Debug: [easyhttp] [38] POST to https://discovery.roonlabs.net/1/query returned after 234 ms, status code: 200
06/13 08:28:02 Info: [stats] 5279mb Virtual, 187mb Physical, 29mb Managed, 1370 Handles, 60 Threads
06/13 08:28:17 Debug: [easyhttp] [39] POST to https://discovery.roonlabs.net/1/query returned after 236 ms, status code: 200
06/13 08:28:17 Info: [stats] 5279mb Virtual, 187mb Physical, 33mb Managed, 1373 Handles, 60 Threads
06/13 08:28:17 Debug: [easyhttp] [40] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/13 08:28:32 Info: [stats] 5283mb Virtual, 187mb Physical, 31mb Managed, 1379 Handles, 61 Threads
06/13 08:28:47 Debug: [easyhttp] [41] POST to https://discovery.roonlabs.net/1/query returned after 232 ms, status code: 200
06/13 08:28:47 Info: [stats] 5275mb Virtual, 187mb Physical, 29mb Managed, 1367 Handles, 59 Threads
06/13 08:28:47 Debug: [easyhttp] [42] POST to https://discovery.roonlabs.net/1/query returned after 228 ms, status code: 200
06/13 08:29:02 Info: [stats] 5279mb Virtual, 187mb Physical, 32mb Managed, 1373 Handles, 60 Threads
06/13 08:29:17 Debug: [easyhttp] [43] POST to https://discovery.roonlabs.net/1/query returned after 233 ms, status code: 200
06/13 08:29:17 Info: [stats] 5279mb Virtual, 187mb Physical, 31mb Managed, 1378 Handles, 60 Threads
06/13 08:29:17 Debug: [easyhttp] [44] POST to https://discovery.roonlabs.net/1/query returned after 236 ms, status code: 200
06/13 08:29:32 Info: [stats] 5279mb Virtual, 187mb Physical, 28mb Managed, 1378 Handles, 60 Threads
06/13 08:29:47 Debug: [easyhttp] [45] POST to https://discovery.roonlabs.net/1/query returned after 236 ms, status code: 200
06/13 08:29:47 Info: [stats] 5279mb Virtual, 187mb Physical, 33mb Managed, 1383 Handles, 60 Threads
06/13 08:29:47 Debug: [easyhttp] [46] POST to https://discovery.roonlabs.net/1/query returned after 236 ms, status code: 200
06/13 08:30:02 Info: [stats] 5279mb Virtual, 187mb Physical, 31mb Managed, 1383 Handles, 60 Threads
06/13 08:30:17 Debug: [easyhttp] [47] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/13 08:30:17 Info: [stats] 5287mb Virtual, 187mb Physical, 28mb Managed, 1388 Handles, 62 Threads
06/13 08:30:17 Debug: [easyhttp] [48] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/13 08:30:32 Info: [stats] 5287mb Virtual, 187mb Physical, 32mb Managed, 1388 Handles, 62 Threads
06/13 08:30:46 Trace: [broker/accounts] [heartbeat] now=12/06/2022 10:30:47 PM nextauthrefresh=12/06/2022 11:20:47 PM nextmachineallocate=13/06/2022 2:20:47 AM
06/13 08:30:47 Debug: [easyhttp] [49] POST to https://discovery.roonlabs.net/1/query returned after 231 ms, status code: 200
06/13 08:30:47 Info: [stats] 5291mb Virtual, 187mb Physical, 30mb Managed, 1388 Handles, 63 Threads
06/13 08:30:48 Debug: [easyhttp] [50] POST to https://discovery.roonlabs.net/1/query returned after 240 ms, status code: 200
06/13 08:31:02 Info: [stats] 5282mb Virtual, 187mb Physical, 33mb Managed, 1378 Handles, 60 Threads
06/13 08:31:17 Info: [stats] 5291mb Virtual, 187mb Physical, 31mb Managed, 1390 Handles, 63 Threads
06/13 08:31:17 Debug: [easyhttp] [51] POST to https://discovery.roonlabs.net/1/query returned after 901 ms, status code: 200
06/13 08:31:18 Debug: [easyhttp] [52] POST to https://discovery.roonlabs.net/1/query returned after 900 ms, status code: 200
06/13 08:31:32 Info: [stats] 5291mb Virtual, 187mb Physical, 30mb Managed, 1392 Handles, 63 Threads
06/13 08:31:47 Debug: [easyhttp] [53] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:31:47 Info: [stats] 5291mb Virtual, 187mb Physical, 28mb Managed, 1394 Handles, 63 Threads
06/13 08:31:48 Debug: [easyhttp] [54] POST to https://discovery.roonlabs.net/1/query returned after 231 ms, status code: 200
06/13 08:32:02 Info: [stats] 5291mb Virtual, 187mb Physical, 32mb Managed, 1394 Handles, 63 Threads
06/13 08:32:17 Debug: [easyhttp] [55] POST to https://discovery.roonlabs.net/1/query returned after 239 ms, status code: 200
06/13 08:32:17 Info: [stats] 5290mb Virtual, 187mb Physical, 29mb Managed, 1393 Handles, 62 Threads
06/13 08:32:18 Debug: [easyhttp] [56] POST to https://discovery.roonlabs.net/1/query returned after 233 ms, status code: 200
06/13 08:32:32 Info: [stats] 5291mb Virtual, 187mb Physical, 33mb Managed, 1394 Handles, 63 Threads
06/13 08:32:47 Debug: [easyhttp] [57] POST to https://discovery.roonlabs.net/1/query returned after 233 ms, status code: 200
06/13 08:32:47 Info: [stats] 5291mb Virtual, 188mb Physical, 32mb Managed, 1394 Handles, 63 Threads
06/13 08:32:48 Debug: [easyhttp] [58] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/13 08:33:02 Info: [stats] 5291mb Virtual, 188mb Physical, 29mb Managed, 1394 Handles, 63 Threads
06/13 08:33:17 Debug: [easyhttp] [59] POST to https://discovery.roonlabs.net/1/query returned after 237 ms, status code: 200
06/13 08:33:17 Info: [stats] 5287mb Virtual, 188mb Physical, 33mb Managed, 1392 Handles, 62 Threads
06/13 08:33:18 Debug: [easyhttp] [60] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:33:32 Info: [stats] 5287mb Virtual, 188mb Physical, 30mb Managed, 1392 Handles, 62 Threads
06/13 08:33:47 Debug: [easyhttp] [61] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:33:47 Info: [stats] 5287mb Virtual, 188mb Physical, 29mb Managed, 1396 Handles, 62 Threads
06/13 08:33:48 Debug: [easyhttp] [62] POST to https://discovery.roonlabs.net/1/query returned after 232 ms, status code: 200
06/13 08:34:02 Info: [stats] 5287mb Virtual, 188mb Physical, 33mb Managed, 1399 Handles, 62 Threads
06/13 08:34:17 Debug: [easyhttp] [63] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:34:17 Info: [stats] 5286mb Virtual, 188mb Physical, 30mb Managed, 1398 Handles, 61 Threads
06/13 08:34:18 Debug: [easyhttp] [64] POST to https://discovery.roonlabs.net/1/query returned after 234 ms, status code: 200
06/13 08:34:32 Info: [stats] 5287mb Virtual, 188mb Physical, 28mb Managed, 1406 Handles, 62 Threads
06/13 08:34:47 Debug: [easyhttp] [65] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:34:47 Info: [stats] 5287mb Virtual, 188mb Physical, 32mb Managed, 1404 Handles, 62 Threads
06/13 08:34:48 Debug: [easyhttp] [66] POST to https://discovery.roonlabs.net/1/query returned after 231 ms, status code: 200
06/13 08:35:02 Info: [stats] 5287mb Virtual, 188mb Physical, 30mb Managed, 1399 Handles, 62 Threads
06/13 08:35:17 Debug: [easyhttp] [67] POST to https://discovery.roonlabs.net/1/query returned after 237 ms, status code: 200
06/13 08:35:17 Info: [stats] 5279mb Virtual, 188mb Physical, 28mb Managed, 1394 Handles, 60 Threads
06/13 08:35:18 Debug: [easyhttp] [68] POST to https://discovery.roonlabs.net/1/query returned after 234 ms, status code: 200
06/13 08:35:32 Info: [stats] 5287mb Virtual, 187mb Physical, 28mb Managed, 1342 Handles, 62 Threads
06/13 08:35:46 Trace: [broker/accounts] [heartbeat] now=12/06/2022 10:35:47 PM nextauthrefresh=12/06/2022 11:20:47 PM nextmachineallocate=13/06/2022 2:20:47 AM
06/13 08:35:47 Debug: [easyhttp] [69] POST to https://discovery.roonlabs.net/1/query returned after 229 ms, status code: 200
06/13 08:35:47 Info: [stats] 5291mb Virtual, 187mb Physical, 26mb Managed, 1344 Handles, 63 Threads
06/13 08:35:48 Debug: [easyhttp] [70] POST to https://discovery.roonlabs.net/1/query returned after 230 ms, status code: 200
06/13 08:36:02 Info: [stats] 5291mb Virtual, 187mb Physical, 30mb Managed, 1344 Handles, 63 Threads
06/13 08:36:17 Debug: [easyhttp] [71] POST to https://discovery.roonlabs.net/1/query returned after 239 ms, status code: 200
06/13 08:36:17 Info: [stats] 5291mb Virtual, 187mb Physical, 29mb Managed, 1344 Handles, 63 Threads
06/13 08:36:18 Debug: [easyhttp] [72] POST to https://discovery.roonlabs.net/1/query returned after 908 ms, status code: 200
06/13 08:36:32 Info: [stats] 5291mb Virtual, 187mb Physical, 26mb Managed, 1346 Handles, 63 Threads
06/13 08:36:47 Info: [stats] 5291mb Virtual, 187mb Physical, 30mb Managed, 1352 Handles, 63 Threads
06/13 08:36:47 Debug: [easyhttp] [73] POST to https://discovery.roonlabs.net/1/query returned after 893 ms, status code: 200
06/13 08:36:48 Debug: [easyhttp] [74] POST to https://discovery.roonlabs.net/1/query returned after 900 ms, status code: 200
06/13 08:37:02 Info: [stats] 5291mb Virtual, 187mb Physical, 28mb Managed, 1352 Handles, 63 Threads

[Adam_Herbert]

Hi,
Based on what I can only assume is a Red Herring my DNS is set to 1.1.1.1/1.0.0.1 (Cloudflare) in case that needed to be said but I can’t see why it would matter. I also use DNSSEC, DNS over HTTPS (DoH) and DNS over TLS (DoT) all enforced by firewall rules. This has been the case for 12 months. Based on your logs I cannot see any issues with the apps resolving DNS anyway.

1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver

[Adam_Herbert]

Ok, I finally found the issue. It was firewall related on the Windows Server that hosts my Roon Core. You guys must have changed the firewall rules in 952 because they were a mess. I removed all the Roon related rules and then added exceptions (inbound & outbound) for RAATServer.exe, RoonAppliance.exe and RoonServer.exe. As soon as I did this it all worked again. The one I suspect was missing was the exception for RoonAppliance.exe. When I first looked it had in inbound rule blocking access and no outbound rule at all.
Anyway all sorted now.

[Maarten_Duits]

Hi @Adam_Herbert,

Glad to hear you find the problem and can listen to music again.
Maybe you already know, then you can forget this message. I few weeks ago there was a webinar from RoonLabs with the title Optimizing your home network for Roon. As i am correct, they also talk about the recommendations about firewalls with Roon.

You can find the webinar here (Youtube - Roonlabs)

Kind regards,

Maarten.