Node HandbookNODE HANDBOOK中文
v2rayNG · Android

v2rayNG on Android: input format first, then connection

Most import failures on Android are format mismatches, not node failures. The three inputs people confuse produce an empty list, a parse error, or a stream of nodes that are not what they expected.

Node Handbook editorial team ·

Three inputs, three paths

InputWhat it isWrong path produces
vmess://, vless://, trojan://, ss://One nodeOne entry, or a parse error if the link is truncated
A Base64 subscription addressA list of share linksMany entries, or none if the body was HTML
A Clash / Mihomo YAMLA configuration for a different client familyEmpty list or a parse error — v2rayNG is not a Clash client

The third row is the most common mistake: a provider offers a Clash endpoint and a universal endpoint, and only the latter suits this client.

Import and select

  1. Copy the address or link from the provider's panel.
  2. Use the entry that matches the input shape.
  3. Update the subscription explicitly, then confirm the node count is plausible.
  4. Select a node — a list without a selection produces no traffic.
  5. Start the connection and confirm the system VPN indicator appears.

Reading the first error

MessageMeaningNext step
allowInsecure has been removedAn imported link uses a retired TLS fieldRepair the share link; do not disable certificate checks
ArgumentOutOfRange on updateThe parser received fewer items than expectedCheck what the body actually is; often empty or a block page
Config parse failureThe input is not a format this build readsUse the provider's format for this client
Connected, no trafficSelection, capture or the node itselfFour-contrast test below

The four contrasts

TestResult means
Client off, ordinary siteBase network health
Another node, same subscriptionWhether that node or its path is the issue
Another network (Wi-Fi vs mobile data)Whether the current network path is involved
One application vs SafariWhether the app bypasses the tunnel

Android specifics

  • The VPN indicator reflects an active configuration; it does not prove a request completed.
  • Battery optimisation can interrupt a background tunnel; that shows up as intermittent failure, not as a parse error.
  • A private DNS setting at the system level can conflict with the client's own DNS handling.
  • Per-app proxy settings, if enabled, decide which applications are captured — a missing app there looks like a routing failure.

Scope

This page describes import, selection and the first-error order. Menu names follow the installed version. Nothing here evaluates a provider or asserts that every protocol is supported by every build.