The Console is the first page most people open and the last one they close. It's the live feed of everything your server prints, the place you start and stop it, and — more and more — the page that tells you what's wrong and offers to fix it. Open it from your server menu.
Starting and stopping
Four power buttons run the show: Start, Restart, Stop, and — while a server is shutting down — Kill. Stop asks your server to close politely (on Minecraft it sends the stop command so the world saves first). The Connect button gives you the address people use to reach the server: on a Minecraft server it opens a join guide with Java and Bedrock tabs and step-by-step instructions; on an app or other server it's the address to copy.
⚠️ Heads up: Kill is the last resort — it force-stops a server that's hung and won't shut down on its own, and it doesn't give the server a chance to save. Reach for it only when Stop isn't working.
Typing commands
Below the output is a command box. Press up and down to walk back through your last ten commands, and Tab to autocomplete — handy for long Minecraft commands. Whatever you type goes straight to the running server, exactly as if you'd typed it into its own terminal.
The live stats
Three cards along the top update in real time: CPU, RAM (shown against your plan's limit), and Network in and out, each with a live chart. A status bar shows whether the server is running, its uptime and how much disk it's using; game servers such as Minecraft also show the current player count.
💡 Tip: If RAM sits pinned at the limit, that's your cue to read Out of memory.
Reading a busy console
Game consoles can be noisy, so Minecraft and Hytale servers get filter tabs above the log — Console, Chat, Errors and Warnings (plus Players), each with a count so you can jump straight to what matters. Share bundles the log into a link you can hand to a friend or to support; Clear wipes the view. On premium you can pop the console out into its own window to watch it beside another page.
The part that tells you what's wrong
This is where the Console earns its place. On application servers it reads your output as it scrolls and steps in when it recognises a problem:
| The console spots… | It offers |
|---|---|
A missing package (Cannot find module 'express', ModuleNotFoundError) |
A one-click Install package button, or Open Packages |
| A missing entry file or project manifest | Open File Manager to check what's actually there |
| A port already in use, or a runtime version mismatch | Open Settings to fix the setting |
| Permission errors | A pointer at what to change |
Each comes with a button that takes you straight to the right page, so you're never left guessing. See My app won't start for the walk-throughs.
Minecraft's helpers
Game servers get their own version of this. When a mod crashes the server, the Console offers to disable the offending file in your /mods folder; plugin problems get a similar hand. And on a brand-new Minecraft server the first boot stops to ask you to accept Mojang's licence — the Console shows an I Agree button that writes eula.txt for you, so you never touch the file by hand. More on first boot in the Minecraft Java quickstart.
Next: the File Manager for the files behind the log, and Settings for the controls the diagnostics point you at.