Import a v2rayN subscriptionand configure the proxy

Step 1: Import a subscription

First, check whether you have a subscription URL or a single share link. A subscription URL retrieves a group of configurations and can be refreshed to sync changes. Content starting with vmess://, vless://, or trojan:// is usually a single share link. They use different import options: don't paste a single link into the subscription URL field just because both can be copied.

v2rayN: Add a group and update the subscription

In the main window, open Subscription Group, then select Subscription Group Settings. Add a group and enter a recognizable name in the remarks field, then paste the full subscription URL into the address field. The remark is for local display only and does not affect the connection. Keep the URL exactly as provided: don't omit trailing parameters or add spaces, line breaks, or punctuation from a chat message.

Save your settings and return to the main window. Open the Subscription Group menu and choose Update all subscriptions. Some versions offer separate options to update through or without a proxy. For a first-time setup, when no working proxy is available yet, try the option to update without a proxy first. If the subscription service requires a specific network connection, follow the provider's instructions. Don't repeatedly choose an update option that depends on a proxy before you're connected.

When the update finishes, check the group you added and confirm that configurations appear in the server list. If the full list has entries but the current group is empty, check that the group filter is set correctly. If the update log reports a download failure, troubleshoot access to the URL first. If the download succeeds but parsing fails, check whether the subscription format is compatible with your client. These errors have different causes and need different fixes.

v2rayNG: Save the URL, then update from the home screen

In v2rayNG, open the sidebar and select Subscription Group Settings. Tap Add to create a group, enter a remark and subscription URL, then save. Return to the home screen and update the subscription from the menu in the upper-right corner. Saving the URL in settings does not automatically retrieve configurations. This step is complete only after the update succeeds and entries appear on the home screen.

If you have a single share link, copy the entire link first. In v2rayN, choose Import share links from clipboard in the main window or press Ctrl + V. In v2rayNG, choose Import from clipboard from the add menu in the upper-right corner. Check that the configuration appears; don't add the same link again as a subscription URL. Configurations imported individually usually aren't refreshed when you update a subscription.

You don't need to edit protocol, transport, or security settings one by one. A valid subscription or share link already includes these parameters. Guessing at changes to the port, transport path, or server name can cause a mismatch. If the list is still empty, see the subscription troubleshooting section in the FAQ. Once the configuration appears, continue to proxy mode settings.

Step 2: Choose a proxy mode

For your first v2rayN setup, choose Auto-configure system proxy, then select a routing preset for everyday use. Leave Enable Tun turned off for now. This keeps troubleshooting simple and makes it easier to tell whether your browser is using the client. System proxy and routing are separate settings: the system proxy determines how apps send connections to the client; routing determines whether those connections go direct or through a proxy outbound.

On desktop, start with Auto-configure system proxy

Find System Proxy in the v2rayN main window or tray menu. Auto-configure system proxy sets the system proxy for apps that follow it. Clear system proxy removes that setting, while Do not change system proxy leaves the current setting as is. For your first setup, choose Auto-configure to avoid leaving the system pointed at another proxy app that is no longer running.

Auto-configuring the system proxy doesn't route every app through the client. Some apps have their own proxy settings, while others connect directly without using the system proxy. Start by testing in a browser that follows the system proxy settings. Once the basic connection works, you can check other apps. If one app behaves differently, don't immediately enable Tun, change ports, and switch cores all at once.

Next, check the routing options. If the interface offers a Bypass mainland China (Whitelist) preset, use it as a starting point for everyday split routing: connections matching the direct-connection rules go direct, while the rest are handled by the preset. The actual behavior depends on the rules and their order; the preset name alone doesn't guarantee how every domain will be routed. Keep the preset for now rather than editing complex rules.

On Android, use the VPN service

v2rayNG typically routes device traffic through the system VPN service, so you don't need to look for the same Auto-configure system proxy option as on desktop. Open the routing options in settings, choose a suitable preset, and return to the home screen. For the initial test, check whether per-app proxy or bypass settings are enabled. Make sure the browser you're testing isn't excluded from the VPN service.

Here, Global typically means that all connections entering the client use a proxy outbound. It does not mean that every configuration in the subscription list connects at once. Nor does it fix expired subscriptions, authentication failures, or unreachable servers. If you switch to Global temporarily to troubleshoot routing, restore your original preset afterward to avoid unexpected traffic routing.

Choosing a mode doesn't necessarily activate a configuration. Next, select an entry and confirm that the client core or VPN service has actually started. A configuration in the list doesn't mean it's handling traffic yet.

Step 3: Select a configuration and connect

Choose a configuration from the group you just imported that your service provider says is available. A name is only a remark, not a guarantee that it works; test results in the list are just a reference. For the initial setup, stick with one configuration and avoid switching servers repeatedly. This makes it easier to track the subscription, entry point, and routing settings.

v2rayN: Check the active server and core status

Select the target configuration in the server list, then choose Set as active server from the right-click menu or use the equivalent option in your version. Check the active indicator and status information at the bottom to confirm that the selected configuration is in use. A single click may only select a row, not activate that server, so check the interface status.

v2rayN typically loads the configuration and starts or restarts the core when you switch active servers. Open the log panel and check for configuration load failures, port binding errors, or core exit messages. If a port is already in use, close other proxy apps listening on the same local port, then restart the client. Don't change multiple settings without understanding how the ports relate.

Check that System Proxy is still set to Auto-configure. A running client core and a correctly configured system proxy are two separate requirements: the core provides the local proxy entry point, while the system proxy tells apps where to find it. If the core is running but the system proxy isn't configured, a regular browser may still connect directly, with no visible change in proxy behavior.

v2rayNG: Allow the system VPN connection request

On the v2rayNG home screen, tap the target configuration and confirm the selection indicator has moved to it. Then tap Connect. The first time you start it, the system will show a VPN connection request. Allow it after confirming it came from the client you just opened. If you deny permission, the client can't route device traffic through the usual VPN mode.

After connecting, check the connection status in the app and confirm the system shows a VPN indicator. If another app on the device is already using the VPN service, you may need to stop that service before connecting in v2rayNG. The system indicator only confirms that the local VPN service is running; it doesn't mean the remote server is reachable. Verify that in the next step.

If the Connect button returns to its stopped state, the core keeps exiting, or the log shows an immediate error, stop here and troubleshoot before continuing. See the FAQ for startup and connection issues. Don't confuse an app showing as started with being able to reach your destination through this configuration. There's no need to change browser settings if the client won't start.

Step 4: Verify the connection

Use a real connection and client logs to check the result. Don't rely only on the Connect button's color or a single latency test. Verify two things: whether the app's connection reaches the client, and whether the client can reach the destination. Check the entry point first, then troubleshoot the remote connection to avoid random changes.

First, confirm the browser is using the client

On desktop, open a browser that follows the system proxy settings and visit a known working site in a new tab. If the browser has a separate proxy extension, disable it temporarily or make sure it isn't overriding the system settings. You can also test with a browser that has no custom proxy settings. Keep v2rayN running and check the logs or connection statistics for activity matching your visit.

On Android, open a new page in a browser that isn't excluded by per-app rules, then check for changes in the v2rayNG logs or statistics. Some pages may be cached, so an old page still on screen doesn't prove a new request was made. If needed, try a new tab or private window. There's no need to clear all browsing data on the device.

The default log level may not record every request, so not seeing a domain isn't enough to prove that traffic missed the client. Check the system proxy status, in-app statistics, and page load together. If you temporarily increase the log level, restore the original setting afterward. Logs may contain the domains you visit, so check them before sharing screenshots.

Then test the destination you want to access through the proxy

Once a basic webpage loads, test a destination that normally requires a proxy. With split-routing presets, some sites may connect directly, so loading a regular site only confirms that basic network access works. A successful connection to the target, along with matching activity in the client, is stronger evidence that the setup is working as intended.

You can use a trusted IP lookup service to check your apparent exit address, but make sure you know which route the lookup request used. If the lookup site is routed directly, seeing your local network's exit address is expected and doesn't mean the proxy is completely down. A location result from one site also can't prove how all app traffic is routed.

If a test succeeds but a webpage won't load, first check whether the browser's traffic reached the client, then check routing and DNS. If some sites work and others don't, note the specific destination and error instead of immediately clearing the subscription. DNS errors, connection timeouts, remote rejections, and certificate errors point to different stages. The original error is more useful than repeatedly clicking Retry.

Troubleshoot in this order

First, confirm the subscription updated successfully, the target configuration is still listed, and the service is active. Next, check that the right configuration is active and that the core or VPN service is still running. Then check whether the desktop system proxy or Android per-app rules are routing the test browser through the client. Check routing and DNS last. Change one setting at a time and revisit the same destination to see what made a difference.

After verification, keep track of the working group, active configuration, and routing preset. There's no need to enable every advanced option. To stop the desktop proxy, clear the system proxy before exiting the client, then make sure the system isn't still pointing to an inactive local proxy. On Android, stop the connection in the app and confirm the VPN service has ended. That way, the next time you open a browser, it won't depend on a client that's no longer running.

Your basic connection is now set up. For subscription maintenance, split routing, Tun, and DNS settings, see the complete beginner-to-advanced guide. If you still can't connect, visit the FAQ and troubleshoot the specific error in the logs. There's no need to repeat the entire installation process.