v2ray.cn · practical reference
This page is more than a row of download buttons. It keeps release verification, first-run setup, configuration import, and fault isolation in one place so each visit starts from a known, repeatable process.
This addition emphasizes configuration imports and change records so every adjustment can be rolled back.
v2rayN is a graphical client, while V2Ray or Xray may provide the core it manages; subscriptions and share links provide server configuration. Record their versions separately when troubleshooting.
Decide what you are trying to do before opening another download or guide page.
| Download or update | Confirm the project release page, operating system, CPU architecture, and package format. |
|---|---|
| Installed but not working | Check that a valid configuration is imported and active, then verify proxy mode and permissions. |
| Connection stopped working | Separate configuration, endpoint, local network, DNS, and stale system-proxy causes before reinstalling. |
| Move to another device | Back up required data, record current version and paths, then restore one item at a time. |
Versions change and search snippets become stale. Return to the project Releases page and compare tag, date, filename, and checksum. A mirror transports a file; it should not be the only evidence of authenticity.
On first launch, complete only one small loop: start the client, import one known-good configuration, select an available item, enable the required proxy mode, and test one clear destination. Add DNS, TUN, or rule overrides only afterward.
App will not start: check system requirements, runtime, permission, and security logs.
Import is empty: verify the URL, expected format, and explicit log error.
Connected but no browsing: compare system proxy and TUN, then inspect DNS and stale proxy settings.
Only some apps fail: confirm whether they honor the system proxy before changing TUN.
Failure after update: back up first, read release notes, and separate incompatibility from a software bug.
Subscription URLs, recovery phrases, private keys, credentials, and debug logs may contain secrets. Redact them before screenshots or support requests; never paste them into unknown online checkers or permanently disable platform protection.
These existing pages are ordered around download, setup, and troubleshooting tasks.
Use these links to confirm project identity, release history, and current documentation.
Use the official release tag, filename, and checksum as the baseline. A mirror may change delivery speed, not the identity or hash of the file.
Reinstallation cannot fix an expired subscription, an invalid configuration, DNS failure, or a stale system proxy, and it may erase useful logs.
Use the architecture reported by the operating system. Intel and AMD PCs are usually x64; Apple Silicon and some Windows devices use arm64; Android users should inspect the ABI.
A useful download center answers more than where to click. It helps confirm the project, choose the correct build, verify the file, and complete the first working run without mixing several unknowns.
A V2Ray / v2rayN download overview from v2ray.cn covering official sources, Windows, macOS, Linux, Android, CPU architecture, package formats, verification, and first run.
An original V2Ray / v2rayN guide for Windows: requirements, CPU architecture, package format, installation, permissions, first run, updates, and troubleshooting.
An original V2Ray / v2rayN guide for macOS: requirements, CPU architecture, package format, installation, permissions, first run, updates, and troubleshooting.
An original V2Ray / v2rayN guide for Linux: requirements, CPU architecture, package format, installation, permissions, first run, updates, and troubleshooting.
An original V2Ray / v2rayN guide for Android: requirements, CPU architecture, package format, installation, permissions, first run, updates, and troubleshooting.
A complete V2Ray / v2rayN workflow from source verification and installation through first run, configuration or account preparation, validation, advanced settings, and rollback.
Diagnose V2Ray / v2rayN install failures, startup errors, import problems, ineffective connections, partial application failures, and post-update issues.
Answers about V2Ray / v2rayN sources, releases, architecture, installation warnings, imports, system proxy, TUN, logs, updates, and privacy.