V2Ray Community

Subscription groups and updates

A subscription URL points to a remotely maintained list of configurations; it isn't a server address you can connect to directly. Create a group, add a label and URL, then update it to see the available configurations. Groups help organize subscriptions by source or purpose; labels are only for local reference. Unlike entering servers one by one, subscriptions make it easier to sync server settings, but updates may overwrite remotely managed entries. To edit a configuration yourself, first make a separate copy. Subscription tokens are access credentials—hide them before sharing screenshots or logs. If an update fails, check that the URL is complete, still valid, and reachable.

https://example.com/sub?token=xxxx

Routing rules and match order

Routing determines which outbound connection handles a request that has reached the core; it doesn't make an app use the proxy automatically. Start with a preset, then add exceptions for a few domains if needed. Rules are usually evaluated in order, so place specific domains before broad categories to keep later rules from being bypassed. Split routing can preserve access to local services while directing other traffic through a remote connection. The snippet below shows only part of a ruleset. The direct outbound tag must exist in the full configuration, and geographic matches depend on the relevant rule data. Test changes in the target app rather than relying on the mode name alone.

{
  "type": "field",
  "domain": ["geosite:cn", "domain:example.com"],
  "outboundTag": "direct"
}

DNS resolution and traffic routing

DNS translates domain names into IP addresses. Consider its request path alongside the path used by application traffic. If a domain fails to load but its IP address works, check the DNS result first, then inspect routing. A GUI client's local DNS, remote DNS, and core DNS may belong to different configuration layers; don't combine fields from separate tutorials without checking where they apply. Before switching public DNS providers, find out how DNS queries are routed. The example below shows only part of a core DNS object, not a complete configuration. Whether to use encrypted DNS and how to avoid dependency loops depend on your client and network.

{
  "dns": {
    "servers": ["https://dns.example.com/dns-query"],
    "queryStrategy": "UseIPv4"
  }
}

Example domains are for illustrating configuration fields only. Use a working, trusted DNS resolver in your actual setup.

Choose a core for your protocol needs

A GUI client and a proxy core are separate software layers: the client stores subscriptions and preferences, while the core reads the configuration and establishes connections. Xray and V2Fly share some technical roots, but their protocol extensions, transport support, and configuration fields aren't identical. Check the server requirements before switching cores; for REALITY configurations, verify Xray support and confirm that the parameters match. The snippet below shows where common transport security fields fit, for reference only. Back up your configuration before switching, then check the startup log. If fields are incompatible, follow the documentation for the core you're using.

{
  "streamSettings": {
    "network": "tcp",
    "security": "reality"
  }
}

Coordinating TUN and routing

TUN receives traffic through a virtual network interface and can capture traffic from some apps that ignore the system proxy. It doesn't guarantee that every request will use the proxy outbound. Compared with a system proxy, TUN depends more on device permissions and coordinated network routing and DNS settings. First confirm that a standard proxy connection works, then enable TUN to avoid troubleshooting server connectivity and traffic capture at the same time. Clients use different traffic-capture components, so don't copy fields from one core to another. The snippet below illustrates a general approach to excluding routes; it isn't a TUN configuration. Whether private IP ranges should connect directly depends on your LAN and remote network needs.

{
  "type": "field",
  "ip": ["geoip:private"],
  "outboundTag": "direct"
}