What happened
Cliamp 2.2.0 cannot connect to a Jellyfin server. cliamp setup fails with 400/401 responses and reports validation failed.
I initially suspected this was caused by Jellyfin 12's removal of legacy authentication, but the same problem occurs with a freshly installed Jellyfin 10.10.7 server.
I tested all three authentication methods supported by the cliamp setup:
- Jellyfin API token
- Jellyfin username/password
- Jellyfin user access token
None of them work.
The Jellyfin server itself is reachable and healthy. The same credentials can successfully authenticate using Jellyfin's HTTP API directly.
For example, a user access token successfully authenticates against /Users/Me:
curl -i \
-H 'Authorization: MediaBrowser Client="curl", Device="curl", DeviceId="curl-test-1", Version="1.0.0", Token="ACCESS_TOKEN"' \
http://localhost:8096/Users/Me
This returns HTTP 200.
An API token also successfully authenticates against a server-level endpoint:
curl -i \
-H 'Authorization: MediaBrowser Client="curl", Device="curl", DeviceId="curl-test-1", Version="1.0", Token="API_TOKEN"' \
http://localhost:8096/System/Info
This returns HTTP 200.
So the Jellyfin server, network connection, and credentials are working; the failure appears to be in cliamp's Jellyfin integration.
Steps to reproduce
- Install Jellyfin 10.10.7 on macOS using the official DMG.
- Start Jellyfin and configure a user and music library.
- Run
cliamp setup.
- Configure the Jellyfin server URL.
- Try API token authentication, username/password authentication, and a user access token.
- Cliamp fails validation with HTTP
400/401 in all cases.
Expected behavior
Cliamp should authenticate with the Jellyfin server and successfully validate the provider configuration.
Screenshots / video
N/A
Environment
- cliamp version (
cliamp --version): 2.2.0
- OS: macOS (Apple Silicon)
- Audio backend (PipeWire / PulseAudio / ALSA): N/A
- Provider(s) involved: Jellyfin
- Jellyfin version: 10.10.7
What happened
Cliamp 2.2.0 cannot connect to a Jellyfin server.
cliamp setupfails with400/401responses and reportsvalidation failed.I initially suspected this was caused by Jellyfin 12's removal of legacy authentication, but the same problem occurs with a freshly installed Jellyfin 10.10.7 server.
I tested all three authentication methods supported by the cliamp setup:
None of them work.
The Jellyfin server itself is reachable and healthy. The same credentials can successfully authenticate using Jellyfin's HTTP API directly.
For example, a user access token successfully authenticates against
/Users/Me:curl -i \ -H 'Authorization: MediaBrowser Client="curl", Device="curl", DeviceId="curl-test-1", Version="1.0.0", Token="ACCESS_TOKEN"' \ http://localhost:8096/Users/MeThis returns HTTP 200.
An API token also successfully authenticates against a server-level endpoint:
curl -i \ -H 'Authorization: MediaBrowser Client="curl", Device="curl", DeviceId="curl-test-1", Version="1.0", Token="API_TOKEN"' \ http://localhost:8096/System/InfoThis returns HTTP 200.
So the Jellyfin server, network connection, and credentials are working; the failure appears to be in cliamp's Jellyfin integration.
Steps to reproduce
cliamp setup.400/401in all cases.Expected behavior
Cliamp should authenticate with the Jellyfin server and successfully validate the provider configuration.
Screenshots / video
N/A
Environment
cliamp --version): 2.2.0