Find out why your server stopped

When a server stops or won’t start, it almost always says why. The trick is finding the line that matters.

Where to look

1. Console tab - press Start and watch. The error usually appears within a few seconds.
2. Logs tab - if the console has moved on, Refresh the logs to see the full output from the start.
3. Action history (Console tab) - shows what happened when you pressed Start, Stop, Restart or Rebuild, in full.

Reading an error

Errors usually end with a few lines like these:

Error: Cannot find module 'discord.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
    at Object.<anonymous> (index.js:1:21)

• The first line says what went wrong: here, a package isn’t installed.
• The lines below say where: here, line 1 of index.js.

In Python the important line is usually the last one:

Traceback (most recent call last):
  File "bot.py", line 2, in <module>
    import discord
ModuleNotFoundError: No module named 'discord'

The usual suspects

Still stuck?

Try the AI server assistant on the Power plan, or open a ticket. Use Copy on the Logs tab and paste the whole error in - it’s the single most useful thing you can send us.