Before start
Before You Start: Client, Subscription URL, and System Time
Before you begin, have an installed client and a working V2Ray subscription link ready. A subscription link is usually a complete URL beginning with https:// and may include parameters used to identify the subscription. When copying it, select everything from the beginning to the end. Do not remove question marks, equals signs, or trailing characters, and do not copy explanatory punctuation from the page. A subscription URL is the client’s entry point for retrieving server profiles, so save it only on devices you control and in trusted clients.
Also check that the device date, time, and time zone are correct. Some protocols use time information during connection setup; if the system clock is far off, the subscription may update while every server still fails to connect. Enable automatic date and time first, then continue. If the client is not installed yet, visit the download page and choose the version for your platform. Installation and permission issues are covered in Frequently Asked Questions.
For the first setup, do not run multiple similar proxy clients at the same time. Programs that simultaneously change the system proxy, occupy local ports, or take over network traffic make problems harder to isolate. Exit other proxy tools and keep only the v2rayN or v2rayNG client you are configuring. Decide whether to keep the other tools after the connection has been verified.
Subscription
Import a Subscription: Save the URL and Update the Server List
In v2rayN, open the “Subscription Groups” menu and enter the subscription group settings. Create a subscription entry, enter an easy-to-recognize name in the remarks field, paste the complete subscription link into the URL field, and save it. The remark is only for local identification and does not change the subscription; a short name is enough if you have only one. Saving the settings does not retrieve server profiles yet. Return to the “Subscription Groups” menu and choose Update Current Subscription or Update All Subscriptions.
Watch the status area or log panel at the bottom of the main window during the update. Normally, several profile rows appear after completion, with fields such as an alias, address, port, and protocol type. The number of servers depends on the subscription and is not a fixed success criterion. Proceed when the list is no longer empty and there are no repeated subscription-parsing or network-request errors.
In v2rayNG on Android, open Subscription Group Settings from the side menu, tap the add button, enter a remark, paste the subscription URL, save it, and return to the profile page. Then open the top-right menu and update the subscription. When the update finishes, the profile list is regenerated from the subscription. If old content remains, confirm the selected subscription group and run the update again. Switching groups also changes the server list shown.
If no servers appear after the update, do not repeatedly start connections. Return to the subscription settings and check whether the URL was truncated, especially its trailing parameters. Make sure there are no leading or trailing spaces or line breaks, and verify that the current network can reach the subscription URL. If the subscription format is invalid, obtain a new link intended for V2Ray clients instead of treating a single profile page URL as a subscription URL.
Single Share Links vs. Subscription Links
A subscription link retrieves a set of profiles at once and can be synchronized with server-side changes through Update Subscription. A single share link contains one profile and usually requires an entry such as Import from Clipboard. Both can create server records, but they are maintained differently. If you have a subscription URL, use the subscription group feature instead of importing profiles one by one. For link structure and subscription updates, continue with the complete guide from beginner to advanced.
Proxy and routing
Choose a Proxy Mode: System Proxy vs. Traffic Routing
Once the server list is ready, distinguish two easily confused concepts. The system proxy determines whether browsers and other programs that follow system settings hand traffic to the client. The routing mode determines whether traffic inside the client leaves through direct, proxy, or block. The first controls whether traffic is intercepted; the second controls how it is routed afterward. Selecting a server without enabling the system proxy is the most common first-time omission.
In v2rayN, find System Proxy in the main window or system tray menu. For a first setup, choose Automatic System Proxy Configuration. The client then writes the local proxy address to the system settings, and the status bar usually shows text such as “System Proxy: Automatic System Proxy Configuration.” Do not enter a different proxy port manually in system settings at the same time, or the browser may continue using the old port.
Next, choose a routing mode. For everyday browsing, start with a preset such as Bypass Mainland China. It typically sends common direct traffic through direct and other matching traffic through proxy. To check whether all proxyable traffic can pass through the current server, temporarily switch to global mode, but do not treat it as a permanent fix for every problem. Rules are matched in order; after an earlier rule matches, later rules are usually not checked. Place more specific custom rules accordingly.
After starting, v2rayNG on Android takes over traffic through the system network connection, so there is no need to copy the desktop system proxy workflow. For the first test, keep the default routing settings, confirm that the basic connection works, and then adjust preset rules or per-app proxying. If per-app proxying is enabled, check that the target browser is included. If the setting is configured to bypass selected apps, those apps connect directly—do not reverse the selection logic.
PAC Mode vs. Automatic System Proxy Configuration
PAC mode relies on a rule script to decide which addresses use the proxy, making it suitable when you understand PAC matching and have a specific need. Automatic system proxy configuration is more direct, and the client’s own routing rules make matched results easier to inspect. For this quick setup, use automatic system proxy configuration. For the boundaries between system proxy, PAC, TUN, and routing rules, see the beginner-to-advanced guide.
Connect
Connect: Activate a Server and Check Its Status
After setting the proxy and routing modes, return to the server list and choose a profile. In v2rayN, select the target row and use the client’s Set as Active Server action. Common methods include double-clicking the row, pressing Enter, or choosing Set as Active Server from the context menu. The active item usually has a different font, color marker, or status indicator. A server appearing in the list does not mean it is in use; confirm that the active profile is the one you selected.
Check the status bar at the bottom of the window. The system proxy status should match your previous choice, and the routing status should show the selected preset. After the core starts, the log area usually reports that the configuration was loaded and local listening ports were created. If errors are not repeating and the client does not exit immediately, the local proxy process is running. You can leave the window in the background; there is no need to keep clicking Start.
In v2rayNG, tap a profile in the list to make it current, then tap the circular connect button at the bottom. On the first launch, Android displays a network-connection permission dialog. Confirm it, then look for the connection indicator in the status bar and a changed button state. If it immediately returns to disconnected, open the logs instead of switching repeatedly between profiles. Record the first clear error; it usually makes it easier to tell whether the issue involves the profile, time, network, or permissions.
A server name is only for identification. It does not indicate availability, and speed cannot be judged from the name alone. Start with the default profile supplied by the subscription. If it fails, compare it with another server from the same subscription: if only one profile fails, the corresponding server is more likely to be the problem; if all profiles fail in the same way, check the system time, subscription expiry, current network, and client permissions first.
Why You Should Not Change Many Settings at Once
Protocol parameters, transport, DNS resolution, routing, and system interception can all affect the final result. Changing them all during first-time setup makes failures difficult to diagnose. Keep imported subscription profiles unchanged and modify only the active server, system proxy, and preset route as needed. After the basic path works, adjust DNS, TUN, or custom rules according to your needs.
Verification
Verify That It Works: Cross-Check the Browser, Status Bar, and Logs
After starting the connection, fully close the test browser and reopen it. This reduces the effect of old connections, cached proxy settings, and background processes. Visit a page that normally opens to confirm that basic network access is intact, then visit the target page that should use the current proxy path. If both open as expected, system interception, routing, and the server connection are basically working.
Do not judge all traffic by the network address shown on one page. With a split route such as Bypass Mainland China, different domains may match direct and proxy respectively; different results are expected under the routing rules. A more reliable method is to watch the client logs at the same time: refreshing the target page should create new connection entries showing the target domain or address being sent through the appropriate outbound.
If the client reports that it is running but the browser shows no change, first check on desktop that the system proxy is still set to Automatic System Proxy Configuration. Then confirm that the browser has no separately configured fixed proxy or proxy extension. Some browsers retain their own network settings and ignore the system setting. On Android, check that the system connection indicator remains visible and that per-app proxying has not excluded the current browser.
If ordinary pages open but some target pages fail, temporarily switch the preset route on the same server for comparison. If the issue clears, inspect domain rules, IP rules, or DNS policy. If it persists, try another server from the subscription. Connection timeouts may indicate that the current network cannot reach the server. Authentication or handshake errors call for another subscription update rather than continued use of an outdated profile.
After verification, restore the routing mode you need for everyday use. On desktop, you can keep automatic system proxy configuration and choose Clear System Proxy from the tray when you are finished. On Android, tap the connect button to disconnect. Force-quitting the desktop client without clearing the system proxy may leave an invalid local proxy address in the system, causing the browser to lose network access unexpectedly.
What to Record When a Connection Error Appears
Record the client name, time of occurrence, current proxy and routing modes, whether every server fails, and the error category in the logs. Before sharing logs, remove subscription URLs, server credentials, and other sensitive fields. Common fixes are collected on the Frequently Asked Questions page; longer topics such as DNS, routing priority, and TUN are covered in the systematic guide.
Daily routine
Everyday Use: Update Subscriptions, Switch Servers, and Exit Properly
After the first setup, everyday use can be reduced to three actions: update the subscription regularly, switch the active server when needed, and disconnect properly when finished. When subscription content changes, update it from the subscription group menu instead of deleting the client and importing it again. The list is regenerated from the current subscription, so expired or replaced profiles may disappear; this is normal synchronization.
When switching servers, set the new profile as active first, then reopen the page you want to test. In most cases, there is no need to reimport the subscription or change the system proxy mode. If the old connection remains active, close and reopen the browser or wait for the existing connection to end. Frequently changing routing, DNS, and local ports increases troubleshooting effort, so keep the basic settings stable during normal use.
When you are done on desktop, choose Clear System Proxy first, confirm that the status bar has changed, and then exit the client. Other programs will return to direct connections. On Android, tap the connect button and confirm that the system connection indicator disappears. If the browser cannot connect after a reboot, check the desktop system proxy settings first for a leftover configuration pointing to a local port.
At this point, the four essential stages—subscription import, mode selection, connection, and verification—are complete. For stable everyday use, keep the subscription updated regularly. To understand the Xray core, protocol transport, DNS, routing-rule order, or TUN scope, continue by topic in the complete guide from beginner to advanced; there is no need to configure every advanced option during the first setup.