BlueKnightNet/Blue-Knight-Panel-Hostless

选用指南

AI 根据 README 整理 · 2026/10/31 04:01:36

适用场景

适用于在Hostless平台上部署代理服务，管理VLESS、VMess、Trojan等协议，并监控流量和资源使用。

查看 README 依据

# Blue Knight Panel · Hostless A Node.js proxy panel adapted for [Hostless](https://hostless.cloud/), with VLESS, VMess, Trojan, subscriptions, engine recovery, and resource monitoring. **[YouTube · @BlueKnight-Net](https://www.youtube.com/@BlueKnight-Net)** · **[Telegram · @BlueKnight_Net](https://t.me/BlueKnight_Net)** ## Deploy on Hostless 1. Sign in to [Hostless](https://hostless.cloud/) and create an **App** connected to this GitHub repository. 2. Select the **`blue-knight-net`** branch. 3. Use these build and startup settings: | Setting | Value | | --- | --- |

The optional URL input on **Run workflow** is for that one run only; scheduled runs use the `PANEL_URL` repository variable. No panel password, subscription token, or Hostless API key is required. Each user configures their own monitoring repository; the shared upstream workflow cannot discover every user's independent Hostless deployment automatically. ## Usage tab The Usage tab includes per-protocol traffic counters and live CPU/RAM readings. When container metrics are available, they include the proxy engines; fallback readings are labelled as panel-process readings.

使用方式

通过Hostless平台部署，使用npm start启动，访问/knight路径进行面板管理。

查看 README 依据

| Build system | Detect automatically | | Working directory | `/` | | Build command | Leave empty | | Start command | `npm start` | | Internal port | Use the `PORT` supplied by Hostless | 4. Attach a persistent volume at **`/data`** to keep panel settings and downloaded engines across deployments. Choose its capacity in the hosting dashboard; storage may incur charges. 5. Keep the default TCP health check, or use an HTTP check on **`/knight/login`**. 6. Deploy. The first startup downloads sing-box and Xray-core from GitHub, so allow time for both engines to install and start.

7. Open **`https://YOUR-APP.hostless.app/knight`**, create your panel password, and open **Subscriptions** to import a link into your client. The included [`hostless.yaml`](hostless.yaml) declares automatic builds and `npm start`. The app binds to `0.0.0.0` and reads Hostless's `PORT`; do not change the internal port to 443. See the official [Hostless Node.js deployment guide](https://docs.hostless.cloud/javascript/express) for platform setup. ## Public URLs and configs

部署要求

需要Hostless账户，部署时需附加持久化卷到/data目录，首次启动会从GitHub下载sing-box和Xray-core引擎。

查看 README 依据

| Build system | Detect automatically | | Working directory | `/` | | Build command | Leave empty | | Start command | `npm start` | | Internal port | Use the `PORT` supplied by Hostless | 4. Attach a persistent volume at **`/data`** to keep panel settings and downloaded engines across deployments. Choose its capacity in the hosting dashboard; storage may incur charges. 5. Keep the default TCP health check, or use an HTTP check on **`/knight/login`**. 6. Deploy. The first startup downloads sing-box and Xray-core from GitHub, so allow time for both engines to install and start.

已知限制

自ping无法唤醒已暂停的容器或重启停止的Node.js进程；面板可访问不代表代理引擎正常运行。

查看 README 依据

- A self-ping checks the panel every five minutes once its public domain is known, with a cache-busting request and visible `[keepalive]` success/failure logs. - IPv4-only domain resolution is selected automatically when no public IPv6 interface is detected. - Internal engine ports are assigned uniquely to avoid collisions between transports. **The self-ping cannot wake a suspended container or restart a stopped Node.js process.** Availability still depends on the host's lifecycle and health checks.

- **VLESS-XHTTP:** served by Xray-core; requires a client with XHTTP support. - **Shadowsocks over WebSocket:** served by Xray-core where generated and supported by the client. A working web panel does not by itself confirm that the proxy engines are running. Use a real connection or URL test in your client. ## Automatic recovery - Each engine has bounded crash-restart retries with backoff. The retry counter resets after a stable five-minute run. - Engine watchdogs check local TCP listeners every minute and request a restart after three consecutive failed checks.