LMS - wrong password/invalid api

Support
1

Issue description:

I’m unable to login to my LMS server - recieving the ‘wrong username or password’ or ‘wrong API key’ message on the LMS logs even though the password, username and API are all correct.

I saw a previous post about an update to LMS, but I’m running the newest version, so a bit confused. Have restarted everything a few times, no changes

Logs:

Upload description: meditate

Additional information:

 

 

Reproduction steps:

 
attempt to connect to LMS for first time
 

Media provider:

Subsonic - LMS

Screenshots:

 

Screenshot 1
Screenshot 11105×224 118 KB
    

2

LMS have migrated away from passwords, you need to use API keys, either as password or by enabling API key usage in Symfonium provider settings.

@itm

3

thanks! managed to get it to work with a new API.
Didn’t see anything about not being able to use the user/password, but I often miss things…

4

Yes ITM went all in with that change :slight_smile:

5

And the documentation what this change will entail could have been a bit clearer (or I missed something). I found out that you simply have to generate an API token and use that instead of the password in Symfonium by trying it on a test instance before migrating the main one.

6

It’s actually better to fully switch to API mode in Symfonium.

But yes @itm docs docs docs :stuck_out_tongue: artists images:)

7

Better in what respect? Is the username not validated anyhow and thus superfluous? I just switched the toggle to “Use an API key” and I can still access lms, so I guess that’s the case. Also, is it expected that switching this toggle invalidates/deletes all thumbs? Even for my fav playlist (that I traverse daily) none of the tracks had an image until they got repopulated while scrolling over them.

8

Don’t you guys read release notes? :wink:

I found that quite self-explanatory, only did Symfonium not yet support a dedicated API Auth mode at that moment.

9

That’s the part that confused me.

If I had not, I wouldn’t have tested how to use the new auth before updating the main instance.