Leadaxe：LxBox 对 encryption 不合规的 VLESS 节点改为解析阶段丢弃并给出原因
在 LxBox 议题 147 中，Leadaxe 表示 v2.25.0 及以后版本（当前 v2.25.1）有两处改动：encryption 字符串不符合内核语法的 VLESS 节点会在解析阶段就被丢弃，并显示「invalid encryption string」的原因，而不是传给内核、把整份配置一起拖垮；作为兜底，若内核仍然因为某一个节点拒绝启动，应用会读取内核的报错、自动禁用该节点，并在其余服务器上启动 VPN，被禁用的节点会在服务器列表里标注原因。他请报告者升级到最新版，若 2.25.1 或更高版本仍出现「Failed to start service」，可带上新截图或 Settings → Diagnostics 的日志重开该议题。
作者原文@LeadaxeThanks for the report and the screenshot.
This is fixed in v2.25.0 and later (current release is v2.25.1). Two changes cover it:
- A VLESS node whose
encryptionstring does not match the core grammar is now dropped at parse time with a visible reason ("invalid encryption string"), instead of being passed to the core and taking the whole config down with it.- As a safety net, if the core still refuses to start because of one node, the app reads the core error, disables that node automatically, and starts the VPN on the remaining servers. The disabled node is marked in the server list with the reason.
Please update to the latest version. If "Failed to start service" comes back on 2.25.1 or newer, feel free to reopen this issue with a fresh screenshot or a log from Settings → Diagnostics.