[Bug]: Bug: minClientVersion and maxClientVersion default values create a logical conflict, dropping PC/Windows connections

[fakepeek]

Describe the bug

After a clean installation/update of the 3x-ui panel, default values for minClientVersion and maxClientVersion under Inbound settings (Reality/Security configuration) are generated with contradictory data.

Specifically, minClientVersion sets itself to a higher version (e.g., 26.3.27), while maxClientVersion sets itself to an older version (e.g., 25.9.11).

How to reproduce the problem

1. Create a new VLESS-Reality inbound in the latest 3x-ui panel.
2. Check the default minClientVersion and maxClientVersion fields.
3. Try to connect from a Windows desktop client. The connection will fail.

Expected behavior

The server should accept incoming connections from valid Xray/sing-box desktop clients without dropping packets, as long as the clients are using standard protocols.

Actual behavior

The server enters a logical loop due to conflicting version constraints (minClientVersion is higher than maxClientVersion). It immediately drops connections from Windows/PC clients with a net::ERR_CONNECTION_CLOSED error during the TLS handshake.

Relevant logs

Screenshots

3x-ui version

3.5.0

Xray-core version

No response

How did you install 3x-ui?

install.sh script

Operating system

Ubuntu 24.04

Which parts of the panel are affected?

No response

Browser (only if it is a UI bug)

No response

Is the panel behind a reverse proxy or CDN?

None

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).

[MHSanaei]

The min/maxClientVersion values shown are Ant Design placeholders, not stored values — nothing is persisted, so there is no conflict. Closing.