· Something else
· None of the above
· Other
Cannot login to Qobuz service from Roon, and it works okay in the Qobuz app. This has worked until I renewed my Qobuz subscription this year. Tried changing Qobuz password and clearing Roon Server cache folder and restarting everything including networking.
Roon Server is running on a Windows Server 2019 Datacenter, playing to 2 RoPieee endpoints.
Hey @Revify5,
Thanks for taking the time to write in, it’s good to see you on community again!
Based on your screenshot, it may be worth double checking your Windows firewall settings, and ensure that Roon is listed as proper exceptions - here’s more info on that:
If you still run into issues after testing your firewall, we’ve seen other users find success when updating the DNS server settings on their Roon Server machine, so in your case, your windows computer. We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
Hi @benjamin,
Thanks for the response. I tried disabling the firewall and checked that rules exist for each app. It didn’t help but I noticed that RoonBridge is missing, maybe that is for a different setup? I also tried changing to Cloudeflare DNS and Google DNS and neither helped. Nothing has really changed since I renewed my subscription and it did work before.
I checked the log in RoonServer/logs and found this error near the end. (Redacted=[—])
Have you seen this problem before?
10/07 15:45:09 Warn: [easyhttp] [41] GET https://www.qobuz.com/api.json/0.2/user/login?device_manufacturer_id=[---] web exception without response: socketmsg (SocketError): The SSL connection could not be established, see inner exception. The SSL connection could not be established, see inner exception.
10/07 15:45:09 Warn: [qobuz] [http] error result from http request: System.Net.WebException: The SSL connection could not be established, see inner exception.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure'.
---> System.ComponentModel.Win32Exception (0x80090326): The message received was unexpected or badly formatted.
--- End of inner exception stack trace ---
Hey @Revify5,
Thanks for the follow up. Based on your account information, we’re seeing two instances of Roon Server that were active at the same time. Since you’re only using 1 license at this time, running two servers may cause some mix up and confusion among your local setup.
Can you confirm you run into the same issue with only one instance of Roon Server on and active?
There still seems to be some network blockage, indicating that the server was unable to establish a connection with the Qobuz server due to a timeout. Do you have any additional network security or antivirus / VPN gear active within your setup?
Can you confirm the same issue occurs if you setup a direct ethernet connection from your server machine to your router?
Hi @benjamin,
Thanks, I had an old second Roon Server running on another machine that wasn’t in use and I have closed the unused copy. The server running Roon is now connected directly to the router and there aren’t any VPNs running. I tried disabling Windows Defender on the server but nothing around that has changed since I renewed the Qobuz subscription. I’ve sent Qobuz emails asking for help but haven’t recieved a response yet.
I can play local music files with Roon. Qobuz service login is still not working from Roon. I can login to the the Qobuz app and music playback using Qobuz works through their app.
Hi @Revify5 ,
Can you try to clear out your Roon cache and let us know if this helps?
RoonServer/Cache/Cache folder elsewhere, like your desktopHello @noris,
Thanks for the steps to try.
I am not running Roon OS so I have instead powered down all Ropieee endpoints, Roon Server, and Roon app. Then I cleared the cache folder for Roon Server and Roon. I restarted Roon Server and Roon and tried logging into Qobuz service but am still getting the same error as shown above.
Hey @Revify5,
Thanks for giving that a try! Sorry to hear you’re still having issues as well.
We have seen this before - typically it’s something network related in regards to the client (your device or system) not reaching the Qobuz server:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Are you able to provide a more thorough description and breakdown of your network chain? How is your Windows connected to your router? Can you set up direct, hardwire ethernet connection?
Here are a few additional next steps to try out:
Check Internet Connectivity : Ensure your network has a stable internet connection and can access other secure websites.
Ping or Trace Route : Try running a ping or traceroute command to the IP 23.41.4.75 to see if there are any network issues or delays reaching the Qobuz server.
Firewall/Proxy Settings : Double check if any firewall or security settings could be blocking the connection to the Qobuz server again.
Hello thanks @benjamin,
My server is connected to my router with a 65 ft CAT 7 outdoor cable to a keystone in the wall, followed by a 3ft cable. I tried skipping the keystone and 3 ft cable but it did not help.
I tried ping and tracert, both worked but the tracert shows 10 hops and items 4, 7, 8, and 9 timeout but it reaches a23-41-4-75.deploy.static.akamaitechnologies.com [23.41.4.75] on the 10th item. All hops that repond do so in under 50ms.
I also tried moving Roon Server on my second Windows machine, and that does work fine. I can login to Qobuz from that machine and play music from there to the Ropieee endpoint. It is connected to the same router as my server machine. When I switch Roon Server back to my server behind the 65 ft cable it cannot login to Qobuz again. It is strange that this used to work until the Qobuz account was renewed for this year. The server has 2 network cards and I tried connecting the 65 ft cable to the other port and it did not help. I could try replacing the 65ft cable but that is a lot more work as it is partially inside the wall and would rather try it last.
Is there any way I could increase the TTL for the Roon Server app to wait for a response? It seems that the first time after a server reboot I try to login to Qobuz via Roon Service it takes a few seconds before failing, after that it fails immedietly to login when I retry it.
Hey @Revify5,
Thanks for the troubleshooting you’ve tried so far!
Was this second Windows machine also tested in the same network environment as your FILESERVER machine - connected via the 65ft cable?
If yes, and you were able to connect, then we can likely rule out your network and focus on the Windows 10 machine. It may be worth comparing privacy settings on both devices to check for any inconsistencies.
Hi @benjamin,
Both machines are an the same network connected to the same router. Which privacy settings do you recommend checking? I have already tried disabling the firewall and Windows Defender on the problematic server machine.
Hi @Revify5,
The most likely culprit is a cipher-related network error some users have resolved by looking into IISCrypto, an open-source tool for editing Windows protocols and ciphers. Note this source is an unsanctioned workaround outside Roon: Server 2019 - SSL handsake error - Windows - Spiceworks Community.
https://www.nartac.com/products/iiscrypto/
If this doesn’t help, Some additional troubleshooting:
Windows updates will sometimes change network handling, including port restrictions and stateful bandwidth restriction.
When the login fails, do you see the Host Network Service processes taking up significant bandwidth in the Windows Services Manager? If you restart the Windows Host Network Service and NAT manager , does the Qobuz API login successfully get through?
You can also use a terminal command prompt:
net stop hns
net start hns
Let us know if this helps.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.