Describe the bug
Hi, I’m testing Qobuz login on streamrip 2.2.0 (installed from this fork), and login consistently fails even though the Qobuz account is a normal local account and the credentials are correct.
Environment
What I did
-
Reset config:
rip config reset
-
Filled in my Qobuz email and MD5 password in config.toml:
[qobuz]
use_auth_token = false
email_or_userid = "MY_EMAIL"
password_or_token = "MY_MD5_PASSWORD"
app_id = ""
secrets = []
-
Ran:
rip -v search qobuz track "test"
What happens
streamrip is able to fetch and populate app_id and secrets automatically, so that part seems to work.
However, the final user/login request fails with HTTP 401.
Relevant debug output:
INFO App id/secrets not found, fetching
DEBUG Request params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG api_request: endpoint=user/login, params={'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG Login resp: {'code': 401, 'message': 'User authentication is required.', 'status': 'error'}
AuthenticationError: Invalid credentials from params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
Important notes
- This is a normal Qobuz local account, not Google/Apple/Facebook login.
- The email/password works on the official Qobuz website.
- app_id and secrets are successfully fetched and written into config.
- The failure seems to happen specifically at the user/login API step.
Expected behavior
Qobuz login should succeed with valid local-account credentials.
Actual behavior
Qobuz returns:
401
User authentication is required.
and streamrip raises:
AuthenticationError: Invalid credentials from params ...
Question
Has Qobuz changed the expected login flow or password/auth format for user/login?
It looks like app ID / secrets fetching still works, but the final authentication request is no longer accepted.
Command Used
rip -v search qobuz track "test"
Debug Traceback
[11:52:47] DEBUG Showing all debug logs
INFO App id/secrets not found, fetching
DEBUG Request params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG api_request: endpoint=user/login, params={'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG Login resp: {'code': 401, 'message': 'User authentication is required.', 'status': 'error'}
AuthenticationError: Invalid credentials from params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
Config File
[qobuz]
quality = 3
download_booklets = true
use_auth_token = false
email_or_userid = "MY_EMAIL"
password_or_token = "MY_MD5_PASSWORD"
app_id = "798273057"
secrets = ["SECRET_1", "SECRET_2", "SECRET_3"]
[misc]
version = "2.2.0"
check_for_updates = true
Operating System
debian 12
streamrip version
2.2.0
Screenshots and recordings
No response
Additional context
No response
Describe the bug
Hi, I’m testing Qobuz login on streamrip 2.2.0 (installed from this fork), and login consistently fails even though the Qobuz account is a normal local account and the credentials are correct.
Environment
streamrip @ git+https://github.com/mikelandzelo173/streamrip.git
What I did
Reset config:
rip config reset
Filled in my Qobuz email and MD5 password in config.toml:
[qobuz]
use_auth_token = false
email_or_userid = "MY_EMAIL"
password_or_token = "MY_MD5_PASSWORD"
app_id = ""
secrets = []
Ran:
rip -v search qobuz track "test"
What happens
streamrip is able to fetch and populate app_id and secrets automatically, so that part seems to work.
However, the final user/login request fails with HTTP 401.
Relevant debug output:
INFO App id/secrets not found, fetching
DEBUG Request params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG api_request: endpoint=user/login, params={'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
DEBUG Login resp: {'code': 401, 'message': 'User authentication is required.', 'status': 'error'}
AuthenticationError: Invalid credentials from params {'email': 'MY_EMAIL', 'password': 'MY_MD5_PASSWORD', 'app_id': '798273057'}
Important notes
Expected behavior
Qobuz login should succeed with valid local-account credentials.
Actual behavior
Qobuz returns:
401
User authentication is required.
and streamrip raises:
AuthenticationError: Invalid credentials from params ...
Question
Has Qobuz changed the expected login flow or password/auth format for user/login?
It looks like app ID / secrets fetching still works, but the final authentication request is no longer accepted.
Command Used
rip -v search qobuz track "test"Debug Traceback
Config File
Operating System
debian 12
streamrip version
2.2.0
Screenshots and recordings
No response
Additional context
No response