When you first use v2rayN, check subscriptions, nodes, and proxy settings separately. Subscriptions fetch your node list, the active node determines connection settings, and System Proxy or TUN controls how app traffic reaches the client. Checking these three layers helps pinpoint subscription update failures, core startup issues, and web access problems.
1. How do I import a subscription into v2rayN?
A subscription URL is usually an HTTPS link that retrieves a list of nodes. Share links starting with vmess:// or vless:// usually represent a single node. Add subscription URLs to a subscription group; import individual nodes from the clipboard. The menu names below refer to the Chinese-language interface in v2rayN 7.x on Windows. Names and locations may vary slightly between versions.
Open subscription group settings
In the main window, go to “Subscription Group” → “Subscription Group Settings” and click “Add.” Enter a recognizable name in the remarks field so subscriptions from different sources don't get mixed up.
Save the subscription URL
Paste the full URL into the subscription address field and save it. Don't copy just the domain or omit query parameters after the question mark. Subscription URLs may contain access tokens, so don't include them in public screenshots.
Update the current group
Switch to the group you just created, then select “Update Current Subscription” from “Subscription Group.” When the update finishes, confirm that nodes appear in the list; saving the URL alone won't add any nodes.
2. Should I update subscriptions through the proxy or directly?
This setting controls how the subscription request is sent. It doesn't change the new nodes' protocols or determine how your browser connects afterward. If you're setting things up for the first time and don't have a working node yet, try updating directly. Once you have a working active node, choose whether to update through the proxy based on whether the subscription service is reachable that way.
- 401 or 403 response: The server received the request and returned a response. Check that the URL is complete, your authorization is valid, and the server doesn't restrict request sources. Changing the local port won't restore a missing token.
- Request timed out: First check whether the subscription download or the node test timed out. If you chose to update through the proxy, make sure the active node works; otherwise, the update request may get stuck too.
- Download succeeded, but the list is empty: Make sure you're viewing the right group, then check the logs for parsing errors. The response may be a login or error page rather than a node list the client can read.
3. Why can't I connect even though nodes appear in the list?
A node in the list only means its configuration has been saved. Select a node, then choose “Set as Active Server” from the right-click menu. Check the logs for core exits or listener failures, then verify that the app is using the local proxy endpoint. When testing, keep the network and destination the same and change only one node at a time.
Local proxy endpoint
- Example listening address
127.0.0.1- Example mixed port
10808- App proxy type
- Choose HTTP or SOCKS5 to match the active listener
Check “Settings” → “Parameter Settings” and the runtime logs for the port number.
Remote node configuration
- Server address
- Domain or address provided by the subscription
- Server port
- Remote port provided by the subscription
- Protocol and transport
- Must match the server configuration
Don't enter the remote port in your browser's local proxy settings.
4. What's the difference between System Proxy and TUN?
System Proxy is a good first step for testing apps that honor desktop proxy settings. TUN uses a virtual network adapter to receive traffic routed by the system and pass it to the proxy core. Enabling TUN doesn't mean every connection goes through a remote node; outbound routing still depends on the routing rules.
System Proxy
RecommendedFrom the Windows tray menu, select “System Proxy” → “Set System Proxy.” The client updates the system proxy settings, allowing browsers that follow those settings to use the local proxy endpoint.
Best for: Initial testing, browser access, and quickly diagnosing connection problems.
TUN mode
Follow the on-screen prompts to grant the permissions needed to create a virtual network adapter. If something goes wrong after enabling TUN, turn it off to restore the baseline, then check other virtual adapters, routes, and DNS settings.
Best for: Apps that don't use system proxy settings.
5. Why won't websites load even though the latency test succeeds?
A latency result only tells you how the selected test performed. A TCP test mainly checks whether a connection to the remote port can be established. A test run through a node only verifies the test address; it doesn't confirm that your browser uses the same endpoint, destination, or DNS route. If the browser still can't load a page, identify where the request is failing.
- Use a browser that follows system proxy settings to test two known-accessible HTTPS sites. If only one fails, check the destination site and the routing rule that matches its domain.
- If the browser reports a proxy connection error, check that the local listener is running and that the system proxy isn't pointing to an old port. If it reports a DNS lookup failure, check the DNS routes used by both the browser and the client.
6. All nodes are timing out. What should I check first?
Check the startup logs first, then the test logs. If every node fails at once, look for shared causes such as the local listener, proxy core, current network, or test address rather than changing passwords or transport settings on each node.
- If you see
address already in use, the local address and port couldn't be bound. Check whether the client is running more than once or another program is using the listening port. If you change the port, update it in any apps where the proxy settings were entered manually. - If you see
i/o timeout, check the surrounding log lines to see whether the timeout occurred while connecting to the remote server, waiting for a handshake, or waiting for a response. Test the same node on another working network to distinguish a network issue from a node issue. - If you see a certificate validity error, check your system date, time, and time zone, then verify the server name required by the node and the server certificate. Disabling certificate verification isn't a fix.
7. Why does my browser work but other apps don't use the proxy?
Check whether the app supports proxy settings
The app has a proxy option
- Check whether it follows system settings or uses its own manual settings.
- For manual settings, enter the local listening address and port, and select the matching proxy type. Reconnect after changing the settings instead of reusing an existing connection.
The app has no proxy option
- Check whether the app ignores system proxy settings; command-line tools may use their own configuration too.
- Test TUN only if the app really needs traffic interception. If it uses UDP, make sure the entire forwarding path supports UDP.
A working browser only confirms that the browser's route works; it doesn't verify the proxy endpoint or routing for other apps.
8. Switching nodes makes no difference. Could routing rules be the cause?
Possibly. Switching the active node usually affects only connections routed through the proxy. Destinations that match direct-connection rules won't change when you switch nodes. You may also see no immediate difference if a request reuses a connection established before the switch.
- After switching nodes, reopen the test app or start a new connection. Note the destination domain and request time, then check the logs for that request.
- If the logs show the destination going direct, check the selected routing rule set and whether an earlier rule matches first. If it only times out when routed through the proxy, go back to troubleshooting the node and remote connection.
- In custom rules,
outboundTagmust reference an outbound tag that actually exists. Check the outbound configuration reference instead of guessing from the node remark.
9. Can I use the same subscription on desktop and Android?
You can try, provided the subscription service allows multiple devices and each client can parse the subscription format. Seeing the same nodes on both devices doesn't mean they support the same transport methods and security settings. A working desktop connection doesn't rule out a core compatibility issue on Android.
- Use v2rayN on desktop. On Android, v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. Choose a client based on the node's full protocol configuration, not just whether its name includes VMess or VLESS.
- Update the subscription on both devices, then compare the same node. If the import succeeds on Android but the connection fails, check parsing and handshake logs, then confirm that the required system permissions for handling network traffic have been granted.
- If the connection drops only when both devices are in use, test each device separately first, then check for server-side limits on concurrent connections or device count.
10. How do I restore my connection after closing the client?
After the client closes, the local port may stop listening while the system or apps continue sending requests to it. Before exiting normally from the tray menu, restore the proxy and TUN settings to their previous state. On a device managed by an organization, don't remove existing network proxy settings without checking first.
- If you enabled TUN, turn it off in the client first, then check whether direct connections work again. Don't remove other virtual network adapters just to troubleshoot.
- If you enabled automatic system proxy configuration, select “Clear System Proxy” from the tray menu. If the client is already closed, open Windows “Settings” → “Network & Internet” → “Proxy” and check whether the manual proxy still points to the stopped local port. Restore the previous settings as needed.
- If system settings are restored but only one app remains offline, check its own proxy configuration. Set it to follow system settings or restore its previous configuration, then restart the app and test again.