Skip to main content

Console

The Console provides real-time access to your server’s output and allows you to send commands.

Accessing the Console

  1. Click on your server from the dashboard
  2. You’ll be taken to the Console page by default

Console Interface

Output Area

The main area displays:
  • Server startup messages
  • Player join/leave notifications
  • Command outputs
  • Error messages
  • Plugin/mod messages

Command Input

At the bottom, there’s a text field to type and send commands.

Sending Commands

  1. Type your command in the input field (without the /)
  2. Press Enter to send

Example Commands

Minecraft:
say Hello everyone!
op PlayerName
whitelist add PlayerName
stop
Vintage Story:
/announce Hello everyone!
/role PlayerName admin
/time set day
Commands are sent without the leading slash (/) in most cases. Check your game’s documentation.

Power Controls

At the top of the console, you’ll find power buttons:
ButtonAction
StartBoots the server
RestartGraceful restart
StopGraceful shutdown
KillForce terminate
Kill should only be used if the server is unresponsive. It may cause data loss!

Resource Graphs

Above the console, real-time graphs show:
  • CPU Usage - Processor utilization
  • Memory Usage - RAM consumption

Console Tips

Search Console Output

Use Ctrl+F (or Cmd+F on Mac) to search through console output.

Copy Console Text

Select text in the console and copy it for troubleshooting or sharing with support.

Clear Console

The console auto-scrolls. Old messages are retained during your session but cleared on page refresh.

Common Console Tasks

Checking Server Status

Look for messages like:
  • Done! For help, type "help" (Minecraft)
  • Server startup complete (Vintage Story)

Troubleshooting Errors

Error messages appear in the console. Look for:
  • [ERROR] or [SEVERE] tags
  • Stack traces (long error messages)
  • Missing file warnings

Best Practices

  1. Check the console first when something goes wrong
  2. Copy error messages before restarting
  3. Use graceful stop instead of kill when possible
  4. Monitor resource usage for performance issues

Next Steps