Qobuz authorization fails
Answered
i have signed up for a free trial of Qobuz with their studio plan. I can login on the Qobuz app, on a browser, but in the music services in BluOS, I always get an authorization failed.
following other advice on forums, I have changed my password on Qobuz, but still cannot login through BluOS.
the only thing i noticed was that if I click the free trial offer link in the BluOS app, it sends me to a location offering prices in euro. I am located in USA, with ATT Fiber. Another suggestion was to use the Google DNS servers, but ATT doesn't allow user to change DNS settings.
Any advice
Firmware is up to date, but I can't see a menu option to find the actual version
-
Official comment
Blusound reached out to me with DM. My fix was related to the security settings on my ATT supplied modem/router. From the app for my router, under advanced setting was a toggle to disable security, then I switched back to BluOS app, logged into Quboz. I then reenabled security on the ATT Smart Home app.
Not had a problem since.
-
Have a look at this… you can set static IP and DNS
-1 -
i was able to set the static IP and DNS servers on the player with that link. rebooted and verified the IP address was updated. Still getting authorization failed message.
other streaming services are logging in fine and playing
0 -
All I can suggest is to powercycle your Router, then when it fully up and running use the Bluesound app, select Help, Diagnotics, Reboot and see if this helps.
If it fails use the app again and select Help…Send Support Request. This way Bluesound will get the logs and be in touch directly.
-1 -
Does anyone else have any suggestions other than reboot or router???
Bluesound support has been worthless so far
1 -
I have the same issue, and I cannot disable security as suggested... Was this solved?
1 -
My solution with ATT Fiber was related to my router. I had to disable the firewall security temporarily in their Smart Home Manager and then Quboz would authenticate. Once connected, I reenabled the firewall settings and its been fine since. Even a full power cycle of router and the Bluesound device has not been an issue.
0 -
Interesting enough, I still get the error, but afterwards, qobuz is connected and works. I think it might just be a glitch in the software
0 -
This has completely ruined using the Node for me. I’m so over dealing with the numerous bugs I’m constantly running across when I should be listening to music.
0 -
Just FYI, I faced the same issue and I have a Netgear ORBI mesh network with Netgear Armor active. From the Orbi app I found that Armor was blocking qobuz auth URLs categorizing them as malware. I was able to unblock the URLs and login to Qobuz from BluOS. There are multiple URLs that I had to unblock for it to work.
0 -
the AT&T firewall began blocking me again. the method to approve URL's had changed and it took me a few hours to realise why the Node has stopped working. Glad others are getting it to work. Spotify/iheart radio, Sirius XM don't have an issue. From the router messages and log, I think the password is being passed by the BluOS to Qobuz unencrypted and that's why my router is blocking it. But it's a generic account name and password - not the account/password I use to listen online with the app or browser.
0 -
Well, it is calling the Qobuz API and passing username and password as URL parameters which is a MAJOR weakness. Though the username and password are not in cleartext, rather, encoded with some pre-shared token but still this appears to be a weakness in the Qobuz API. Public APIs should never accept credentials in URL parameters, rather negotiate a secure TLS session first and pass such data through that. This looks like a Qobuz weakness that BluOS maybe cannot address.
1
Please sign in to leave a comment.
Comments
12 comments