#6583 [Bug]: VLESS-REALITY node converted to Clash fails in v3.8 (worked in v3.3)

Describe the bug

Nodes created in 3x-ui v3.8 fail to connect in Clash (e.g., Clash Verge) after passing through a subscription converter (subconverter). However, nodes created with identical settings in v3.3 work perfectly under the exact same setup and converter. Comparing the raw vless:// links generated by v3.3 and v3.8 reveals no obvious structural differences, but the converted node from v3.8 results in connection timeouts/errors in Clash.

How to reproduce the problem

Steps to Reproduce Create a VLESS + REALITY + Vision (TCP) inbound/client in 3x-ui v3.8. Copy the generated vless:// link (or subscription link). Convert the link to Clash YAML format using a subscription converter. Import into Clash / Clash Verge and test connection -> Fails / Timeout. (Comparison) Do the same in 3x-ui v3.3 -> Works as expected.
Environment & Configuration 3x-ui Version: v3.8 (Fails) vs v3.3 (Works) Protocol: VLESS + REALITY + XTLS-Vision + TCP Client / Tools: Clash / Clash Verge via Subscription Converter
Sample Link

v3.8 link vless://[email protected]:59131?encryption=none&flow=xtls-rprx-vision&fp=chrome&pbk=e6Q2usn6jvP0qs0boZMsO9-4wkbYI8bIp8QzkdhZfXo&security=reality&sid=76c6047e5acdd8&sni=tesla.com&spx=%2F41482e4075084d6&type=tcp#ppp-iivoua3hz9

v3.3 link vless://[email protected]:59131?encryption=none&flow=xtls-rprx-vision&fp=chrome&pbk=DFWrM741ujw8tiKMMkWGxIOjL_FJU3xYzV5FbcIo4R8&security=reality&sid=cf74ab057a&sni=tesla.com&spx=%2Fnn9yBs6dyB3JOpB&type=tcp#ppp-yqxe1verjc

Expected behavior

No response

Actual behavior

No response

Relevant logs

Screenshots

No response

3x-ui version

3.8.0

Xray-core version

No response

How did you install 3x-ui?

install.sh script

Operating system

Ubuntu 24.04.5 LTS

Which parts of the panel are affected?

Frontend (UI / panel pages)

Browser (only if it is a UI bug)

No response

Is the panel behind a reverse proxy or CDN?

Yes — Nginx

Before submitting

I searched existing issues and this bug has not been reported.
I am running the latest released version of 3x-ui (or have verified the bug still exists on it).
This bug report is written in English.
I have redacted any sensitive data (tokens, real domains, client UUIDs).