Step 01 Subscription group
Import a subscription
First, make sure you have a subscription link. It’s usually a full URL provided by your service, which the client uses to fetch a list of servers. Links starting with vmess:// or vless:// are usually single-server share links. Import those from the clipboard instead of entering them in the subscription URL field. A QR code may contain different kinds of data, too; if you’re not sure, check the provider’s instructions. Haven’t installed a client yet? Choose an installer on the Get a Client page, then return here.
v2rayN: Add the URL, then update
Open “Subscription Groups” in the main window, then choose “Subscription Group Settings” or an add option in the same menu. Create a group, paste the full URL into the subscription URL field, enter a name you’ll recognize, and save. Back in the main window, select the group and choose Update from the “Subscription Groups” menu. If there’s an option such as “Update Current Subscription,” update only the group you just added the first time. That makes it easier to tell which group worked and where an error occurred. Seeing the group name after saving only confirms that the URL was added. Servers appearing in the list after an update confirms that the content was fetched and parsed.
v2rayNG: Enter the URL in group settings
Open the side menu from the main screen and go to “Subscription Group Settings,” then tap the plus button in the upper-right corner. Enter a name and the subscription URL, tap Save, and return to the main screen. Choose “Update Subscription” from the upper-right menu. If the list has a group filter, select the group you just added to check the results. “Import from Clipboard” on the main screen is for importing a single server. For a subscription URL, save it in group settings first so you can update it from the same place later.
If the list is still empty after updating, check for spaces at either end of the URL and make sure you copied everything, including any parameters after the question mark. Then check that your current network can reach the subscription URL. If the client reports a parsing error, make sure the provider gave you a subscription format the client supports, not a login or management page. Subscription URLs may contain personal access tokens, so don’t post the full URL in public forums. Once the list contains servers, move on to the next step; there’s no need to keep updating the subscription just to test the connection.
Step 02 Traffic entry
Choose a proxy mode
Decide which apps should use the client first, then choose how their traffic will enter it. On desktop, “System Proxy” and “TUN Mode” control how traffic enters; routing rules determine where it goes afterward. If an app doesn’t use the system proxy, switching to global routing won’t make it start doing so. For your first test, leave your existing routing settings in place and connect one app whose response is easy to check. Adjust rules later if needed.
v2rayN: Start with the system proxy
Find “System Proxy” at the bottom of the main window or in the tray menu, then choose “Automatically Configure System Proxy.” This points the system proxy to the client’s local entry point, allowing browsers and apps that use the system proxy to connect through it. “Do Not Change System Proxy” keeps the current system settings; it does not turn the proxy on. “Clear System Proxy” removes the current system proxy settings, but won’t disconnect apps that have their own proxy configured. If your device already has proxy settings required for work or school, note them down before making changes.
Leave “TUN Mode” off for your first connection. If the browser test works but another app doesn’t use the system proxy, first check whether that app has its own proxy address and port settings. If you need to route that app’s traffic through the client, learn about TUN permissions and routing requirements separately; don’t change the entry point and server at the same time. For an explanation of system proxies, TUN, and routing, see the glossary. For platform-specific permissions and settings, see the all-platform guide.
v2rayNG: Start with VPN mode
For your first test on Android, use the client’s VPN mode, which lets the system send eligible traffic through the client. If the settings include a run mode, make sure it isn’t set to local proxy only. If you see a “Per-app proxy” option, leave the app list unchanged for your first test. If you’ve already set up an app list, note the current settings and check that your browser and target app aren’t excluded. If another VPN is running on your phone, check whether it can be paused. Don’t disable it without permission if it’s required for work or device management.
Step 03 Active server
Connect to a server
Return to the subscription group you just updated and pick one server for a complete test. An update confirms that the client fetched the configuration; it doesn’t mean every server in the list is available. If you have recent connection test results, start with a server that worked. Otherwise, just choose one. Note the group and server names so you can tell what changed if you switch servers later.
v2rayN: Set the active server
Right-click the selected server in the list and choose a command such as “Set as Active Server.” Some versions also let you switch servers by double-clicking. Make sure the active indicator is on the server you chose, then set “System Proxy” to “Automatically Configure System Proxy” as described in the previous step. You usually don’t need to look for a separate Connect button: the active server tells the core which configuration to use, while the system proxy determines whether apps that follow that setting send requests to the client. After switching, check the main window’s logs for core startup failures or messages that a local port is already in use. If there’s a port conflict, first check whether another copy of the client is running. Don’t change the subscription as your first fix.
v2rayNG: Connect and approve the system request
Tap the server you want and make sure the selection indicator moves to it, then tap the Connect button in the lower-right corner. The first time you use VPN mode, the system will show a connection request. Make sure it was just initiated by v2rayNG, then allow it. If you cancel or don’t approve the request, the server may still appear selected, but the system won’t establish a VPN connection. A change in the button state, or a VPN icon or notification from the system, means you can start testing. If the button quickly returns to the disconnected state, check your notifications and client logs, then see whether another app is using the VPN.
At this point, the client should report no startup errors. On desktop, you should see an active server and the expected system proxy status; on Android, the VPN should be connected. These signs confirm that the local entry point is ready, but don’t prove that the remote server is reachable or that a particular app is using it.
Step 04 Real-world requests
Check that it works
Start with a clean browser test. Reopen your browser, visit a site you’re allowed to test, and load something that actually requires a network request, such as a frequently updated page. Don’t rely on an already-open tab or cached content. Once the browser test works, restart the app you actually want to use and repeat a clearly network-dependent action. Some desktop apps read the system proxy only at startup, so an app that stays open may keep using the old settings. On Android, if only one app fails, check the per-app list before importing the subscription again.
A page loading doesn’t necessarily mean its request went through the proxy; routing rules may send that site directly. If your client provides connection logs, check the entries at the time you make a request. Look for whether the request never reached the client, was routed directly by a rule, or attempted to connect through the selected server. Don’t treat a single server latency test as a test of your target app: they may request different addresses and use different routes.
Browser works, but other apps don’t
Keep the server you’ve already verified. On desktop, check whether the target app has its own proxy settings or is still using an old port. On Android, check whether the app was excluded in the per-app list. If only certain sites behave differently, check where the current routing rules send them instead of resetting all your rules for one site. Change one setting at a time and repeat the same action so you can tell whether the difference comes from the proxy entry point, app settings, or routing.
Connected, but requests still fail
First check the connection status and local entry point. Then figure out whether the request fails before it reaches the client or encounters a timeout or connection error after reaching it. If requests are reaching the client but the current server keeps failing, leave the proxy mode and routing settings as they are. Switch to another server in the same group and test the same site again. If the other server works, the issue is more likely with the original server or the network path to it. If several servers behave the same way, use the all-platform guide to check ports, permissions, and network settings. When sharing troubleshooting details, include the error text and what stage it occurred at, but hide your subscription URL and connection credentials.