DBM Host Docs
Menu

Articles

Why did my bot stop?

Written by Elgade

Published

When a bot stops by itself, DBM Host writes the reason in its logs and sends you a notification. Most of the time, the answer is already written there.

Read the logs first

  1. Open your bot in DBM Host, then Logs.

  2. Find the first red line (it starts with [error]). It tells you what went wrong. The lines after it are usually the consequence, like Bot exited with code 1.

  3. Need help? Tap Copy under the logs and paste them in our Discord server. Hide your token if it appears in them.

Common messages and how to fix them

In the logs

What it means

How to fix it

TokenInvalid or An invalid token was provided

The bot token is wrong, or it was reset.

In the Discord Developer Portal, open your app, then Bot > Reset Token. Paste the new token in Startup > Variables.

Used disallowed intents or Your bot asks for privileged intents

Your code needs an intent that is turned off in Discord.

Developer Portal > your app > Bot > Privileged Gateway Intents. Turn on the ones your bot uses, save, then press Start.

Discord keeps refusing the connection

The same bot also runs somewhere else (your PC, another host), or it sets an invalid status.

Stop the other copy: one token can only run one bot at a time.

uses the same bot token

Two bots in DBM Host have the same token.

Give each bot its own token.

Cannot find module (JavaScript) or ModuleNotFoundError (Python)

A package your code uses is missing.

Add it to package.json or requirements.txt, then press Start: the app installs it.

Package install failed

No internet, or a wrong package name or version.

Check the connection and the names in package.json or requirements.txt.

Out of memory or RAM almost full

The bot uses all the RAM it was given.

Open your bot, then Resources, and give it more RAM. Free bots go up to 512 MB, Premium bots up to 2 GB.

CPU above the or CPU stayed above the

The code works non-stop, often a loop that never ends or a timer that runs too often.

Look for endless loops and very short timers. Premium bots can use 100% CPU.

No start file yet

DBM Host does not know which file starts your bot.

Add an index.js (JavaScript) or a main.py (Python), or choose the start file in Files.

It stopped, but the logs show no error

Then the phone stopped DBM Host, not your code. It happens when:

  • Android paused the app to save battery (battery saver, sleeping apps).

  • DBM Host was swiped away from the recent apps list.

  • The phone restarted or switched off.

  • You started the bot on another phone. DBM Host then shows Stopped on this phone: you started it on another phone.

For the first three, read Keep your bot online 24/7 in the docs.

Start it again

Once it is fixed, press Start. DBM Host never restarts a bot by itself, so a broken bot does not crash again and again: you decide when it runs.

Still stuck? Copy your logs and ask on our Discord server, we are happy to help.