At a glance

When setting up v2rayN or an Android client for the first time, check that your nodes appear in the list, then make sure the app you want to use is routing traffic through the client. When something goes wrong, first determine whether the subscription failed to download, the core failed to start, or the node couldn’t connect. Then decide whether to switch nodes, change a port, or check the routing rules.

Importing Subscriptions: Add an Address and Update the Group

01. What’s the difference between a subscription link and a single-node link?

A subscription link is usually an HTTPS URL provided by your service provider. The client uses it to fetch a list of nodes periodically. A single-node link contains the configuration for one specific server and often starts with vmess:// or vless://. VMess and VLESS are protocols used for communication between a client and server, not client names. Pasting a single-node link into the subscription address field won’t give you a list of nodes.

  • Desktop v2rayN: Using the common 7.x interface as an example, open “Subscription Group” → “Subscription Group Settings,” add a group, enter a name and subscription URL, then save. Select the new group and choose “Update current subscription” from the “Subscription Group” menu. To import a single-node link, use the clipboard import option under “Servers.”
  • Android v2rayNG: Open “Subscription Group Settings” from the sidebar, tap the add button, and save the URL. Return to the configuration list, open the menu in the top-right corner, and select “Update subscription.” To import a single-node link, choose the clipboard import option from the add menu on the main screen. Menu labels may vary slightly by version.

02. The address is saved. Why don’t I see any nodes?

Saving the address and updating the subscription are separate steps. Switch to the group you just created, clear any search filters on the list, then run an update manually. When it finishes, check the result: a download failure and a successful download with an empty list point to different issues.

  1. Timeout message: First, make sure the device has a working internet connection. If the old client has been closed but the desktop system still points to its local proxy, restore the previous system proxy settings before trying again. Check whether the timeout occurred while updating the subscription or testing a node; these involve different addresses.
  2. 401 or 403 message: Check the provider’s website to confirm that the subscription is still active, then copy the latest URL. Keep the full query string when copying. Don’t share your subscription URL, QR code, or screenshots containing credentials in public groups.
  3. Update succeeded, but the list is empty: Check which group is currently selected, then make sure you copied the subscription URL intended for clients, not an account or login page URL. If the update reports a parsing error, ask the provider to confirm the output format rather than repeatedly deleting and recreating the group.

Clients and Connection Modes: Choose Based on Your Device and Apps

03. Which client should I install on desktop or Android?

Use v2rayN on desktop. On Android, first check which core supports your configuration. The core is the program that establishes connections and handles traffic; the client imports configurations, switches nodes, and displays status. Seeing a node name in the list only means the client read the entry—it doesn’t mean the core supports every setting in it.

v2rayNG: Xray core

Recommended

If your subscription provides configurations for Xray—for example, one explicitly labeled VLESS with REALITY (a connection security configuration)—choose this option first and import the settings exactly as provided by the service.

Best for: Android configurations explicitly marked as Xray-compatible.

v2flyNG: v2fly core

Choose this when the service provider explicitly offers v2fly-compatible configurations, such as VMess nodes documented as supported. Don’t try to make settings for another core work by changing them one by one.

Best for: Android configurations confirmed to work with v2fly.

Check that the core supports your configuration before importing

If the logs say a protocol or security setting isn’t supported, first check with the provider which core and minimum version are required, then import the matching configuration. Switching regions or changing the system proxy won’t make a core recognize unsupported fields.

04. Are system proxy, TUN, and global mode the same switch?

No. System proxy and TUN determine how traffic enters the client; global proxy and rule-based routing determine where traffic goes after that. The system proxy usually covers only apps that follow system settings. TUN receives traffic through a virtual network interface and generally covers more apps, but it’s still subject to system permissions and routing rules.

Getting Started: Test One App Before Routing More Traffic

Desktop: Test the system proxy first
  • Select a node in v2rayN, then choose “Set system proxy” from the tray menu. Test it with a browser that follows the system proxy settings.
  • If the browser works but another app doesn’t use the proxy, check that app’s own proxy settings first. Try TUN separately only if needed.
Android: Confirm the connection permission first
  • Select a node and tap Connect. When prompted the first time, grant permission to create a VPN connection.
  • Once the browser test works, set up per-app proxying. If another VPN is running, make sure you can disconnect it before starting the current client.

Change one setting at a time: first confirm that app traffic reaches the client, then compare global proxy and rule-based routing.

Node Latency and Connection Status: Don’t Confuse the Two

05. Is the node with the lowest latency always the fastest?

Not necessarily. TCP latency mainly measures how long it takes to establish a TCP connection to the server. Latency measured by accessing a test address through a proxy also includes the proxy connection and the destination site’s response time. The two figures aren’t directly comparable, and neither tells you the download speed. A timeout doesn’t always mean the node is down—the test address itself may be unreachable.

  1. On the same network, test a few candidate nodes using the same test address and method. Don’t compare a TCP latency test on your home network with a proxy test on a mobile network.
  2. In the v2rayN node list, select a candidate and run the real connection latency test from the right-click menu (the label varies slightly by version). Then open two sites you normally use and check for repeated loading spinners or intermittent timeouts.
  3. If you often download files or join video calls, check connection stability separately. For example, if one node shows 85 ms but times out frequently, while another shows 140 ms and loads pages consistently, choose the latter for everyday use. This is an example of how to judge performance, not a test result for any specific node.

06. The client says it’s connected. Why won’t websites load?

“Connected” may only mean that the local service has started or that the system’s VPN interface is up. It doesn’t guarantee that the remote node can connect or that your browser is using it. On desktop, check that the system proxy points to the current client’s listening address and port. On Android, make sure the affected browser hasn’t been excluded by per-app routing rules.

127.0.0.1
Loopback address: a connection to this device
10808
Common local proxy ports in v2rayN; check your actual settings

For v2rayN 7.x, open “Settings” → “Parameter Settings” to check the local listening port and inbound type. When configuring an app’s proxy manually, its HTTP or SOCKS setting must match the inbound type; a mixed inbound accepts both. This is the local inbound port, not the remote server port shown in the node details. After checking it, open a new test page and watch the logs for a corresponding new connection.

Can’t Connect? Troubleshoot Based on Logs and Scope

07. The port is already in use on startup. Should I change nodes?

Don’t change nodes yet. If the logs show address already in use, note the address and port in the error, then check whether an old client instance is still running in the system tray. If you find a duplicate, exit it from the tray and try again. If the conflict is with the local proxy inbound, go to “Settings” → “Parameter Settings” and choose a port you’ve confirmed is free, such as 10818. After restarting the core, set the system proxy again. Update the port in any apps where you entered it manually, too.

08. The same nodes worked yesterday, but they all time out today. Why?

First, test the same node on the same device using a different network—for example, switch from home Wi-Fi to a mobile hotspot. If it works on the other network, check whether the original network requires a sign-in or has recently changed its proxy settings. If both networks fail, check for node updates and whether the subscription has expired. If the logs say a certificate isn’t yet valid or has expired, sync the device’s date, time, and time zone. If the clock is correct and the error persists, ask the provider to check the certificate; don’t disable certificate verification.

09. Only one website won’t open. Should I change DNS?

Don’t change DNS and nodes at the same time. DNS resolves domain names to addresses. Try opening another site in the same browser, then check the client logs while the failed page is open. If the logs clearly show a DNS resolution failure, check the client’s DNS settings and the browser’s secure DNS settings. If DNS succeeds but the connection times out, check whether the domain matched a direct or proxy rule. If the page returns 403, the server has already sent an HTTP response; investigate the site’s access restrictions rather than treating it as a DNS failure.

10. After closing the client, even regular websites won’t load. What should I do?

First, check whether the system is still sending connections to a local proxy that has been shut down. On desktop, reopen v2rayN, choose “Clear system proxy” from the tray menu, then exit. If you were using a proxy provided by your workplace or school, restore its original settings instead of clearing them. If you entered proxy settings manually in your browser, check those too. On Android, make sure the VPN is disconnected. If Always-on VPN and Block connections without VPN are enabled, first check whether your device’s management policy requires them; don’t turn them off without authorization.