Console and usage
Send commands, follow the output, start and stop, and what the bars mean.
2 min read
On this page
The console
The Console is your server's real standard output, live over a WebSocket connection. Whatever you type into the Command field at the bottom goes in as standard input, exactly where it would go on your own machine.
On a game server you can send any server command this way: op, whitelist add, say, stop. You do not need a slash in front. Enter sends the command, the ↑ and ↓ arrow keys browse the history. Commands only reach a server that is online.
Above the output you find Pause (the output stops scrolling, new lines are collected), Scroll to bottom, Copy and Clear. Screen reader mode has new lines read out by screen readers. If the connection drops, the console reconnects by itself.
Start, stop, restart
The Controls buttons sit at the top next to the name, in every tab of the server. Restart is stop and start in one. If starting or stopping takes longer than usual, the page says so and points you to the console.
If the server comes back up by itself after a crash, that is the Restart after a crash switch under Settings, General: it restarts the server when it stops unexpectedly, at most five times per hour. A stop you asked for does not trigger it.
The bars
In the Overview, Usage shows CPU, RAM and storage: what the container is really using right now, measured, not estimated. The number after it is your plan's limit. CPU and RAM are only shown while the server is running.
From about 70 % the bar turns yellow, from 90 % red. Red on RAM is a reason to take a look: a Java process that runs into its memory limit does not slow down, it gets killed.
Below that is the traffic of the last 24 hours or 7 days, see Traffic and DDoS protection, and the Connection box shows when the server was last started.