Import a subscription
First, identify what you have. A subscription URL usually starts with https:// and provides a set of configurations. The service documentation should identify it as a subscription URL; don't enter the URL of an account management page. Links starting with vmess:// or vless:// are single-node share links. Import them from the client's clipboard option instead; there's no need to create a subscription group. When copying a subscription URL, keep the question mark and everything after it. Remove only accidental spaces or line breaks at either end. Don't include the full URL when reporting an issue.
v2rayN for desktop: Add a subscription group
Open Subscription Group from the main window menu and select Subscription Group Settings, then click Add. Enter a recognizable name in Remarks and paste the full subscription URL into Address (url). Make sure Enable Update is on. For the first import, leave the Automatic Update Interval (minutes) unchanged and keep Filter blank so you don't exclude usable entries. Click OK, close the settings window, and return to the node list in the main window.
Select the group you just created, then choose Update Current Subscription from the Subscription Group menu. If the menu offers both Update without proxy and Update through proxy, choose without proxy the first time, before you have a working connection. Wait for the update to finish and confirm that nodes appear in the selected group. Seeing the group name alone doesn't mean the import is complete. If other groups have entries but this one is empty, first make sure you updated the selected group rather than mistaking old entries for the new results.
v2rayNG for Android: Save, then update from the list
Tap the menu in the upper-left corner of the main screen and open Subscription Group Settings (called Subscription Groups in some versions), then tap + in the upper-right corner. Enter a remark and the subscription URL, then tap the check mark in the upper-right corner to save. Return to the node list, switch to the new group, then tap Update Subscription in the overflow menu at the upper right. If the client shows multiple groups, switch back to the new one after updating and check its contents. Don't simply tap an old node that was already selected in the list.
On both clients, this step is complete when the new group contains nodes. If the update fails, check the group settings to make sure the full URL was pasted and that your network can reach the subscription service. Don't add the same URL repeatedly. If the device clock is noticeably wrong, enable automatic time setting before trying again. See FAQ for URL formats and import options. Once the list has entries, configure how traffic is routed.
Choose a proxy mode
Keep two things separate: the proxy entry point determines which apps send requests to the client; routing rules determine whether requests the client receives go through the proxy or connect directly. Choosing Global for routing doesn't automatically make every desktop app use the system proxy. For your first setup, choose one test browser and one test page. Open the page before connecting and note whether it loads. Keep the same network and browser for comparison later.
v2rayN for desktop: Choose a route, then enable the system proxy
Open Routing from the system tray menu or use the routing control in the main window. To use a preset that separates direct and proxied traffic, choose Bypass Mainland China. To check whether a request can use the selected node, temporarily choose Global to reduce the chance that the test page is routed directly. Preset names vary by version and imported rules, so use the name shown in your client. There's no need to import extra rules just to find a particular preset. Note your original selection and switch back after testing.
There's no need to change LAN sharing, listening ports, or virtual adapter settings at this stage. For an initial browser test, use the system proxy, which affects only apps that follow this setting. If your browser is controlled by an extension or manual proxy configuration, note its current settings and use a browser that follows the system proxy for testing. Enable the system proxy after choosing a node in the next step. This makes it easier to tell whether the proxy entry point is misconfigured or the node can't connect.
v2rayNG for Android: Don't limit the apps yet
Use VPN mode for the first test. If your version offers a running mode setting under Settings, confirm that VPN is selected rather than a mode that starts only a local proxy. If you can't find this option, use the system connection prompt in the next step as your guide. If per-app proxying is enabled, note the current settings and turn it off temporarily before the first test so the browser isn't excluded by the app list. Once a regular connection works, restore the app list if needed and test an app on it separately. See the glossary for the difference between routing presets and proxy entry points.
Connect
Return to the group you just updated and select one entry to test. Note its remark and use the same node for each check that follows, so you aren't changing the node, route, and network at the same time. If an entry looks unavailable, first check that the client has finished starting. A single test result in the list isn't enough to conclude that the entire subscription is invalid.
v2rayN for desktop: Set the active server
Right-click the selected node and choose Set as active server. Confirm that the active-node indicator appears on the target entry, not just that its row is highlighted. Then right-click the v2rayN icon in the system tray and select Auto configure system proxy under System proxy. If your desktop environment doesn't offer this menu, or the system proxy can't be set, check your desktop environment and app settings in Troubleshooting. Don't treat a routing option as a replacement for the system proxy.
Check the log or status area in the main window after switching nodes. Make sure there are no recurring startup failures, port conflicts, or similar messages. If an error appears, save the first useful message and stop to investigate; repeatedly clicking the same toggle usually won't help. A clean log confirms only that the client started. Test in the next step to see whether the browser is actually using the system proxy.
v2rayNG for Android: Approve the system VPN request
Tap a node in the list and confirm that the selection indicator moves to that entry. Tap the Connect button in the lower-right corner. The first time you connect, the system displays a VPN connection request. Confirm that it came from the client you just opened, then tap OK or Allow; the button label depends on your system. Wait for the client button to show that it's running, then check the system status bar or VPN settings for an active connection. Selecting a node without tapping the button in the lower-right corner doesn't route traffic through it.
If the button quickly returns to the stopped state, first check whether another VPN app is using the connection. Close the conflicting connection and try again with the same node. On a managed device, confirm that its policy allows the connection; don't change the management settings. Once the status is stable, open the test browser. This avoids mistaking the brief connection startup delay for a failure.
Verify the connection
Keep the same network and browser, reopen the test page, and refresh it once to rule out cached content in an old tab. If the page shows your public IP address, compare the results from before and during the connection. A changed exit IP is useful evidence that the test page used the proxy. If it hasn't changed, check whether the route sends it directly and whether the browser uses the proxy entry point; don't assume the node is faulty. A page loading or the client showing Connected doesn't, by itself, prove that the request went through the proxy.
Change one setting at a time
If the browser can't open the test page after connecting, first try another ordinary site that was accessible before. This helps determine whether the issue affects one destination or browsing in general. Then check the proxy entry point: on desktop, make sure Auto configure system proxy is still selected in the tray menu; on Android, check that the system still shows an active VPN and that the browser isn't excluded by the app list. If the entry point is set correctly, try another node in the same group and repeat the original test. Comparing both results makes it easier to pinpoint the cause than changing the node, port, and route all at once.
If the browser works but another app behaves the same as before, test that app separately. On desktop, first check whether it follows the system proxy. On Android, check whether it's included in the per-app proxy list. There's no need to change DNS or reinstall the client before identifying an entry point or routing issue. For repeated subscription update failures, persistent node timeouts, or disconnections after sleep, follow the relevant steps in Troubleshooting.
Compare again after disconnecting
On desktop, select Clear system proxy from the tray menu to remove the settings written by the client for this session. If the device already had a manual or organization-managed proxy, restore its original configuration using your notes and management requirements; clearing the proxy isn't the same as restoring it. On Android, return to the main screen and tap the lower-right button again to stop the connection. Confirm that the system no longer shows this VPN as active. Reopen the test page in the same browser and compare the result with the initial state. Finally, restore any routing or per-app proxy settings you changed temporarily for testing.
Complete: The subscription group contains nodes, and the client can connect and disconnect as needed. A request that should use the proxy shows the expected difference before and after connecting.