librespot-java
librespot-java copied to clipboard
librespot-org
BadAuth when creating session
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
Version/Commit c3473bda8a70fad209c8525b04c2fd23ccc0d2fa
I don’t think it’s an ip ban issue. I tried making a whole new deployment on a new server and it’s not working for me.
On Apr 22, 2022, at 9:57 PM, KagChi @.***> wrote:
Is this working for you today?
no, is it possible to get IP ban?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
If it's not shown when using a proxy it must be something related to your IP... Which proxy did you use?
Same issue on an android app that I custom-built. Username and passwords are being passed in correctly yet it throws BadCredentials.
@bs2kbs2k @KagChi Can you post the full log please? Set the logLevel to all in the config file first :)
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 @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]
Has anyone found a fix for Bad Credential error? Works fine running locally but doesnt work when hosted on Heroku for example.
Do you have an example how to do this on Heroku ?
On Dec 4, 2022, at 10:48 PM, KagChi @.***> wrote:
Use proxy for temp fix
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
I wasn’t using any proxies and didn’t have any problems for 6+ months. Now all of a sudden I get Bad Credentials error
On Dec 6, 2022, at 12:49 PM, arch-btw @.***> wrote:
I'm getting the same error with a SOCKS proxy, is that what you meant?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
@Iscle https://hastebin.de/ozejeniwiw.apache here is the full stackrace, please investigate out
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.
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
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 ?
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
The “Bad Credentials” error is gone ?
On Dec 10, 2022, at 7:47 AM, KagChi @.***> wrote:
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
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
It doesnt throw the error on my local pc, but it does throw the error on my vps
On Sat, Dec 10, 2022, 23:11 jpgrovy @.***> wrote:
The “Bad Credentials” error is gone ?
On Dec 10, 2022, at 7:47 AM, KagChi @.***> wrote:
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
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
— Reply to this email directly, view it on GitHub https://github.com/librespot-org/librespot-java/issues/488#issuecomment-1345296817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFDZ34XL4EGJL2OWQZ2Y43WMSTTNANCNFSM5T65LQLA . You are receiving this because you were mentioned.Message ID: @.***>
Ok.. so same problem then. And you’ve tried good proxies on your vps? Spotify started blocking all vps provider ip’s.
On Dec 10, 2022, at 11:34 AM, KagChi @.***> wrote:
It doesnt throw the error on my local pc, but it does throw the error on my vps
On Sat, Dec 10, 2022, 23:11 jpgrovy @.***> wrote:
The “Bad Credentials” error is gone ?
On Dec 10, 2022, at 7:47 AM, KagChi @.***> wrote:
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
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
— Reply to this email directly, view it on GitHub https://github.com/librespot-org/librespot-java/issues/488#issuecomment-1345296817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFDZ34XL4EGJL2OWQZ2Y43WMSTTNANCNFSM5T65LQLA . You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
I already said, proxy has no effect. the proxy only proxy http request. i dont think we login to Spotify only using their http. pretty sure they have ws
On Sat, Dec 10, 2022, 23:40 jpgrovy @.***> wrote:
Ok.. so same problem then. And you’ve tried good proxies on your vps? Spotify started blocking all vps provider ip’s.
On Dec 10, 2022, at 11:34 AM, KagChi @.***> wrote:
It doesnt throw the error on my local pc, but it does throw the error on my vps
On Sat, Dec 10, 2022, 23:11 jpgrovy @.***> wrote:
The “Bad Credentials” error is gone ?
On Dec 10, 2022, at 7:47 AM, KagChi @.***> wrote:
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
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
— Reply to this email directly, view it on GitHub < https://github.com/librespot-org/librespot-java/issues/488#issuecomment-1345296817 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOFDZ34XL4EGJL2OWQZ2Y43WMSTTNANCNFSM5T65LQLA
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
— Reply to this email directly, view it on GitHub https://github.com/librespot-org/librespot-java/issues/488#issuecomment-1345302744, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOFDZ34EJYBIUI2RKZZAH5DWMSXBJANCNFSM5T65LQLA . You are receiving this because you were mentioned.Message ID: @.***>
I found a workaround for this issue.
Steps.
- Log in locally following the suggested way.
- Copy the
credentials.jsonfrom local to VPS. - On VPS, log in using stored credentials.
- Voila. 🎉
