Server will not start / "unexpected error"
A checklist for when a Victus server refuses to start or the panel shows an unexpected error — read the console, check the EULA, ports, memory and the JAR.
When a server will not start, the answer is almost always in the Console tab. The panel replays the last output, and the reason it stopped (EULA, port, memory, a bad config, or the wrong JAR) is usually in the final lines. Work through this checklist top to bottom before opening a ticket.
Read the console first
- Open the Console tab and scroll to the very last lines before it stopped.
- Look for a specific error keyword: "eula", "already allocated", "OutOfMemoryError", "Failed to bind", or a stack trace naming a plugin/mod.
- Match the keyword to the fixes below.
Common causes and fixes
| What the console shows | Fix |
|---|---|
| You need to agree to the EULA | Set eula=true — see "You must accept the EULA". |
| Port is already allocated / Failed to bind | A stale process or wrong port — see the "Port is already allocated" article. |
| java.lang.OutOfMemoryError | Not enough RAM or a leak — see "Out of memory / server keeps crashing". |
| Error occurred during initialization of VM | The version needs a newer Java than the egg provides — lower your MC version or check the Startup Java setting. |
| Exception in a plugin/mod (stack trace) | A broken or wrong-version add-on — remove the last thing you added. |
If it is "unexpected error" in the panel (not a Minecraft error)
- This usually means the daemon could not run the container — do a full Stop, then Kill (Console power menu), then Start.
- Confirm the service is not suspended. Check Victus Billing for paid invoices; for a free server, check the renewal status and deadline directly in Victus Panel.
- Check the Startup tab — a blank or invalid JAR/version variable stops the container from launching.
If it worked yesterday and not today, whatever you changed last (a plugin, a config edit, a version bump) is the prime suspect. Undo that single change and try again.
Copy the last ~20 lines of the console and open a Discord support ticket (or use the on-site support widget). The log text lets staff diagnose it far faster than "it won't start".