ESN Docs

Docs › Help

Why is my Discord bot offline? Causes and fixes

3 min readUpdated Oct 31, 2026

Your bot shows offline or keeps going offline. Work through the common causes in order: the process, the token, crashes, intents, memory and two copies.

A bot shows online only while its program is running and logged in to Discord. So "offline" always means one of two things: the program isn't running, or it is running but can't log in. Go through these in order; the Console usually tells you which one it is.

Quick checklist #

  1. Open your server in the panel. If it says Offline, press Start and watch the Console.
  2. Read the last lines of the Console. A red error near the bottom is almost always the cause.
  3. If you see an invalid token or 401 error, reset the token in the Developer Portal and update your .env file.
  4. If you see a privileged intents error, turn on the intents your code asks for in the Developer Portal, or remove them from your code.
  5. If you see a module or package error, add the package to requirements.txt or package.json and restart.
  6. If the server stops by itself after a while, check the memory graph for an out of memory stop.
  7. If the bot is online but ignores commands, check that it isn't also running on your PC and that its slash commands are synced.

The common causes #

1. The program isn't running #

If the bot only runs on your computer, it goes offline when the computer sleeps, restarts or loses internet. Run it on a host instead: see how to host a Discord bot 24/7.

2. The token is wrong or was reset #

Discord resets a token if it is posted publicly, and you may have reset it yourself. The Console shows an invalid token or 401 error. Copy a fresh token into .env with no quotes or spaces. See bot token setup.

3. It crashes on start #

A missing package, a typo or the wrong start file stops the bot before it logs in. Fixes for the usual errors are in common bot errors.

4. Privileged intents #

If your code asks for the members, presence or message content intent and it isn't turned on for the bot in the Developer Portal, Discord refuses the login.

5. Out of memory #

The bot runs for a while, then stops. Watch the memory graph; see how much RAM a bot needs.

6. An unhandled error #

One uncaught error in an event can stop the whole program. Wrap command code in try/except (Python) or try/catch (JavaScript) and log the error.

7. Two copies running #

If the bot runs on your PC and on a server, both answer and both fight over the session. Stop the copy you don't use.

8. Rate limits #

Restarting in a fast loop or sending too many requests can get the bot temporarily rate limited by Discord. Fix the crash first, then start it once.

9. Discord itself is having problems #

Rarely, the problem is on Discord's side. Check discordstatus.com. For ESN's own servers, check the ESN status page.

Help on ESN #

In the ESN Systems Discord, the Helper bot's /botfix command walks through common bot problems, and /ask reaches staff. You can also use the live chat on the panel. More fixes: troubleshooting and keep your bot online 24/7.

FAQ #

Why does my Discord bot go offline when I close my laptop? #

Because the program runs on your laptop. When it sleeps or loses internet, the bot disconnects. Run it on a host to keep it online 24/7.

My bot is online but not responding. Why? #

Usually a second copy is running somewhere, slash commands aren't synced yet, or the message content intent is off for a prefix bot.

How do I know why my bot stopped? #

Open the Console on your server page and read the last lines. The error near the bottom is usually the cause.

Who can help me fix it? #

Ask in the ESN Systems Discord (Helper /botfix and /ask) or use the live chat on the panel.

Still stuck? Use the live chat on the panel or ask in the ESN Systems Discord. Last updated October 31, 2026.