-
Notifications
You must be signed in to change notification settings - Fork 5
Web Console
im-pingo edited this page Mar 26, 2026
·
1 revision
English | 中文
LiveForge includes a built-in web console for real-time stream management and monitoring.
- Real-time stream list -- view all active streams with state, codecs, bitrate, FPS, and subscriber counts, updated live
- Per-stream details -- inspect individual streams with GOP cache statistics (total frames, video frames, audio frames, duration)
- Multi-protocol preview player -- play any stream directly in the browser using HLS, DASH, HTTP-FLV, WebRTC, or WebSocket
- WHIP publish from browser -- publish a live stream from your camera and microphone using WebRTC WHIP, with outbound stats overlay
- Stream management -- kick publishers and delete streams from the UI
- Server information -- view server version, uptime, loaded modules, and endpoint addresses
-
Start LiveForge with the API module enabled:
api: enabled: true listen: ":8090" console: username: "admin" password: "admin"
-
Open a browser and navigate to:
http://localhost:8090/console -
Log in with the configured username and password (default:
admin/admin). -
The dashboard displays all active streams. Click on a stream to view details and open the preview player.
The console includes a multi-protocol preview player that supports:
| Protocol | Description |
|---|---|
| HTTP-FLV | Low-latency FLV playback via mpegts.js |
| WS-FLV | WebSocket FLV playback |
| HTTP-TS | MPEG-TS chunked playback |
| FMP4 | Fragmented MP4 via MSE |
| HLS | HLS.js adaptive playback |
| DASH | DASH.js adaptive playback |
| WebRTC | Ultra-low-latency WHEP playback |
Click "+ WebRTC Publish" to open the browser publish panel:
- Select camera and microphone devices
- Enter a stream key (e.g.,
live/browser1) - Click Start to begin publishing via WHIP
- Monitor outbound bitrate and frame stats in the overlay
- Click Stop to end the session
The published stream is immediately available for playback via any protocol.
The console is protected by session-based authentication. Change the default credentials in production:
api:
console:
username: "${CONSOLE_USERNAME}"
password: "${CONSOLE_PASSWORD}"Environment variable expansion is supported for all credential fields.