Console

What the console is#

The console is the Home tab of your server, and it is where you run the server day to day. From here you start and stop the server, read and search its log output, send commands, and keep an eye on live stats. It is the page you will spend most of your time on, so the sections below walk through each part of it.

At the top you will see the server name and the power buttons, with an optional description card just beneath them. The main column holds the console, and a sidebar on the right shows a column of stat cards for the server address, uptime, CPU, memory, storage, and network. If your server is installing, has a broken install, is being transferred to another node, or its node is under maintenance, a warning banner appears at the top and most actions are turned off until that finishes.

Power controls#

The power buttons sit next to the server name at the top of the page. Which one you can press depends on the state the server is in right now. Start only lights up while the server is offline, and Stop is only active while it is running.

  • Start turns the server on. It only works when the server is offline.
  • Restart stops the server and brings it back up again.
  • Stop asks the server to shut down cleanly. While it is shutting down, the same button changes to Kill.
  • Kill forces the server process to end right away. Use it only when a normal stop is stuck.

When you press Kill, a confirmation dialog appears titled Forcibly Stop Process, warning that forcibly stopping a server can lead to data corruption. Press Continue to go ahead.

Note: Killing the server ends it without saving whatever is in progress. If your game saves on shutdown, prefer Stop and give it a moment to finish. You can protect your world either way with regular backups.

Reading the console#

The large dark panel in the main column is the log. It shows the server's output as it runs, including startup messages, player joins, plugin warnings, and errors. When something goes wrong, the log is the first place to look, since the error lines here usually point straight at the cause. Lines produced while a server is being transferred between nodes are tagged with a [MIGRATION] prefix so you can tell them apart from your game's own output.

New lines stream in at the bottom and the view follows along on its own. Scroll up and the auto-scroll pauses so you can read older output without being yanked back down; scroll to the bottom again and it resumes. Keep scrolling up and the console pulls in older history from the server, so the log is not lost when you refresh the page.

Hover over any line to reveal a copy button on the right that copies just that line. To grab the whole log instead, use the toolbar button described below.

Note: The console renders live ANSI colors from your game, so warnings and errors keep the coloring you would see in a normal terminal.

Searching and the toolbar#

Above the log is a search box with the placeholder Search all logs.... Type at least two characters and the console searches your full log history, not just what is currently on screen. While a search is active the placeholder changes to Click a result to jump..., and clicking any matching line jumps you to that point in the live log. Clear the box with the small x to return to the normal view.

To the right of the search box is a small toolbar of icon buttons. Each one shows a tooltip when you hover it:

  • Show timestamps toggles a timestamp in front of every line. The button label flips to Hide timestamps once they are on, and your choice is remembered per server.
  • Copy all logs copies everything currently loaded, with timestamps, to your clipboard.
  • Auto-scroll turns the follow-the-bottom behavior on and off. It also flips off automatically the moment you scroll up.
  • Fullscreen expands the console to fill the screen; press it again, or the x that replaces it, to exit.

Sending commands#

At the very bottom of the console, below the log, is a command box with a terminal icon and the placeholder Type a command.... Type your command there and press Enter to send it to the server. The box is disabled while the console is still connecting, so wait for the log to load before you type.

To repeat an earlier command, press the Up and Down arrow keys while the command box is focused. Up steps back through commands you have already sent, and Down steps forward again toward the most recent one.

Note: The command box only appears if your account has console permission. If you do not see it, an owner or admin can grant access on the users and permissions page.
Note: Command history holds the last 32 commands and is stored per server in your own browser. It does not follow you to another device or to a different browser.

Live stats#

The sidebar on the right of the Home tab is a column of stat cards that update live while the server runs. Each card shows a number, and most carry a small inline chart of that value over recent time so you can spot a spike or a slow climb at a glance.

  • IP Addressshows your server's connection address: its subdomain when one is active, and the IP and port otherwise. Click the card to copy the address.
  • Uptime shows how long the server has been running.
  • CPUshows current processor use against the server's limit.
  • Memory shows how much memory the server is using against its limit.
  • Storage shows how much disk your files take up against your storage limit.
  • Network shows live inbound (↓) and outbound (↑) transfer rates.

When the server is offline, the Uptime, CPU, and Memory cards read Offline and their charts clear. Storage still shows a value, since your files sit on disk whether the server is running or not.

If you want to reach the server from outside, the full address and ports live on the networking page.