Import subscriptions
A subscription URL provides a refreshable list of nodes; a single share link adds just one node. In v2rayN, create a subscription group, paste and save the URL, then update the group. Once the nodes appear, select one and test the connection. Unlike importing links one at a time from the clipboard, subscriptions let you refresh the whole group at once. In v2rayNG, the option is usually under subscription settings. If the list is still empty after updating, first make sure you have a subscription URL, then check that it’s accessible.
Subscription group settings
Routing rules
Routing sends different requests to direct, proxy, or block outbounds. Start with a specific domain rule and test it against a known domain before adding broader rules. Cores usually process rules in list order, so a broad rule near the top may override exceptions below it. Compared with editing a full JSON config, v2rayN’s routing list makes rule order and outbounds easier to check. On mobile, review which fields are supported and what the default outbound is.
Routing settings
Switch cores
The client edits and starts the configuration; the core handles protocol handshakes and traffic forwarding. Before switching cores, check the node’s protocol, transport, and security options. Then select a compatible core in v2rayN settings and check the startup log using the same node. If a field is unrecognized, check whether the current core supports that option before changing subscriptions. On Android, v2rayNG targets Xray and v2flyNG targets V2Fly, so choose based on config compatibility.
Core type settings
Share with your LAN
To temporarily share a desktop proxy with another device on the same network, enable LAN connections in v2rayN, then enter the host’s local network address and proxy port on the other device. Unlike importing subscriptions on each device, this lets the host manage node selection centrally, but only works with apps that honor proxy settings. Enabling it exposes the listener to more devices, so use it only on a trusted network, restrict access in your firewall, and turn sharing off when you’re done.
Allow connections from the local network
DNS settings
If an IP address works but domain names don’t, first check whether the app resolves the name itself or hands the request to the core for resolution. Then set separate DNS servers for direct and proxied requests as needed, and test each change. Unlike changing system DNS, client DNS settings only affect requests that enter the relevant resolution path; a browser’s own DNS settings may be unaffected. If routing depends on the destination address, check the order of domain and IP rules after making changes.
DNS settings