A subscription link may return Clash, Mihomo, Clash Meta, generic proxy links, or a rule set. Clients and cores do not all recognize exactly the same formats. Ask the provider to generate the Clash or Mihomo format directly. If the log reports unsupported proxy type, use a core that supports the protocol; simply deleting fields leaves compatibility problems behind.
Where is the subscription format incompatible with the current core?
In the subscription preview, inspect the top-level fields and the type of the first node, then compare them with the core name and version in the client's About page.
- Does the subscription response contain proxies, proxy-groups, and rules?
- Does the log report unsupported proxy type, unknown field, or parse failed?
- Does the client's actual core support the protocol fields in the subscription?(See Outbound proxy configuration)
- Was the subscription mistakenly imported as a rule-provider or local configuration?
Switch to a configuration format the client can recognize
- First confirm the core name and version in the client(See Client directory)
- Review the subscription preview or logs to determine whether the response is a complete configuration, node list, or rule set
- Use the protocol documentation to confirm support for fields such as type, transport, tls, uuid, and password
- If the format is incompatible, use a client that supports it or ask the configuration provider to generate a configuration for the appropriate core
Do not delete unfamiliar fields and then use the result long term
Original Clash and Mihomo extension fields differ
Subscription-conversion services may handle sensitive URLs; verify that the source is trustworthy before using one