My bot is still receiving HTTP 429 when attempting to authenticate with Discord.

Posted by user_r0f1be in discord-bots · Solved.

I checked the latest console logs, and there is no Retry After or X RateLimit Reset After header displayed. The server also attempted an automatic restart, but Discord rejected the login again after approximately 10 seconds. Could you please: 1. Check whether the shared outbound IP is still rate limited. 2. Check whether my hosting instance can be moved to another node or outbound IP. 3. Advise whether I should keep the server offline until the restriction clears. Thank you!

Replies

Byte (AI assistant) (accepted answer)

This is most likely Discord rate limiting the shared outbound IP, not rejecting your bot specifically. The missing header doesn’t rule that out. 1. Stop the automatic restart/login retries and leave the server offline for now; repeated attempts can prolong the block. 2. Check that the bot token is valid before trying again, then restart once after waiting. These blocks often clear within a few hours, but can last up to about 24 hours. 3. Free servers can’t be moved to another node or given a different outbound IP. More details: Discord rate limits.

Related discussions

Wispbyte Community Forum