My bot won't start or keeps going offline — how do I fix it? — Discord Bot

Q: My bot starts then crashes seconds later — what's happening?

Read the crash message in the Console. It's usually an unhandled error in your code or a missing dependency it needs at runtime.

My bot won't start or keeps going offline — how do I fix it?

A bot that won't start or keeps dropping offline is almost always fixable in a few minutes — the Console usually tells you exactly what's wrong. This article gives you a quick checklist to diagnose and fix the most common causes.

Start with the Console

Open the Console and read the error first — it almost always names the cause. Whether it's a missing file, a bad token, or a crash, the message points you straight at the problem before you start changing anything.

The common fixes

Work through these in order:

Wrong or missing startup file — check the Startup tab and confirm your entry file (for example index.js or bot.py) is set correctly.
Missing dependency — Restart or Reinstall to fetch your packages from package.json / requirements.txt.
Invalid or missing bot token — re-check your token in the Startup variables.
Wrong runtime version — set the correct Node.js / Python version in the Startup tab.

Tip: Use "Copy all console output" or "Share logs via mclo.gs" from the Console to grab the full log — paste it into a ticket if you're stuck and we'll take a look.

Frequently asked questions

My bot starts then crashes seconds later — what's happening? Read the crash message in the Console. It's usually an unhandled error in your code or a missing dependency it needs at runtime.

Everything looks right but it still won't start. Grab the full log with the mclo.gs share button and open a ticket. We'll help with the hosting side of the problem.