Console - StellarStack

Overview

The integrated console provides real-time access to your game server’s command-line interface. View live log output, execute commands, and monitor server activity—all through a modern web interface with WebSocket streaming.

Real-Time Streaming

WebSocket connection streams console output instantly

Command Execution

Send commands directly to your game server

Color-Coded Output

Syntax highlighting for info, error, and debug messages

Auto-Scroll

Automatically follows new messages with smart pause

Console Interface

Visual Components

The console appears on the server overview page and consists of: Log Output Area:

Dark terminal-style background
Scrollable message history
Color-coded message types
Timestamp for each line
Auto-scrolls to newest messages

Command Input:

Text field at bottom of console
Send button (or press Enter)
Command history (up/down arrows)
Disabled when server is offline

Message Types

Console messages are color-coded by type:

Info
Error
Default

[12:34:56] Server started on port 25565

Standard informational messages:

Server startup
Player joins/leaves
World saving
Plugin loading

WebSocket Connection

The console uses WebSocket for real-time bidirectional communication:

Connection Process

Request Console Credentials

GET /api/servers/{serverId}/console

Returns:

{
  "websocketUrl": "wss://node1.example.com:8080/api/servers/{id}/ws",
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

Establish WebSocket

const ws = new WebSocket(websocketUrl)
ws.send(JSON.stringify({ event: 'auth', args: [token] }))

Receive Events
- console output - Log messages from server
- stats - Resource statistics (CPU, RAM)
- status - Server status changes

Send Commands

ws.send(JSON.stringify({ event: 'send command', args: ['say Hello'] }))

Connection States

Connected
Connecting
Disconnected

Connected to daemon

Live console output streaming
Commands can be executed
Real-time statistics updates
No connection banner shown

If WebSocket fails to connect within 3 seconds:

⚠️ Unable to connect to daemon. Server controls may not work until connection is restored.

This indicates:

Daemon node is offline
Network connectivity issues
WebSocket port blocked
Token expired or invalid

Sending Commands

Execute commands on your game server:

Via Web Console

Type Command
```
say Hello players!
```
Press Enter or click Send
Command Executes Output appears in console:
```
[Server] Hello players!
```

Required Permission: console.write

Command Format

Commands are sent exactly as typed:

Minecraft: say, op, stop, whitelist add
Rust: save, kick, ban
Source Games: changelevel, sv_cheats

No prefix needed (e.g., type say Hello, not /say Hello).

Command History

Navigate previous commands:

Up Arrow: Previous command
Down Arrow: Next command
History persists during session
Cleared on page refresh

Common Commands

Minecraft

# Player management
op PlayerName              # Grant operator
deop PlayerName            # Remove operator
kick PlayerName Reason     # Kick player
ban PlayerName Reason      # Ban player
whitelist add PlayerName   # Add to whitelist

# Server control
say Message                # Broadcast message
stop                       # Stop server
save-all                   # Force world save

# Teleportation
tp Player1 Player2         # Teleport player

Rust

# Server management
save                       # Save server state
quit                       # Stop server

# Player management
kick PlayerName "Reason"   # Kick player
ban PlayerName "Reason"    # Ban player
unban PlayerName           # Unban player

# Admin
ownerid SteamID64          # Grant owner
moderatorid SteamID64      # Grant moderator

Source Games (CS:GO, TF2)

# Map control
changelevel de_dust2       # Change map
mp_restartgame 1           # Restart match

# Player management
kick PlayerName            # Kick player
ban PlayerName             # Ban player

# Server settings
sv_cheats 1                # Enable cheats
mp_roundtime 5             # Set round time

Viewing Console Output

Log Streaming

Console messages stream in real-time:

[12:34:01] [Server thread/INFO]: Starting minecraft server version 1.20.4
[12:34:02] [Server thread/INFO]: Loading properties
[12:34:03] [Server thread/INFO]: Default game type: SURVIVAL
[12:34:05] [Server thread/INFO]: Preparing level "world"
[12:34:08] [Server thread/INFO]: Done (6.234s)! For help, type "help"

Auto-Scroll Behavior

The console automatically scrolls to show new messages: Auto-Scroll Enabled:

Scrolled to bottom
New messages auto-scroll into view
Keeps latest output visible

Auto-Scroll Paused:

User scrolls up to view history
New messages don’t interrupt reading
Resume by scrolling to bottom

Message Limits

To prevent memory issues:

Buffer Size: 1000 most recent messages
Older Messages: Automatically removed
History: Not persisted across page reloads

For complete logs, use:

Server log files via file manager
SFTP to download log files
Third-party logging services

Timestamps

Each message includes:

Browser Timestamp: When message was received by client
Format: HH:MM:SS
Timezone: User’s local timezone

Server may also include its own timestamps in the message.

Console Permissions

Console access requires permission nodes:

Permission	Description
`console.read`	View server console output
`console.write`	Send commands to server console

Permission Examples

View-Only:

["console.read"]

User can see console output but cannot send commands. Full Console Access:

["console.read", "console.write"]

User can view output and execute commands. Console Wildcard:

["console.*"]

Grants all console permissions.

Non-WebSocket Fallback

If WebSocket is unavailable, use the HTTP fallback:

Send Command via API

POST /api/servers/{serverId}/command
Content-Type: application/json

{
  "command": "say Hello from API"
}

Fetch Logs

GET /api/servers/{serverId}/logs

Returns recent log lines (not real-time).

The fallback provides basic functionality but lacks real-time streaming. Use WebSocket for the best experience.

Activity Tracking

Commands executed through the console are logged:

Activity Feed: Shows who ran what command
Timestamp: When command was executed
User Attribution: Links command to user account
Command Content: Full command text

Required Permission: activity.read (to view activity logs)

Auto-Shutdown Integration

Servers with auto-shutdown enabled track console activity:

Sending a command updates lastActivityAt
Resets inactivity timer
Prevents shutdown during active management

EULA Extension

Some games (Minecraft) require EULA acceptance: Automatic Detection:

Console monitors for EULA prompt:

You need to agree to the EULA in order to run the server.

Panel shows EULA modal:
- Full EULA text
- Accept/Decline buttons
- Link to Mojang EULA
On accept:
- Creates eula.txt with eula=true
- Restarts server automatically
Server starts successfully

This eliminates manual file editing for first-time Minecraft servers.

Troubleshooting

No Console Output

Symptoms: Console is blank, no messages appear Causes & Solutions:

Server Offline
- Check server status badge
- Start server if stopped
- Console only shows output when running
WebSocket Disconnected
- Check for connection banner
- Verify node is online
- Refresh page to reconnect
Missing Permission
- Ensure you have console.read permission
- Contact administrator to grant access

Commands Don’t Work

Symptoms: Commands sent but no response Causes & Solutions:

Server Not Running
- Console commands only work when server is RUNNING
- Start server first
Wrong Command Format
- Check game-specific syntax
- Some games use different prefixes
- Refer to game documentation
Missing Permission
- Verify you have console.write permission
- Admin must grant console access
WebSocket Disconnected
- Commands require active WebSocket
- Wait for connection to restore
- Use HTTP fallback endpoint

Console Shows Old Messages

Symptoms: After starting server, console shows previous session Cause: Message buffer retains history across server restarts Solution: Refresh page to clear buffer, or scroll to bottom for latest output

WebSocket Won’t Connect

Symptoms: Connection banner persists, no console output Causes & Solutions:

Node Offline
- Check node status in admin panel
- Verify daemon is running on node
- Check daemon logs for errors
Firewall Blocking
- WebSocket uses node’s primary port (8080)
- Allow inbound/outbound on daemon port
- Check browser console for network errors
Invalid Token
- Tokens expire after 15 minutes
- Refresh page to generate new token
- Check browser console for auth errors
HTTPS Mixed Content
- Panel on HTTPS but node on HTTP
- Browser blocks insecure WebSocket
- Use HTTPS for daemon or HTTP for panel

Best Practices

Monitor Server Startup

Watch console during server start:

Verify plugins load correctly
Check for errors or warnings
Confirm “Done” message appears
Test with simple command

Use Console for Diagnostics

When troubleshooting:

Check console for error messages
Look for exception stack traces
Identify failed plugin loads
Monitor resource warnings

Be Cautious with Commands

Some commands are destructive:

stop - Stops the server
ban - Permanently bans players
delete - Removes data

Double-check before executing.

Grant Console Access Carefully

Console write permission is powerful:

Can execute any server command
Can ban/kick players
Can stop server
Can modify game state

Only grant to trusted users.

Overview

Getting Started

Core Features

User Management

Automation

Advanced

Deployment

​Overview

Real-Time Streaming

Command Execution

Color-Coded Output

Auto-Scroll

​Console Interface

​Visual Components

​Message Types

​WebSocket Connection

​Connection Process

​Connection States

​Connection Banner

​Sending Commands

​Via Web Console

​Command Format

​Command History

​Common Commands

​Viewing Console Output

​Log Streaming

​Auto-Scroll Behavior

​Message Limits

​Timestamps

​Console Permissions

​Permission Examples

​Non-WebSocket Fallback

​Send Command via API

​Fetch Logs

​Activity Tracking

​Auto-Shutdown Integration

​EULA Extension

​Troubleshooting

​No Console Output

​Commands Don’t Work

​Console Shows Old Messages

​WebSocket Won’t Connect

​Best Practices

Build docs developers (and LLMs) love

Overview

Console Interface

Visual Components

Message Types

WebSocket Connection

Connection Process

Connection States

Connection Banner

Sending Commands

Via Web Console

Command Format

Command History

Common Commands

Viewing Console Output

Log Streaming

Auto-Scroll Behavior

Message Limits

Timestamps

Console Permissions

Permission Examples

Non-WebSocket Fallback

Send Command via API

Fetch Logs

Activity Tracking

Auto-Shutdown Integration

EULA Extension

Troubleshooting

No Console Output

Commands Don’t Work

Console Shows Old Messages

WebSocket Won’t Connect

Best Practices