All nodes unusable after import
Separate a link problem from a protocol problem: if the log shows a parse failure, the subscription is at fault; if every speed test times out, look at the nodes and core version.
Protocols
Which proxy protocols does Mihomo support
What SS, VMess, VLESS, Trojan, and Hysteria2 mean, and whether the core or the node decides protocol support.
Content reviewed · Nov 3, 2026
Who it is for
People who see SS, VMess, Trojan, and similar labels on nodes and want to know what they mean and what Mihomo supports.
Before you read
- No software installation required
- Know that node information comes from your provider
Key ideas
- 1
A protocol is the agreed encryption and transport method between the client and a node. One subscription can mix nodes of several protocols.
- 2
Mihomo covers the mainstream set: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, TUIC, WireGuard, SOCKS5, HTTP, and more. The full list lives in the official Mihomo documentation.
- 3
What you can use is decided by the node, not the client. If the core supports a protocol but your provider offers no such node, you cannot use it.
- 4
Newer protocols such as Hysteria2 and TUIC do not work on old cores, which is one more reason not to stay on a discontinued client.
- 5
Do not agonize over protocol choice: that is the provider’s decision. You only need to confirm the core supports the node types in your subscription and that speed tests pass.
Common issues
Same-named protocols behave differently
Protocols have versions and transport variants, so differences may come from the transport layer rather than the protocol itself. Confirm version and transport settings first.
Next step
To see how these nodes appear in a profile, continue with the config structure guide.
Read next：How a Mihomo config file is structured