Lots of Received unknown response errors about rust-nitro-sniper HOT 13 CLOSED

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.

from rust-nitro-sniper.

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?

from rust-nitro-sniper.

e 2.2.3 I've added some more verbosity on what exactly happened if an unkn

Sure!

It's now running, I'll send a screenshot as soon as I can!

from rust-nitro-sniper.

from rust-nitro-sniper.

It disconnected from my acc too for some reasons and connected back

from rust-nitro-sniper.

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.

from rust-nitro-sniper.

happens when there is a minor outage, or

Probably the minor outage cus I'm using Microsoft Azure's RDPs xD

I host a gaming server with it didn't stop workin, also weird how only 1 of 3 disconnected :v

Any updates about this?

from rust-nitro-sniper.

Any updates about this?

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.

from rust-nitro-sniper.

Well, If the channel ID is not required and It still snipes, Then remove it ^^

I'll keep testing

from rust-nitro-sniper.

Then remove it

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!

from rust-nitro-sniper.

Then remove it

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!

Welp, Btw by any chance, Can we talk on discord? I don't like Git too much for communication xD

from rust-nitro-sniper.

Sure, what's your DiscorD?

from rust-nitro-sniper.

Fixed in RNS 2.3.0!

from rust-nitro-sniper.