For users setting up v2rayN for the first time or moving to a new device. First, make sure the client can recognize your subscription and start its core. Then test the proxy with a browser, and decide whether you need TUN. When troubleshooting, check subscription downloads, local traffic capture, and the remote handshake separately. Don’t change nodes, ports, and modes all at once.
1. Which client should I use on Windows or Android?
Choose a client for your platform, then check that its core supports your node configuration
Windows:v2rayN
- In Windows 11, go to Settings → System → About to check your system type, then choose a build for your device architecture.
- Run an installer through its setup wizard. For an archive, extract it to its own folder before launching the app; don’t run it from the archive preview.
Android: v2rayNG or v2flyNG
- v2rayNG uses the Xray core and is a good fit for configurations that rely on Xray-specific protocols or transport features.
- v2flyNG uses the V2Fly core. Before choosing it, check that the core and version support the features your node requires.
The same subscription may not import the same nodes across different cores. Test the specific node you plan to use first. See the client downloads.
2. Are V2Ray, v2rayN, and Xray the same thing?
- v2rayN is a client. It displays nodes, manages subscriptions, generates core configurations, and sets up the system proxy or starts TUN, depending on the selected mode.
- Xray and V2Fly are core projects. The core reads the configuration and handles inbound traffic, routing, and outbound connections. Seeing a node in the list only means the client recognized it; it doesn’t mean the core can start or complete a handshake with the remote server.
- VMess and VLESS are protocols. WebSocket is a transport, and TLS is a security layer. When troubleshooting, compare the individual settings—using VLESS doesn’t mean two configurations match. See the glossary.
3. How do I import a subscription URL into v2rayN?
These steps use the common Chinese-language menus in v2rayN 7.x; button labels may vary by version. A subscription URL is an endpoint the client reads periodically to retrieve a list of nodes. Share links beginning with vless:// or vmess:// usually represent a single node and shouldn’t be entered in the subscription URL field.
Copy the subscription URL
Copy the full URL from your provider’s client configuration page, including any query parameters. Don’t use the account sign-in page URL as the subscription URL.
Add a subscription group
In the main window, open Subscription Group → Subscription Group Settings, click Add, enter a name and subscription URL, then save. The name helps identify the source and doesn’t affect connectivity.
Update the list
Go back to Subscription Group and select Update All Subscriptions (without proxy). If you have multiple groups, select the one you want and update it individually to avoid mixing errors from different sources.
Select a node
Switch to the new group, right-click a node, and choose Set as Active Server. Check which node is active, then test a browser request; importing nodes doesn’t enable the proxy by itself.
If the interface differs from these steps, see the setup guide.
4. No nodes appear after updating a subscription. What should I check?
The request timed out. Should I keep retrying?
First, check that you can reach your provider’s account page on your current network, then review the update log. If you already have a working proxy, try Update All Subscriptions (through proxy) to test the download route. Without a working proxy, don’t rely on this option for the initial import.
The log shows 401 or 403. Will switching nodes help?
These are HTTP status codes returned by the subscription request, not results of a node handshake. Check whether the subscription has expired or the URL has been reset, then copy it again from your provider. If it still returns 403, ask the provider about access restrictions.
The update completed without errors, but why is the group still empty?
Select the relevant group and clear any list filters. If it’s still empty, check the export format provided by your service. A sign-in or error page can return HTTP 200 but still fail to parse as a node list. Never paste a subscription URL containing an access token into a public diagnostic tool.
For other subscription update messages, see the Help Center.
5. Should I use the system proxy or TUN?
System proxy
- How it works
- Apps use the system proxy settings
- What to test
- A browser configured to use the system proxy
- Where to check
- Windows Settings → Network & Internet → Proxy
Use this route for your initial test. Apps with their own proxy settings may not follow the system proxy.
TUN mode
- How it works
- Routes traffic through a virtual network adapter and system routing
- Permissions
- Requires permission to configure the network adapter and routes; grant elevated permissions if prompted by the client
- What to test
- Apps that don’t use the system proxy
Test TUN on its own first. Consider using it alongside the system proxy only after that, so it’s easier to isolate problems.
TUN captures traffic, but that doesn’t mean every destination goes through the remote server; routing rules in the core still determine whether traffic is direct, proxied, or blocked. See the proxy mode setup guide.
6. How can I tell whether a request is reaching the core when the proxy is on?
- In v2rayN, go to Settings → Parameter Settings and check the local listening port. If your version shows
10808as the mixed port, check whether apps configured manually point to127.0.0.1:10808, and confirm that the proxy type they use is supported by that listener. This port is only an example; don’t assume it’s the right value for your setup. - Make sure your browser uses the system proxy, then open a known reachable site. Check the client log as well. If access logging is enabled and the log level records requests, match the request time and destination to see whether it reached the core.
- The local proxy port and the remote node port are separate settings. If the remote configuration specifies
443, that doesn’t mean your browser should connect to443on your own device. See inbound and outbound terminology.
7. Why won’t a website load even though the latency test shows a value?
- Ping responds: This only means the test target responded to ICMP. It doesn’t confirm that the node’s port is reachable or that the protocol handshake will succeed. Conversely, a host that doesn’t respond to Ping may still provide a working proxy service.
- The real connection test returns a result: Check which test target the client uses. A successful result means that test request got through; it doesn’t prove that your target website or browser settings are working. The browser may not be using the proxy, or the destination may match a different routing rule.
- How to interpret the results: For example, the same node might show a Ping of 35 ms and a real connection time of 380 ms. These sample readings measure different things, so their difference isn’t a direct measure of packet loss or server processing time. To compare nodes, keep the test method and target the same, run several tests, then verify with the apps you actually use. See connection troubleshooting.
8. The connection fails. What should I check, and in what order?
- Start with your network. Temporarily turn off the system proxy and TUN, then use the same device to test a site that normally works without a proxy. If your regular connection is down, check Wi-Fi, network sign-in, or other system network issues first.
- Next, check that the core starts. Switch back to the original node and enable only one traffic capture method. If the startup log says
address already in use, check whether another process is using the local port. If you change the port, update any apps where you entered the proxy address manually. - Finally, check the node connection. If the log reports a DNS resolution failure, check whether the error refers to the node’s domain or the destination you’re trying to reach. For a TLS certificate error, check the system clock, server name, and subscription settings; don’t hide the problem by skipping verification. If another node in the same group works, focus on the failing node. See the protocol guide.
9. Can switching to global routing fix an app that isn’t using the proxy?
- First, distinguish traffic capture from routing. The system proxy or TUN determines whether an app’s request can reach the core. Routing rules determine which outbound the core uses for requests it receives. Changing to global routing won’t capture requests that never reached the core.
- Change one setting at a time. Keep the same browser, destination, and node; change only the routing mode and try again. If only one mode fails, check the rule matching that destination and its outbound. If both modes fail, go back to traffic capture and connection logs.
- Restore your original settings afterward. Local devices, corporate intranet sites, and services on your own computer may need a direct connection. Restore the original mode after testing, then check those addresses. See routing rules terminology.
10. The internet stops working after I close the client. How do I restore it and report the issue?
- If the client is still open, use System Proxy → Clear System Proxy in the tray menu, turn off TUN, and then exit normally. Force-quitting the process can leave a system setting pointing to the local proxy port even though nothing is listening there.
- In Windows Settings → Network & Internet → Proxy, check the manual proxy settings. If the leftover entry is a local address set during your test, restore the settings you had before testing. Don’t clear a proxy managed by your organization without permission. If the problem only occurs after enabling TUN, reopen the client, turn off TUN normally, and test your direct connection again.
- When asking for help, include your Windows version, the client’s full version number, current mode, time of the issue, and the first error message. Before sharing logs, remove subscription URLs, user IDs, and any server details you shouldn’t make public. Use the Help Center to identify which layer is failing.