No. and the same setup could be fine to login Qobuz within Roon a few months ago. Clash acts as a system proxy and plays the same role for Roon and browser. Judging from Clash’s logs, Qobuz Webplayer send a request for “www.qobuz.com” when logging in, but Roon request a dynamic IP(e.g.31.13.95.48:443).
It looks like you are getting an HTML error response from the login request, which is very strange. I suspect that a VPN or your Clash software is injecting this HTML response. Can you try to fully disable Clash or temporarily try to login with the Server on a different network?
Thanks for your reply, glad to see the news that Roon supports Tidal Max, which means I don’t need to stick with Qobuz.
I know there are quite a few users in mainland China who have encountered the same problem as me. The only thing I can’t figure out is that I can login to Qobuz within third-party software and Webplayer, but not Roon.
I tried Qobuz Downloader and Qobuz Webplayer in the same environment(using Clash), and their login APIs were identical to the requests made by Roon. Since Clash is a necessary software for me, I give up using Qobuz.