Hysteria2 and TUIC are newer proxy protocols based on QUIC. Performance is significantly better in weak network and high packet loss environments——For example, when traditional protocols are stuck during mobile phone hotspots, evening rush hours, and cross-border line jitters, they can often still hold up. The premise is that v2rayN must use the correct kernel.
1What's good about them
- Anti-packet loss: Based on UDP/QUIC, with built-in congestion control, there is no cliff-like slowdown like TCP when losing packets.
- Weak network friendly: It is more stable under mobile networks, satellites, and cross-border high-latency lines.
- Hysteria2 You can also customize the uplink and downlink bandwidth, which is suitable for situations where "the line is sufficient but TCP is not full".
When to consider it: If your commonly used lines are severely stuck during the evening peak hours, or the mobile network experience is poor, you can ask your service provider to try a Hysteria2 / TUIC node, which is usually more stable than VMess/VLESS on the same line.
2Key prerequisite: use sing-box kernel
This is the easiest trap to step into. Hysteria2 / TUIC support is mainly in sing-box Kernel-wise, the default Xray kernel has limited support for them. So:
- First confirm that the sing-box kernel is installed in v2rayN: Menu "Check for Updates" → Update/Download the sing-box kernel.
- After importing such nodes, v2rayN will usually Automatically select sing-box for it; If not, manually edit the node and set the "core type" to sing-box.
For details on multi-core switching see Kernel switching tutorial.
3Import node
The import method is the same as that of ordinary nodes: copy hysteria2:// or tuic:// To share the link at the beginning, use "Server" → "Import batch URL from clipboard", or pull the entire batch by subscribing. After importing, there is no difference in the process of selecting, measuring speed, and connecting.
4Troubleshooting for failure to connect
- The kernel is wrong: Most common. Confirm that this node uses the sing-box kernel and that the kernel has been updated to a newer version.
- UDP is restricted: These two protocols use UDP. A few network environments (some companies/campus networks) will restrict UDP, causing the connection to fail. At this time, you can only switch back to the TCP protocol (VLESS/Trojan).
- Port/Firewall: Verify that there are no port conflicts locally (see Port conflict), the firewall did not block v2rayN.