Read logs and debug crashes | Guides

Everything your bot prints (console.log, print) appears in the panel console. There is no separate log file unless your code writes one.

Reading a crash

Scroll to the last lines before the process stopped.

Node.js: the stack trace begins with the error (TypeError: Cannot read properties of undefined (reading 'send')) followed by at ... lines. The first at line that points to your file (/home/container/commands/ping.js:12) is where it happened. Line 12 of that file.
Python: the trace starts with Traceback (most recent call last). Read it from the bottom: the last line is the error, the line above it the file and line number in your code.

An invalid token was provided: the token is wrong or was reset. See Token security.
Used disallowed intents: enable the intents in the Developer Portal (Bot → Privileged Gateway Intents) and request them in code.
Cannot find module 'x' / ModuleNotFoundError: add the package to package.json / requirements.txt.
EADDRINUSE: your bot opens a web server on a fixed port; use the port from the Network tab (process.env.SERVER_PORT).
Exit code 137: out of memory. Upgrade RAM or fix the leak.

Ask "Why did my bot crash?" and it reads the console history, finds the trace and explains it in plain words, often with the line to change.