V2Ray Desktop client downloads

{
  "remarks": "Main subscription",
  "url": "https://example.com/sub?token=xxxx",
  "autoUpdateInterval": 360, // Unit: minutes
  "enabled": true
}

A subscription is the middle layer between node information and the client: one subscription URL points to a set of configurations maintained on the server, and the client re-fetches it at a set interval, so nodes can be added or removed without editing the configuration by hand. In v2rayN you set the auto-update interval for each subscription separately in the subscription group; 6 to 24 hours is the usual range — too short means frequent requests, too long means node changes arrive late. When an update fails, first check that the subscription URL is complete, then check the local clock and network status, and finally read the response shown on the log page. On Android, pull down on the subscription group page to refresh manually.

{
  "domainStrategy": "IPIfNonMatch",
  "rules": [
    { "type": "field", "outboundTag": "direct", "domain": ["geosite:cn"] },
    { "type": "field", "outboundTag": "proxy", "domain": ["geosite:geolocation-!cn"] },
    { "type": "field", "outboundTag": "direct", "ip": ["geoip:private"] }
  ]
}

Routing decides which traffic goes through the proxy and which connects directly. The snippet above sends sites in mainland China and LAN addresses to the direct outbound and everything else to the proxy outbound, while domainStrategy controls when domain names are resolved. The two rule sets adjusted most often are geosite and geoip: the first groups by site, the second by IP range, and both come from rule files bundled with the core. A typical sign of a bad rule is a local service that will not open or sites that slow down noticeably; when troubleshooting, open the log page and look at the line showing the matched rule, then go back to the rule set and compare entries one by one.

{
  "outbounds": [{
    "tag": "proxy",
    "protocol": "vless",
    "settings": { "vnext": [{
      "address": "example.com",
      "port": 443,
      "users": [{ "id": "b831381d-6324-4d53-ad4f-8cda48b30811", "flow": "xtls-rprx-vision" }]
    }]},
    "streamSettings": { "network": "tcp", "security": "reality" }
  }]
}

The outbound protocol and transport decide how the client and server complete their handshake. VMess and VLESS are two common outbound protocols: the first carries its own authentication fields, while the second hands authentication to the transport layer and stays lighter. The transport layer can be tcp, ws or grpc, and the security layer can be tls or REALITY; all three layers are written into the same outbound entry. v2rayN and v2rayNG use the Xray core by default and also ship V2Fly core builds; if an imported configuration reports an unrecognized field, the core and the protocol usually do not match — switch to a core that supports that protocol.

{
  "inbounds": [{
    "tag": "socks",
    "listen": "127.0.0.1",
    "port": 10808,
    "protocol": "socks",
    "settings": { "udp": true }
  }]
}

System proxy mode has the client listen on a local port, and the system or browser then hands traffic to that port. The snippet above is a typical local inbound: it listens only on the loopback address and is not exposed to the LAN or the internet. The system proxy switch in v2rayN writes the system proxy settings for you, and turning it off restores them; TUN mode takes over all traffic and does not depend on an application's own proxy settings. On Android, VpnService creates a virtual network interface with behaviour close to TUN mode, and you can decide per app in settings which apps go through the proxy and which connect directly.