Discord Bot Showing Offline? Fix It Step by Step
Is your hosted Discord bot offline? Check the token, the variables and the app status with the SolumeCore assistant, and read the console errors.
If your Discord bot shows offline after you deployed it on SolumeCore, the cause is almost always one of three things: Discord rejected the token, the app hasn't read the token yet, or the app isn't running. The Discord bot assistant in the panel runs exactly those three checks, so start there and then read the console for anything else.
Step 1: Run the three checks
- Open your app in the panel and go to Code > Deploy.
- On the Discord bot assistant card, press Open assistant. You can also use Code > Variables > Import / export > Discord bot assistant.
- Go to the Connect step. If a token is already saved, the assistant checks it right away. Press Check again after each fix.
| Check | If it is not green | Fix |
|---|---|---|
| Discord accepted the token | Discord rejected the token | Open the Discord Developer Portal, go to your application's Bot tab, press Reset Token and paste the new token in the first step |
| Your app has the token (or Restart the app so it reads the token) | The app was started before the token was saved | Press Restart next to the check. Apps only read variables when they start |
| Your app is running (or Your app is stopped) | The app is off or crashed | Press Start, then open the console if it stops again |
If the message says there is no token saved yet, go back to the first step and paste it. Make sure you copy the bot token from the Bot tab, not the Client Secret or the Application ID.
Step 2: Read the console
If all three checks are green but the bot is still offline, the app probably starts and then crashes. Open Console > Live console (or Logs & health for older lines) and look at the first error after the app starts:
| Error | Meaning | Fix |
|---|---|---|
TokenInvalid / "An invalid token was provided" (discord.js), LoginFailure / "Improper token" (discord.py) |
The token is wrong or was reset | Save the current token again in the assistant or Code > Variables and restart |
Used disallowed intents / PrivilegedIntentsRequired |
Your code asks for an intent that is off in the portal | In the Bot tab turn on the intent, usually Message Content Intent, and restart |
Cannot find module 'discord.js' / ModuleNotFoundError: No module named 'discord' |
Dependencies weren't installed | Set the Build command (npm install or the pip install -r requirements.txt line) and deploy again |
undefined / KeyError: 'DISCORD_TOKEN' |
The variable name in your code doesn't match the one in the panel | Use the same name in both, then restart |
SyntaxError or another error pointing to your own file |
A bug in the code | Fix it and deploy again |
More about reading the console in View your app's logs and live console.
Step 3: The bot is online but doesn't answer
- Slash commands don't appear: the commands must be registered with Discord by your code, and they can take a moment to show. Reinvite the bot with the Basic preset, which includes slash commands.
- The bot ignores normal messages: turn on Message Content Intent in the portal and request that intent in your code.
- It can't see a channel or can't send messages: check the channel and role permissions in your Discord server. In the assistant, the Invite step lets you choose Basic, Moderation, Music or Administrator; pick the preset that matches what your bot does. Administrator gives it full control of your server, so use it only if you know why.
- It was invited to the wrong server: press Invite to my server again and choose the right one.
Step 4: The bot goes offline after a while
- Look in the saved logs for the last lines before it stopped: an unhandled error or running out of memory are the usual causes.
- Fix the bug, or wrap risky code so one error doesn't stop the whole process.
- To keep it healthy, schedule a restart. See Restart your app and set up auto-restart. A normal bot doesn't listen on a port, so don't turn on a TCP or HTTP health check unless your code also answers on the
PORTvariable, or the check will fail and restart it in a loop.
Step 5: It broke after an update
Open Code > Deploy and look at the last deploy. If it says Failed, press View log. If the new version is the problem, open Deploy history and press Roll back on the last version that worked. See Deploy an app from GitHub or GitLab.
When to reset the token
Reset the token if it appeared in a repository, a screenshot or a chat, or if you can't tell who has seen it. In the portal press Reset Token, then paste the new one in the assistant or under Code > Variables, and restart the app. The old token stops working immediately.
FAQ
Why does my Discord bot show offline even though the app is running?
Most likely the token is wrong, the app started before the token was saved, or the code crashes after login (for example because of a disallowed intent). The assistant's Connect step and the console will show which one.
How do I know if Discord accepted my token?
The Connect step shows your bot's name and ID and the line Discord accepted the token. If Discord rejects it, you see an error asking you to reset the token in the portal.
Do I have to restart the app after changing the token?
Yes. The app reads variables when it starts, so press Restart in the assistant or Restart to apply under Code > Variables.
Why does my bot disconnect when I deploy?
During a deploy the app restarts, so the bot reconnects to Discord and is offline for a short time. Discord doesn't allow two connections with the same token, which is why bots can't use zero-downtime deploys.
Related articles
- Host a Discord bot 24/7
- Deploy a Discord.js bot (Node.js)
- Deploy a Discord.py bot (Python)
- View your app's logs and live console
Still stuck? Open a support ticket from the panel with your app's name and the last console lines. If you are still choosing where to host your bot, compare the app plans.