Import a Subscription
Start with the complete subscription URL provided by your service. Subscription URLs usually begin with https:// and let the client fetch a list of nodes, which you can update later using the same URL. Links beginning with vmess:// or vless:// usually share a single node; import them through the client's clipboard import option instead of pasting them into the subscription URL field. Keep any parameters at the end of the URL when copying it. A full subscription URL may contain access credentials, so don't post it in group chats or screenshots when asking for help.
v2rayN: Save the Group, Then Update the Subscription
Open the main window and select “Subscription Group” from the top menu, then choose “Subscription Group Settings.” Add an entry, give the group an easy-to-recognize name, and paste the full URL into the subscription URL field. Save, return to the main window, and switch to the group you just added. Open the “Subscription Group” menu again and update the current subscription. Updating only this group on the first import keeps the results separate from other groups. When the update finishes, check the group for server entries.
v2rayNG: Add a Group from the Side Menu
Open the menu in the upper-left corner of the main screen and go to “Subscription Group Settings.” Tap the plus sign in the upper-right corner, enter a name and URL, then save. Return to the main screen and select the new group. Open the menu in the upper-right corner and choose “Update Subscription.” When the update finishes, check the node list for that group. If other groups are listed, make sure the selected tab matches the name you entered before deciding whether the import worked.
Choose a Proxy Mode
For your first connection, answer one question: will the app you're testing send its requests to the client? The system proxy or Android VPN determines whether requests reach the client. Routing rules determine whether requests that reach it go through the proxy, connect directly, or get blocked. These are separate settings. Keep your existing routing rules for now; don't switch rule sets or enable multiple connection methods at once. Otherwise, if the test fails, it will be hard to tell whether the app never reached the client or its requests were routed somewhere else.
v2rayN: Start with the System Proxy
Open the v2rayN tray menu and find the system proxy options. For your first test, use “Set system proxy.” Note where this option is; you'll enable it after selecting a node in the next step. Leave TUN off, and don't manually enter a local proxy address in the test browser. The system proxy works with apps that read this setting. If your browser or a proxy extension is set to connect directly, use another proxy, or apply separate rules, switch it back to the system setting before testing. A successful browser test doesn't mean an app that ignores the system proxy is connected.
v2rayNG: Use Android VPN Mode
Open “Settings” from the side menu. If your version offers a run mode, keep or select VPN mode rather than a mode that only provides a local proxy port. If per-app proxying is configured, check whether the browser you plan to test is covered: when the rule includes only selected apps, the browser must be selected; when the rule bypasses selected apps, the browser must not be on the bypass list. If another VPN is active on the device, check whether it's safe to turn it off. Keep connections required by your organization in place and test on a device where you can change the settings.
There's no need to change protocols, ports, or DNS yet. Note the test app and connection method, then select a single node in the next step. If you later need to switch to TUN or adjust routing rules, first get a repeatable test result, then make changes one at a time using the routing and traffic-splitting section of the full manual.
Connect to a Node
Return to the subscription group you just updated. Select a node you can identify and note its name. The imported configuration already includes the address, protocol, and transport settings, so don't change them just for testing. Highlighting a row only selects it; check the active status to see whether the client is actually using it. Set the node as the active configuration and check the startup result so you don't accidentally test with a previous node.
v2rayN: Set the Active Server, Then Enable the System Proxy
In the main window's node list, right-click the node you want and choose “Set as active server.” Confirm that the active node indicator points to it. Then open the tray menu and select “Set system proxy” under the system proxy options. Check the startup output in the main window. If it reports that the core failed to start or a local port is in use, address the first clear error instead of repeatedly toggling the proxy. For a port conflict, check whether another client instance is running. Don't close programs you need to keep open.
v2rayNG: Start the Client and Approve the VPN Request
Select the node you want in the node list and make sure the selection moves to it, then tap Start at the bottom of the main screen. The first time you use VPN mode, Android will usually show a connection request. Confirm that it comes from the v2rayNG app you just opened before approving it. Return to the main screen and wait for the button to show that the client is running. If it stops immediately, check the client message and make sure you didn't miss the system confirmation. If you change nodes while the client is running, confirm the new configuration is active. If it hasn't switched, stop the client and start it again with the newly selected node.
The active-node indicator on desktop, the running status in Android, or the system VPN icon only confirms that the corresponding step ran on your device. None of these proves the remote node works or that browser traffic uses the proxy. Once the client shows that it's running, continue without changing the node, connection method, or network.
Test the Connection
Open the browser you chose earlier, create a new tab, and visit a site you can normally access. Send a new request rather than relying on an old page: cached content can still appear without a new connection. If the page loads, the app can access the network. But if your current routing rules send that destination direct, this doesn't confirm that the proxy is working.
Confirm the Proxy Is Used, Not Just That the Page Loads
Choose a test destination that your current rules are set to send through the proxy, then visit it again in the same browser. If the client logs connections, match the request time and destination address, and check whether the connection is marked as proxy outbound. A node latency check or a number shown in a node list isn't a substitute: the client's built-in test and your browser may use different connection paths. If the logs don't show the outbound route or you're unsure which rule matched, record the result as “app can access the network; proxy route not confirmed.”
Narrow Down the Cause Based on Where It Fails
If the client won't start, begin with the main window output or startup message. If the client is running but the browser can't connect, check whether the desktop browser reads the system proxy or whether the Android browser is covered by VPN mode. If you can see the request reaching the client and only destinations routed through the proxy fail, keep the same test destination and connection method, and try another node from the same subscription group. If switching nodes fixes it, investigate the original node or its route first. If both fail, that doesn't prove the client is at fault; use the logs to distinguish a timeout, a name resolution failure, or a remote connection refusal.
If the browser is confirmed to use the proxy but another app still doesn't, focus your troubleshooting on that app. Check whether it supports the system proxy, has a separate proxy configured, or is included in v2rayNG's per-app list. Compare results directly only when both apps have the same connection settings. If you change networks, nodes, and rules all at once, you won't know which change made the difference—even if the connection starts working again.
After your first successful connection, note the group name, active node, connection method, and test result—but not the full subscription URL. For subscription updates, traffic routing, or TUN mode, continue with the full manual.