Bot Panel: logs and diagnostics - why a bot does not work

Logs

The Logs tab shows bot output live. Filter: All, Errors, Warnings, Watchdog, plus a line search. "Autoscroll" keeps the newest lines in view, "Download" saves the log to a file, "Clear" clears the window.

Live bot logs
Live bot logs

If the bot crashes, the error text is in the log - start there. Only recent lines are kept, so logs never fill up the disk.

Diagnose

Diagnose tab - "Check" button. The panel checks whether the token is set and accepted by Telegram, whether there is a dependency file and a .env file, and whether the bot is running.

The Diagnose tab
The Diagnose tab

Common causes

SymptomWhat to do
Token missing or invalidset the token in Config Vars and verify it with "Check token"
ModuleNotFoundError / Cannot find module in the logthe library is missing from the dependency file - add it and click "Install dependencies"
Conflict: terminated by other getUpdates requestthe same bot is running somewhere else (on your computer or another server). Stop the other copy
The bot keeps restartingmemory limit exceeded - raise the RAM limit in the Overview tab
Code changes have no effectclick "Restart" after saving
Questions and answers
The bot is not running or has not printed anything yet. Click Start and send the bot a message.
Yes: Settings - Crash notifications. See the article on panel settings.