V2Ray Mac Client v2rayN Download and Setup Guide

Subscription → Add subscription
  Address     https://example.com/api/v1/client/subscribe?token=xxxx
  Remarks     Example subscription
  Update interval   1440 minutes
  Auto update   On

A subscription link is how node configs get distributed: the client pulls a node list at a set interval and stores only the link locally, while nodes are added or removed server-side by the provider. v2rayN supports multiple subscriptions, each with its own update interval, and you can turn off auto-update and refresh manually instead; in v2rayNG the subscription entry sits in the sidebar, and you can long-press to rename after importing. Import failures usually come down to three causes: the link itself has expired, the network was unreachable when pulling, or the response isn't a standard node list. To troubleshoot, first open the link in a browser and confirm it returns data, then check the exact error in the client's update log.

{
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      { "type": "field", "domain": ["geosite:cn"], "outboundTag": "direct" },
      { "type": "field", "ip": ["geoip:cn"], "outboundTag": "direct" },
      { "type": "field", "network": "tcp,udp", "outboundTag": "proxy" }
    ]
  }
}

Routing decides whether a connection goes through the proxy or direct. Rules match from top to bottom and stop at the first hit, so direct rules must come before the catch-all proxy rule. Domain rules use geosite:cn to cover common sites in mainland China, while IP rules use geoip:cn to catch the addresses those domains resolve to; with domainStrategy set to IPIfNonMatch, a domain rule that doesn't match is resolved to an IP and matched once more. After editing rules you need to reload the config or restart the core for the change to take effect, and the log prints the tag of the rule that actually matched, which you can use to verify the split behaves as expected.

Core settings
  Current core    Xray-core
  Alternative core    V2Fly-core
  Switch path    Settings → Core settings → Select core file
  Takes effect    After restarting the core

The GUI client itself doesn't handle proxy traffic — the core is what actually opens connections: v2rayN and v2rayNG ship with Xray-core by default and can also switch to V2Fly-core. Both share the same protocol base, such as VMess and VLESS, and their config formats are nearly identical; Xray moves faster on new features like REALITY and XTLS Vision, while V2Fly is more conservative about compatibility with older configs. Switching cores only changes how your machine parses and sends traffic, and whether a node works still depends on the server-side config. If a protocol errors out on the new core, try the other core first to see whether the problem lies in the config or in a difference between cores.

{
  "log": {
    "loglevel": "warning",
    "access": "none",
    "error": ""
  }
}

The runtime log records three things in order: config loading, the handshake with the node, and the connection going out according to the rules. When reading logs, find the first error — the lines above it usually provide context; failed to parse points to a config syntax problem, connection refused means the target is unreachable, and context deadline exceeded is usually a timeout. Setting loglevel to warning filters out everyday noise, while debug shows the full handshake, so remember to switch it back afterwards. The log panel supports clearing and exporting, which makes it easier to line entries up against the moment things went wrong.