-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Login Command: decode JSON failed #57
Comments
cloudflare updated about ssl 2 days ago I try to fix it every day. Some people can use it normally. Some people just can't use it. |
Oh wait I think this time it could actually be not on your side. AFAIK there a currently some issues with the login in the game client too. BTW thx for the fast response |
Okay the server issues seems to be fixed. At least I can login again in the game |
I also have the same issue, here is the error when trying to login, but instead of showing me an error on discord it just says that the application isn't available and it outputs me this in the console.
INFO - I'm using the latest release. |
try master version |
It didn't work for me either, I deleted and reinstalled and it works! @osu |
Using master version got this error still.
|
cloudflare gave me a huge headache. you can try again master |
Tried again importing master directly. Getting this.
|
Tomorrow I will try to fix it again. ;-;) |
All good, let me know ! |
try replace utils/valorant/auth.py |
|
os windows 10 right? |
No, Debian OS based server hosted at Hetzner (Nuremberg city) |
It has to do with protocol, ssl, or internet related stuff, I'm not really sure. |
Issue still exists, there is no valid response by the Riot Auth servers |
Using the login command results in an error.
changing the code in
https://github.com/staciax/Valorant-DiscordBot/blob/c76f330f2d3d1dc691330e542dab056fc3122dd2/utils/valorant/auth.py#L97 to disable the content_type check to
r.json(content_type=None)
reveals that the response of the riot games api tohttps://auth.riotgames.com/api/v1/authorization
is returning a 403.I don't know what your source is but the same issue is mentioned here but the suggest fix doesn't work for me.
I also found this which might be helpful.
The text was updated successfully, but these errors were encountered: