Skip to content

Power Controls

Power controls sit in the server header on the server page, and on the card or row for each server on the Servers page.

  • A server you own or can access. The controls are hidden without the matching permission (see below).
  • An online node — power actions fail while the node’s agent is offline.
Action What it does When to use it
Start Boots the server. After creating, editing configs, or a crash.
Restart Stops gracefully, then starts, using your saved startup command. After config or plugin changes.
Stop Asks the game to shut down cleanly. Before editing world files or upgrading.
Kill Force-stops the server immediately. Only when Stop/Restart hang (the world may not save).

Each button is enabled only when it makes sense for the current state — for example, Start is disabled while the server is already running. You also need the matching permission: Start needs server.start, Stop needs server.stop, Kill needs server.kill, and Restart needs both server.start and server.stop. Without them the controls are hidden.

Pressing Kill always asks for confirmation first: “This will force-terminate the server process immediately without saving. Data may be lost. Are you sure?”

While a server is installing, the header offers Cancel install (needs server.install or server.reinstall). It kills the stuck installer and resets the server to stopped; partial install files are kept. You can then reinstall or start normally.

  1. Warn players if anyone is online.
  2. Prefer Restart over Kill — graceful stops let the game save the world.
  3. After changing configs, plugins, or startup variables, always restart; most games only read those files at boot.
  1. Wait 60 seconds — large worlds take a while to save.
  2. Use Kill as a last resort.
  3. If it still shows as running, check server issues or ask your administrator — the node agent may need attention.

If the node denies host networking for the server, Start answers with a dialog titled “Host networking is disabled on this node”. Selecting Enable and start turns host networking on for the node (you need the node.agent_control permission), then starts the server.

Nightly restarts and similar routines belong in Tasks, not in manual clicking.

  • Console — watch the boot log after starting
  • Tasks — scheduled power actions