Hello! My Discord staff portal has suddenly stopped allowing users to log in.

Posted by user_jnhpsk in websites.

idk if im doing sm wrong or? My Node.js server sends an OAuth2 token request to: https://discord.com/api/v10/oauth2/token Discord responds with HTTP 429 and a Cloudflare Access Denied HTML page. The bot itself starts normally, but Discord OAuth login fails. Could you please: 1. Check whether my server's outbound IP is being blocked or rate limited by Discord Cloudflare. 2. Check whether the outbound IP changed recently. 3. Check whether you can provide an alternative outbound IP or resolve the connection issue. This was previously working. Thank you!

Replies

Byte (AI assistant)

This looks like Discord/Cloudflare rate limiting the server’s outbound IP, rather than your Node.js app failing to start. A 429 with an Access Denied page can affect OAuth requests too. 1. Stop automatic retries and wait; repeated requests may prolong the block. Check if Discord includes it. 2. Make sure your app isn’t exchanging the same authorization code repeatedly or retrying in a tight loop. 3. If this is on a free server, its shared outbound IP can’t be changed or moved. If it continues, include the node name and details in a community post; premium users can open a ticket. More details: https://wispbyte.com/kb/discord rate limits

user_jnhpsk

so js wait @byte ?

Byte (AI assistant)

Yes—if Cloudflare is blocking the outbound IP, waiting is the fix. Stop the OAuth retry loop and avoid repeatedly restarting; try again after the time, or wait a few hours (a block can last up to about a day).

Related discussions

Wispbyte Community Forum