Subscription import guide

Clash Subscription Import and Troubleshooting

Choose the right import path for a complete Clash/Mihomo YAML profile or a node provider, then diagnose download, parsing, and connection errors.

Updated: 2026-10-29

Start the import checklist

Direct Answer

Check what the URL returns before importing. A complete Clash/Mihomo YAML profile is different from a node-provider list. V2CROSS supplies ordinary node subscriptions, not a complete profile. Use a compatible client, or configure a supported Mihomo provider inside your own profile.

Complete profile or node provider?

A full profile supplies the configuration for the client. A provider supplies nodes to an existing configuration. Mihomo documents YAML, URI, and Base64 provider content; the profile must still reference that provider in a proxy group and define routing. Support depends on the installed core and node protocols.

Choose a supported import path

For a first import, use a compatible complete profile in the client profile interface. If you only have ordinary node links, use a client that supports them, or follow the Mihomo provider documentation. Do not paste a node list into a full-profile field and assume it is a complete configuration.

Keep private subscriptions local

If another format is needed, ask the provider for a compatible profile or prepare it locally using official documentation. Do not submit private subscription URLs or tokens to public conversion websites.

Use provider health checks deliberately

Mihomo proxy providers can define a refresh interval and a health-check URL, interval, timeout, lazy mode, and expected status. Use conservative intervals instead of continuously probing free nodes.

Steps

Identify whether the response is a complete YAML profile, provider content, ordinary URI/Base64 nodes, or an HTML webpage. A webpage URL is not a subscription.
Back up the current configuration. Import a compatible full profile through the profile interface, or add supported provider content to an existing Mihomo configuration and reference it from a proxy group.
Update and check the error message. A successful download does not prove successful parsing; a parsed list does not prove connectivity.
Select a node or group, enable the documented proxy or VPN mode, and test an actual website. If supported, compare routing modes one at a time and restore settings that do not help.

Checklist

Input format matches the selected profile or provider import path.
The installed core supports the node protocols and required fields.
The provider is referenced by a proxy group and routing uses the intended group.
Update, parsing, and real connection tests are checked separately.

Troubleshooting

Download or parsing fails

For download errors, check the complete URL, expiry, and network. For parsing errors, check for HTML responses, YAML errors, unsupported protocols, or use of a node list as a full profile. Do not disable certificate verification.

Nodes import but all time out

Refresh and try another current node before changing routing or DNS. Public nodes can fail; importing successfully or measuring low latency is not a safety or availability guarantee.

Only some sites fail

Review rules and DNS before replacing all nodes.

Clash Verge Rev quick setup Client import steps and format checks in English. Clash/V2Ray setup Full setup guide. Today's V2Ray nodes Ordinary node subscriptions, not ready-made full Clash profiles. DNS leak test Check routing behavior. V2Ray vs VPN Choose the right route model.

Official sources

FAQ

Can every V2Ray subscription work in Clash?

No blanket compatibility is guaranteed. Mihomo can read supported URI/Base64 node lists as provider content, but those lists are not complete profiles. Core versions, protocols, and the surrounding configuration still matter.

Should I switch to global mode first?

First verify the import and choose a node. If your client supports it, comparing routing modes can help diagnose a later connection problem. Global mode does not guarantee that every app uses the proxy.

Why does DNS break rule mode?

Rule mode depends on domain and DNS behavior. Conflicting DNS settings can route traffic incorrectly.