V2Ray Beginner FAQ: Cores, Clients, Subscriptions & Connection Issues

1. What are V2Ray, Xray, and a client?

Think of the configuration interface and the software that actually handles traffic as separate parts. V2Ray is a proxy software project; its core listens on local ports, applies routing rules, and connects to remote servers. Xray is a core in a related but separate technology ecosystem. Its protocol support and configuration details differ, so the names alone don't tell you whether the two are interchangeable.

• Client: Provides the server list, subscription management, system proxy controls, and logs. It also generates or loads the core configuration.
• Core: Applies inbound, outbound, DNS, and routing settings. A client interface starting successfully doesn't mean the core is listening on its port.
• Server: Provides a remote address and authentication details. Installing a client doesn't give you a working server.

v2rayN is a desktop client that can manage different cores. v2rayNG is an Android client built around the Xray core, while v2flyNG uses the v2fly core. If you see an error that a configuration field isn't supported, check the core and version actually in use rather than relying on the client name alone.

2. Which should you choose: v2rayN, v2rayNG, or v2flyNG?

Start with your operating system, then check compatibility with your node's settings. Use v2rayN on desktop; on Android, choose between v2rayNG and v2flyNG. Don't apply desktop instructions for setting a system proxy directly to Android: Android typically routes device traffic through a system VPN permission, which works differently.

3. What's the difference between a subscription link and a single-node link?

A subscription link is usually a remote URL that the client fetches to get a list of nodes. A single-node share link contains the connection details for one node. A successful subscription update only means the content was retrieved and parsed; it doesn't mean every server in the list is online or that your account still has available data.

• Subscription URL: Often starts with https://, but regular web pages can too, so the prefix alone isn't enough to identify one. Use the subscription URL explicitly provided by your service.
• Node share link: Common prefixes include vmess:// and vless://. These aren't subscription URLs; don't paste them into a subscription URL field.
• Full configuration: A JSON file may include inbounds, outbounds, and routing rules; it's not the same as a node list. Import it through the client's custom configuration option.

Treat your subscription URL like a credential. Don't show its token, node UUIDs, or passwords in public screenshots. When moving to a new phone or computer, don't post the full URL in a public forum for convenience. If it has been exposed, reset it through your provider's account page.

4. How do you add and update a subscription in v2rayN?

Keep your current working configuration, then add a separate subscription group so you can tell its source apart. The steps below use common v2rayN menu names. If your version uses buttons instead, look for subscription group settings. Don't import a subscription URL as a single node.

1. Create a group

   Open “Subscription Group” → “Subscription Group Settings,” add a group, and enter a recognizable label and the full subscription URL. Check that there are no spaces or line breaks at either end.

2. Update the subscription

   After saving, open the “Subscription Group” menu and select “Update All Subscriptions (without proxy).” First check that a direct fetch works; don't rely on a proxy update before you have a working proxy.

3. Check the results

   Review the update message and the number of servers in the group. If it returns zero records, first check whether the URL returns a login page, an expiration notice, or content the client can't parse. Don't immediately delete the whole client.

4. Select a server

   Select a server in the list, then use the context menu's “Set as active server” option. Once the core has started, enable the system proxy and test a webpage.

Try updating “through a proxy” only if you already have a working proxy and direct access to the subscription URL is blocked. Check the current settings screen for the auto-update interval's units; don't confuse minutes with hours. More frequent updates won't improve server quality.

5. Do you need to enter VMess, VLESS, and TLS settings manually?

Use a share link or subscription generated by your provider whenever possible to avoid manual entry errors. VMess and VLESS are protocol names; TLS is a security layer, and transport is a separate setting. These fields must match the server configuration—they aren't independent speed controls.

• Address and port: Make sure you're entering the server address, not a subscription URL or management page. Use the port the server is configured to listen on.
• Authentication: Check that fields such as the UUID are complete. VMess also requires the device clock to be accurate; a significant time difference can cause authentication to fail.
• Transport: Keep WebSocket settings such as the path and Host exactly as provided. A missing slash or different capitalization in the path can affect the connection.
• Security: When TLS is enabled, check the server name, certificate trust, and device clock. Don't disable certificate verification as a routine fix.

For example, if the server requires WebSocket and TLS, entering only the address and UUID may not be enough to connect. For any unfamiliar fields, check whether the core supports them and ask your provider for details. Don't replace an existing node's settings with a full block copied from another guide.

6. What's the difference between a system proxy, TUN, and a local port?

A system proxy sends requests from apps that honor the operating system's proxy settings to a local listening port. TUN uses a virtual network interface to capture traffic, with different coverage and permission requirements. Test your browser using the system proxy first, then consider TUN if needed; this keeps troubleshooting simpler.

In v2rayN, check the local listening ports and related options under “Settings” → “Parameter Settings.” HTTP, SOCKS, and mixed listeners may be configured differently across versions, so don't assume every port accepts the same proxy protocol. The numbers above distinguish address roles; they aren't default settings for every installation.

7. What do global mode and routing rules control?

The system proxy determines whether an app sends traffic to the client; routing rules determine how traffic received by the client leaves. These are separate layers. “Global” usually means that captured traffic uses the proxy outbound. It doesn't mean every app is captured, and it doesn't enable TUN.

• Direct: Connects your device to the destination without a remote proxy server. Some local services and LAN addresses should stay on direct connections.
• Proxy: Sends matching traffic through the proxy outbound. The remote connection still needs to succeed.
• Block: Rejects matching requests. If a block rule matches by mistake, switching nodes repeatedly won't fix it.

Standard V2Ray/Xray routing rules are evaluated in order; the first match determines the outbound. Domain and IP rules rely on different information, and DNS resolution strategy can affect the result. To get started, use a routing preset provided by the client. If only one site fails, check the logs and adjust the relevant rule instead of permanently sending every destination through the same outbound. For more on routing, see the advanced handbook.

8. Why won't webpages load even though the client says it's connected?

The VPN icon in Android's status bar mainly indicates that the local VPN service is running. On desktop, a running core only confirms that the local process exists. Neither proves that remote authentication, DNS resolution, or the request to the webpage has succeeded. Check the connection from the local end outward rather than repeatedly clicking Connect.

1. Check locally: Did the core fail to start? Is its listening port already in use? Does the browser have its own proxy extension or manual proxy settings enabled?
2. Check traffic handling: On desktop, confirm that “Set system proxy” took effect. On Android, make sure the target app isn't excluded from per-app proxying.
3. Check the remote end: Try another server from the same subscription and check your account's expiration date, data allowance, and node settings.
4. Check the request: Test two different websites. If only one fails, focus on that destination's DNS, routing, and any server-side restrictions.

A successful latency test doesn't prove that a webpage will load. A TCP connection test, a proxy request test, and a real page-load check don't cover exactly the same steps. Note which tests pass and which fail; that's more useful than simply saying “it won't connect.”

9. How should you interpret common log errors?

Note when the failure happens, reproduce it once, then read the surrounding log entries. An address in an error could refer to the local listener, a DNS server, a remote node, or the final destination; context matters. These are common error snippets, though the exact wording may vary by system and core version.

Before sharing logs, redact subscription tokens, UUIDs, passwords, and other authentication details. Keep the exact error, timestamp, client and core versions, and steps to reproduce. Don't share only the final “failed” line, and don't publish a full configuration containing credentials.

10. What settings should you keep after the first successful setup?

Keep a known-working baseline: one active server, one traffic-handling method, and one routing preset. Change one setting at a time and revert it if something breaks. This makes it easier to tell whether the issue came from a new rule, a DNS change, or the node itself, and avoids turning a working setup into an unrepeatable one.

• Note your operating system, client version, core version in use, and local listening port.
• Keep a record of your subscription source and account management method. Store backups somewhere only you can access.
• After closing the client, confirm that the system proxy has been cleared so your browser won't keep pointing to a stopped local port.
• If you need to start over, follow the quick-start guide to get the simplest working setup first, then restore your custom rules.