LxBox｜科学之家 kexuezj.com
LxBox · 科学之家
LeadaxeLxBox / sing-box-lx 开发者
GitHub·2026.09.19 03:31:49（UTC+8）

Leadaxe：LxBox 可用自定义抓取身份导入 Happ 的 Xray JSON

Leadaxe 说明 Happ 返回节点差异常来自请求头，而非内核限制；LxBox 可在订阅/全局设置自定义 User-Agent 与 HWID，并解析 Xray JSON 中的 proxy/member/balancer 等。详见原文。

作者原文@Leadaxe

Hi! This is most likely not a core limitation. Both outbounds in the Happ config are plain vless + REALITY + vision, sing-box handles those fine. What differs is the servers themselves: note the different shortIds (0c / 1f vs 26a8). Your provider simply hands out a different set of nodes depending on which client asks.

The panel decides that by the request headers, and you can change both in LxBox:

  • per subscription: open the subscription → settings → Fetch identity → enable Custom identity. There you get Custom User-Agent and Send HWID (x-hwid, plus x-device-os, x-ver-os, x-device-model, all editable);
  • globally for all subscriptions: app Settings → Subscriptions, same fields.

So set the User-Agent to what Happ sends (and turn on Send HWID if the panel has device limits), update the subscription, and you get the Happ version of it, which LxBox can use as is. It parses Xray JSON configs: proxy and member become nodes, and the balancer comes along too. routing.balancers + burstObservatory turn into an auto-select node named after remarks (your roundRobin becomes a round-robin pool over both servers, with the ping URL and interval taken from pingConfig). Only the Xray routing rules and DNS are not imported, LxBox has its own routing for that.

Please tell me what you get after that: do the nodes appear, and do they pass the whitelist?