v2rayN and v2rayNG
Subscription Import and Connection Setup

Step 1 of 4

Import a subscription and update configurations

It is normal for the server list to be empty the first time you open v2rayN. Copy the subscription URL from your provider, then open Subscription Group Settings from the Subscription Groups menu at the top. Click Add, enter a recognizable name for the group, paste the full URL into the address field, save, and return to the main window. The name only helps identify the source; it does not change connection settings. Leave other options at their defaults unless you know what they do.

After saving a group in v2rayN, update the subscription to load configurations into the server list. If no proxy is available yet, choose the option to update without using a proxy from the Subscription Groups menu, then update the group you just added. Wait for the process to finish, then select that group or All and confirm server entries appear. An update can take a while, so avoid clicking repeatedly. If the list is still empty, check the update message first.

In v2rayNG, the equivalent option is usually Subscription Group Settings in the sidebar. Tap Add, enter a name and subscription URL, save, and return to the configuration list. Then choose Update Subscription from the menu in the upper-right corner. Some versions put this option in a group-specific menu; either way, it fetches the contents of the saved URL. After a successful update, selectable configurations should appear in the main list, not just a group name in settings.

A subscription URL and a single share link are different inputs. A subscription URL usually retrieves multiple configurations and can be refreshed later. Content beginning with vmess://, vless://, trojan://, or ss:// is usually a single connection configuration. For a single link, use Import share link from clipboard in v2rayN, or Import from clipboard in the v2rayNG add menu. Do not use a web login page URL as a subscription URL, and do not combine multiple lines into one before pasting.

If a subscription update fails, first check that the URL has no extra spaces, line breaks, or missing characters, then check its validity period and your provider’s instructions. If you see a login page, an unsupported format, or an authorization error, return to the source and copy the subscription format for your client instead of repeatedly reinstalling it. If configurations appear but some fields are not recognized, keep the warning and consult the glossary entry on subscriptions and configurations before deciding whether to change the export format.

After updating v2rayN or v2rayNG, do not connect just yet. Check that the configuration names, protocol types, and source descriptions look reasonable; there is no need to edit addresses, ports, or encryption settings manually. A subscription update may overwrite those fields, and arbitrary changes make later troubleshooting harder. Next, choose how traffic enters the client and how it is routed.

Step 2 of 4

Choose a proxy mode and routing preset

In v2rayN, the system proxy and routing are separate settings. The system proxy tells supported apps to send requests to the local proxy; routing then decides whether those requests connect directly or go through a remote server. For a first setup focused on browser access, start with the system proxy; you do not need to enable TUN as well. This keeps the traffic path simple and makes it easier to tell whether a problem is caused by the client, the app, or routing.

The System Proxy menu at the bottom of the v2rayN main window usually includes options such as Set system proxy automatically and Clear system proxy. Choose Set system proxy automatically, then select Bypass mainland China or an equivalent preset from the adjacent routing menu. Note the preset name; after connecting, check its status again. Depending on the version, the label may be longer, such as Bypass LAN and mainland China addresses. Follow the rule description shown in your client.

In a routing preset, Bypass means traffic matching specified addresses is sent directly, while other traffic follows the preset’s rules. Global usually means that most traffic entering the client uses the proxy. Global routing does not automatically send traffic from every app through the client, nor does it enable the system proxy. For everyday browsing, start with a bypass preset as a baseline. Test other routing modes only when needed, rather than adding custom rules during your first setup.

For a first-time setup, v2rayNG can use VPN mode, which lets Android route app traffic through a virtual network interface. Open Settings in the sidebar, make sure a proxy-only connection mode is not selected, then find the routing settings and choose the option to bypass LAN and mainland China addresses. Some versions show modes such as VPN or proxy-only, while others use VPN mode by default. Check the current interface description instead of looking for a specific switch.

If per-app proxying is enabled in v2rayNG, make sure the browser you use for testing is included in the apps being routed. For the initial setup, avoid complex app allowlists or exclusion lists until the connection is verified. Proxy-only mode generally provides a local proxy endpoint that apps must configure themselves. It is not the recommended starting point for this guide, and the presence or absence of a system VPN indicator does not show whether proxy-only mode is working.

After choosing a mode in v2rayN or v2rayNG, the subscription list is still just a set of available configurations; it does not mean one is active. Next, select an active configuration and check the startup status shown by the client or system. Keep routing unchanged for now so you do not mix configuration changes with mode changes in the same test.

Step 3 of 4

Select a configuration and connect

In v2rayN, select a configuration in the server list, then choose Set as active server from the context menu, or use the equivalent option in your version. A highlighted selection does not necessarily mean the server is active; check for an active marker or a status bar message. The client usually reloads the core configuration when you switch servers. Wait a moment, then confirm the system proxy and routing mode at the bottom are still set as expected.

Connecting with v2rayN on desktop may not involve a separate Connect button. For this guide, the core must be running, an active configuration must be loaded, and the system proxy must be enabled. Open the log or information panel and check for errors such as configuration parsing failures, a port already in use, or the core failing to start. If the log shows a startup failure, address it before testing in a browser.

In v2rayNG, return to the configuration list, tap the entry you want to use, and confirm that the active marker changes. Then tap Connect. The first time you start the VPN, Android displays a connection request explaining that the app can handle network traffic through the VPN interface. Check the app name, read the prompt, and approve it. If you cancel, the client cannot establish the VPN connection; tap Connect again to request permission.

After v2rayNG starts, check both the client and system status. Android usually shows a VPN indicator or notification, and the Connect button changes to Stop. Notifications vary by device, so their persistence alone does not determine whether the connection is active. If the client immediately returns to a disconnected state, check its logs for a configuration load failure, missing permission, or another VPN using the connection slot.

Built-in connection tests in v2rayN and v2rayNG can provide an initial clue, but the result only reflects that test method and target. A failed test for one configuration does not necessarily mean all access will fail; a successful test does not guarantee that a specific site or app is using the proxy. Do not keep switching configurations based on a single test. Keep the current entry and use the next step to verify the complete path with real traffic.

If v2rayNG repeatedly disconnects after the screen locks, check Android battery management and background activity permissions after basic verification, rather than changing every power-saving setting before connecting. If v2rayN reports a port conflict, close other proxy programs and restart the core as prompted. For help diagnosing other errors, visit the Help Center. Before sharing logs, remove subscription URLs, identifiers, and other access credentials.

Step 4 of 4

Verify access and traffic routing

When v2rayN or v2rayNG shows that it is running, that only confirms the local startup process has reached a particular stage. First open a site that normally works and should connect directly, then a site that should use the proxy under your current routing rules. If both load, the basic access path works. However, a page loading does not prove that traffic is leaving through the expected route; also check an IP lookup or the logs.

When testing v2rayN, use a browser that follows the system proxy and temporarily disable browser extensions or settings that configure a separate proxy. A desktop app that ignores the system proxy may behave differently; that does not necessarily mean routing is broken. When testing v2rayNG, make sure the browser is not excluded by per-app rules and the system VPN is still active. After switching networks, repeat a basic access test.

Use a reputable IP lookup page to check your traffic’s public exit address. First, note your current public IP with the connection stopped. Then connect and visit an IP lookup target that should use the proxy; compare the result with your provider’s instructions. The lookup page is also subject to routing rules: if it is set to connect directly, seeing your local IP is expected. If the address does not change, check the route for that target before concluding that the whole connection has failed.

You can also use client logs to check routing. Set the log level to show requests or routing information, make a new web request, and look for the relevant domain and outbound connection. If needed, temporarily increase the log detail as described for your version, then restore the default. Existing connections may reuse an old route, so make a new request after changing routing. A domain not appearing in the logs does not necessarily mean traffic failed to reach the client; this depends on the log level and how traffic is resolved.

When troubleshooting v2rayN or v2rayNG, change one variable at a time. Keep the same network, configuration, and routing mode, and note which targets work. Then switch to another valid configuration and repeat the test. If only certain sites fail, check the target and routing rules first; if all access fails, check the basic network and core status. DNS, transport security, and protocol compatibility are covered in more advanced troubleshooting; continue with the protocol deep dive.

In v2rayN, finish by practicing how to restore your settings: choose Clear system proxy from the system proxy menu, then exit the client and confirm ordinary websites still load. This prevents apps from trying to connect to a local proxy port after the client has stopped. In v2rayNG, tap Stop, confirm the system VPN has ended, and test basic access. If you enabled always-on VPN or blocked connections without a VPN, check that these system settings still match your needs.

After completing these checks in v2rayN or v2rayNG, re-enable the configuration you verified and note the client, active configuration, and routing preset. Use this baseline for comparison after subscription updates, network changes, or routing adjustments. You do not need to learn every protocol setting to get started. Look up unfamiliar terms in the glossary, and visit the Help Center for specific setup questions.