V2Ray Subscription Import and Connection Steps

Confirm the Subscription Link Is Complete

When copying a subscription link, copy everything from the protocol prefix through the final character. Links usually begin with https:// and may contain a long path or query parameters. Do not remove anything after the question mark or copy an ellipsis shown by a webpage. The safest approach is to use the provider's copy button, then paste directly into the client's subscription URL field rather than through software that may rewrite links.

If the provider supplies a QR code, you can use the scan option in v2rayNG; on desktop, directly pasting the subscription URL is usually easier. A QR code is simply another way to carry the configuration and does not require opening the camera. Whichever import method you use, the final check is whether the main screen displays a node list.

Sync the System Clock

A large error in the system date, time zone, or clock can cause a TLS connection to fail during setup. Open the system date and time settings, enable automatic time, and confirm the time zone is correct. You do not need to change transport settings in the client; update the subscription again first. If the system clock caused the error, the connection can usually recover immediately after synchronization.

Temporarily Close Other Proxy Apps

Running multiple proxy clients on one device can cause local port conflicts or make them overwrite the system proxy settings in turn. During the first setup, exit other similar programs and keep only the current client running. If your browser has a separate proxy extension, temporarily switch it to “follow system settings” or disable it. This ensures the verification results reflect the current configuration rather than another background app.

Using v2rayN on Desktop

After opening v2rayN, find “Subscription Groups” or “Subscription Settings” in the top menu or a subscription-related menu. Wording may vary slightly by version, but the entry will include functions for adding, editing, and updating subscriptions. In the settings window, choose Add and give the group a recognizable note, such as the provider name or intended use. This note is shown only on your device and does not affect the connection.

Paste the complete link into the URL field, confirm that the group is enabled, then save and close the settings window. Saving alone does not create nodes. Return to the subscription menu and choose “Update All Subscriptions,” or update the group you just added. Watch the status area or log window during the update: a successful operation usually reports that the subscription update is complete, followed by several node configurations appearing in the main list.

If the main list is still empty, do not keep clicking Connect. Reopen the subscription settings and check for spaces at either end of the URL, a disabled group, or a truncated link. You can also place the cursor at the end of the address to make sure it contains no line break. A subscription opening in a browser does not guarantee that its response is compatible with the client. If the update reports a format error, return to the provider's page and obtain a subscription URL compatible with V2Ray clients.

Using v2rayNG on Android

Open v2rayNG, expand the side menu, and enter the subscription group settings. Tap Add, enter a note and the subscription URL, and make sure the enable switch is on before saving. Return to the main screen, open the menu again, and update the subscription. Some versions show a brief message at the bottom; after the update, the nodes will appear in the main list.

If you received a QR code for a single configuration, use the scan import option in the upper-right menu. If it is a subscription QR code, save it through the scan option in Subscription Groups. The difference is that a single configuration adds one node, while a subscription group can refresh a batch of nodes at once. For ongoing use, save it as a subscription group so future updates are easier.

If the system asks for camera permission while you are using a clipboard link, go back and choose manual entry instead; this does not affect other connection features. Always update once after pasting: saving the subscription URL and downloading the node data are separate actions. Once the list appears, tap the node you plan to use to make it the current selection.

Understand the Update Result

Node names are usually defined by the subscription provider. Region, multiplier, and route labels are identification details only; the client does not decide that a node is better simply because it appears near the top. For the first test, choose any one configuration. If every node fails, investigate the subscription status, network environment, or configuration compatibility. If only a few nodes fail, the issue is more likely limited to those nodes.

After the subscription updates successfully, stay on the main screen and confirm two things: the list contains at least one configuration, and one of them is selected. Only then move on to proxy mode settings. For a deeper explanation of subscription formats, clipboard imports, and group management, see the detailed subscription import guide.

Rule Mode Works Well for Daily Use

Rule mode directs traffic based on domains, IP addresses, or predefined rules. Common local services and LAN addresses can stay direct, while requests that need a proxy go through the current node. In v2rayN, these settings are usually under the system proxy or routing menu. In v2rayNG, choose a preset rule set in Settings or Routing. Depending on the version, it may be called “Bypass LAN,” “Rules,” or “Route by rules”; the meaning is the same.

For the first run, do not import a large set of custom rules or change domain strategies at the same time. Start with the client's built-in basic rules and refine them only after the connection works. The more rules you add, the more complicated the matching order becomes during troubleshooting. If one website connects directly while another uses the proxy, that may be the expected behavior of Rule mode rather than a fault.

Use Global Mode for a Short Comparison Test

Global mode sends more requests within the proxy's scope through the current node. It is useful as a comparison: if a webpage fails in Rule mode but works immediately in Global mode, the node and basic connection are usually fine, and the issue is likely in routing rules rather than subscription import or core startup.

Global mode does not necessarily capture every program on the device. On desktop, when only the system proxy is enabled, usually only apps that follow system proxy settings will use it; some programs have their own network stack or proxy options. On Android, the capture scope after establishing the system connection depends on both client settings and system mechanisms. If you need to handle more desktop application traffic, investigate TUN mode later rather than adding that variable during the basic test.

Direct Mode Is Not a Connection Test

Direct mode sends requests around the proxy. Use it to temporarily restore ordinary network access or compare behavior with and without the proxy, not to determine whether a node works. If the client reports that it is running while Direct mode is active, the browser's exit address will not change as expected. Before connecting, confirm that the current mode is Rule or Global, not Direct.

Do not close the client immediately after choosing a mode. The next step is to select a specific node and start the connection. Mode and node are separate requirements: the chain is incomplete if the mode is correct but no node is selected, or if a node is selected but the system proxy is not enabled.

Enable the System Proxy in v2rayN

Return to the node list and click the node you want to use. Some versions require a double-click, or let you choose “Set as Active Server” from the context menu. The selection is usually indicated by a highlighted row, status icon, or tray notification. Then open the system proxy menu and choose the option to configure the system proxy automatically, or the enable option associated with Rule mode.

Afterward, check the v2rayN icon in the desktop notification area. A changed icon state shows that the client has switched modes, but the logs contain the more useful details. Open the log window; a normal startup should show configuration loading, a local listener being established, and the core finishing startup. The local address in the log usually looks like 127.0.0.1 followed by a port. It means the client is waiting for application traffic on this device, not that it is the remote node address.

If the log says that a port is already in use, exit other proxy apps, then fully close and restart v2rayN. Do not arbitrarily change every port in the settings to different numbers: the system proxy, HTTP inbound, and SOCKS inbound settings are related. During basic setup, removing conflicting programs is safer than rewriting port assignments.

Start the Connection in v2rayNG

Tap a node in the main list, then tap the connect button in the lower-right corner. The first time you start it, the system shows a connection authorization dialog; approve it so the client can create the system connection. Follow the system prompt once. After returning to v2rayNG, the button and top status should show that it is connected, and a connection indicator should appear in the system status area.

If it stops immediately after you tap Connect, open the log and find the first specific error. Common causes include an invalid subscription configuration, an unreachable server, an incorrect system clock, or a transport restricted by the current network. Do not change settings based only on “connection failed.” Identify the stage: address resolution, TCP connection, TLS handshake, or authentication. Each stage requires a different fix.

Wait a Few Seconds Before Testing

When the client starts, it needs time to load the configuration, initialize routing, and establish required connections. Wait a few seconds after starting it, then open a new browser page. An existing webpage may reuse an old connection, so refreshing the current tab may not show a change. Opening a new tab—or restarting the browser—is more reliable.

On desktop, also check whether the browser follows the system proxy. Major browsers usually read system settings by default, but a separate proxy, command-line launch option, or extension rule can bypass v2rayN. On Android, confirm that v2rayNG remains connected and has not been stopped by a battery-saving policy. Before the basic connection works, do not enable multiple per-app proxy rules at once.

Layer 1: No Persistent Errors in the Log

Open the client log and confirm that the core started successfully and that the same error is not repeating continuously. An occasional retry does not necessarily mean the whole connection failed; network requests can reconnect. If the same timeout, refusal, or resolution error appears every time you open a webpage, the chain still has a problem.

You do not need to understand every log line. Start with the newest error that appears most often, then look for terms related to DNS resolution, connection timeouts, certificates, authentication, or routing. Classifying the error before acting is more effective than replacing every setting. For common error meanings and corresponding checks, see the FAQ troubleshooting categories.

Layer 2: New Webpages Open Normally

Open a new browser tab and visit one website that normally works directly and another that should use the proxy. In Rule mode, both should open, showing that basic routing and the proxy chain are working. If direct sites work but the proxied site times out, focus on the node and subscription status. If Global mode works while Rule mode does not, focus on routing rules.

If the browser cannot open any page, first turn off the system proxy and confirm that the ordinary network works, then enable the client again. If access still fails with the proxy off, the issue is probably not V2Ray configuration; restore the local network first. If access returns when the proxy is off but everything fails after re-enabling it, check the local listener, port conflicts, and whether the system proxy address matches.

Layer 3: The Exit Address Matches Expectations

Before connecting, search the web for “current IP” and note the displayed network exit. After connecting, search again in a new tab. If the exit address changes and its region roughly matches the selected node, browser traffic is passing through the proxy. In Rule mode, the lookup service may be routed directly, so if the address does not change, briefly switch to Global mode for a comparison, then switch back to Rule mode.

A changed exit address proves only that the current browser request went through the proxy; it does not mean every app on the device uses the same path. If a separate program still cannot connect, check whether it supports the system proxy or has its own HTTP or SOCKS settings. To capture more desktop apps that do not follow system proxy settings, see the TUN configuration in the complete guide.

Save the Working Configuration

Once the connection works, do not immediately change DNS, ports, or routing. Note the subscription group, node, proxy mode, and system proxy state in use. When you later add rules or change the operating mode, you can return to this verified baseline for comparison if something goes wrong.

Subscription contents can change when the provider updates them. When the nodes change, use “Update Subscription” instead of deleting and re-importing the group. If the current node disappears after an update, choose another configuration from the new list. Edit the group URL only when the subscription address itself has changed or expired.