Connecting Instances
bext companion connects to your bext instances via the admin API at /__bext/admin.
Local instance#
If bext is running on your machine:
- Click the system tray icon
- Select Add Instance
- Enter
http://localhost:3000(or your configured port) - The companion auto-discovers the admin endpoint
Remote instance#
For remote servers, you need network access to the admin port. Two options:
Option 1: SSH tunnel (recommended)#
ssh -L 3000:localhost:3000 user@your-server.com
Then connect the companion to http://localhost:3000 as if it were local.
Option 2: Expose admin endpoint#
In bext.config.toml:
[admin]
enabled = true
listen = "0.0.0.0:9100" # Separate port for admin
username = "admin"
password = "your-secure-password"
Then connect the companion to https://your-server.com:9100.
Always use authentication when exposing the admin endpoint to the network. The admin API provides full access to configuration, cache management, and server control.
Multiple instances#
The companion supports connecting to multiple instances simultaneously. Each appears in the sidebar with a color-coded health indicator:
- Green — Healthy, responding normally
- Yellow — Degraded (high latency or partial errors)
- Red — Unreachable or error state
Health is polled every 30 seconds by default. Adjust in the companion settings.
For quick remote access without exposing the admin port, prefer the SSH tunnel option — it needs no config change and keeps the admin API off the network.
Related#
- Companion Overview — feature list and licensing tiers
- Download — install the companion first
- Request Inspector — inspect traffic once connected
- Cache Explorer — browse and purge cache once connected
- Configuration → Environment Variables —
BEXT_ADMIN_TOKENand related settings