[Bug]: when i create a new client on hysteria 2 xray restart and all user must restart the vpn connection

[usamirali]

Describe the bug

xray goes restart and all client on node or local panel on hysteria protocol needs to restart the vpn client

number two problem is when the client vpn app is on and it doent work about 5 minutes connection goes drop iuse udp hop but it doesnt work

How to reproduce the problem

1.create new client
2.on hysteria protocol
3.xray goes restart about 10 second later
4.all client needs to restart the app to connect to server again
5.when client dont use hysteria for about 5 minutes the connection goes disconnet
6. i use udp hop but it doesnt work

Expected behavior

No response

Actual behavior

No response

Relevant logs

Screenshots

No response

3x-ui version

3.3.0

Xray-core version

26.6.1

How did you install 3x-ui?

install.sh script

Operating system

ubuntu 26

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

[github-actions]

This report covers two problems that are already tracked separately.

Problem 1 (Xray restarts when adding a Hysteria2 client) is a duplicate of your own earlier report: #5062. That issue already has a detailed investigation — including how to enable debug logging to confirm whether the Xray gRPC AddUser API is failing for Hysteria2 — and your follow-up comment there confirmed the restart is happening. Please continue the conversation on #5062 rather than opening a new issue.

Problem 2 (connections drop after ~5 minutes of inactivity) is tracked in #5117. As documented there, udpIdleTimeout on the Hysteria2 inbound controls the server-side idle teardown window. The default is 300 s (5 minutes), which matches the timing you are seeing. You can raise it in the inbound's stream settings JSON, but note that xray-core enforces a maximum of 600 s — see the constraint reported in #5117's comments. Combining a longer timeout with a keepalive in your client app is the most reliable fix.

Closing this as a duplicate. Please use the existing issues for follow-up.