Hi Noris,
Doesn’t the error message from the log indicate an SSL certificate problem or SSL TSL version problem?
If an existing registration is not terminated, this may not be noticeable. I hadn’t used ROON for a long time and was logged out of both ROON and TIDAL / Qobuz. Possibly auto logoff?
1 Like
Don’t know, I have never been auto-logged off in 4 years but I don’t know what happens if it’s not used for a long time.
do you also use roon 1.8?
In this case you could easily test it. Log out of Qobuz and then log in again.
I tested the login with different front ends: MAC, Phone, IPAD. The same error always occurs when logging in to qobuz. This only leads me to the conclusion that the error occurred during the “Qobuz API call” and lies in the ROON application itself.
No, I use 2.0, sorry
Hi @Ralf_G,
Thanks for all the additional information! We’re unfortunately no longer able to test the legacy version of Roon, nor release any software fixes or updates.
That said, perhaps clearing your Qobuz cache within your Roon Server database may help:
- Exit out of Roon
- Find and open your Roon database
- Navigate to
/Library/Roon/Cache - Move the contents of the
/Cachefolder elsewhere, like your desktop - Try restarting Roon and verify if the issue still occurs
Hi Benjamin,
The error persists even after moving the cache. Does the implementation of the qobuz api call in the current ROON version differ from version 1.8? Here is another log excerpt:
10/19 13:36:18 Warn: [easyhttp] [130] Get https://www.qobuz.com/api.json/0.2/user/login?device_manufacturer_id=6bd9f5e623974317a74d82b502d90be8&email=ap_rg%40outlook.de&password=2968a597bcce2514bc6fb808b7d20b2a&request_sig=8f04617db315a4a86aa80d4b972e9a8c&request_ts=1729337777 web exception without response: Error: SecureChannelFailure (Authentication failed, see inner exception.) Authentication failed, see inner exception.
10/19 13:36:18 Warn: [qobuz] [http] error result from http request: System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.) —> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. —> Mono.Security.Interface.TlsException: Unknown Secure Transport error `PeerHandshakeFail’.
Hello @Ralf_G ,
That error message looks like the Roon Server isn’t able to use the proper certificates. Please note that Roon 1.8 is no longer under active development, any sort of resolution would come in the form of configuration changes on the affected Mac.
If you are unable to update to Roon 2.0 due to the Mac being too old, you may want to check out a tool that a few of our users suggested in the past (but please be warned that we have no affiliation with this tool and cannot provide any specific guidance):
Hello Noris,
o.k., that means the bug is in the ROON software 1.8, right?
So a patcher for a new ROON version on an old MAC is the only solution?
@Ralf_G yes that is correct if your Mac cannot run Roon 2.0 as is.
Hi Daniel,
the question again:
Does the implementation of the qobuz api call in the current ROON version differ from version 1.8?
Hi @Ralf_G ,
Yes, the Qobuz login mechanism varied between Roon 1.8 and Roon 2.0 but it is also very possible that something changed on Qobuz’s end and they are no longer accepting older security ciphers (older than TLS 1.2). Roon 1.8 is no longer under development, we strongly encourage updating to Roon 2.0 on a compatible operating system.
addition:
The error also occurs on my iOS devices. But tls 3 is installed there (checked with howsmyssl,com). Is the relevant tls version for the qobuz-api-request permanently specified in the ROON application?
Hello @Ralf_G ,
For your Roon Server to communicate with the Qobuz servers, you would need to be able to use TLS 1.2 or higher on the server. You can try the TLS homebrew update, it may help, but we cannot comment on specifics as we did not test it.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.