A rate limit means requests arrived too quickly. Discord HTTP 429 responses tell your client when it may retry. Cloudflare error 1015 also indicates rate limiting. Repeated restarts or immediate retries can keep sending the requests that caused the problem.
Stop the repeated requests
Stop the bot and inspect the code path making requests. Look for tight retry loops, commands registered on every reconnect, repeated message edits, or background tasks started more than once. Start one copy of the bot. Check that a laptop or another host is not running a second copy with the same token.
Let the library handle the wait
Use the request queue in your Discord library. When you make HTTP calls yourself, respect the Retry-After header or retry_after response value. Queue work and bound retries. Avoid hard-coding a universal delay: Discord applies different limits to different routes, and those limits can change.
When the page says 1015
Pause requests and allow the temporary restriction to clear. Do not rotate addresses or create accounts to evade it. Free bots share an outgoing IP address, so include the time and the affected endpoint when contacting support. Remove tokens, authorization headers, and private message contents from any evidence you send.
Start carefully
After fixing the repeated request path, restart once and watch the console. Increase activity gradually and confirm that requests wait instead of looping. A hosting plan change does not remove Discord's API rules. If the error persists, contact support with a short redacted excerpt and your bot name.
References: Discord's rate-limit guidance and Cloudflare error 1015. See troubleshooting for other startup errors.
Still stuck? Contact support