VelocityWebPanel

VelocityWebPanel

Requires LuckPerms

A distributed Minecraft network web panel for Velocity + Paper environments. `VelocityWebPanel` runs a central panel on your Velocity proxy and connects Paper servers as backend agents, giving you one place to monitor and manage your network.

What It Does

- Hosts a browser-based admin panel from the Velocity side - Connects multiple Paper servers through a backend WebSocket channel - Streams server stats, players, plugins, and console output in near real time - Lets authorized users run commands on individual backend servers - Includes account-based login with BCrypt-hashed passwords

Architecture

1) Velocity Side (Central Hub)

- Serves the web UI over HTTP (`web-port`, default `8080`) - Exposes API endpoints for auth, polling, and actions - Runs internal backend WebSocket server (`ws-port`, default `8100`) - Maintains connected server sessions and broadcasts updates to browsers - Includes a built-in `Velocity` node in the dashboard via `VelocityProxyBridge`

2) Paper Side (Agent on Each Server)

- Connects to Velocity using shared secret handshake - Sends periodic stats (TPS, memory, CPU, uptime, players) - Streams console lines and command outputs - Sends plugin list and player list updates

Web Panel Features

- Users: all connected servers with online status and quick metrics - Users: live output + remote command execution - Users: per-server player list view - Users: server performance cards + historical player samples - Users: installed plugin list per backend - Users: aggregated table across all servers - Users: list/remove panel users from the UI

Authentication & Access

- Players register or update panel password using: - `/vwpanel <password>` - Passwords are stored as BCrypt hashes in `users.dat` - Required LuckPerms integration validates `velocitywebpanel.use` permission - Backend agent connections are protected by a shared `secret` value

Configuration (from `config.yml`)

- `panel-name`: panel branding/title - `web-port`: panel HTTP port - `ws-port`: backend agent WebSocket port - `secret`: shared backend handshake secret - `velocity-host`: proxy host used by Paper agents - `server-name`: backend display name - `server-type`: backend type label - `update-interval`: stats push interval (seconds) - `console-buffer-size`: retained console lines on agent side

Typical Use Case

Ideal for network operators who want lightweight centralized visibility and control across multiple Paper servers behind Velocity, without requiring a heavy external dashboard stack.