Troubleshoot a Node.js Discord bot that stops or stays offline

Open Console in the game control panel and find the first error from the latest start. Stop a repeated restart loop while investigating. Back up your project before changing files; reinstalling is not a substitute for fixing code or configuration.

Check the startup file and dependencies

• “Upload your bot files and set the Main file”: check Startup → Main file. The file must exist at that exact relative path, including letter case. Valid examples include index.js, bot.cjs and dist/index.js. Do not enter npm start or a command.
• Module not found: confirm your runtime packages are in package.json's dependencies, then set Install dependencies on start to 1. Development packages are omitted. Check that local imported files were uploaded too.
• Lockfile error: synchronize and test package.json and package-lock.json on your computer, then upload both. npm ci intentionally rejects a mismatched lockfile.
• Process exits without an error: check that Main file starts the long-running bot. A command-registration script may finish successfully and exit; it is not the bot's main process.

Check Discord authentication and responses

For token errors, confirm .env is in the server's main folder and its variable name matches your code. The template loads it automatically. Never paste the token into logs or a support ticket. If exposed, reset it in the Discord Developer Portal, update your private file and restart.

For disallowed-intent errors, compare the intents requested by your code with the Bot settings in the Developer Portal. Enable only those your bot needs; privileged intents require the corresponding portal permission. Follow Discord's intent guidance.

If the bot logs in but does not respond, check installation in the correct Discord server, channel permissions and your project's command-registration instructions. The hosting startup message alone does not prove login.

If the console reports an out-of-memory kill, compare the memory graph with your plan and recent code changes. Contact support with the error, time, Main file and recent changes. Remove tokens and other secrets from anything you attach.