V2Ray FAQ
Find answers by symptom: start with installation and setup if you haven't imported a server yet; go straight to troubleshooting if you're connected but requests are failing.
Basics
Learn the difference between clients, cores and configuration entries, then see our client comparison.
Which should you choose: v2rayN, v2rayNG or v2flyNG?
For Windows, macOS and Linux, start with v2rayN. On Android, consider v2rayNG, which uses Xray-core. Choose v2flyNG if your configuration specifically targets the V2Fly core. Check your operating system first, then verify the protocol, transport and security layer. A share link importing successfully into two clients doesn't mean both clients' cores can run that configuration.
What do the client and core each do?
The client provides subscription management, a server list, connection controls and logs. The core reads the runtime configuration, establishes connections and applies routing rules. A successful import only means the client read the entry. If startup logs report unsupported fields, check that the entry's transport and security layer are compatible with the core instead of importing it again.
What's the difference between a subscription URL and a single-server share link?
A subscription URL fetches a set of server entries and uses the same URL for future updates. A single-server share link usually imports just one entry and isn't updated with the subscription. Service information and login pages aren't subscription URLs: opening a page in a browser doesn't mean the client can parse its contents as a server. Both link types may contain credentials, so don't include them in public screenshots or logs.
Are VLESS, REALITY and transport the same kind of setting?
No. VLESS is a proxy protocol, REALITY is a security layer, and TCP and WebSocket are transport options. Check each separately when troubleshooting; the server name alone won't tell you which settings to use. If the server requires a specific combination, follow the original configuration. Switching the protocol to VLESS won't automatically set the transport or security parameters.
Installation & Setup
Choose a client installer for your OS and device architecture, then import a subscription using the quick start guide.
Which Android package should I choose: arm64 or universal?
Choose the arm64 package if your device's OS supports arm64-v8a. Choose universal if you don't know which app architecture the OS supports or need one package for devices with different architectures. Don't rely on the processor model alone: a 64-bit-capable processor doesn't mean the OS can install 64-bit apps. If the universal package won't install either, check the OS version, available storage and whether its signature conflicts with an existing app.
Which v2rayN desktop version should I choose: Avalonia or classic WPF?
On Windows, choose between the Avalonia desktop version and classic WPF. On macOS and Linux, use the Avalonia desktop version. If you're following screenshots, make sure the guide matches your version's interface before looking for settings. Back up your configuration before switching versions, then test a familiar configuration after installation. A subscription can fetch your servers again, but may not restore local routing and proxy preferences.
I've added a subscription. Why is the server list still empty?
Adding a subscription URL and fetching servers are two separate steps. In v2rayN, save the group under Subscription Group Settings, then update the current group from the Subscription Group menu. In v2rayNG, save it under Subscription Group Settings, return to the main screen and update subscriptions from the menu. Switch to the relevant group to view the results. If it's still empty in v2rayN, check that updates are enabled for the group and that filters aren't excluding every entry. Then use the logs to tell a failed request from content the client can't parse.
What permissions does TUN mode require?
On desktop, TUN mode requires the client to create a virtual network interface and adjust routes. If v2rayN logs a permissions error on Windows, exit it completely, restart it as an administrator and try again. On macOS and Linux, grant the permissions requested by the client; Windows instructions don't apply. On Android, confirm the system prompt the first time v2rayNG or v2flyNG creates a VPN connection. If another VPN is already running, disconnect it and try again.
Usage Tips
Choose how to route traffic, manage multiple subscription sources, and understand speed test and routing results.
When should I use the system proxy, and when should I use TUN?
If you only need browsers or desktop apps that follow system proxy settings to use the proxy, start with v2rayN's Set system proxy automatically option. Consider TUN if an app doesn't use the system proxy and has no separate proxy settings. TUN routes traffic through a virtual interface according to system routes; it doesn't mean every request exits through the proxy. Routing rules still determine whether traffic is proxied or goes direct.
How can I update and filter multiple subscriptions separately?
In v2rayN's Subscription Group Settings, create a separate group for each URL and use Remarks to identify its source. When troubleshooting a source, switch to its group and update only that group so changes from other sources don't affect your diagnosis. Add a Filter condition only when you need to narrow the list. Note the original condition first; if the list suddenly shrinks after an update, remove the filter and compare again.
Why is the actual connection latency high when TCPing is fast?
TCPing measures whether a TCP connection to the server port can be established and how long that takes. Actual connection latency also includes the proxy handshake and the time to reach a test address through the proxy. These tests measure different things, and neither measures download speed. To compare servers, use the same test method and address, then retest on the same network. Don't compare results from different tests directly.
How can I tell which routing rule takes effect after an edit?
First confirm that v2rayN has selected the routing configuration you just edited. Start a new connection to the same test destination and check the corresponding outbound in the logs. If the result isn't what you expect, check rules in order: typically, the first matching rule takes effect, so a broad rule near the top may override a later exception. Change one rule at a time, without switching servers or test destinations.
Troubleshooting
First determine whether the issue affects one server, one app or the entire client. For OS-specific settings, see the cross-platform setup guide.
Does a node test timeout mean the server is down?
Don't draw conclusions from a single timeout. First check that the core starts without errors, then test a previously working server using the same method. If only one fails, check its server address, port and transport settings. If several fail at once, check your local network, core logs and test address. A real connection test also depends on its destination, so an unreachable test address can show a timeout too.
The client says connected. Why won't web pages load?
A connected status doesn't mean browser requests are getting through. First check that the desktop client has the expected system proxy or TUN enabled, or that Android has established a VPN connection. Reload the page and check the client logs. If there's no matching request, check whether the app's traffic is reaching the proxy. If a request appears with a DNS, handshake or routing error, troubleshoot that step. If only one site won't load, compare with another known-working site.
Why are apps still connecting directly after v2rayN sets the system proxy?
First confirm in the tray menu that Set system proxy automatically is selected, not Do not change system proxy. Then check that the proxy address and port in system settings match v2rayN's actual listening address and port. Make sure the app uses system settings and doesn't have its own proxy, extensions or exception rules. Reconnect after making changes. If the logs show the app's request going out through direct, check routing rules rather than setting the system proxy again.
A subscription updated yesterday but fails today. What should I do?
Keep the existing entries; don't delete and recreate the group. Update only the group that's failing and note the logs. For a request timeout, check the current network and whether the URL is reachable. For a 401 or 403 response, check the subscription credentials, expiration and access permissions. If the request succeeds but parsing fails, confirm the response is subscription content supported by the client, not a login or error page. If the provider issued a new URL, replace it in the existing group and update again. Remove the full URL and credentials before sharing troubleshooting logs.