[Bug]: Xray-core crashes (exit status 23) when Hysteria inbound is enabled instead of throwing a validation error

[mardrake]

Describe the bug

When using Xray-core as the panel's core, users can accidentally or intentionally create and enable a Hysteria inbound. Since the original Xray-core does not support Hysteria, it causes a critical crash with exit status 23 on startup.

Because Xray crashes in a loop, it completely locks down the panel web interface, forcing users to manually fix the database via CLI (sqlite3).

How to reproduce the problem

1. Set the panel core to Xray-core.
2. Create a new inbound with the Hysteria protocol.
3. Enable it and save.
4. Xray crashes with status 23, and the web UI becomes completely inaccessible.

Expected behavior

The panel should prevent users from enabling or saving a Hysteria/TUIC inbound if the active core is set to Xray-core. A validation error message should pop up in the UI (e.g., "Hysteria requires Sing-box core").

Actual behavior

The panel allows saving the inbound, generates an invalid config.json for Xray, and crashes the core with:
ERROR - XRAY: Failed to start: main: failed to load config files... > infra/conf: failed to build inbound config

Relevant logs

Screenshots

No response

3x-ui version

3.1.0

Xray-core version

26.5.9

How did you install 3x-ui?

install.sh script

Operating system

Ubuntu 24.04.4

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

[GamesIS]

I have the same problem, only in outbound

[MHSanaei]

What are you talking about of course xray support hysteria
https://xtls.github.io/en/config/inbounds/hysteria.html

[SweatierUnicorn]

I have same issue