Diagnosing RAAT not connecting

Roon Core Machine

Intel NUC running 1.8 (build 884)
Intel i3-8109U
32G ram
Running on Ubuntu with 5.4.0-94-generic kernel

Networking Gear & Setup Details

Ubiquiti edgerouter 6p

Connected Audio Devices

Oppo HA-1
Various Sonos

Number of Tracks in Library

36,000 tracks

Description of Issue

After updating the firmware on things (updating roon, updating router, updating wifi - lots of security issues in the world right now) and rebooting it all, my PC running windows 10 and Roon 1.8 (build 884) stable doesn’t show up as an audio zone. Looking at my RAATServer_log, I see several complaints it couldn’t create a secure channel:
01/22 13:06:17 Warn: [easyhttp] [1] Post https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery. web exception without response: The request was aborted: Could not create SSL/TLS secure channel.
It ends with:
01/23 08:41:41 Warn: [easyhttp] [2] Post https://discovery.roonlabs.net/1/register web exception without response: The request was aborted: Could not create SSL/TLS secure channel.
01/23 08:41:41 Warn: [inetdiscovery] failed to register: Result[Status=NetworkError]
01/23 08:41:46 Trace: [RAATServer] refreshing @ 10s
01/23 08:41:46 Trace: [raatmanager] announcing
01/23 08:41:46 Debug: [discovery] broadcast op is complete

Are the warnings benign? Any tips on diagnosing this? I hate having to hall out a ethernet hub and packet capture this. Did 1.8 change how raat discovery works?

Hi @Robert_Greenwalt,

Are you still having these issues on the newest version of Roon, Build 903/904? If looks like this could be security/permissions settings. From checking your history it appears that you’ve used robust security measures in the past and had similar issues.

Please send us an update, if you’re still having trouble we’d be happy to help.

We can close this - it was an issue on my side. The logging is mysterious, but not evidently the root cause. Updating my router at the same time was mistake, compounding factors and confusing the diagnostics… the router update caused it to lose some rules.

Sorry about the noise, and thanks for getting back to me.

Hey @Robert_Greenwalt,

No worries, we’re happy to hear that everything is working for you now. Happy Listening! :loud_sound:

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