V2Ray for Mac Download & Setup>_

A subscription URL fetches server configurations in one place, unlike a share link for a single server. In subscription group settings, enter the URL, save the group, and run an update to add its contents to the server list. Separate groups make it easier to manage different sources and identify which one failed to update. If the list is empty afterward, check that the URL is complete and the subscription is still valid, then try an appropriate update method. Unlike adding servers one by one, subscriptions can reflect changes from their source, but they do not sync all local routing settings.

The server list stores connection details; the active server is the configuration currently in use. After importing, check the protocol, address, port, and transport options, then set the server as active. Share links reduce manual entry, but verify that they include all required transport and security parameters. A server appearing in the list does not mean the connection is working. Check server selection separately from the local proxy mode to narrow down issues more quickly than repeatedly reinstalling. To use a setup on multiple devices, keep connection details separate from each device’s local listening settings.

Routing sends requests entering the core to the appropriate outbound. A common setup sends specific domains, addresses, or rule sets directly and routes everything else through a proxy. Rules are matched in order, so put narrower exceptions before broader rules. When editing, confirm that each outbound tag exists and understand when the domain strategy triggers resolution. Unlike switching a global mode, split routing lets you handle destinations independently. After adding a rule, verify that it matches as expected rather than assuming it works because a website opens.

Set system proxy automatically points supported system proxy settings to the client. Clear system proxy removes those settings. Do not change system proxy leaves them as they are—it does not switch traffic to a direct connection. System proxy usually works for browsers and apps that follow system settings, but it does not necessarily handle every program. Compared with TUN, its scope is more limited and explicit, making it a good starting point for a basic connection. After changing networks or quitting the client, check that the system is not still pointing to a local address where nothing is listening; stale settings can look like a server problem.

TUN uses a virtual network interface to capture eligible traffic, including traffic from apps that ignore system proxy settings. Before enabling it, make sure a standard proxy connection works, then check the required permissions and whether another network interception tool is active. Automatic routing, the network stack, and DNS settings need to work together, so avoid changing them all at once. TUN captures more traffic than system proxy and requires extra care with local network access and conflicts with network services. If you lose connectivity, disable TUN to restore the basic route, then check permissions, routing, and DNS one at a time.

DNS translates domain names into addresses, and the path used for DNS requests should match your routing policy. Direct and proxied traffic may need different resolution paths, while a browser’s encrypted DNS can bypass system settings. Keep a working default configuration unless you have a clear DNS resolution or rule-matching problem to address. Rather than changing a single DNS server address, check the query strategy, connection path, and app-specific settings together. When testing, review both DNS results and connection logs so you don’t mistake a certificate error or unreachable server for a DNS issue.