ESN Docs

Docs › Help

Troubleshooting: bot offline, crashes and common errors

Fix the most common ESN Hosting problems: a bot that won't start, missing modules, file not found, out of memory, a full disk, or a Minecraft server that won't start.

Most problems show their cause in the Console. Start the server, wait for it to fail, and read the last few lines. Then find the matching error below.

"No such file or directory" / "Cannot find module" for your main file

The server can't find the file it was told to run.

  • Check the main file variable on the Startup page. It must match your file name exactly, including capitals.
  • Check your files are in the top folder, not inside a folder that came from your zip. See Extracting archives.

ModuleNotFoundError (Python) / "Cannot find module 'x'" (Node.js)

  • Python: add the missing package to requirements.txt (for example discord.py), then restart. Packages are installed on every start.
  • Node.js: add the package to package.json dependencies (run npm install name on your computer and upload the new package.json), then restart.

"Improper token" / 401 Unauthorized

Discord rejected your bot token. Copy a fresh token from the Discord Developer Portal (Bot → Reset Token), update it in your .env or config, and restart.

"Privileged intent(s) … not enabled" / disallowed intents

Turn on the intents your code asks for (Message Content, Server Members, Presence) on your app's Bot page in the Discord Developer Portal, then restart.

The server keeps stopping or restarting on its own

It's often running out of memory. Watch the memory graph on the Console page. If it climbs to your plan's limit just before the crash, either reduce what your bot or server loads, or move to a bigger plan.

"No space left on device" / uploads fail

Your disk is full. Check disk use on the Console page, then delete old logs, archives you've already downloaded, or unused worlds in Files.

The panel says "Starting" forever

For Discord bots this is normal. The panel doesn't know which line means your bot is ready, so it keeps showing Starting. If the console shows your bot logged in, it's running.

Minecraft won't start

  • EULA: accept it (see first start).
  • "Unsupported class file major version" or a Java error: choose a newer Java version in the Docker Image box on Startup.
  • A plugin error loop: stop the server, move the newest plugin out of plugins, and start again to find the bad one.
  • "Failed to bind to port": put server-port in server.properties back to the port shown on your Network page.

"This server is suspended"

A suspended server is usually a trial that has ended or a payment that didn't go through. Your files are kept. See after the trial or contact support.

Is it ESN or is it me?

Check the ESN status page. It shows live uptime for every ESN node and the panel. If everything's green and you're still stuck, contact support.

Still stuck? Ask in the ESN Hosting Discord. Last updated October 27, 2026.