VyroAI

Loading...

When Your Bot Will Not Come Online

Your bot code looks fine but the bot stays offline in Discord. Check the hosting, the console, the token, the intents and the invite, in that order.

Offline has only a few causes

A Discord bot is a program that has to be running somewhere, signed in with your token. When it shows offline, one of three things is almost always true: nothing is running it, the token is wrong, or the code asks for an intent Discord has not granted.

Work down the list below in order. Each check takes a minute, and the first ones are the most common.

The checklist

  1. Does it have hosting? Open the bot project in the Code Studio and look at the Bot Console under the editor. Pressing Start on a bot with no plan opens Choose Hosting Plan instead of starting it, and a plan that has run out shows Add Days. A bot with no plan never runs on VyroAI.
  2. Is it actually running? Read the badge beside the bot name: Running, Starting…, Stopped, Crashed or Error. Starting… means the server is up and VyroAI is waiting to see the bot sign in to Discord. Neither badge proves the sign-in, though: if no sign-in shows up within about two minutes, the badge switches to Running anyway and the console adds a warning that VyroAI never saw the bot sign in. So check that the bot really shows online in Discord. Open Console output — this run and read the last lines.
  3. Did Start refuse it? Start checks your code first. A fault that stops the bot booting, or code the safety scan blocks, means the bot is not started at all. The findings arrive in your project chat, with an Auto Fix button.
  4. Is the token right? An invalid-token error in the console means the token saved in the project is wrong, or was reset on Discord. On the Discord Developer Portal, open your application, go to Bot and press Reset Token. Then, in the Bot Console, press Change beside Token saved if a token is already saved: a New bot token box opens (press Keep the saved token to back out). Paste the new token and press Save Token, then press Start so the bot signs in with it. A bot with a bad token is not running, and the panel only draws Restart while a bot is running — so Start is the button on screen. Resetting kills the old token everywhere.
  5. Does the console say "Used disallowed intents"? Your code asks for an intent the portal has not switched on. Turn it on under Privileged Gateway Intents on the Bot page, save, then press “Start” in the Bot Console — a bot killed by that error is stopped, so the button there is Start, not Restart.
  6. Is it in your server at all? A bot you never invited cannot appear there, however well it runs. Build an invite link under OAuth2 → URL Generator with the bot and applications.commands scopes, and open it.

Do not trust the Bots list for this

The Bots list on the Projects page shows the last status something wrote, so a bot that falls over on its own keeps saying Running there. Open the project and read its console instead.

Running it on your own computer?

The same checks apply, with one more at the top: the bot is only online while the program is running. Close the window, or let the computer sleep, and the bot goes offline. See Running Your Bot on Your Own Computer.

You do not have to catch a crash yourself. When a hosted bot errors, a red card appears in your project chat naming the file and line, with Auto Fix on it.

Where to next

10 of 10 in Discord Bots · Last checked 17 September 2026 · Previous: Commands Not Showing Up