Installation & Connection Troubleshooting
v2rayN FAQ
First identify where the problem occurs: the installer won’t open, the subscription won’t import, or app traffic isn’t reaching the proxy. Choose the section that fits and change one thing at a time while troubleshooting.
Basics
Start by distinguishing the client, core, and configuration. Knowing what each layer does makes it easier to find the right setting.
What’s the difference between v2rayN, V2Ray, and Xray?
v2rayN is a desktop GUI client for managing configurations, launching a core, and setting up a local proxy. V2Ray is proxy software in the Project V ecosystem, with related implementations maintained by the V2Fly community. Xray is a separately developed core project. Switching the GUI and switching the core are two different things. Before importing a configuration, make sure the selected core supports its protocols, transports, and security options.
What’s the difference between a subscription URL and a single-node link?
A subscription URL points to configuration data that can be fetched periodically, letting you refresh a group of entries at once. A single-node link describes one connection and usually won’t receive subscription updates after import. Check which type your provider supplied, then use the subscription group or single-entry import option accordingly. Both may contain credentials, so don’t share them in public screenshots, support ticket titles, or online conversion tools.
What’s the difference between system proxy and TUN mode?
System proxy provides a local proxy endpoint for apps that follow the system settings, but apps with their own network settings may bypass it. TUN uses a virtual interface to receive traffic routed into it; coverage depends on system routes, exclusion rules, and permissions. When troubleshooting, start with one mode and confirm a single app can connect before expanding coverage.
Why are there no usable nodes after installing the client?
The client runs connection configurations; it doesn’t provide remote connections. An empty list on first launch is normal. Once you have a subscription or individual configuration you’re authorized to use, import it, select an entry, and check whether the core starts. If the entry still doesn’t appear, check the selected group and search filters instead of importing the same data repeatedly.
Installation & Setup
Choose a package for your operating system and architecture first. Once the client opens, check separately that subscriptions can be read and the virtual interface can be created.
Which v2rayN version should I choose on Windows: Desktop or WPF?
The Desktop version uses a cross-platform interface, while the WPF version keeps the classic Windows interface. Check your system architecture and the release notes for runtime requirements, then choose the interface you prefer. If you already have configurations, back up the client data before switching. Quit the current client before testing another version to avoid two processes changing system proxy settings or competing for the same local listening port.
Which Android APK should I choose: arm64 or universal?
If your device’s operating system supports arm64-v8a, choose the arm64 package. If you’re unsure which app architectures the system supports, check the device specifications or choose the universal package, which supports multiple architectures. A 64-bit processor doesn’t necessarily mean the operating system can run 64-bit apps. If the universal package also fails to install, check the Android version requirements and whether its signature conflicts with an installed app.
What should I do if a subscription won’t import or no entries appear?
Make sure you copied the complete subscription URL, with no line breaks or extra spaces, and that it isn’t an account login page. Save it to a subscription group, update the group manually, and check the logs. A login or error page can’t be parsed into nodes, even if the request succeeds. If the logs report an unsupported format, ask your configuration provider whether they can supply a format compatible with your client.
What should I do if TUN reports insufficient permissions?
Check the logs to see whether the error occurred while creating the virtual interface or adding routes. On Windows, quit the client and relaunch it with administrator privileges as described in the release notes. On macOS and Linux, check the documentation for your version for virtual interface, helper process, and authorization requirements. If the device is managed by your organization, confirm that the required permissions are allowed. Don’t disable system protections to get past a startup failure.
Using v2rayN
Compare test results with actual requests. Port reachability, a request reaching the core, and a rule selecting the expected outbound are three separate checkpoints.
How can I tell whether an app is actually using the proxy?
Use a single test app to make a new request, then check the client logs for the matching destination and outbound record. If there’s no record, check whether the app uses its own proxy settings or is reusing an existing connection. A log entry only confirms that the request reached the core; check whether the matched outbound is proxied or goes direct.
Why does a port test pass while a real connection test fails?
A successful tcping test usually means only that the target TCP port was reachable at that moment. It doesn’t verify the protocol handshake, authentication, or access to the test URL. If a real connection fails, test a known-good entry against the same URL, then check whether the logs show a handshake error or a timeout reaching the test target. Don’t judge a node’s usability by the port test alone.
Why does an older rule still match after I add a routing rule?
Make sure you edited the currently active routing configuration, reload it after saving, and then start a new connection. Rules are usually evaluated in order, so a broad rule earlier in the list may match before a later exception can take effect. Check whether the destination reaches the core as a domain name or an IP address, and consider the domain resolution strategy when choosing the match condition.
What should I back up before updating the client?
Note the current client version and core, then quit the client and back up its data directory as described in the documentation for that version. Keep custom routes, subscription groups, and manual configurations; don’t assume the data directory is the installation directory. Backups may contain credentials, so store them somewhere secure. After upgrading, test a known-good entry before restoring custom settings one at a time.
Troubleshooting
First determine the scope: is one app failing, is one configuration timing out, or is the subscription request itself failing? Note the first error, then decide which layer to investigate.
What should I check first when a node suddenly times out?
First confirm that your current network can reach commonly used sites, then run the same test against another known-good entry. If only one entry fails, check the logs for a DNS resolution, connection timeout, or handshake error, and verify the server address, port, and current configuration. If all entries fail, check whether the core has started and whether the local port is listening.
Why can’t I access the internet even though the client says it’s connected?
A running client or selected entry doesn’t mean app traffic is flowing through it. Disable duplicate proxy access methods so only one is active, then make a new browser request and compare it with the logs. If there’s no request record, check app proxy settings and the local port. If there is, check the routing match, DNS, and outbound errors. If access still fails after you stop the client, check whether the system is still pointing to a proxy port that is no longer listening.
Why doesn’t system proxy work in a particular app?
Compare with a browser that follows the system proxy. If the browser works but the target app produces no request records, check whether it has its own proxy settings, a bypass list, or another tool managing its network settings. If you enter proxy settings manually, make sure both the protocol and port match the client’s actual inbound settings. If the app caches proxy settings, quit and reopen it after making changes.
What should I do if a subscription worked before but now fails to update?
Keep the existing group, try a manual update, and check the error. For 401 or 403 errors, first check whether the subscription authorization or URL has changed. For connection timeouts, check the network path used by the client to fetch the subscription. If updates rely on a proxy and the current entry is unavailable, restore a working connection or, if the subscription source allows it and is directly reachable, update over a direct connection.