Skip to content
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

BadAuth when creating session #488

Open
KagChi opened this issue Apr 21, 2022 · 29 comments
Open

BadAuth when creating session #488

KagChi opened this issue Apr 21, 2022 · 29 comments
Labels
bug Something isn't working

Comments

@KagChi
Copy link

KagChi commented Apr 21, 2022

Describe the bug
Somehow I can't login to spotify account, it always throwing BadAuth error, I tried with other account, still same. (im sure the pass i use is valid, tried on web player)

To Reproduce
Login as usual

Expected behavior
Logged in with provided account

Screenshots/Stracktraces/Logs
Screenshot_2022-04-21-18-18-29-07

Version/Commit
c3473bd

@KagChi KagChi added the bug Something isn't working label Apr 21, 2022
@KagChi
Copy link
Author

KagChi commented Apr 21, 2022

Note: this error does not throw when using proxy.

@jpgrovy
Copy link

jpgrovy commented Apr 22, 2022

Is this working for you today?

@KagChi
Copy link
Author

KagChi commented Apr 23, 2022

Is this working for you today?

no, is it possible to get IP ban?

@jpgrovy
Copy link

jpgrovy commented Apr 23, 2022

I’m not sure. It’s very frustrating. I really need to fix this 😭

@jpgrovy
Copy link

jpgrovy commented Apr 23, 2022 via email

@iscle
Copy link
Collaborator

iscle commented Apr 28, 2022

If it's not shown when using a proxy it must be something related to your IP... Which proxy did you use?

@KagChi
Copy link
Author

KagChi commented Apr 28, 2022

i use webshare.io proxy

@bs2kbs2k
Copy link

Same issue on an android app that I custom-built. Username and passwords are being passed in correctly yet it throws BadCredentials.

@iscle
Copy link
Collaborator

iscle commented May 7, 2022

@bs2kbs2k @KagChi Can you post the full log please? Set the logLevel to all in the config file first :)

@KagChi
Copy link
Author

KagChi commented May 7, 2022

Its was working yesterday. but i think the reason i got blocked is because too many times relogin to that account.

iirc the error is same if you provide wrong creds.

@bs2kbs2k
Copy link

bs2kbs2k commented May 7, 2022

@bs2kbs2k @KagChi Can you post the full log please? Set the logLevel to all in the config file first :)

2022-05-07 20:37:15,175 INFO  ApResolver:90 - Loaded aps into pool: {accesspoint=[ap-gae2.spotify.com:4070, ap-gae2.spotify.com:443, ap-gae2.spotify.com:80, ap-gew1.spotify.com:4070, ap-guc3.spotify.com:443], dealer=[gae2-dealer.spotify.com:443, guc3-dealer.spotify.com:443, gew1-dealer.spotify.com:443], spclient=[gae2-spclient.spotify.com:443, guc3-spclient.spotify.com:443, gew1-spclient.spotify.com:443]}
2022-05-07 20:37:15,268 DEBUG TimeProvider:90 - Loaded time offset from NTP: 13ms
2022-05-07 20:37:15,994 INFO  Session:137 - Created new session! {deviceId: 2c89be24c40cc491dd131e3c5f06b98adae0dc40, ap: ap-gew1.spotify.com:4070, proxy: false} 
2022-05-07 20:37:16,831 INFO  Session:331 - Connected successfully!
2022-05-07 20:37:17,342 ERROR Log4JUncaughtExceptionHandler:31 - [main]
xyz.gianlu.librespot.core.Session$SpotifyAuthenticationException: BadCredentials
        at xyz.gianlu.librespot.core.Session.authenticatePartial(Session.java:450) ~[librespot-player-1.6.2.jar:1.6.2]
        at xyz.gianlu.librespot.core.Session.authenticate(Session.java:339) ~[librespot-player-1.6.2.jar:1.6.2]
        at xyz.gianlu.librespot.core.Session.access$600(Session.java:77) ~[librespot-player-1.6.2.jar:1.6.2]
        at xyz.gianlu.librespot.core.Session$Builder.create(Session.java:1029) ~[librespot-player-1.6.2.jar:1.6.2]
        at xyz.gianlu.librespot.player.Main.main(Main.java:80) ~[librespot-player-1.6.2.jar:1.6.2]

@bs2kbs2k
Copy link

bs2kbs2k commented May 7, 2022

I ripped out everything on my android app so the player log is there

@jpgrovy
Copy link

jpgrovy commented Dec 4, 2022

Has anyone found a fix for Bad Credential error? Works fine running locally but doesnt work when hosted on Heroku for example.

@KagChi
Copy link
Author

KagChi commented Dec 5, 2022

Use proxy for temp fix

@jpgrovy
Copy link

jpgrovy commented Dec 5, 2022 via email

@KagChi
Copy link
Author

KagChi commented Dec 5, 2022

Wdym? just configure your session conf

@arch-btw
Copy link

arch-btw commented Dec 6, 2022

I'm getting the same error with a SOCKS proxy, is that what you meant?

@jpgrovy
Copy link

jpgrovy commented Dec 6, 2022 via email

@KagChi
Copy link
Author

KagChi commented Dec 9, 2022

image

Looks like proxy isnt working now, still got bad authorizations.

@KagChi
Copy link
Author

KagChi commented Dec 9, 2022

@iscle https://hastebin.de/ozejeniwiw.apache here is the full stackrace, please investigate out

@jpgrovy
Copy link

jpgrovy commented Dec 9, 2022

image

Looks like proxy isnt working now, still got bad authorizations.

They made a lot of changes yesterday. They are blocking IP’s now of data centers. They have done this in the past and then reversed it. Proxies must be good residential proxies for sure to work.

@KagChi
Copy link
Author

KagChi commented Dec 10, 2022

image
Looks like proxy isnt working now, still got bad authorizations.

They made a lot of changes yesterday. They are blocking IP’s now of data centers. They have done this in the past and then reversed it. Proxies must be good residential proxies for sure to work.

Proxy has no effect this time, tested on my local it works neither proxied nor doesnt

@jpgrovy
Copy link

jpgrovy commented Dec 10, 2022

image
Looks like proxy isnt working now, still got bad authorizations.

They made a lot of changes yesterday. They are blocking IP’s now of data centers. They have done this in the past and then reversed it. Proxies must be good residential proxies for sure to work.

Proxy has no effect this time, tested on my local it works neither proxied nor doesnt

You can’t even log in locally ?

@KagChi
Copy link
Author

KagChi commented Dec 10, 2022

image
Looks like proxy isnt working now, still got bad authorizations.

They made a lot of changes yesterday. They are blocking IP’s now of data centers. They have done this in the past and then reversed it. Proxies must be good residential proxies for sure to work.

Proxy has no effect this time, tested on my local it works neither proxied nor doesnt

You can’t even log in locally ?

I mean, i can log in with same proxy or without proxy. so i suppose the proxy has no effect rn

@jpgrovy
Copy link

jpgrovy commented Dec 10, 2022 via email

@KagChi
Copy link
Author

KagChi commented Dec 10, 2022 via email

@jpgrovy
Copy link

jpgrovy commented Dec 10, 2022 via email

@KagChi
Copy link
Author

KagChi commented Dec 11, 2022 via email

@leon-sleepinglion
Copy link

I found a workaround for this issue.

Steps.

  1. Log in locally following the suggested way.
  2. Copy the credentials.json from local to VPS.
  3. On VPS, log in using stored credentials.
  4. Voila. 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants