Game server will not start: choose the next safe check

Use this guided check when a game service stays offline, exits during startup or never becomes ready. It routes evidence to a next action; it cannot establish the cause from a panel status alone. Have access to the correct service and its console or log files. Preserve your worlds, player data and current configuration.

Choose what you can observe

Follow the link matching your symptom. All sections remain visible. Keyboard users can Tab to a link and press Enter; use the return links to choose another branch.

• The panel or console itself will not connect.
• I can open the console and see startup output.
• The process exits with no useful output.
• It says ready, but players cannot join.

1. Is the console unavailable?

Check: note the exact browser error and timestamp. Open this service's file manager, if available, and see whether its latest log has new entries. Do not assume the game is stopped because its browser console is disconnected.

If files or logs are accessible: follow the console connection guide. Then continue with the startup log if it shows an actual game failure.

If the service's controls are unavailable or the panel reports a node connection error: collect a support report. Reinstalling the game or changing its world cannot repair an unavailable management connection.

2. What is the first relevant error?

Read from the beginning of the failed attempt, not only the final exit line. For Minecraft, use the log collection guide. Record the first error plus surrounding lines without posting credentials or player addresses.

• Java/runtime or missing JAR error: check the selected software and file.
• Plugin/mod/dependency error following a change: compare the changed component.
• Memory, killed process, full disk or write failure: check resource evidence.
• Bind/listen error, unfamiliar error or another game: use the relevant game route.

3. Does the runtime match the selected release?

Check: compare the startup-selected runtime, installed server release and configured JAR filename with the actual uploaded file. Paper's current requirements list Java 21 for Paper 1.20–1.21.11 and Java 25 for 26.1+. Other loaders and older releases have their own requirements.

If a mismatch is confirmed: follow the compatibility and update procedure for the exact installed release. Do not bypass Java-version protection or downgrade the world. If those values match: continue to game-specific evidence.

4. Did one component change?

Check: write down the last known working time and the exact file or setting changed. Back up the current state before correction. Use a separate mod-conflict test copy for modded Minecraft, or the plugin compatibility checks for Paper/Purpur.

If the change explains a documented incompatibility: apply the supported correction on the copy first. Restore matching code and data together where a migration occurred. If no change is established: do not remove half the production plugins speculatively; send the evidence for review.

5. Is there a resource error?

Memory message or abrupt exit: use the Java-versus-process-kill guide. High RAM usage or an exit code alone does not prove host OOM. Host-side evidence may require support.

Full disk or write error: inspect quota and file sizes through the storage investigation guide. Do not delete worlds, plugin data or your only backup to make space. If neither branch provides evidence: escalate with the original logs.

6. No useful output?

Check whether installation, a restore or another panel task is still active. Record its status and age; do not start a competing task. If it is unexpectedly stalled, or the process disappears without a log, ask support to inspect the task and process event. Avoid repeated start clicks or forced kills.

7. Use the game-specific route

A bind error needs the service's assigned endpoint checked, not an arbitrary replacement port. Rust startup checks, CS2 startup checks and FiveM/ESX dependency checks provide narrower paths. Paper's official troubleshooting reference covers its own startup errors. If the route does not match your game, send the exact error.

8. The game reports ready

A ready message changes the question to reachability or login. Follow Minecraft connection checks or your game's joining guide. Keep the running world intact.

Outcome: verify a correction or request investigation

After a supported correction, verify readiness, one normal player join and the expected world. If it fails, preserve the new log and stop stacking changes. Open a support ticket with the service ID, game/build, incident time, first error, last change and task status. Never include passwords or tokens. Return to symptom choices.