-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] BadCredentials #277
Comments
If it can't be reproduced, I have a server that has this problem, and I'm up for helping in any way I can! |
I don't know the details, I suspect that your IP address has been blacklisted due to the number of login attempts? |
given that this occurred the only time I had ever tried on this server, no I don't believe that |
also i have this issue for login auth with this error |
I also got this error sometimes |
i solve this problem it belongs to ip of datacenters which in blacklist popular Datacenters like hetzener,...etc has this problem you can solve this issue by use a fresh ip |
@kokarare1212 I've started to encounter this too. |
I also encounter this issue since today.. Any fix? |
Same issue here with the bad credentials. |
This just started happening to me today too, might be an issue with spotify's client? I tried on a MacBook with latest MacOS and my linux desktop, both having same issue. I also tried with the latest install of librespot, that was working yesterday. Since this is happening to so many people they might have an issue with their api right now? |
I also have this issue on a windows machine. It's also being discussed in the librespot project directly here : librespot-org/librespot#1308 Feels like spotify changed something on their end maybe? |
@shayanmaher happening to me on a residential IP. Definitely not data center blacklisting, but rather seems like a buggy rolled-out deploy in their end or rather some of their pesky A/B API testing |
this is not true. happens on all residential IPs ive tried now. that was absolutely just part of the rollout. |
Happening to me as well. |
It appears that login using username and password has been discontinued. |
@kokarare1212 Could you then provide the instructions on how to use Zeroconf instead of Session? |
Same issue for me, even changing IP's through a VPN doesn't work.
|
UPDATE: Got it to work... Somehow... Still not quite sure how but I tried restarting my PC and deactivating my VPN, and it worked. Perhaps through trial and error? Or Spotify is blocking CLI requests that come from known VPN servers? I have no idea... |
Please provide the instructions on how to use Zeroconf instead of Session? |
It is incomplete but should work. Sample code can be found here. Remember I have very little time to devote to these projects. |
Very unclear. btw, I don't see
|
Forgive me for jumping in, but you have to actually use the zeroconf server to auth a client before a session will be created. Given the log you provided, it doesn't look like you did that. |
idk about you guys i can still login fine with email and password and whenever i get BadCredentials issue i delete the credentials json and change my account password and it starts working again. tho its been a while since i had that issue |
Login with username/password via
@pdtan you may use this very sketchy code to generate credentials file to use further. Notice that device running the script should be on the same network as a desktop client in order to transfer playback or/and grab session Use session = Session.Builder() \
.stored_file() \
.create() It should use |
Cool beans, that works. Question: do the credentials expire? |
Reusable credentials do not expire. |
@clemwo they don't expire, unless you change your password or Spotify does. Successful login with zeroconf should always return the same long-live credentials that The Spotify desktop client stores account login data in the client configuration file in a similar way: .config/Spotify/prefsautologin.blob="BLOB"
autologin.saved_credentials="{"USERNAME": ["USERNAME", "BLOB"]}" |
@clemwo thanks, but I use credentials.json from start, sometimes BadCredentials still happended, not usual. If using zeroconf to only create credentials.json, I actually don't need it.
|
On Windows (this works on Linux) trying to use zeroconf results in the following:
|
Hello everyone. Tell me if the librespot.core problem has been |
I don't quite get how to generate the credentials. Quick glance at zeroconf.py tells me that I somehow need to get into
|
Select the running librespot instance in your Spotify client. You should find it in the list of Spotify Connect devices in Spotify's client. That device menu is at the bottom of their app on the currently playing bar, it has a speaker/computer icon. Selecting the librespot instance will send the required auth data to the Zeroconf server where it can be stored and reused indefinitely. |
Unfortunately this code doesn't work when run in asyncio. I get the following error:
Does anyone have an idea on how to adjust the code to make it run in async? |
This tool helped me to generate the |
Describe the bug
Login fails on some accounts on some devices. My current guess is they're doing some kind of A/B test to phase out something this relies on? Maybe the protocol version needs to be updated?
Occurs not just here but also on the separate librespot-js project and librespot-java. The bug is not with some library-specific logic but with a change to Spotify- a fix here will likely also be able to be applied everywhere else.
To Reproduce
Expected behavior
The login should be successful.
Screenshots
Client Information (please complete the following information):
The text was updated successfully, but these errors were encountered: