Qobuz connect returning “bad request” on multiple fresh installs the past few days. Tidal connect working fine on all devices.
Also, Spotify plugin will connect and authorize but anytime the device is restarted it has to be authorized over again.
And Roon Bridge also not working. Will install, connect and “play” but no audio.
Documented on Pi 5 in separate post but now occurring on PC based installation:
Version 4.103
Tried the following:
Confirmed time settings correct.
Reset password on Qobuz and confirmed via web and app login.
Changed Volumio DNS to Cloudflare (1.1.1.1) and Google (8.8.8.8).
Logged out of Volumio, powered down and unplugged device for 10 minutes.
It’s happening on 4.084 and 4.103 on Pi 4, Pi 400, Pi 5 and X86 builds.
I can connect and authenticate into Qobuz via browser, Windows app and Android app on multiple devices so it’s not “my network”. Waiting for this suggestion next.
I have 2 RPi4s running Volumio, and they’re almost exclusively used with Qobuz, usually Connect. They sometimes disappear from Connect, but rebooting my router brings them back. The one time it didn’t it was a problem with the Qobuz Android app that was fixed in the next update.
On my existing Volumio devices (both running 4.084) that were setup months ago it setup and works fine. The past couple of weeks I have performed over 40 fresh installations on Pi 4, Pi 5, Pi 400 and x86 using 4.103 and 4.084 and setting Qobuz up as a SOURCE (like Tidal) fails every time. I have tried Chrome and Firefox and just for grins rebooted my router.
The fact that I can log into Qobuz via Chrome, Firefox in windows, the Windows App and Android App and authenticate tells me the only culprit left is Volumio.
Have either Qobuz or Volumio discussed a timeline for a fix? I can’t find any such statements online. I’m on a 30-day trial for Volumio, and while I really love how it sounds, a lack of native Qobuz integration is a deal-breaker for me given the cost of the Volumio subscription. (Qobuz Connect doesn’t sound as good.)
Yes, there is supposed to be Qobuz native integration, but a bug has developed that prevents Volumio Premium subscribers from linking their Qobuz accounts on new installations of the platform. Like @Rochambeaux, the starter of this thread, I keep getting taken to a “Bad Request” error screen after I enter my Qobuz subscription credentials on the Volumio’s “Sources” page. To be more precise, I am taken for just a second to a Qobuz page showing that I am logged in, but that is visible for just a moment before the “Bad Request” error screen appears. I am running on a Pi 4. I encounter this same bug when I test out earlier versions of Volumio, going back to version 3.795 (February 2025); these must have worked last year or we’d have heard about it then, so I assume the problem is a recent change by Qobuz. My concern is this is a low priority for Qobuz to fix, especially after the launch of Qobuz Connect, so who knows when they’ll get around to it.
Okay, I now have an explanation thanks to much backing and forthing with the lovely Clara, the customer service bot from Qobuz. Here’s what she/it wrote:
"What you’re describing - where existing integrations work fine but new setups suddenly fail across all Volumio versions - sounds like it could be related to our ongoing server migration to cloud infrastructure.
We’ve been migrating from our old servers to the cloud, which can sometimes cause temporary issues with third-party integrations during the transition process. This type of infrastructure change could explain why existing connections remain stable while new authentication attempts fail.
Since this affects new Volumio setups specifically and you’ve already tested with a fresh account, this needs technical investigation from our team. The authentication flow between Qobuz and Volumio’s integration system may need adjustment on our end.
You’ll need to request help from a human agent through this chat. Customer service is currently experiencing high volume, so don’t wait at your computer - an agent will respond by email in the coming hours or days."
So, there we have it. I’ll report back when a human gets in contact with me.
Not sure how Qobuz does the cloud migration, per region, country.
I’ve tested it with several rPi4, rPi5, x86 and a few Volumio OEM device. Running V3 (Buster) and V4 (Bookworm).
So far Qobuz hasn’t failed yet.
If there where serious issues with Native Qobuz, the forum would have been flooded with complaints by now.
Were those new installations? That is, did you flash a new SD card to set up Volumio/Qobuz from scratch, or did you use an existing system? I was at a friend’s house on Sunday who had a working Volumio/Qobuz system–in fact, the amazing sound I heard there is why I chose to go down the Volumio path myself. But then I couldn’t get native integration to work on a newly installed system (and I tried a bunch of different Volumio releases). I even created a brand new Qobuz account on a 30-day free trial offered directly from Volumio. No dice. So there seems to be a difference between existing systems and new systems. The Qobuz AI bot gave a reason why this could be the case. Stay tuned.
Yes the rPi4 and X86 where from Yesterday. These where all clean installs (no upgrades)
rPi4 booting from USB, x86 booting form it’s internal eMMC (All BW)
An Odroid M1S with a clean Buster install.
I did 25+ fresh installation attempts using a Pi 4, Pi 400, Pi 5 and X86 using 4.103 and it didn’t work on any of them. The DNS “fix” was proposed and it didn’t make a difference. The device time clock idea was thrown out as all devices checked out there.
After that i switched to 4.084 and that solved all my problems except the Qobuz one (fails across all) and an issue with Roon and HDMI on the Pi 5 and X86.
At that point i took what I had as a “not bad for Volumio” and decided to wait and see what happens with Qobuz.
