Flirexa / Protocol guides / Hysteria2

Starter and above

Hysteria2 protocol guide

Hysteria2 is a TCP and UDP proxy built on QUIC. Its official protocol can behave like a normal HTTP/3 server to an unauthenticated observer.

TCP and UDP proxying

The protocol carries proxy requests over QUIC and supports both TCP and UDP relay. It is not a WireGuard peer and its configuration and client compatibility are different.

HTTP/3 masquerading

The official protocol specification requires an unauthenticated server to behave like a standard HTTP/3 web server or reverse proxy rather than exposing a distinctive authentication failure.

UDP dependency

If a network blocks or severely degrades QUIC or UDP, Hysteria2 may be the wrong option for that path. Protocol variety matters because no transport wins on every network.

Operator workflow

Test the route, not only the server

  • render the supported URI or client payload without leaking another account
  • monitor the server and test the actual route from target networks
  • verify QUIC and UDP from the target network
  • test TCP and UDP relay separately
  • confirm the unauthenticated HTTP/3 response
  • keep a different protocol available when UDP is unsuitable
TransportQUIC with the unreliable datagram extension, according to the official specification
Default appearanceAn unauthenticated endpoint can resemble an HTTP/3 server when configured correctly
CDNThe official documentation says ordinary CDN proxying does not carry authenticated Hysteria traffic
RouteThe protocol needs a directly reachable UDP path

Protocol statements are based on the official Hysteria2 specification and documentation. Availability must be tested on the operator's actual networks.