Recurring TLS handshake failure with api.roonlabs.com affecting metadata improver (ref#SP8QXI)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Subject: Metadata improver paused - api.roonlabs.com TLS handshake failure (recurring)

Hi Roon Support,

I'm having a recurring connectivity issue with Roon's metadata service.

Symptom:
In Roon, the "Metadata improver" shows as "Paused" with the message: "Roon is having trouble verifying your connection with our servers, so metadata improvement has been paused." Tracks get added to the library fine, but 0 get identified. Right now it shows 1257 tracks added, 0 identified.

Technical detail:
Running curl directly from the machine hosting RoonServer to your API endpoint fails at the TLS layer:

curl -sS -o /dev/null -w "%{http_code}
" https://api.roonlabs.com --max-time 5
curl: (35) TLS connect error: error:0A000410:SSL routines::ssl/tls alert handshake failure

All other HTTPS traffic from this machine works normally - this failure is specific to api.roonlabs.com.

Timeline:
I first saw this exact issue in mid-August 2026, then it seemed to resolve on its own after a while. It's now back (first noticed again around August 31, still occurring as of September 5).

Important context from last time: when this happened in August, I independently verified it wasn't specific to my network - I tested api.roonlabs.com from a completely separate machine in another country, and also from a phone on cellular data (no Wi-Fi), and both got the same failure reaching api.roonlabs.com at that time. That pointed to the issue being on your end (or with the CDN/TLS termination in front of api.roonlabs.com) rather than my ISP or home network.

Setup for reference:
RoonServer runs in a self-hosted Debian LXC container on my own Proxmox server (not a NUC/ROCK). Resources are not a bottleneck (plenty of idle CPU/RAM), and the container has otherwise been stable for weeks.

Could you look into whether api.roonlabs.com has intermittent TLS/reachability issues (possibly region-specific)? This has now recurred more than once over the past few weeks.

Happy to send full diagnostics if useful.

Thanks,
Sait

Tell us about your home network

· there isn't complex network with wifi 6 ap and there isn't any problem with my network

2

and you can see ;
root@ofroon:/opt/RoonServer# curl -sS -o /dev/null -w “HTTP code: %{http_code}\n” https://api.roonlabs.com --max-time 5
curl: (35) TLS connect error: error:0A000410:SSL routines::ssl/tls alert handshake failure
HTTP code: 000
root@ofroon:/opt/RoonServer#

3

There is actually no DNS entry ($ nslookup api.roonlabs.com) for a machine by that name. It is then obviously not possible to make a successful connection to an unknown machine. Is your Roon Server version current?

Note: api.roonlabs.com is not their current API endpoint, it is api.roonlabs.net.

4

Update: restarting RoonServer cleared it. “Metadata improver” is no longer showing as Paused, and metadata is being fetched/identified normally now.

For reference, the RoonServer logs showed all the metadata HTTP requests to api.roonlabs.net returning clean 200s throughout, and the pending identification queue (4425 adds) was actually just waiting on an internal 7-day refresh window (last full refresh 08/30, next one not due until 09/06) - so connectivity was never actually broken on my end. The “trouble verifying your connection” message in the UI seems to be a bit misleading in this case, but restarting the server resolved it regardless.

Thanks for the help tracking down the api.roonlabs.com/.net mix-up along the way - marking this solved.

Google Chrome -2026-09-05 at 22.05@2x
Google Chrome -2026-09-05 at 22.05@2x1224×822 53.8 KB

5

I don’t start the Roon Server container until tje network is up. I handle this with Systemd using After=network-online.target in the service file.

This may help to remove the problem.