Skip to Content
🇬🇧Server Console

Game Server Console

Web console allows direct management of your game server — start, stop, restart, send commands, and view logs in real-time.


Overview

FeatureDetails
TypeWeb console (WebSocket)
AccessThrough CoreSynth panel
ANSI supportYes (colored logs)
HistoryYes (scrollback)

Accessing Console

Step 1 — Open Service

  1. Log in at coresynth.io 
  2. Go to Dashboard > Services
  3. Select your game server

Step 2 — Launch Console

  1. In sidebar, click Console
  2. Console loads and displays logs

Controls

Power Buttons

At the top of console you have power buttons:

ButtonFunctionDescription
StartStartStarts the server
StopStopSafely stops server (graceful shutdown)
RestartRestartSafely restarts server
KillKillForcefully terminates process (emergency only)

Server States

StateColorDescription
RunningGreenServer is running
StartingYellowServer is starting
StoppingOrangeServer is stopping
OfflineRedServer is stopped
InstallingBlueInstallation in progress

Sending Commands

To Console

  1. Find input field at bottom of console
  2. Type command (e.g., list, op Player1)
  3. Press Enter

Favorite Commands (Favorites)

Save frequently used commands:

  1. Type command in input field
  2. Click (star) next to field
  3. Command is saved to favorites
  4. To use, click saved command

Tip: Save commands like list, whitelist on, save-all

Command History

Console automatically saves history:

  • Press (up arrow) for previous command
  • Press (down arrow) for next command
  • History is stored for the session

Viewing Logs

ANSI Formatting

Console supports colored logs:

  • Green — informational messages
  • Yellow — warnings
  • Red — errors
  • Blue/Blank — debug messages

Scrolling

  • Scroll up — older logs
  • Scroll down — newer logs
  • Auto-scroll — automatically scrolls to new messages

Tip: If you want to read older logs, scroll up and auto-scroll will pause.

Copying Logs

  1. Select text in console with mouse
  2. Press Ctrl+C to copy
  3. Paste into text editor or ticket

Game Commands

Minecraft

Examples of frequently used commands:

CommandDescription
listList online players
op <player>Grant OP permissions
deop <player>Remove OP permissions
whitelist add <player>Add to whitelist
whitelist remove <player>Remove from whitelist
whitelist onEnable whitelist
gamemode <mode> <player>Change gamemode
tp <player1> <player2>Teleport players
save-allSave world
say <message>Send message to all

FiveM/GTA

CommandDescription
statusServer status
clientlistPlayer list
say <message>Global message
kick <id> <reason>Kick player
ban <id> <reason>Ban player

Rust

CommandDescription
statusServer status
usersPlayer list
kick <name/steamid>Kick player
ban <name/steamid> <reason>Ban player
global.say <message>Global message

Server Statistics

Next to console you see live statistics:

MetricDescription
CPUProcessor usage (%)
RAMMemory usage (used/max)
DiskDisk usage (used/max)
UptimeServer uptime
PlayersConnected player count

Tip: If CPU or RAM consistently exceeds 90%, consider upgrading.


Troubleshooting

Server Won’t Start

Causes:

  • Insufficient RAM
  • Misconfiguration
  • Missing EULA acceptance

Solution:

  1. Check logs in console
  2. Increase RAM in settings
  3. For Minecraft, accept EULA (eula=true)

Console Not Responding

Cause: WebSocket connection issue.

Solution:

  1. Refresh page (F5)
  2. Clear browser cache
  3. Try different browser

Commands Not Working

Cause: Server offline or wrong format.

Solution:

  1. Verify server is running (status: Running)
  2. Check command syntax
  3. Some games require / prefix

Server Automatically Restarts

Cause: Crash or resource limit.

Solution:

  1. Check logs for crash reason
  2. Increase allocated RAM
  3. Check plugins/mods

High CPU/RAM

Cause: Unoptimized server or too many players.

Solution:

  1. Optimize server configuration
  2. Lower view-distance
  3. Upgrade to higher plan
  4. Use optimized plugins (Paper instead of Spigot)

Security Recommendations

  • Commands carefully — some commands can cause data loss (/stop, /kill)
  • Regular backups — create backup before major changes
  • RCON password — if using RCON, set strong password
  • Whitelist — enable whitelist for private servers

Next Steps


Need help? Open a support ticket  or ask Alex.

Last updated on