Set up a v2rayN subscription
and system proxy

Step 1: Add a subscription

Copy the full subscription URL, then create a group with a name that identifies its source. The group name is for local reference only and does not affect the connection. When pasting the URL, check for extra spaces or line breaks at either end. Do not copy button text, an entire page of instructions, or an account sign-in URL. Subscription URLs may grant access to your account, so do not share them publicly or include them in error screenshots.

v2rayN: Add a subscription group and update it

Open the v2rayN main window, find Subscription Groups at the top, and open Subscription Group Settings. In some versions, the settings option is under a menu with the same name. Add a group, enter a recognizable name in the remarks field, paste the subscription URL into the URL or address field, and save. Return to the main window and select the group you just created. An empty list at this point does not necessarily indicate a problem: saving the URL and fetching configurations are separate steps.

Open the Subscription Groups menu again and choose Update Current Subscription or update all enabled subscriptions. If you do not have a working proxy yet, first try updating without a proxy. Check the status area or logs, then wait for the update to finish and review the server list. Configuration entries should appear; their names and number depend on the subscription. Confirm that the entries belong to the group you created before moving on. There is no need to edit each server's settings individually.

v2rayNG: Add a URL and refresh the subscription

Open v2rayNG, find Subscription Group Settings in the menu, tap the add option, enter a name and subscription URL, and save. Return to the configuration list, open the top-right menu, and choose Update Subscription or the equivalent option to update all subscriptions. When the update finishes, select the relevant group and check for configuration entries. The Import from clipboard option in the add menu is generally for shared configurations, not for creating a subscription group that can be updated.

If the update reports success but the list is still empty, check that you selected the right group and that no filters are enabled. If parsing or request errors appear, copy the URL again and confirm that the subscription has not expired and returns a configuration format the client supports. Consider updating through a proxy only if you already have a working connection but cannot access the subscription URL directly. Repeatedly toggling this option while the list is empty usually will not help. For specific symptoms, see the FAQ. For the difference between subscriptions and individual nodes, see the glossary.

Step 2: Choose a proxy mode

Once configurations appear in the list, decide how requests enter the client and which route they take afterward. These are separate settings: System Proxy and VPN mode control how traffic enters; routing options such as Bypass mainland China, Global, and Direct determine where it goes. Global routing does not mean every app is automatically intercepted. An app that does not use the system proxy may never pass through the client, even when Global is selected.

v2rayN: Configure the system proxy automatically

Find System Proxy in the main window's status bar or the system tray menu, then select Set system proxy automatically. Clear system proxy removes the system proxy settings; Do not change system proxy keeps the current settings and is not a substitute for enabling it during initial setup. After automatic configuration, browsers and apps that follow the system proxy settings will send requests to the local client. You do not need to enter a port manually in your browser yet.

Next, find the routing option. For a first setup, choose Bypass mainland China or a similar preset so requests matching direct rules connect directly, while other requests follow the preset. Preset names and rules vary by version; check the current client documentation for details. Leave TUN off for now. It can help later with apps that do not follow the system proxy, but adds variables such as a virtual network adapter, permissions, and routing, making it a poor starting point for your first connection test.

v2rayNG: Use VPN mode

Open v2rayNG settings, find Running Mode, and select VPN mode. This mode uses Android's VPN interface to capture traffic and pass it to the client core; seeing a VPN indicator in the system bar is normal. Proxy-only mode mainly provides a local proxy port that other apps must configure themselves. It does not automatically capture requests from regular apps, so it is not recommended for your initial setup.

In routing settings, choose an appropriate bypass rule. For your first test, leave per-app proxying off so your browser is not accidentally excluded. If you previously changed the app list, check whether the setting is Proxy selected apps only or Bypass selected apps; they mean opposite things. Leave DNS and domain policies at their defaults for now. These options do not need changing just because a connection is difficult. Adjust them to suit your needs after confirming a basic connection.

Step 3: Select a configuration and connect

Return to the subscription group and choose a configuration that your service provider says is available. Do not change the protocol, transport, and encryption fields all at once. Subscription parameters are usually designed to work together, and changing one field can cause a handshake failure. Speed tests can help you choose, but results depend on the test address and method. For your first connection, select a known working configuration and check that the core runs normally.

v2rayN: Set the active server

Select a configuration in the server list, open the right-click menu, and choose Set as active server or the equivalent option. Some versions also let you switch configurations by double-clicking. If you are unsure what double-click does, use the right-click menu instead. Then check whether the active configuration shown in the status bar has changed and look for errors such as core startup failures or port conflicts in the logs. v2rayN may not have a separate Connect button; selecting the active server and checking that the core is running are what matter.

Confirm that System Proxy is still set to Set system proxy automatically, then leave the client running. You can minimize it to the system tray, but do not exit the process. If a system firewall prompt appears, verify the program name and installation location before allowing access based on your network environment. Do not disable the entire firewall just to test. If the logs report that a local listener failed to start, quit any other proxy tool and try again. For persistent port conflicts, follow the port conflict troubleshooting guide. Do not end unfamiliar system processes.

v2rayNG: Start the connection and allow VPN access

Tap a configuration in the v2rayNG list and confirm it is marked as current, then tap Connect on the main screen. On first launch, Android displays a VPN connection request. Verify that v2rayNG is the requesting app, then allow it. Return to the client and check the button, notification shade, and logs. If the system reports that another VPN is running, stop that connection first. In most cases, two tools cannot use the same system VPN interface to capture traffic at the same time.

If the connection stops right after starting, check the first specific error in the logs rather than focusing only on the final Stopped message. If it disconnects after running in the background for a while, check whether the system restricts background activity or battery usage, and adjust the relevant settings only for the client that needs to stay connected. For certificate, time, or handshake errors, first correct the device's date and time, then check the subscription status. Disabling certificate verification is not a routine fix.

Step 4: Verify that it works

Open your usual browser and refresh an HTTPS page that should use the proxy under your current routing rules and is known to be available. Then open a familiar page that should connect directly. If both work, the connection and routing are likely working together. A single site failing may be due to the site itself, your account, or regional policies; it does not prove that all connections are broken. A connected icon alone also does not prove that app requests are reaching the proxy.

Check the browser and logs

If your desktop browser has a separate proxy extension, switch it to use system settings so it does not override the system proxy you just configured. If only the browser fails on Android, check whether per-app proxy settings exclude it. Make another request while checking the client logs for a corresponding connection entry or error. Not every log level records every request, so the absence of an entry is not conclusive; also consider the mode, ports, and what happens when you load the page.

If direct pages work but pages that require the proxy do not, check the following in order: the active configuration, whether the desktop system proxy or Android VPN is enabled, and whether the subscription is still valid. If needed, test one different configuration without changing anything else. If that works, the issue is likely with the original configuration or remote service. If all configurations fail, focus first on your local network, client mode, and logs. Change only one thing at a time so you can tell what fixed the problem.

If no pages load, temporarily stop the proxy from capturing traffic and test your regular internet connection. On desktop, clear the system proxy before exiting the client. On Android, tap Stop and confirm that the system VPN indicator disappears. If regular internet access also fails, troubleshoot Wi-Fi, mobile data, or sign-in requirements instead of repeatedly importing the subscription. Once regular access is restored, re-enable the connection by following steps 2 and 3.

Save working settings and disconnect safely

After the first successful test, note the working subscription group, active configuration, and routing mode. When you later add rules, enable TUN, or change per-app settings, repeat the connection test after each change. Do not enable Update subscription through proxy, Global routing, and TUN all at once before testing; that makes the source of any problem harder to identify. When subscription details change, update the existing group. You usually do not need to delete and recreate it every day.

When you are done, clear the system proxy in v2rayN before exiting the client, so your system does not keep pointing to a local port that is no longer listening. In v2rayNG, stop the connection in the app and check whether Android's Always-on VPN or Block connections without VPN setting is enabled. These system policies affect network behavior after you disconnect. Keep the subscription URL on your device; do not leave screenshots containing the full link in a public photo library or shared document.

You have now completed the full setup: adding a subscription, choosing a mode, starting the connection, and verifying access. For everyday questions, start with the FAQ. To understand the differences between system proxy, TUN, DNS, and routing, see the glossary. For persistent timeouts, failed updates, or background disconnects, use Troubleshooting to investigate by symptom.