RoonBridge update error [Ticket In]

Core Machine (Operating system/System info/Roon build number)

Synology DS916+ Roon Version 1.7 (build 537)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Ethernet based network

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

RoonBridge running on RaspberryPi 4 with HifiBerry Digi+ Pro

Description Of Issue

My RoonBridge running on a RaspberryPi 4 reports Version 1.0 (build 171)
in the log I get the following error

05/09 23:49:15 Debug: [appupdater] Update failed
05/09 23:49:16 Warn: [appupdater] Couldn't connect to update server: System.Net.WebException: Error: ConnectFailure (TLS Support not available.) ---> System.NotSupportedException: TLS Support not available. ---> System.NotSupportedException: No such TLS Provider: `btls'.
  at Mono.Net.Security.MonoTlsProviderFactory.LookupProviderType (System.String name, System.Boolean throwOnError) [0x00032] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsProviderFactory.LookupProvider (System.String name, System.Boolean throwOnError) [0x00000] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsProviderFactory.TryDynamicLoad () [0x00019] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsProviderFactory.CreateDefaultProviderImpl () [0x00000] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x0001a] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
   --- End of inner exception stack trace ---
  at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x0002e] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsProviderFactory.GetProviderInternal () [0x00010] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Mono.Net.Security.MonoTlsStream..ctor (System.Net.HttpWebRequest request, System.Net.Sockets.NetworkStream networkStream) [0x00027] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at System.Net.WebConnection.CreateStream (System.Net.HttpWebRequest request) [0x00066] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
   --- End of inner exception stack trace ---
  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <b184df7fd7654b5abda93ba34c7d29e0>:0 
  at Sooloos.Updater+WebUpdate.Load (System.String updateurl) [0x00028] in <45ecdb513d4c44c0ba00307524e7086a>:0 
  at Sooloos.Updater+WebUpdate.CheckForUpdate (System.String serial, System.String userid, System.String product, System.String branding, System.String desired_branch, Sooloos.Version version, Sooloos.Updater+WebUpdate& update) [0x000a7] in <45ecdb513d4c44c0ba00307524e7086a>:0 
  at Sooloos.Updater+<>c__DisplayClass26_0.<ScanOnce>b__0 (System.Object <p0>) [0x0002a] in <45ecdb513d4c44c0ba00307524e7086a>:0 

Any advice is greatly appreciated

I am seeing the same issue since a few days on an Odroid C2
@support

Hi @Chris_KA,

Build 171 is the latest version of RoonBridge at this time, but we can certainly gather some more information regarding this issue, can you please let me know:

  1. What is the model/manufacturer of your networking gear?

  2. Can you please provide a full set of your RoonBridge logs via Dropbox / Google Drive / Your preferred upload service?

  3. Are you using any firewalls which could be impacting RoonBridge from connecting to our update servers?

  4. Are you experiencing any issues with this zone or is the update message the only problem?

  5. Is there any change in behavior if you reboot your Roon Bridge?

Hi Noris,

Here it comes:

  1. What is the model/manufacturer of your networking gear?
    I use a ipv4 based lan with a aim fritz bod 7490 as main router and a couple of 1Gbit Network switches.
    all involved components are Ethernet based. No WiFi involved.

  2. Can you please provide a full set of your RoonBridge logs via Dropbox / Google Drive / Your preferred upload service?
    Link: https://drive.google.com/open?id=112EnyXwDnAHWAt_llgfimZGHoJbuP2VV

  3. Are you using any firewalls which could be impacting RoonBridge from connecting to our update servers? The Raspberry Pi is working in the same environment as my iMac and my PC running Roon and they have no problem getting access to the network servers

  4. Are you experiencing any issues with this zone or is the update message the only problem?
    The update message is the only problem currently.

  5. Is there any change in behavior if you reboot your Roon Bridge?
    I tested this with roopieee, volumio and a fresh Raspbian Lite with manually installed RoonBridge and did reboots several times with no change of the behavior.

1 Like

Hi @Chris_KA,

Thanks for the information, let me get this over to the QA team for closer review.
If any other questions come up, I’ll be sure to let you know, appreciate the report!

@noris
I am having the same issue. Here’s my inputs:

  1. Networking Gear: Swisscom Internet Box for internet, access, Planet GSW-2401 Gigabit switch. Roon Core: ROCK on Asrock Deskmini 310

  2. Logs are here: https://www.dropbox.com/sh/157h92ig4mljjqj/AABhNQgZo1QfJ3Aewg26kui1a?dl=0

  3. No firewalls, all devices on same LAN

  4. no other issues than update message

  5. No change after reboot of Roon Bridge

Here’s a screenshot:

Devices from top to bottom on Screenshot:

  • audiolinux with Roon Bridge on Intel X86. Does NOT show the issue
  • Odroid C2 with volumio and Roon Bridge plugin. Shows the issue
  • Raspberry Pi4 with volumio and Roon Bridge plugin. Shows the issue

Hope this helps

I have the same errors on my 2 PI3B, one under DietPi, the other customised MoodeAudio.
So there seems to be something wrong with the update servers for ARM Roon Bridge.

1 Like

RoonBridge on ARM has always been a little screwed up. The logs have long been full of messages like

05/21 02:19:46 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Error: ConnectFailure (TLS Support not available.))
05/21 02:19:46 Trace: [push] request to manager failed
05/21 02:19:46 Trace: [push] retrying connection in 5300061ms
05/21 02:25:43 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Error: ConnectFailure (TLS Support not available.))
05/21 02:25:43 Trace: [push] request to manager failed
05/21 02:25:43 Trace: [push] retrying connection in 6402393ms

We’ve always been told that these are “harmless” and we should ignore them.

Now they are joined by

05/21 03:31:02 Trace: [rnet/RnetJsonServer] [client 192.168.0.13:58300] GOT {"request":"updates_check_for_updates"}
05/21 03:31:02 Trace: [rnet/RnetJsonServer] [client 192.168.0.13:58300] SENT {"status":"Success"}
05/21 03:31:02 Debug: [base/updater] Checking for updates: http://updates.roonlabs.com/update/?v=2&serial=ED29DFB5-4E5F-4FCF-A79E-9AF225183B64&userid=&platform=linuxarmv7hf&product=RoonBridge&branding=&curbranch=stable&version=100000171&branch=stable
05/21 03:31:02 Trace: [rnet/RnetJsonServer] [client 192.168.0.13:58300] SENT NONFINAL {"status":"Changed","updates":{"is_supported":true,"status":"Checking","progress":null,"current_version":{"machine_value":100000171,"branch":"stable","display_value":"1.0 (build 171) stable"},"available_version":null,"update_mode":"AutoCompatible"}}
05/21 03:31:03 Debug: [appupdater] Update failed
05/21 03:31:03 Warn: [appupdater] Couldn't connect to update server: System.Net.WebException: Error: ConnectFailure (TLS Support not available.) ---> System.NotSupportedException: TLS Support not available. ---> System.NotSupportedException: No such TLS Provider: `btls'.
  at Mono.Net.Security.MonoTlsProviderFactory.LookupProviderType (System.String name, System.Boolean throwOnError) [0x00032] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsProviderFactory.LookupProvider (System.String name, System.Boolean throwOnError) [0x00000] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsProviderFactory.TryDynamicLoad () [0x00019] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsProviderFactory.CreateDefaultProviderImpl () [0x00000] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x0001a] in <b184df7fd7654b5abda93ba34c7d29e0>:0
   --- End of inner exception stack trace ---
  at Mono.Net.Security.MonoTlsProviderFactory.InitializeInternal () [0x0002e] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsProviderFactory.GetProviderInternal () [0x00010] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Mono.Net.Security.MonoTlsStream..ctor (System.Net.HttpWebRequest request, System.Net.Sockets.NetworkStream networkStream) [0x00027] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at System.Net.WebConnection.CreateStream (System.Net.HttpWebRequest request) [0x00066] in <b184df7fd7654b5abda93ba34c7d29e0>:0
   --- End of inner exception stack trace ---
  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <b184df7fd7654b5abda93ba34c7d29e0>:0
  at Sooloos.Updater+WebUpdate.Load (System.String updateurl) [0x00028] in <45ecdb513d4c44c0ba00307524e7086a>:0
  at Sooloos.Updater+WebUpdate.CheckForUpdate (System.String serial, System.String userid, System.String product, System.String branding, System.String desired_branch, Sooloos.Version version, Sooloos.Updater+WebUpdate& update) [0x000a7] in <45ecdb513d4c44c0ba00307524e7086a>:0
  at Sooloos.Updater+<>c__DisplayClass26_0.<ScanOnce>b__0 (System.Object <p0>) [0x0002a] in <45ecdb513d4c44c0ba00307524e7086a>:0
05/21 03:31:03 Trace: [rnet/RnetJsonServer] [client 192.168.0.13:58300] SENT NONFINAL {"status":"Changed","updates":{"is_supported":true,"status":"Error","progress":null,"current_version":{"machine_value":100000171,"branch":"stable","display_value":"1.0 (build 171) stable"},"available_version":null,"update_mode":"AutoCompatible"}}

Note that it’s really the same error in both cases:

Error: ConnectFailure (TLS Support not available.)

Just, this time, the error-reporting is better.

1 Like

Thanks for the reports all. I have been discussing this issue with QA and they will attempt to reproduce this issue in the lab, if we need any further information, I’ll be sure to reach out again here!

Here’s what I see:

1 Like

Hello All,

I wanted to touch base with some good news, which is that our technical team has been able to reproduce this behavior and we’ve opened up a bug report with our developers.

While I can’t say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and I will keep this thread up to date as the team passes along feedback and work begins to get this resolved.

Thanks again for the report!

I see the issue is fixed now.

Thanks!

N.B.: We still get

06/11 02:14:24 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Error: ConnectFailure (TLS Support not available.))
06/11 02:14:24 Trace: [push] request to manager failed
06/11 02:14:24 Trace: [push] retrying connection in 7279227ms

errors. But the

05/21 03:31:03 Warn: [appupdater] Couldn't connect to update server: System.Net.WebException: Error: ConnectFailure (TLS Support not available.) ---> System.NotSupportedException: TLS Support not available. ---> System.NotSupportedException: No such TLS Provider: `btls'.

errors are gone.

Yes as opener of this ticket I can confirm that the problem is solved.
Good work. This is very much appreciated

regards
Chris

3 Likes

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