Thought it was resolved but alas. Today again no connection with Qobuz via Roon. Can play directly in Qobuz. There was a warning in Roon that there was an error in the connection, but logging in again with usersname and password has no result:
It is noticeable that the Qobuz folder has disappeared (Tidal too but I don’t have an account for that) and further the folder httpccache.db
Is there a simple explanation for this result and is there an advice to do this regularly: once a…?
Happened here again as well (US)! With multiple reports of users with the same issue, something is definitely up with Roon/Qobuz. This never happened for years, now this is the second time in the past few weeks.
Rebooting and logging in again resolved it for now, but like was mentioned, we shouldn’t have to keep doing this.
Not to pile on, but I am having the issue as well. I have cleared the cache on the Roon remote (macos) and on the core (Rock) multiple times with reboots of all. One thing I have not seen mentioned is where does the auth attempt get logged? It would be nice if I could see some attempt being made. I don’t see it on the controller or the core in the normal Roon logs locations. This is getting annoying as it is a bit source of the music I listen to in Roon.
P.S. Everyone is up to date with 1.8 1021.
Edit. I lied, there is something in the log. So time to figure that out. (It had been working fine up until last week. Wish I could see the host…) 08/22 22:38:15 Warn: [qobuz] [http] error result from http request: Request canceled due to timeout
The message I’d received opens with:
Thank you for your message, we hope that you are doing well. We have contacted Roon about this issue, this should solve the problem:…and then you see the seven points.
So it looks like the solution for this bug, but not who’s the cause of it.