V2Ray FAQ
Find the cause of common v2rayN, v2rayNG, and v2flyNG issues by checking each step, from installation packages to runtime logs.
Basics
Understand the client, core, and traffic entry point before deciding which layer to troubleshoot.
What’s the difference between the V2Ray core and a GUI client?
The core parses configuration, evaluates routing rules, and establishes connections. The GUI client imports subscriptions, switches nodes, and manages the core process. An open client window does not mean the core started successfully. If startup fails, check the first configuration- or listening-port-related error in the runtime log, then decide whether to adjust the config or system settings.
Which should I choose: v2rayN, v2rayNG, or v2flyNG?
Choose v2rayN for desktop. On Android, v2rayNG, which uses the Xray core, is usually the first option to consider. Use v2flyNG if the server configuration specifically requires the V2Fly core. Check the protocol, transport, and security layer—not just the node name. Even two nodes using the same protocol may require different client cores.
Are subscription URLs and single-node share links the same thing?
A subscription URL retrieves a group of nodes; after adding it, you’ll usually need to update the subscription. A single-node link describes one connection and should be imported from the clipboard or by scanning a QR code. Pasting a subscription URL into the single-node import field may result in an unsupported-format error. Subscription URLs may contain account credentials, so don’t post the full URL in a group chat or public support ticket.
Are system proxy, TUN, and global routing the same setting?
No. System proxy and TUN determine how traffic enters the client; routing mode determines which outbound connection the core uses for traffic it receives. Switching to global routing won’t make apps that ignore the system proxy send traffic through the core. When troubleshooting an app, first confirm its requests reach the client, then check which routing rule matches.
Installation & Setup
Choose a package for your system architecture, then check import formats and system permissions.
Which Android package should I choose: arm64 or universal?
Choose arm64 if your device’s operating system supports arm64-v8a. If you’re unsure which architectures the OS supports, check the universal build’s compatibility first. A 64-bit processor doesn’t necessarily mean the device runs a 64-bit operating system. If Android reports an architecture incompatibility, try the universal build of the same client. If it reports a conflict with an installed app, check the signing source and back up your settings first.
Should I choose the v2rayN desktop edition or the classic WPF edition?
The desktop edition has a cross-platform interface; the classic WPF edition is for users who prefer the traditional Windows interface. For a first-time install, choose a package for your operating system and processor architecture, then check its runtime requirements. Before migrating, back up your subscriptions, routing, and DNS settings. Run only one client instance on first launch to prevent two instances from competing for the same local proxy port.
What should I check first if a subscription won’t import?
First, make sure you copied the subscription URL provided by your service—not a login page or single-node link. Check for leading or trailing line breaks, spaces, or quotation marks. Save the URL to a subscription group, then update that group manually. If the log shows the request succeeded but parsing failed, check whether the client supports the configuration format returned by the server. Don’t test URLs containing credentials with an online converter.
What should I do if TUN reports insufficient permissions?
On desktop, follow the client’s prompt to see whether elevated permissions or a companion service are required. On managed devices, contact your administrator. On Android, approve the system VPN connection request and check whether another app is using the VPN connection. After confirming permissions, restart TUN. If it still fails, check the log for the specific virtual network adapter creation or route-writing error.
Usage Tips
Update subscription groups individually; when adjusting routing or DNS, test one change at a time.
How do I troubleshoot subscription updates when my old nodes still connect?
Subscription downloads and node connections use separate paths. Keep the old group and update only the group with the problem. For a 401 or 403, check subscription authorization. For certificate errors, check the system clock and certificate chain. For connection timeouts, compare direct updates with updates through a proxy. If the proxy node itself is no longer working, don’t keep relying on it to refresh the subscription.
How should I group multiple subscriptions for easier troubleshooting?
Create a separate group for each source and give each one a clear, distinct label. Update groups manually one at a time, confirm new nodes appear in the right group, then enable automatic updates. If the node count suddenly drops after an update, check the server response and local filtering rules before deleting the group. Keep manually added nodes in a separate group so subscription updates don’t mix them with remote entries.
How can I check whether my routing changes use the expected outbound?
First, make sure you edited the currently active rule set. Then test a domain and a local network destination separately using new connections; existing connections may not be matched again. If the log shows a different outbound than expected, check whether a broad rule precedes a more specific one, whether the request still includes its domain when it reaches the core, and which default outbound is used when no rule matches.
When should I change DNS settings or enable FakeDNS?
If the log repeatedly shows resolution failures, or domain-based rules depend on resolved addresses, first check the DNS configuration actually in use and the outbound used for DNS requests. FakeDNS maps domains to virtual IP addresses and is often used with TUN; enabling it won’t fix every DNS issue. Confirm the core and traffic-capture method support it, record the current settings, and change one thing at a time before testing again.
Troubleshooting
Check whether requests reach the core, then troubleshoot DNS resolution, routing, and outbound connections in that order.
Does a node test timeout mean the server is definitely unavailable?
Not necessarily. A timeout can mean the test destination is unreachable, the network is having issues, the server address failed to resolve, or the handshake parameters don’t match. Compare two configured nodes using the same test destination, then test again against a destination you normally access. If only one node fails, check its address, port, and transport settings. If all nodes fail, check the core and your current network first.
The client says it’s connected. Why won’t web pages load?
A connected status doesn’t necessarily mean browser requests are being forwarded successfully. Try opening a known accessible site and watch the log. If no new entries appear, check whether the browser is using the client. If there are entries but DNS resolution fails, check DNS. If resolution succeeds but the connection times out, check routing and the selected outbound. If neither local nor remote sites load, restore your original proxy settings first to test basic connectivity.
Why isn’t an app using the proxy when system proxy is enabled?
Some apps don’t use the system proxy; others keep settings they read when they started. Restart the app and compare its behavior with a browser known to follow the system proxy. If only one app is affected, check its own proxy settings first and enter the protocol and listening port provided by the client. If it has no separate proxy settings, consider whether TUN is suitable for capturing its traffic.
The log says a local port is already in use. How do I fix it?
Check the log to identify the conflicting listening port, then see whether an old client, leftover core process, or another proxy service is using it. Don’t terminate unfamiliar system processes. Exit duplicate client instances normally, or choose an unused port in the client. After restarting the core, update any apps configured manually to use the proxy so they don’t keep connecting to the old port.