-
Notifications
You must be signed in to change notification settings - Fork 4
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
Lots of Received unknown response errors #9
Comments
We couldn't reproduce the error you shown, we're adding some more verbosity to the unknown code message you shown to include the status code, to help us reproduce the error. |
In the latest release 2.2.3 I've added some more verbosity on what exactly happened if an unknown response was received. Could you please try running that again? |
Sure! It's now running, I'll send a screenshot as soon as I can! |
It disconnected from my acc too for some reasons and connected back |
It only happens when there is a minor outage, or you lost internet connection for a bit. |
We just figured it out. Usually, Discord bots (and therefore selfbots, too) receive 403 errors if they try to access a resource they do not have the permissions to see. In our case a request to redeem a Nitro code always includes a channel ID where this code was found at. If the account that is trying to redeem the Nitro is not in this channel, you get a 403. It may be that the channel ID is not even required in the request, but we need to test more to find out. |
Well, If the channel ID is not required and It still snipes, Then remove it ^^ I'll keep testing |
It could be important, because the Discord client itself actually sends these two properties as the request body as it tries to redeem. This easily could just be ignored by the back-end, but it might also be the difference between sniping the code and getting blocked by Discord. Anyway, I'll remove this property from the request entirely, but I can't guarantee it'll manage to successfully snipe anything this way. Nevertheless, this has to be tested! |
Sure, what's your DiscorD? |
Fixed in RNS 2.3.0! |
I run two snipers for testing purposes , i don’t mind the risk of getting banned but i receive unknown response with rns and the other sniper receives already redeemed? I don’t what could possibly be wrong
The text was updated successfully, but these errors were encountered: