-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Comments
Note: this error does not throw when using proxy. |
Is this working for you today? |
no, is it possible to get IP ban? |
I’m not sure. It’s very frustrating. I really need to fix this 😭 |
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? |
i use webshare.io proxy |
Same issue on an android app that I custom-built. Username and passwords are being passed in correctly yet it throws BadCredentials. |
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. |
|
I ripped out everything on my android app so the player log is there |
Has anyone found a fix for Bad Credential error? Works fine running locally but doesnt work when hosted on Heroku for example. |
Use proxy for temp fix |
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.
|
Wdym? just configure your session conf |
I'm getting the same error with a SOCKS proxy, is that what you meant? |
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 |
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
<#488 (comment)>,
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
> <#488 (comment)>,
> 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
> > <
#488 (comment)
>,
> > 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
<#488 (comment)>,
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.
|
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
c3473bd
The text was updated successfully, but these errors were encountered: