Setting up V2Ray for the first time? Choose a client based on your device and the node’s protocol, then check whether your link is a subscription or a single-node link. If you can’t connect, confirm the configuration was imported and the selected node is active. Next, check whether your app is using the proxy, then use logs from the same time to pinpoint the issue.
Choosing a client: V2Ray, the core, and the client explained
1. I installed v2rayN. Do I need to install V2Ray separately?
First, check whether the installer includes the core required by your configuration. v2rayN manages nodes, subscriptions, and proxy settings; the core reads the configuration, listens on local ports, and establishes connections. If the installer already includes the core you need, you don’t need to install another one just because V2Ray appears in the name. Opening the client window doesn’t necessarily mean the core has started.
- Seeing nodes in the list only means the client has saved the configuration. Select a node and set it as the active server, then check the runtime log for startup errors.
- If the log says the core can’t be found, first check the installer’s notes and the selected core type. There’s no need to change the node address or password yet. For definitions, see the glossary.
2. Which client should I use on desktop or Android?
Use v2rayN on desktop. On Android, first check which core the service provider requires. The recommendations below are for readers importing a configuration on Android for the first time, when no specific v2fly core is required. Matching protocol names don’t guarantee compatibility; check the transport and security layer too.
v2rayNG
RecommendedAn Android client using the Xray core. If your provider specifies a VLESS and REALITY setup, first check whether this client supports it.
Best for: importing an Xray configuration on Android for the first time
v2flyNG
An Android client using the v2fly core. Check the protocol, transport, and security layer specified by your provider; don’t assume an Xray-specific configuration will work as-is.
Best for: configurations explicitly provided for v2fly
v2rayN
A desktop client for Windows, macOS, and Linux. Check your operating system and processor architecture before downloading, then verify which core is actually running after import.
Best for: managing subscriptions and routing rules on desktop
Compare options in the client comparison, then download after confirming your platform and core.
Subscription links: how to identify, import, and update them
3. What’s the difference between a subscription URL and a single-node share link?
A subscription URL usually returns a list of nodes over HTTPS. The client can request the same URL again to refresh the list. A single-node link describes just one connection and won’t update along with the provider’s subscription. Don’t identify a link by https:// alone: both account pages and subscription endpoints may use HTTPS. Copy the URL from the subscription section provided by your service.
Subscription URL
- Common format
https://- Where to import
- Subscription group settings
- How to update
- Request the subscription URL again
The URL may contain an access token. Don’t post it in public forums or paste it into online decoding tools.
Single-node share link
- Common format
vmess://orvless://- Where to import
- Import configuration from clipboard
- How to update
- Import the new link provided by your service
Links may contain authentication details. Hide the full link in screenshots, too.
Base64 is encoding, not encryption. Some subscriptions encode multiple share links as a single block of text; whether it can be imported depends on the client’s support for that subscription format. Usually, try importing it directly rather than decoding it yourself. For more on formats, see the glossary.
4. Why is the node list still empty after adding a subscription in v2rayN?
Saving a subscription URL and fetching its nodes are two separate steps. The instructions below use v2rayN 7.x on Windows with the classic menu layout. Menu labels may vary slightly between minor versions.
Create a group
In the main window, go to “Subscription Group” → “Subscription Group Settings” and select Add. Enter a name you’ll recognize, paste the subscription URL into the URL field, and save. Don’t paste a single-node share link here.
Update the current group
Switch to the new group, then go to “Subscription Group” → “Update Current Subscription (No Proxy).” Use this option when your current network can access the subscription URL directly. If it times out, check the update message rather than repeatedly creating the same group.
Check for nodes
Stay in the current group and confirm that nodes appear in the list. Right-click the node you want and select “Set as Active Server.” Seeing nodes in the list doesn’t prove they work or that your browser is using the proxy.
If the update succeeds but no nodes appear, first check that you’re in the right group and that no search filter is active. Then ask your provider whether the URL has expired and whether its response format is supported. For Android import steps, see the client setup guide.
System proxy, TUN mode, and traffic routing
5. What’s the difference between system proxy and TUN mode?
System proxy writes proxy settings to the operating system; whether an app uses them depends on the app. TUN mode receives traffic through a virtual network interface, and which traffic it captures depends on system routes and client settings. For your first test, use a browser that follows the system proxy instead of switching between multiple modes at once.
| Mode | How app traffic enters | What to check first |
|---|---|---|
| System proxy | Apps that follow the proxy settings send requests to the local proxy port. | Check whether the app follows system settings, then verify the listening address and port. |
| TUN mode | Traffic matching the system routing rules enters the virtual network interface. | Check whether the virtual interface is running and whether the target traffic is routed through it. |
If v2rayN listens locally on 127.0.0.1:10808, also check whether that port is configured for SOCKS, HTTP, or a mixed inbound. This port is only an example; use the value in your client settings. When configuring an app manually, make sure the address, port, and proxy type all match. For setup steps, see the system proxy setup guide.
6. If system proxy is enabled, does every request go through a remote node?
No. The app first decides whether to send a request to the local proxy. Then the core’s routing rules decide which outbound connection to use. When troubleshooting a browser request, check two things:
- Check whether the request reached the core. If the app is set to bypass the proxy or the target matches a system proxy exclusion, changing the core’s routing rules won’t affect that request.
- Check which outbound connection handled the request. If the log shows a match for a direct outbound, the request reached the core but was routed directly by the rules. Before changing anything, check the rule order and the corresponding outbound tag.
Opening a website in your browser only confirms that the specific visit succeeded. To verify the proxy route, compare the logs with the actual outbound connection at the same time. For field definitions, see the routing and outbound configuration reference.
Connection problems: from subscription updates to core logs
Note what you did and when the problem occurred: did the update fail, or did access fail after you activated a node? Change one setting at a time, then repeat the same action. This makes it easier to tell whether the cause is the subscription, the node, or a local setting.
7. Does a subscription update timeout mean all the nodes are down?
No. The timeout applies to that subscription request; nodes in the existing list may still work. First check that the subscription URL includes all query parameters, then check the update log to see whether DNS resolution failed or the connection timed out. If you have a working node and the subscription URL is reachable through it, try “Update Current Subscription (Proxy).” If you don’t have a working node, ask your provider to confirm the subscription URL and access requirements. Further reading: importing and updating subscriptions.
8. Why can’t I open a webpage even though the latency test shows a response?
The latency value only reflects the selected test method and target; it doesn’t mean your browser’s request took the same route. Retry the target page in your browser while checking the core log. If the current log level records access, but you can’t find the request, check your browser and system proxy settings. If the request appears under a proxy outbound but then times out, check the node address and port. Further reading: inbound and outbound configuration.
9. The log says “address already in use.” What should I change first?
First, check the local listening address and port in the error. If binding to 127.0.0.1:10808 fails, check whether another client instance or program is already using that port. If that program needs to keep running, change the client’s listening port to another unused port, such as 10809, after confirming it’s available. After restarting the core, update any apps where you manually entered the old port. Change the local inbound port, not the server port. Further reading: local listening configuration.
10. The log reports a TLS handshake failure. Should I disable certificate verification?
Don’t treat disabling verification as a fix. First check whether the failure is from a subscription request or a node’s outbound connection. If the error specifically says the certificate is expired or not yet valid, sync your system clock and check the certificate’s validity period. If the name doesn’t match, compare the server name and connection address with the original configuration from your provider. If the handshake timed out, check network reachability instead of assuming it’s a certificate error. When reporting the problem, include the time and error text, but hide the subscription URL and authentication details. Further reading: transport and security layer configuration.