VLESS: unsanitized `encryption` param crashes core and aborts batch URL test

[Normone]

Operating system

Windows

System version

10

Installation type

zip

Version

1.1.6 x64

Description

When running a URL test on a proxy group, the test aborts early if one of the profiles is a VLESS node with a malformed encryption query parameter. The core fails to build the outbound config, returns IPC code 1, and the entire batch is marked as done — leaving the remaining profiles untested.

This issue is not present in the legacy version 1.0.13 x64 of Throne, which handles the same subscription correctly.

Before passing encryption to the core, trim the value to the first recognised token (none), or wrap config build errors per-outbound so one invalid profile does not abort the entire batch.

Reproduction

1. Add a subscription containing a VLESS node whose encryption query parameter has extra data appended after the valid value (e.g. encryption=none=-@username---@username-... instead of encryption=none). Example malformed link: "vless://c5d39e5e-de2c-4614-af1a-652692097224@179.237.73.189:17931?security=none&encryption=none=-@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann&host=tci.ir&headerType=http&type=tcp#%F0%9F%87%A8%F0%9F%87%AD34745%20%7C%20%E2%9A%A1%EF%B8%8FTelegram%20%3D%20t.me%2FSOSkeyNET".
2. Add these nodes to a URL-test group.
3. Run "Test group latency" (ping test).

Logs

[Core error] infra/conf: failed to build outbound config with tag proxy-52-0 > infra/conf: failed to build outbound handler for protocol vless > infra/conf: VLESS users: unsupported "encryption": none=-@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann---@ghalagyann
IPC call failed (code 1)
URL test for batch done.