Get the client from its own project
| Client | Official source | What this page verifies |
|---|---|---|
| Clash Verge Rev | github.com/clash-verge-rev/clash-verge-rev and its documentation site | Remote subscription URL, URL profile, local YAML, import errors |
| v2rayN | github.com/2dust/v2rayN and its subscription description wiki | Subscription, share links, QR import, node selection, system proxy / TUN, logs |
A GitHub release or project document proves where the software comes from and what it claims to do. It does not prove that a third-party download site ships the same binary. Check the project owner, the release page, the version and the checksum when you download.
Clash Verge Rev: from subscription to traffic
- Open the Profiles page and paste the full Clash or Mihomo subscription URL into the remote subscription field, then import. The official documentation lists three remote methods: URL import, URL profile, and URL scheme.
- Run an update after importing, and confirm a profile card appears with a non-empty node list. If you see
client error(Connect), check URL reachability and the system clock first, then try another method from the documentation. - Select the proxy group and a node on the Proxies page. A node name appearing is not proof it works — run a latency test and check the connection log.
- Turn on System Proxy when applications that honour the OS proxy need traffic. Evaluate TUN only when you need wider capture; if TUN misbehaves, switch it off first to restore networking.
- Open an IP check to confirm the egress address and region. A green icon is not verification.
The documentation also covers importing a compatible local YAML. If the remote address returns a login page, an HTML error page or an empty file, a successful HTTP request still produces zero nodes.
v2rayN: keep subscriptions and single links apart
- Add your subscription address in the subscription group and run an update. The documentation describes a subscription as a collection that maintains multiple server configurations.
- If what you have is a single
vmess://,vless://ortrojan://share link, use that version's single-node import path. Do not paste a single link into the remote subscription field. - After updating, select a configuration in the server list and start the matching core. v2rayN can manage cores such as Xray and sing-box; whether a protocol works still depends on the core version and the configuration fields.
- Enable system proxy or TUN depending on how you use it. System proxy affects only applications that honour OS proxy settings; TUN covers more, and is more exposed to permissions, the virtual adapter and DNS configuration.
- When traffic fails, read the current client log, the core error output and the active node configuration. Log locations differ between versions — do not just press update repeatedly.
v2rayN has the subscription but says the import failed
When Failed to import subscription content appears, first check whether the log shows the body being retrieved before the error. A Windows case in v2rayN issue #10138 showed a response carrying Content-Encoding: gzip — the raw body was compressed bytes; the same content imported fine from the clipboard while the online update failed during parsing. Verified 2026-11-10. That single case does not diagnose your version or your subscription.
| Observed result | Check first | Next |
|---|---|---|
| Timeout, or HTTP 401 / 403 | Address, account permission, path | Subscription update troubleshooting |
| Request succeeds, body is HTML or empty | Login page, challenge, wrong endpoint | Ask the provider for the correct endpoint |
| Body retrieved, import fails, response is gzip | Compressed response vs the client's parsing path | Record masked response headers, then read the gzip-specific page |
| Import succeeds, list still empty | Group, filter, node format, maximum count | Empty-list troubleshooting |
Do not hand a full subscription URL to an online converter. Keep the original configuration, and record on a trusted machine: client version, time, HTTP status and response encoding. If the response is confirmed compressed, work through the gzip case step by step. After importing, verify the active node against a real HTTPS request — "the list appeared" is not "the network works".
The shared troubleshooting order
| Symptom | Check first | Evidence to keep |
|---|---|---|
| Subscription download fails | Complete URL, HTTP status, certificate, system clock | Browser response and client log |
| Update succeeds, zero nodes | Whether the body is compatible YAML or HTML | Content type, file header, parse error |
| Nodes present, no traffic | Node parameters, core start, system proxy / TUN, DNS | Core log and egress IP |
| Everything dies after enabling TUN | Administrator rights, virtual adapter, DNS, rules | Whether networking returns when TUN is off |
| Only some applications work | Whether they honour the system proxy | System proxy vs TUN comparison |
Four checkpoints that decide the outcome
| Stage | Evidence of success | First move when it fails |
|---|---|---|
| Fetch | Expected HTTP response received | Check status code, certificate, network |
| Parse | Body recognised as a supported format | Confirm it is not an HTML error page |
| Import | Nodes enter the local list | Stop overwriting; keep a backup and a masked log |
| Activate | Active configuration switched | Check the current group, core and capture mode |
A received HTTP response is not a populated node list, and a finished import is not an activated profile. If the log shows a successful fetch followed by ArgumentOutOfRange_Count with an empty list, move to the v2rayN exact-error page. If the import is clean but pages still fail, continue with system proxy without internet.
Before updating, keep a recovery point
Keep the current configuration and subscription group information, and store the backup somewhere you trust. Full subscription URLs, tokens and node passwords are credentials: they do not belong in public screenshots, logs or support attachments. If you need to inspect a link's format first, use the browser-side converter.
Safe recovery after a failed import
- Stop repeating the update.
- Back up the current state.
- Run one minimal comparison in a temporary profile group.
- If needed, restore the pre-failure backup.
If the list is restored but traffic still fails, check the active server, the core, system proxy or TUN — do not change several conditions at once.
Evidence boundary
This page is assembled from the two clients' own projects and documentation. It does not claim the steps were verified on your device. Menu names and supported configuration ranges change between versions; compare against the documentation for the version you run.
Common questions
Is a Clash subscription the same file as a v2rayN subscription?
Not necessarily. Both usually return share links or a configuration, but accepted formats differ by client. When a provider offers separate Clash and universal endpoints, use the matching one.
The import succeeded but the list is empty. What now?
Check what the address actually returned — login page, HTML error page, empty body or compressed body all download successfully — then confirm the profile is selected and the maximum node count is not zero.
Is it safe to run the URL through an online converter?
Treat the URL as a credential: a converter receives every node and password in it. If you only need the format, use a client-side parser where nothing is uploaded.
Related
v2rayN: subscription imports as empty · invalid yaml remote profile · Subscription converter · Error index