Skip to content

Console and power controls

The Console page is the operational home for a selected server. It combines current state, power controls, command progress, live RCON/RPT/system output, and recent performance metrics.

  • Tell players about planned downtime.
  • Save any open Config, Advanced, or file edits.
  • Make a current backup before updates or risky configuration changes.
  • Wait for an existing Starting or Stopping state to finish.

Your service policy controls whether power actions and RCON are available. A disabled button usually means the server state is incompatible with that action, another command is running, or the action is not enabled for your service.

Control What it checks When to use it
Check status Asks the server host whether the selected server exists and what state it is in. The displayed state is old, Unknown, or different from what players report.
Check version Compares the installed server version with the game-title version already available on its host. After a game update or when clients report a version mismatch.
Scroll to see all columns →

Check version does not search Steam for a newer release and does not install an update. It reports one of these situations:

  • The server matches the host’s installed title version.
  • A different version is installed on the server.
  • The host is still downloading or has locked the title files.
  • The host cannot provide a usable comparison.

Version checks may be rate-limited. Repeated clicks do not accelerate an update.

Control Effect Typical use
Start Starts an offline server. Bringing the server online after maintenance.
Restart Stops and starts an online server through one tracked action. Applying saved settings or mod changes during a planned window.
Stop Stops the running server. Maintenance that must not happen while the process writes data.
Scroll to see all columns →

After selecting an action, watch the progress message instead of sending another request. The panel can show stages such as accepted, connecting, dispatching, waiting, completed, or failed. The final server status is more important than the button click itself.

RCON sends an administrative command to an online DayZ server.

  1. Confirm the server state is Online.
  2. Enter one complete command in the RCON field, such as say -1 Server restart in 5 minutes to broadcast a BattlEye message to every player.
  3. Select Send once.
  4. Check the system message and console output for the result.

RCON is disabled while the server is offline and may be unavailable under your service policy. The panel does not store the command text in its customer activity record, but the game server or RCON logs may still record it.

The console combines multiple sources:

Source Content
RCON Server and player messages delivered through the RCON stream.
RPT DayZ runtime report output, including script and startup messages.
System Panel-generated status, action, and connection messages.
Scroll to see all columns →

Use the checkboxes to hide a source without deleting its lines. Type in Filter to match line text, source, channel, or timestamp.

Control Meaning
Follow Keeps the view scrolled to the newest matching line. Turn it off when reading older output.
Pause Freezes the visible line set so new events do not move the view. It does not pause the server or stop collection.
Clear Clears console lines and metric samples from your current browser view. It does not delete DayZ log files.
Scroll to see all columns →

If live output stops, check the connection indicator in the panel header, refresh once, then run Check status. Use the separate Logs guide when you need persisted profile logs rather than the current live session.

When the host supplies samples, the Console page shows recent trends for:

  • CPU usage
  • Memory use
  • Network traffic
  • Player count and maximum players
  • Disk read and write counters

These are short operational trends, not long-term monitoring reports. A blank metric area means the panel is waiting for host data; it does not by itself prove that the server is down.

Look for a sustained pattern instead of reacting to one spike. For example, recurring CPU saturation during the same gameplay event is more useful diagnostic evidence than a single brief peak.

Problem Check
An action button is disabled Wait for the current state/action to settle. Confirm the action is available for your service.
Server is Online but players cannot connect Open Network and confirm the address and ports; then check RPT/error logs.
Version mismatch remains Check version once, allow any host download to finish, then restart during a maintenance window.
No RCON output appears after a successful command Some commands do not echo a response. Confirm the intended effect or inspect the persisted logs.
Console has too much output Pause, select only the relevant source, and filter by a specific error, player, or timestamp.
Scroll to see all columns →