First Connection · 4 Steps

V2Ray Quick Start

Update your subscription to get a list of available nodes, choose a mode, connect, then confirm it works with a real browser request.

Before you start, get a working subscription URL and make sure your browser can open websites on your current network. Need to install a client? Choose a package on the client downloads page.

01 Import a Subscription

Import a Subscription and Update the Node List

A subscription URL is the address a client uses to retrieve a list of configurations. Each entry in the list is a node, with the server and protocol settings needed to connect. Subscription groups help organize configurations by source: saving a group stores its URL, while updating it downloads the list. For your first setup, add just one group so it's easier to identify where the nodes came from.

v2rayN on Desktop: Add a Group and Update It

Open the main window, find Subscription Groups and its settings in the menu, then add a group. Enter a recognizable name and paste the full subscription URL into the address field, then save. Back in the main window, select the new group and use the subscription menu to update the current group. Menu names vary slightly by version; make sure you're updating the group you just added, not another one.

Some versions offer separate options to update through or without the proxy. If you don't have an active connection yet and the subscription URL is reachable on your current network, choose the option to update without the proxy. When the update finishes, return to the node list and check whether the group now contains entries. If the group name appears but the list is still empty, you can't move on to connecting yet.

v2rayNG on Android: Update Subscriptions and Return to the List

Open the side menu, go to Subscription Group Settings, and tap Add to create a group. Enter a name and subscription URL, save, then return to the node list. Open the menu in the top-right corner and select Update subscription or the equivalent option. Whether the menu updates the current group or all groups depends on the version; if you can choose a group, select the one you just created.

When the update finishes, switch to the new group and check that at least one node appears in the list. If the group has a name but no entries, first make sure you've selected the right group and cleared any filters. Then check that the URL wasn't truncated, split by a line break, or replaced with an account page URL. Subscription URLs may contain access credentials, so don't post them in public forums when troubleshooting.

This step is complete once nodes appear in the list. If an update fails, first work out whether the URL couldn't be reached or the client couldn't parse the content it retrieved. Repeatedly clicking Connect won't help diagnose either issue. If the error message isn't clear, see the subscription update section in Beginner Q&A.

02 Proxy Mode

Choose a Proxy Mode and Traffic Scope

For your first setup, keep the default routing rules and limit testing to your browser. Two settings are easy to confuse: the system proxy or VPN service determines how requests reach the client; routing rules determine whether requests that reach it go through a node, connect directly, or get blocked. So even when the browser sends a request to the client, the website may not be using a proxy node.

v2rayN on Desktop: Find the System Proxy Setting

Find the system proxy option in the main window's status bar or system tray menu, but don't enable it just yet. Use a browser that reads the system proxy settings for testing. A browser extension with its own proxy settings, or a browser launched with a dedicated profile, may bypass the system settings. For your first test, use a browser without separate proxy settings so you don't have to troubleshoot multiple configurations at once.

Next, check the routing configuration selected in the client. If there's a default ruleset, leave it in place. Rule-based routing typically sends traffic direct or through a proxy based on the destination. Some versions offer a global proxy mode, which usually applies to traffic already sent to the client; it doesn't mean the client takes over every app on your device. Don't enable another traffic-capture method such as TUN for your first test, so you can tell how the request reached the client.

v2rayNG on Android: Start with VPN Mode

Open Settings from the side menu and check the current service mode. If you can choose between VPN and proxy-only mode, select VPN. Android's VPN service lets the app handle network requests; it's not the protocol used by a node in your subscription. If you've configured per-app proxying, make sure the browser you're testing is included. If not, keep the default scope for your first connection.

After choosing how traffic is handled, return to the node list. You don't need to change DNS (the settings that map domain names to addresses) or edit individual rules for your first test. See the glossary for routing terms. If the default rules work for everyday use, explore Advanced Setup when you need per-app routing or more specific rules.

03 Connect to a Node

Select a Node and Connect

Return to the group you just updated and choose one node to test. A group can contain several configurations, but selecting a row doesn't always make that node active. Check which node the client shows as active and whether traffic handling is enabled. Note the selected node's name so you can tell whether later changes came from the node or a setting.

v2rayN on Desktop: Set the Active Node, Then Enable the System Proxy

Find the node you want in the list, right-click it, and choose the option to set it as the active server. Some versions also let you double-click to switch; check the name shown in the status bar or active indicator. Then open the system proxy menu you found earlier and select Set system proxy to auto-configure, or the equivalent option. Check that the status changes. A blue highlighted row alone isn't enough; confirm both the active node name and proxy status before moving on.

If an error appears as soon as you enable it, check the first specific error in the main window or logs. For example, if a local port is already in use, check whether another proxy client is running or the same client was started twice. Find the source of the conflict before retrying; that's more reliable than changing ports at random.

v2rayNG on Android: Start the Service and Approve the System Prompt

Tap the node you chose in the list and make sure it's marked as selected, then tap Connect at the bottom of the screen. The first time you start it, Android usually shows a system connection prompt. Check that it names the current client before approving. Return to the client and wait for the Connect button to show that it's running, or check the system notifications for the VPN service.

If the button immediately returns to its original state, check the client logs or messages for a reason. You can also check system settings to see whether another VPN service is running. If your device is managed by your organization and you can't grant permission, don't keep trying to change system permissions. Once the service starts reliably, continue to the next step. A status icon shows only that the service is running, not that a browser request successfully used a node.

04 Test the Connection

Check Your Connection in the Browser and Logs

In the browser you prepared, open a public website that already works on your current network. To avoid mistaking cached content for a successful connection, try a page on that site you haven't visited before. If the client logs show connections, check the timestamp and destination domain; check the outbound tag too if one is shown. An outbound tag names the path a connection takes out of the client. Direct connections and traffic sent through a node usually show different tags.

The Page Loads: Check Which Route It Took

A page loading successfully only means the request got a response. If the logs explicitly show a direct connection, the request reached the client but didn't use a node; that may be what the routing rules are meant to do. To test the proxy route, try a public destination that should use the proxy under your current rules, then confirm the matching log entry shows proxy outbound. Don't rely on a system icon or the page loading alone as proof. If the client doesn't show outbound details, you can also run its built-in connection test, but that doesn't replace checking the browser's route.

The Page Won't Load: Check Whether the Request Reached the Client

If there's no matching log entry, first make sure the current log view shows connections. Then check whether the browser uses the system proxy or is excluded by Android's per-app settings. If you find a matching entry with a timeout or connection error, leave the proxy mode and routing settings unchanged. Try another node in the same group, then open the same address in the same browser. This makes it easier to tell whether the problem is specific to a node.

If several nodes show the same error, disconnect the client and try the same page that normally works to check whether your network is still online. If regular browsing also fails, restore your network connection first. If it works again after disconnecting, note where the connection failed and the type of error in the logs, then troubleshoot by symptom in Beginner Q&A. When sharing diagnostic details, include the error text only—never the full subscription URL or node configuration.

After testing, you can keep using the configuration that works. When you're done, turn off or clear the system proxy setting in v2rayN; restore its previous value if you had a separate proxy configuration. In v2rayNG, tap Connect again to stop the service. Next time, just select a node and connect. If your provider updates the nodes, refresh the relevant subscription group; there's no need to import the URL again.