FWIW, I reported the same issue with a screenshot exactly like @Anders_Annerstedt . I had to reboot my Roon server (running on a PC, in my case), re-login to Qobuz through Roon Settings in the client, then restore from the most recent Roon backup to get all the Qobuz album additions to my Library re-established correctly.
FWIW, when I have restarted my Roon Core I have seen this message. “Retry” works in my case.
Hi all,
Same issue here in Ireland. Ive logged out of core and back in. Turned core off and back on. Will try rebbot as last resort. Qobuz app and web working just cant add to Roon. Any suggestions?
Thanks
Sean
Hi all,
Update!!,after reboot to rooter all ok and Qobuz added. Happily listening to Rory Gallagher 
In my case, turning the Nucleus off and back on solved the problem.
Far from it for me. Turning off and on my Sonictransporter to try resolving this hjas resulted in Roon can no longer find it, despite its being connected on the network and rebootable with the sonicorbiter software. Meanwhile, yes, Audirvana and Qobuz apps work fine but Roon is completely lost. I’ve rebooted everything in the chain. Nada.
Sonictransport shows on my Mac network as connected, shows in the web-based sonic orbiter software as connected - it’s only Roon that can no longer see it. This is really infuriating. Why the loss of Qobuz in the first place?
Resolved this for SonicTransport after finding the following advice on a forum - might help another: “I ended up resolving the issue today by checking the “Expose Roon Server database for backup and edits” option. Remote then connect to Core. I then unchecked the option and it still works.” Also, I can now log into Qobuz…
From the Qobuz website, was able to play an album to my computer. Roon sees the same album, but cannot access it. I therefore assume (simplistically?) that it is Roon/Qobuz interface issue. And there is a new behavior: Typically, when an album is unavailable or loading slowly, a related message appears. But now that doesn’t happen. The progress bar just zips back and forth as if the connection/location is never found.
Other new behavior: When I chose an album I ripped to my library, although it plays, there is a delay during which Roon seems to not only list the Qobuz equivalents (has always done that), but also tries to play one of those first, can’t, then finally plays the one in the library. Never saw that behavior before.
Thing tried but that didn’t work:
– emptying Qobuz cache within Qobuz website
– synching Qobuz library within Roon (setting, devices, open device, synch)
– shutting down Roon and restarting
Same login issue here - Qobuz through Roon not working
Tidal works fine, also through Roon
Have reset PW and multiple tries
If I unauthorized Roon Nucleus and sign in from local app, Qobuz available. Sign out from that and back into Nucleus and the problem reoccurs.
Solution turned out to be rebooting the Nucleus. Unplug it for a few minutes and then re-engage. Problem solved
Same for me, rebooted my Antipodes and was able to sign in.
on Antipodes interface you just need to restart Roon, not even to reboot the device
getting so tired of buggy roon
1 Like
What makes me snigger is the fact that Roon is openly developing the product to favour streaming providers as the music source and then this happens…
1 Like
Next step:
- Logout of Qobuz in Roon
- Stop Roon
- Find and open your Roon database
- Navigate to
Roon/Cache - Rename the
/Cachefolder to/Cache_old - Reboot your Roon Core and then Login to Qobuz
I guess I’m one of the lucky ones, power cycling my core eventually allowed me to log in to Qobuz. Weirdly I had to change my user name from my email (as in the screenshot) to some username I found in my records.
Tried clearing the cache via Qobuz website, then resynching the Qobuz library via Roon. Didn’t work. Cleared the cache in Roon (Settings, setup, clear cache). Nothing. Logged out of Qobuz, then could not log back in.
After those steps, finally rebooted the Grimm MU1, then was able to activate Qobuz service by logging into Qobuz as usual.
Indeed, simply rebooting Roon Core has fixed the problem. Thanks.