v2rayN · v2rayNG · v2flyNG FAQ

V2Ray Client FAQ v2rayN Setup

From choosing a client to importing subscriptions, follow the actual menus to configure routing and proxies.

  • VMess
  • VLESS
  • Trojan
  • REALITY
Core families

Xray
V2Fly

GUI and core: different roles

Client setup FAQ

Find the right setting for your question

Before changing settings, distinguish the server address, protocol, and proxy entry point. The menu names below help you locate features; their layout may change between client versions. If you can't find an option, first check whether you're using the desktop or Android app.

Protocols and transports

Match the server configuration before choosing a client

The server configuration determines the protocol; changing its name to VLESS won't make a connection work. When importing VMess, VLESS, or Trojan share links, keep the address, port, credentials, transport, and security settings intact. REALITY is a security mechanism, not a standalone proxy protocol. For a first setup, import the complete link rather than guessing each field. If the client doesn't recognize a field, check core compatibility. A GUI client makes fields easier to review than editing a configuration by hand, but you still need the exact parameters supplied by the server.

Protocolvless
streamSettings.securityreality
Browse protocol definitions →

Client downloads

Choose a package for your OS and architecture

For desktop systems, start with v2rayN; for Android, start with v2rayNG. Check your device's architecture before choosing an installer. Matching protocol names don't guarantee that every client supports the same additional parameters. The links below open the relevant platform section on the download page; they don't start a download directly.

Windows

v2rayN offers Desktop and the classic WPF edition. Desktop uses a cross-platform interface, while WPF retains the classic desktop experience. If you're new to v2rayN, start with the option recommended on the download page; there's no need to install both. Check the OS version and runtime requirements first. Keep portable apps in a fixed folder so clearing your downloads doesn't move the app or its configuration.

After launch, import a subscription and select a working configuration before setting the system proxy. Closing the window may only minimize the app to the system tray, so check the proxy status before quitting. If your browser can't connect after you exit, make sure the system proxy isn't still pointing to a local port that is no longer running.

Go to downloads · Windows

macOS

The v2rayN downloads for macOS are listed separately for Apple Silicon and Intel. Open “About This Mac” from the Apple menu: devices showing an Apple chip generally need arm64, while those with an Intel processor need x64. Don't infer the architecture from the computer's purchase year or mistake architecture variants for different feature editions.

Move the app to Applications before launching it. If macOS shows a security warning on first launch, verify the source and read the system guidance; disabling system-wide security to open one app isn't recommended. System proxy and TUN permissions are different, so grant them only as needed. If the connection fails, switch back to regular proxy mode for troubleshooting.

Go to downloads · macOS

Android

We recommend v2rayNG with the Xray core; v2flyNG, based on the V2Fly core, is another option. Most recent phones use arm64 packages. If you aren't sure of your device's architecture, check system information or use the universal package listed on the download page. Check the configuration and feature support for each client separately; don't assume their exported files are fully interchangeable.

On the first connection, approve the system VPN request. Other VPN apps in the same user profile may compete for the connection slot. If the connection drops after running in the background, check battery optimization and background activity permissions, then review the client logs. A dropped connection doesn't necessarily mean the subscription has expired.

Go to downloads · Android

Linux

v2rayN for Linux comes in deb and rpm packages for x64 and arm64. Desktop users on Ubuntu or Debian-based distributions generally need deb; Fedora and similar distributions generally use rpm. Choose the package format for your distribution and the architecture for your device. Before opening a package in the graphical installer, review the desktop environment and dependency requirements on the download page.

Desktop system proxy settings aren't used by every app. If your browser works but another program can't connect, check that program's own proxy settings before reinstalling the client. To start the app automatically after login, first verify that manual launch and exit work as expected; then enable autostart to avoid leaving duplicate instances running in the background.

Go to downloads · Linux

Quick-start preview

Three steps: import, select, test

After downloading a client, you'll still need a working server configuration or subscription URL. The client doesn't generate server connection details. Get a link from a trusted source, then follow these steps in order. If something goes wrong, troubleshoot the current step before changing other settings.

Step 1 · Add a source

Add the subscription URL to a group

On desktop, open “Subscription Groups” in v2rayN, enter a recognizable name and the full URL, save, then update. On Android, open “Subscription Group Settings” in v2rayNG, add and enable the group, return to the home screen, and update. Saving the URL alone doesn't fetch server entries. Confirm that the group appears in the list before moving on.

If you have a single share link starting with vmess:// or vless://, import it from the clipboard or scan its QR code; don't enter it as a subscription URL. Subscription links often contain access credentials, so hide the full URL in screenshots and support requests to avoid exposing a working configuration.

v2rayNG menu path

Subscription Group Settings

Add group → Enter a name and URL → Save

Return to home → Update subscriptions → Check the group entries

Step 2 · Set the traffic entry point

Select a configuration, then enable the proxy

Select the configuration you want from the server list. In v2rayN, start with “Set system proxy automatically” and a routing preset suited to your needs. In v2rayNG, tap Connect and approve the system VPN request. The proxy entry point sends traffic into the client; routing rules decide which outbound handles it. Check both separately.

For the first connection, keep the default DNS and basic routing, and check only the required settings. Changing the listening port, DNS, ruleset, and TUN all at once makes it hard to identify the cause of a problem. If another proxy or VPN tool is running, stop any potentially conflicting connection before testing.

First connection with v2rayN

Active configuration → System proxy

Select a server → Set system proxy automatically

Test your browser first; consider TUN mode only if needed.

Step 3 · Check the results

A successful startup doesn't guarantee a working connection

A connected status usually means the local proxy service has started; it doesn't prove that the remote server is reachable. First, open a website that normally works to confirm your basic internet connection. Then test a service that should use the current configuration and check the logs for authentication errors, DNS failures, or connection timeouts. Different errors call for different checks—not always a different port.

If your browser works but one app doesn't, first check whether that app follows the system proxy. If no apps work, check the active configuration, subscription status, and network. Before quitting the desktop client, clear the system proxy; on Android, disconnect explicitly. Change one setting at a time to make troubleshooting clearer.

Troubleshooting order

Local entry point → Remote connection

Basic network → Active configuration → Proxy entry point → Logs

Note the error type; hide addresses and credentials before sharing.

Open-source projects and maintenance

What clients, cores, and subscriptions do

Sharing “V2Ray” in their names doesn't mean these tools are the same kind of software. Understand each one's role to make better choices and troubleshoot the right layer.

Project VXrayV2Fly

Project V and the core families

V2Ray grew out of the Project V ecosystem, where the core processes inbound connections, routing, and outbound connections according to its configuration. V2Fly is a community project continuing development of the V2Ray core. Xray developed from related code and now follows its own feature set and development path. They share a background, but their features, configuration fields, and compatibility don't always match. A tutorial using the same protocol name may still rely on a different core, transport, or security setup. Check those details rather than comparing protocol names alone.

What the three GUI clients are for

v2rayN, v2rayNG, and v2flyNG are open-source clients with GUIs for organizing imported configurations and handing them off to a core. v2rayN is for desktop use, with tools for managing subscriptions, the system proxy, and routing. v2rayNG is a common Android option using the Xray core; v2flyNG is an Android alternative based on V2Fly. An option in the client interface isn't necessarily supported by every core or server. The full connection requirements still need to match.

Open-source software and service providers are separate

Open source means the source code is available under the applicable licenses; the terms depend on each project and its dependencies. A free client doesn't mean the client project provides remote server resources. A subscription is a way to distribute configurations, usually collecting multiple server entries at an updateable URL. The subscription provider, GUI client, and core maintainers may all be different organizations. Evaluate service providers separately; a client name doesn't guarantee service quality or availability.

Keep a recoverable configuration before updating

The GUI, core, and routing data may be updated separately. GUI updates mainly affect the interface and configuration management; core updates can change supported fields; routing data updates can change which domains or IPs match. Back up essential settings and note the current proxy mode before updating. Afterward, retest startup, import, connection, and routing one by one. Avoid replacing every component at once in a working setup. Clear notes on what changed are more useful than repeated reinstallations when compatibility issues arise.

Frequently asked questions

Four common points of confusion before and after downloading. Start with the answer, then explore the terms if needed.

Can I use a server as soon as I download the client?

You'll need to obtain a working server configuration or subscription URL separately. The GUI manages connections; the installer doesn't provide a remote service. Once you have a link, distinguish a single share link from an updateable subscription URL, then import it from the appropriate menu. See the glossary for how these link types differ.

Why can't I connect after a successful subscription update?

A successful update only means the client retrieved and parsed the subscription. You still need to check whether the remote server is reachable, the credentials are valid, and the local proxy entry point is enabled. Select the updated configuration and review the connection logs. “Configuration retrieved” doesn't mean “connected.” The glossary explains the difference between a subscription, a server, and an outbound.

Are REALITY and VLESS the same setting?

No. VLESS is a protocol; REALITY is a security mechanism that can be combined with compatible protocols. A connection may also require a transport, server name, and other authentication fields. Entering only one of these names isn't enough. Import the complete parameters provided by the server, and see protocol and transport terms for how these layers differ.

Do I still need routing rules with TUN enabled?

Usually, yes. TUN changes how traffic enters the client; routing rules decide which outbound handles it. Enabling TUN doesn't automatically apply split-routing rules that suit every app, and DNS behavior also needs to be considered. Learn how the two features differ in client and routing terms before changing your current mode.

Blog · Configuration guides

Three recent guides

Clear explanations of commonly confused tasks: package formats, share-link import, and DNS rules each need different checks. Get a basic connection working first, then read guides that match your needs rather than applying advanced examples to an untested setup.