Protocol support depends on the core implementation and client integration. The original Clash, Clash Meta/Mihomo, and different clients do not support the same set of protocols. If you see unsupported proxy type, upgrade or switch to a core that supports the protocol and ask the provider for a compatible configuration; Mihomo extension fields cannot be copied directly into the original Clash.
What determines protocol support?
Read the core name and version from the client's About page, then compare the node's type, TLS, and transport fields against the documentation for that version.
The name and version of the core the client is actually using
Whether the subscription's node protocol is supported by the current core
Whether transport-layer fields match the core documentation
Whether the client allows the corresponding experimental or extended feature
What to do when a protocol is unsupported
- Confirm the core version on the client's About page or in the logs(See Client directory)
- Check fields such as type, server, port, uuid, tls, and transport against the protocol documentation(See Outbound proxy configuration)
- If you see unsupported proxy type, switch to a core or client that supports the protocol
- Do not apply Mihomo extension fields directly to the original Clash
Protocols with the same name can still differ in transport and field definitions
Support for new protocols can change between versions; review the project's release notes
The subscription provider should clearly identify the core its configuration targets