Server stuck on starting or won't start on Schokr
Fix an Schokr server that will not start, stays on starting or crashes on boot: read the console, check startup settings, EULA, ports and files.
Updated · 2 min read
When a server will not start or stays on "starting", the answer is almost always in the console output. Start the server, watch the console and look for the first error.
Step 1: read the console
- Open the server's console.
- Start the server and watch the output from the beginning.
- Find the first line with
ERROR,Exception,Traceback,FATALorError:.
Copy that line and the few lines around it. Most fixes below match a specific message.
Stuck on "starting" but the server works
The panel marks a server as running when the template sees a specific "done" message in the output. If the server is actually up (players can join, the bot is online) but the status still says starting, the software just did not print that message. This is common with custom bots and some modded servers. It is harmless, and you can keep using the server.
Common causes and fixes
| Console shows | Likely cause | Fix |
|---|---|---|
| You need to agree to the EULA | Minecraft EULA not accepted | Accept it via the link in the console, or set eula=true in eula.txt |
| Unable to access jarfile | Wrong jar name | Check the jar variable in Startup matches the file in the file manager |
| Cannot find module or ENOENT | Bot main file path is wrong | Set the main file variable to your entry file, such as index.js |
| ModuleNotFoundError | Python package not installed | Add it to requirements.txt and restart |
| Failed to bind to port or address already in use | Port mismatch or conflict | Make the software use the allocated port. See port allocations |
| UnsupportedClassVersionError | Java version too old | Pick a newer Java runtime in Startup |
| No space left on device | Disk full | See disk full |
| Killed, or exit code 137 | Out of memory | See out of memory |
Minecraft's EULA file looks like this once accepted:
eula=true
Starts, then stops after a few seconds
- A bot exits right away: often an invalid token or missing environment variable. Check your
.envfile or Startup variables. Never paste your token in public when asking for help. - A plugin or mod crashes the server: the console names it. Remove it from the
pluginsormodsfolder, start again, then update or replace it. - Corrupted world or data: usually after a kill or crash during saving. Restore a snapshot.
Started failing after a change
Think about what changed last:
- Check the activity log for recent file, startup or settings changes.
- Undo the change, for example the version variable or a new plugin.
- If you cannot find it, restore the last snapshot from before the problem.
Install never finished
If the server was just created, the template may still be installing. Big games like ARK and Rust download many gigabytes. Wait, and watch the console for install progress or an install error.
Nothing in the console at all
- Refresh the page.
- Check status.schokr.gg for issues at your location.
Still stuck?
Ask in the Schokr Discord. Include the template, the first error line and what you changed last. Remove tokens and passwords from anything you paste.