Console and commands
Reading server output, sending commands and understanding the warnings the panel raises for you.
The console on the Dashboard tab is a live view of your server's output. It is the same stream the game process writes on a dedicated machine — nothing is filtered out or rewritten.
Sending commands
Type into the field below the console and press Enter. Whatever you type goes straight to the server process, exactly as if you were sitting at its terminal.
That means the syntax is the game's, not ours. Minecraft takes op PlayerName without a leading slash. Rust expects say Hello. Factorio uses its own console prefix. If a command works on a dedicated server, it works here.
Quick commands next to the input holds a short list of the ones people use most for that game, so you do not have to remember the exact spelling.
Why commands sometimes do nothing
Three common reasons, in order of how often they turn out to be the cause:
The server is not running. Commands go to a process; without one, they go nowhere. Check the status in the header.
The server is still starting. A game that is loading mods has not opened its console yet. Wait for the line that says it is done — Minecraft prints Done (12.345s)!, other games have their own.
The game does not have that command. Plugins and mods add their own; without the plugin installed, the command does not exist. The console usually says so.
Warnings the panel raises
The panel reads the console alongside you and opens a window when it recognises a failure it can help with. These are not generic errors — each one comes with the specific fix.
EULA acceptance required — Minecraft will not run until you accept Mojang's licence. One click accepts it. See Accepting the Minecraft EULA.
Out of RAM — the server tried to use more RAM than the plan allows and was stopped. Usually a modpack or plugin set that outgrew the machine, or a world that has grown over months of play. The fix is a larger plan or a lighter setup; the event is recorded in your Activity log.
Java version mismatch detected — modern Minecraft needs a modern Java, older modpacks often need an older one. The Java tab lets you switch versions.
Engine file missing — the server jar is not where the game expects it. Usually happens after a manual upload went to the wrong folder.
Reading a crash
When a server dies, the useful information is almost never the last line. It is the first line that mentions an error, often several screens earlier.
Scroll back to where the output stops looking normal. Java stack traces are long, but the first line names the cause and that is usually enough to search for. Copy that line — not the whole trace — when you open a ticket.
Log analysis (Minecraft)
Minecraft servers have a Log analysis tab that reads a log file you select and points out known problems — missing dependencies, port conflicts, Java mismatches, mods that failed to load. It is worth trying before reading a 5000-line file by hand.
Scheduled commands
Anything you can type, you can schedule. Schedules runs commands on a timetable — a warning message before a nightly restart, a periodic save, a daily announcement.
One caveat: Restart, Stop and Command only do something while the server is running — they are sent to a live process. Start is the exception and works on a stopped server, which is what you want for a scheduled boot after a nightly shutdown.