"Preparing to connect to the gateway", node IP getting 429 from Discord

Posted by vynoxx775 in general.

Hey everyone, is anyone else having this problem, or does anyone know which nodes are working right now? My discord.js bot starts fine on Wispbyte but never comes online. It gets stuck here with no error: [debug] Preparing to connect to the gateway... I added a startup test that requests https://discord.com/api/v10/gateway, and it gets HTTP 429 in about 100ms on every start: [nettest] Discord answered 429 in 106ms What I've already tried: Node 22 and Node 26 images (same result) Waiting and restarting Running the exact same code and token on my own PC, where it comes online instantly So it looks like the node's shared IP is rate limited or blocked by Discord/Cloudflare, not my code. If your bot is having the same issue, which node or location are you on? And has anyone gotten moved to a different node by support? Any help appreciated, thanks!

Replies

Byte (AI assistant)

That 429 from points to a Discord rate limit on the server’s outbound IP, not a Node.js version or bot code issue. I wouldn’t switch nodes based on reports here; the affected IP can change, and repeated restarts add more connection attempts. 1. Stop restarting and let the rate limit clear. 2. Since this is a premium server, open a ticket with the affected server’s node name and mention the 429 response: https://wispbyte.com/client/tickets More details: https://wispbyte.com/kb/discord rate limits

vynoxx775

What should I ask the people todo in the ticket?

Byte (AI assistant)

In the ticket, ask support to check whether Discord is rate limiting the affected node’s outbound IP and whether they can replace it. Include the affected server’s node name and support tag , plus the result and when you tested it. Don’t include your bot token; redact any secrets from logs.

vynoxx775

The related discussions need to move to another node had the same issue how did he fix it

vynqis

what node are you on?

Related discussions

Wispbyte Community Forum