First connection
V2Ray Quick Start
From subscription URL to your first real request. With a client ready and a subscription URL on hand, follow the steps to import it, choose a mode, connect, and verify.
Need to install a client first? Download a client. This guide assumes the client opens, your network is working, and you have a valid subscription URL.
Import a subscription
A subscription URL lets your client retrieve a list of servers. Saving the URL and loading the servers are separate steps: saving creates a subscription group, and the servers appear only after an update succeeds. Before you start, copy the full URL from your provider and check for extra spaces, line breaks, or punctuation at either end. The URL may contain credentials that grant access to your subscription. Don’t share it in screenshots, public posts, or online conversion tools.
Add a group in v2rayN
Open the main window, find “Subscription Group,” then open “Subscription Group Settings.” Click Add, enter a recognizable alias, paste the URL into the subscription address field, and save. Back in the main window, switch to the new group, then use the Subscription menu to update it. If the menu offers “Update through proxy” and “Update without proxy” and you don’t yet have a working proxy connection, try updating without a proxy first.
Wait for the update to finish, then check the list instead of repeatedly clicking Refresh. If you have multiple subscriptions or manually added configurations, make sure the list is filtered to the group you just created. Server entries with names indicate that the client has read and recognized at least some of the configuration. You don’t need to test every server or switch cores yet; just confirm that you can select an entry.
Save and update in v2rayNG
Open the menu in the upper-left corner of the main screen and select “Subscription Group Settings.” Tap Add, enter a remark and subscription URL, then save. Return to the server list and select “Update subscription” from the upper-right menu. If your version supports filtering by group, switch to the new group to check the results. If you end up on the manual configuration screen, go back to Subscription Group Settings. Don’t paste the entire subscription URL into a single server’s address field.
If your provider gave you a server share link rather than a subscription URL, use the share-link import option on the main screen, such as importing from the clipboard. This creates a single configuration entry, not a group of servers you can update. If the provider lists formats for multiple clients, copy the URL specifically intended for your client rather than guessing from its file extension.
If the list is still empty after an update, check the client’s message first. A connection timeout means you should check whether your current network can reach the subscription URL. A parsing error or a message that no usable configuration was found calls for checking the format and whether the URL has expired. A URL opening in your browser doesn’t guarantee that the client can parse its response. For help identifying format issues, see Troubleshooting. Once servers appear in the list, configure how app traffic reaches the client.
Choose a proxy mode
The server determines which machine the client tries to connect to; the proxy mode determines which apps can send traffic through the client. Consider them separately. For your first setup, the goal is to send a request from an app you can monitor. There’s no need to change routing rules, DNS settings, or local ports first. Limit the test to one browser so it’s easier to tell whether the app isn’t using the proxy or the server can’t connect.
Desktop: start with the system proxy
In v2rayN, find “System Proxy” in the status area at the bottom of the window or in the tray menu. Select “Set system proxy” or the equivalent option in your version. Check the menu selection or status text to confirm the setting changed. This option directs apps that honor the system proxy setting through the client; it doesn’t mean every desktop app will use it.
Use a browser that normally follows your system settings as the test app. If the browser has a separate proxy setting or an extension that manages connections, check which setting is active first. “Do not change system proxy” usually means the existing system setting is left as is, not that old settings are cleared. If the device uses a proxy for work, note its current settings and restore them after testing.
For your first test, leave TUN disabled. TUN routes traffic through a virtual network interface and can work with apps that don’t use the system proxy, but it also involves system permissions and routing settings. Test the browser first, then decide whether to cover more apps. Don’t change the system proxy, TUN, and custom routing all at once; even if a page loads, you won’t know which route the request took.
Android: check VPN mode and app scope
If your version of v2rayNG offers service modes such as VPN and proxy-only, select VPN mode in settings first. The system will ask for permission when you start the connection in the next step. If you’ve configured per-app proxying, check that the browser you’re testing is included in the VPN’s app scope. Allow and exclude lists work in opposite ways. If you’re unsure, turn off custom app filtering, then return to the server list.
System proxy and VPN mode determine how traffic enters the client; routing settings determine whether it connects directly or through a server. Don’t infer the route from the mode name alone. To learn about routing rules and protocol capabilities, read the Protocol Handbook after your first test. For now, keep your existing routing rules, note which browser you’ll use, and select a server.
Connect to a server
Return to the subscription group you just updated and select a server your provider identifies as available. For your first connection, keep the protocol and transport settings supplied by the subscription. Don’t manually change the port, transport, or security options. Server names are just labels to help you identify entries. If several names look similar, note which one you select so you can identify it when checking status or testing another server.
v2rayN: Set the active server
Select an entry in the list, then use the right-click menu to choose “Set as active server” or the equivalent option in your version. Moving the mouse over a row doesn’t necessarily change the server in use. After selecting it, check the active indicator in the list or the server name in the status bar to make sure it matches. The client may reload its core after you switch servers; wait for the status to settle before sending a request.
Next, check the messages at the bottom of the window for startup failures, configuration errors, or messages that a local listening port is already in use. Recheck the system proxy setting from the previous section as well. If an older client is still using the port, make sure it isn’t handling other tasks before closing it, then retry in the current client. Don’t cycle through several servers yet: if the local service hasn’t started, the remote server can’t explain the error.
v2rayNG: Select a server and start the service
Tap the server you want in the list and confirm it’s selected, then tap the Connect button, usually in the lower-right corner of the main screen. The first time you start the VPN, the system will ask you to approve the connection. Make sure the request comes from the client you’re using before allowing it. If another VPN is running, check whether you can disconnect it first. If device management policies prevent this, don’t try to change them; follow your administrator’s instructions.
After granting permission, return to the client and check that the Connect button shows an active state. Also check the system’s VPN notification. If the button quickly returns to disconnected, open the client’s log or status page and check the latest startup message. If configuration parsing failed, check the subscription and core compatibility. If system permission wasn’t granted, start authorization again from the Connect button; there’s no need to import the subscription again.
At this point, the active server, running status, and system icon only show that a server is selected or the local service has started. They don’t prove that the remote server is reachable. Some connections are established only when an app sends a request, so no traffic immediately after startup can be normal. Keep the current server and proxy mode, open the browser you chose, and run a real request test.
Verify the connection
In the browser you selected earlier, open a test page you’re authorized to access. Refresh it or open a page you haven’t visited before. Don’t rely on content already displayed in an old tab; cached content and existing connections can skew the results. Note roughly when you send the request. Pause other downloads if possible so background traffic doesn’t make the test harder to identify.
In v2rayN, check the available messages, access logs, or traffic display in the main window. In v2rayNG, check the status, logs, or traffic activity provided by the client. If your configuration displays individual requests, find this one by its time and check whether the record indicates a direct or proxy outbound route. Seeing a request reach the client doesn’t mean it went through a remote server; a direct outbound rule may still let the page load normally.
If you can use a trusted service to check your exit IP address, record the result for a new request when no other activity is underway, both with and without the connection. Before comparing on desktop, make sure the system proxy is cleared or restored to a known direct-connection state; simply closing the client may not be enough. On Android, check VPN status after disconnecting in the client. Reconnect, then visit the same test page in the same browser and compare the exit-IP result with the client logs. An unchanged address doesn’t necessarily mean something is wrong: the request may match a direct-routing rule. A change in total traffic alone also doesn’t confirm the route taken by that request.
If something looks wrong, trace the request in order
If the client shows no startup failure but you can’t find the request, first check whether the browser uses the system proxy or whether an Android per-app rule excludes it. If there are no access logs, check whether your version provides them before assuming no traffic passed through. If the request appears in the client and is sent to a proxy outbound, but then times out, switch just one server on the same network and repeat the same test. Change one thing at a time to pinpoint what made a difference.
If the browser test succeeds but another app still has connection issues, don’t reinstall the client or reimport the subscription right away. Check whether the app uses the system proxy, has its own connection settings, or falls outside the proxy scope on Android. A server latency test only tells you what that particular test measures: a latency value doesn’t prove every app’s requests go through that server. For help with timeouts, certificate errors, and DNS failures, see Troubleshooting.
Your first setup is complete once a new request succeeds and takes the expected route. Note the group, server, mode, and app you tested. When you’re done, restore the original system proxy settings on desktop before closing the client if needed. On Android, tap Disconnect in the client. The next time you update the subscription, check that the active server is still in the list, then repeat the same request test.