Is your feature request related to a problem?
Is your feature request related to a problem? Please describe.
Yes. While 3x-ui already supports Hysteria2 as an Outbound protocol, it still lacks native Inbound (Server) UI support. Currently, users are forced to manually inject JSON in the "Custom Configuration" box to host a Hysteria2 server. This is inconvenient and breaks the panel's core functionality, such as real-time traffic monitoring and multi-user management.
Describe the solution you'd like
Please add hysteria2 to the Inbound Protocol dropdown list. Based on the technical evolution of Xray-core (2025-2026), the protocol is now stable for production deployment. The UI should include the following fields:
Auth Password: A field for the password (auth string).
Bandwidth Control: Mandatory up_mbps and down_mbps fields (Required for Hy2 congestion control).
Obfuscation: Support for salamander (Type and Password fields).
Ignore Client Bandwidth: A toggle for the ignore_client_bandwidth option.
TLS Settings: Integration with the panel's existing certificate management.
Additional context (Technical Milestones)
The Hysteria2 implementation in Xray-core has reached technical maturity:
v1.8.4: Initial introduction of Hysteria2 Inbound support.
v1.8.8 - v1.8.10: Stabilized salamander obfuscation and optimized UDP buffer handling.
v24.x - v25.x: Refined auth logic and fixed memory leaks in long-running sessions.
Latest (Feb 2026): Finalized transport layer integration. Parameters are now fully standardized and ready for production-grade deployment.
Describe alternatives you've considered
Currently using manual JSON injection, but it is error-prone, lacks visual traffic statistics, and makes it difficult to manage multiple inbounds.
Checklist
Is your feature request related to a problem?
Is your feature request related to a problem? Please describe.
Yes. While 3x-ui already supports Hysteria2 as an Outbound protocol, it still lacks native Inbound (Server) UI support. Currently, users are forced to manually inject JSON in the "Custom Configuration" box to host a Hysteria2 server. This is inconvenient and breaks the panel's core functionality, such as real-time traffic monitoring and multi-user management.
Describe the solution you'd like
Please add hysteria2 to the Inbound Protocol dropdown list. Based on the technical evolution of Xray-core (2025-2026), the protocol is now stable for production deployment. The UI should include the following fields:
Additional context (Technical Milestones)
The Hysteria2 implementation in Xray-core has reached technical maturity:
Describe alternatives you've considered
Currently using manual JSON injection, but it is error-prone, lacks visual traffic statistics, and makes it difficult to manage multiple inbounds.
Checklist