My bot is offline or not responding: what should I check?
First check whether the server is running in the panel. If it shows as Stopped or Crashed, click Start and watch the Console page for the first 30 seconds of output.
Common causes of bot failure:
Missing or invalid token: if you see "An invalid token was provided" or "TokenInvalidError", your DISCORD_TOKEN environment variable is missing or has a typo. Check the Startup page variable value. Regenerate the token in the Discord Developer Portal if needed and update the variable.
Missing intents: if your bot uses GuildMembers, GuildPresences, or MessageContent but has not enabled these in the Discord Developer Portal, the gateway connection will be refused. Enable the required Privileged Intents on your application's Bot page at discord.com/developers.
Crash on startup: a syntax error or missing import throws an exception before the bot logs in. The Console page will show the exact error and file path.
Bot connects but does not respond to commands: check that slash commands are registered and that you are in the correct guild. If you registered commands to a guild, they only appear there. If registered globally, allow up to an hour for Discord to propagate them.
Want to try this on a real server?
Everything described here is available on the trial too, on the same hardware and the same panel as the paid plans. Try it free for 24-hour, no credit card required.
Didn't fix it? Ask in Discord.
Ask in our Discord - we help with hosting questions whether or not you host with us.