I tried to connect with my bot project (https://glitch.com/~collaboradev-game-voting) but it refuses to connect. I downloaded the files and ran them locally on my local machine changing only the .env values to be constants and it works perfectly.
When I run the same thing in glitch, I get no errors, nothing, it just hangs. My other bot works perfect and has the exact same connection code.
If you need a quick solution, I’d recommend remixing the app then boosting the new app. This way you can get a new IP that hopefully, isn’t banned from Discord.
@glitch_support Maybe we could put boosted apps/bots on different IPs that are not being used by all the free apps, so they are less likely to get banned. Just an idea and it will possibly avoid people leaving/going to a different hosting provider that doesn’t have these issues because their bots that they are paying for are not actually working
Unfortunately, Glitch doesn’t really have control of what IP’s get banned and what don’t. Discord immediately escalates to an IP ban if there are multiple instances of abuse, which sometimes means one problematic bot can affect all the bots on that same IP. Glitch doesn’t really have a way to see which apps abuse Discord’s API.
Yeah, think like sending out mass DM’s, spamming the API. Take a look at this, it was sent by a Discord Staff member.
Regarding Rate Limits
A new system has been deployed that auto ip-bans IP addresses that send the API too many invalid requests. Today, that is considered to be requests that result in a 401, 403 or 429 HTTP status code as a response. This is in response to some pathologically bad bots spamming our API with said invalid requests.
This means that you need to send 25,000 requests in 10 minutes that result in a 401, 403 or 429 in order to be auto-banned.