Unlimited Credits is now available for just $10 with a one-time payment! Upgrade today before this limited-time offer ends.
Documentation

Startup and console

Change the startup command manually in Pterodactyl and use the console to start and troubleshoot the bot.

Change it in Pterodactyl

Startup is changed in the Pterodactyl server. The documentation page does not change it for you.

Change the startup command

  1. 1
    Open the server in Pterodactyl.
  2. 2
    Open the Startup tab.
  3. 3
    Find the main-file value or startup-command field provided by the server egg.
  4. 4
    Set it to the command or file used by your project.
  5. 5
    Save the value when the panel shows a save action.
  6. 6
    Open Console and press Restart.
  7. 7
    Read the first console lines and confirm that the correct file starts.

Common commands

ProjectExample
Node.js main filenode index.js
Node.js package scriptnpm start
Python main filepython3 main.py
Python alternativepython app.py
Good to know

Use the command that matches the files in your project. Do not copy an example when your main file has a different name.

Install packages

RuntimeFiles and command
Node.jsKeep package.json in the server root. Use npm install when dependencies were not installed automatically.
PythonKeep requirements.txt in the server root. Use pip install -r requirements.txt when needed.

Read the console

Console textWhat to check
Cannot find module / packageThe dependency is missing or package files are in the wrong folder.
No such file or directoryThe startup file name or folder is wrong.
Invalid token / unauthorizedThe Discord token is wrong, expired, or was reset.
Process exited with code 1Read the error lines above it for the actual code problem.
Out of memory / killedThe bot may need a RAM upgrade or lower memory use.
Server stays online but bot is offlineCheck the token, intents, event code, and that the correct process started.

After a change

  • Restart after changing code, dependencies, startup values, or environment values.
  • Use Stop before replacing many files.
  • Use Kill only when the process will not stop normally.
  • Keep the console open during the first start after an update.