Topic guides

Hysteria2 Node Parser

Parse hysteria2:// or hy2:// links and inspect server, port, password, SNI, insecure, and obfuscation parameters.

Last updated
hysteria2 node parserhy2 parserhysteria2 parsernode inspector
On this page

When to use it

  • A Hysteria2 import fails and you need to inspect the original fields.
  • You want to check SNI, port, password, insecure, obfs, and related parameters.
  • You need a readable breakdown for client compatibility debugging.

Privacy

Parsing is for field inspection and troubleshooting. The node content is not stored just because you inspect it.

Identify Hysteria2 before changing formats

Paste this fictional link into Node Inspector. hy2:// is an alias for Hysteria2; renaming a Hysteria v1 URI does not upgrade its protocol. These credentials and documentation address are not for connection tests.

hysteria2://[email protected]:443/?sni=hy2.example.com&alpn=h3#HY2-Demo

Expect protocol hysteria2, server 192.0.2.30, port 443, TLS name hy2.example.com and ALPN h3. HY2-Demo is just a label. Inspection does not authenticate or measure download speed.

Compare the Mihomo node extract

proxies:
  - name: HY2-Demo
    type: hysteria2
    server: 192.0.2.30
    port: 443
    password: demo-password
    sni: hy2.example.com
    alpn: [h3]
    skip-cert-verify: false

This example retains normal certificate verification. If a real source has obfuscation, port hopping or certificate pinning, review each option and the conversion diagnostics. pinSHA256 identifies a certificate hash, not a browser TLS fingerprint. A target that cannot preserve that trust requirement must not be made to appear compatible by deleting the pin.

Why ping can work while the node fails

Hysteria2 uses UDP-based transport. ICMP ping or a successful TCP check does not prove that the required UDP port is open or that authentication succeeds. Check core support, the UDP listener and cloud firewall, then SNI/certificate/password and any obfuscation or port ranges. Compare networks before changing security settings.

If a node disappears from a dynamic subscription, inspect input/output counts, the chosen format, filters and skipped-node diagnostics. Updating an upstream does not rewrite an already saved static file. Share only redacted diagnostics when asking for help.

Client reference