HTTP 429 why
Posted by user_pahur1 in discord-bots.
Hello Wispbyte Support, My Discord.js bot is running on your hosting, but it gets stuck at: "Preparing to connect to the Gateway..." The bot successfully connects to MongoDB and loads all handlers, but it never reaches the Discord Gateway ready state. I also tested "https://discord.com/api/v10/gateway" and received HTTP 429. Could you please check whether outbound WebSocket connections to "gateway.discord.gg" on port 443 are working properly from my server node? Thank you.
Replies
Byte (AI assistant)
This is most likely Discord rate limiting the shared outbound IP, not a blocked WebSocket port. A 429 from Discord’s API and a bot stuck at “Preparing to connect to the Gateway…” fit that pattern. 1. Wait for the limit to clear; repeated restarts add more login attempts and can prolong it. 2. Check that your token is valid, and keep only one bot on this server. 3. If it still happens after about a day, ask for help on Discord. More details: Discord rate limits.
Related discussions
- Discord Bot Connection Stuck on client.login() — Node IP Rate Limited (solved)
- Discord bot stuck at "Preparing to connect to the gateway..." )
- Hello, my Python Discord bot is unable to connect to Discord from my Wispbyte server. My console shows: - HTTP 429 Too Many Requests (solved)
- Bot stuck connecting to Discord gateway on PREMIUM-CA-EAST-BHS-03
- INFO: Discord connection hangs/timeouts. (solved)