v2rayN docs

v2rayN is a graphical client for Windows, macOS, and Linux. It manages cores such as Xray and sing-box, and keeps servers, subscriptions, routing, and network settings in one window.

Yes. v2rayN is open source, and the project is hosted on GitHub.

v2rayN currently has desktop builds for Windows, macOS, and Linux. Download the build that matches your system and processor. Packages follow the current GitHub Releases.

No. v2rayN is the client. It imports, manages, and uses connection profiles. You provide the server, subscription, or other connection details. This site does not host them.

v2rayN supports cores such as Xray and sing-box, and can manage profile types including VLESS, VMess, Trojan, Shadowsocks, SOCKS, and HTTP. Support can change with the core and the release. See supported cores and protocols.

Add a profile from a share link, a QR code, or a subscription, or create one by hand for the protocol you use. After it is imported, it appears in the server list.

A subscription collects and maintains several server profiles. Add your own subscription address in v2rayN, then refresh it to pick up the latest profiles instead of editing each server by hand. This site does not fill in or store subscriptions.

Check that the profile is valid, a server is selected, the core started, and the system proxy or TUN mode is on for the way you are using the client. If it is still failing, read the client log and the core log. Issues in v2rayN itself are mainly in guiLogs. Core output is available from the information area in the main window.

The system proxy uses the operating system’s proxy settings for apps that follow them. TUN mode uses a virtual network interface and can cover a wider range of traffic. For everyday use, start with the system proxy. Look at TUN mode when a specific app or a more involved traffic setup needs it.

Apps do not all honor the operating system proxy. Some keep their own network settings. Check that app’s proxy options, or consider another way to handle its traffic. System proxy behavior also differs by operating system.

TUN depends on a virtual adapter, DNS, routing, the core, and the operating system’s network setup, so more than one thing can be involved. Confirm you are on the current release, then check the TUN, DNS, and routing settings and read the logs. There is no single fix for every environment.

DNS is tied to TUN, the core, and routing. No single setup fits every network. v2rayN includes direct DNS, remote DNS, and related advanced settings. If name resolution fails, check the core you are using, the operating system, and the logs.

Routing rules decide which outbound connection handles each kind of traffic. For example, traffic that matches a rule can use the proxy, while other traffic uses a different connection.

On macOS, automatic system proxy setup runs a script. If that script does not succeed on the machine, check the related entries in guiLogs.

You can allow LAN connections in settings, then set the listen port, the firewall, and the proxy settings on the other devices. This exposes the service to other devices on the LAN, so keep the network and who can reach it in mind.

The portable build can be copied into separate folders and run as more than one instance. Each instance needs its own local listen port so they do not conflict.

Back up important profiles and client data before you update. Where that data lives can differ by package, install method, and major version. Read the release notes for the version you are moving to.

Include the v2rayN version, the operating system version, the core, the steps to reproduce the problem, and the logs. For issues in the window, settings, speed test, or updates, check guiLogs. For core problems, also include the core output. “It does not work” alone is usually not enough to find the cause.