xfleet

An admin panel that sits in front of 3X-UI.

3X-UI is fine with one server and a few clients. Once you have more of either, you end up logging into separate panels, copying UUIDs around, and pasting share links into chats by hand. xfleet does that part for you — add a user once, it shows up on every server, with a share link you can send.

Useful if you're self-hosting a VPN for yourself and a few people and don't want it to feel like a job.

Prereqs

• Bun >= 1.2
• Postgres 14+

Setup

For local dev, docker compose up -d starts Postgres with the xfleet and xfleet_test databases pre-created.

cp .env.example .env
# generate secrets
openssl rand -hex 32                    # SESSION_SECRET
openssl rand -base64 32                 # MASTER_KEY
bun scripts/hash-password.ts 'pass'     # ADMIN_PASSWORD_HASH
# then fill .env manually
# NOTE: ADMIN_PASSWORD_HASH must be double-quoted with \$ escaping in .env:
#   ADMIN_PASSWORD_HASH="\$2b\$10\$..."
# Both docker compose and Bun's dotenv loader correctly strip \$ → $.

createdb xfleet
bun install
bun run migrate
bun run dev

Tests

createdb xfleet_test
TEST_DATABASE_URL=postgres://$USER@localhost:5432/xfleet_test bun test

Deploy

Production command:

bun run migrate
bun run start

The SSE endpoint /api/admin/events requires proxy_buffering off; (nginx) or equivalent.

Docker

A self-contained production example (app + Postgres) lives in docker-compose.prod.yml.

cp .env.example .env
# generate and fill POSTGRES_PASSWORD plus the same secrets as the non-docker setup
docker compose -f docker-compose.prod.yml up -d

The app runs migrations automatically on container start and publishes port 3000. Put your own reverse proxy (nginx/Caddy/etc.) in front — remember proxy_buffering off; for the SSE endpoint, and bind to 127.0.0.1:3000 in the compose file if you don't want port 3000 publicly exposed on the host.

License

AGPL-3.0-or-later. See LICENSE.