Closed mistralwz closed 2 years ago
Yeah, rito have seen a lot of malicious traffic from people trying to crack Valorant accounts, so as a part of the 2FA update they're tightening security on the auth via a very strict Cloudflare firewall.
Here are a few screenshots from the conversation with a riot dev:
So yeah, Riot are not too keen on apps that use usernames/passwords to log in.
Personally using /cookies
still works, but I think cookies have gotten longer as well, so much so that they're over the 4000 char limit for nitro users lol. Cutting out the __Secure-id_hint
and __cf_bm
cookies is just enough to get under it, but that doesn't help non-nitro users.
A fix for that would be to let users upload their cookie in a txt file.
Overall, this is a change on Riot's end, most if not all third-party unofficial projects are affected, and no clear solution is available at the moment.
Your reply is really detailed yet easy to understand for someone as inexperienced as I am, thank you!!
And regarding the cookies command, a friend of mine (w/o Nitro) could send the command with the cookies being 3.5k characters so I think for now everyone can login like that. Perhaps changing the /login output linking this wiki would be nice for the time being...
Yeah, changing the /login
command to accept cookies by default is the last resort.
Until then, I think I might have fixed it with https://github.com/giorgi-o/SkinPeek/commit/abcc431ba777d5b2c5971652b157c0114f75ccee, could you give it a go?
Tried abcc431ba777d5b2c5971652b157c0114f75ccee, everything seems to be working fine!!
Ok so it's been a week and it seems to work fine, I think I can consider this resolved :)
Started happening this morning, I think Rito updated something on their end. This crash gets triggered whenever someone /login or when there's an existing users.json DB on startup,