This page explains the boundaries of v2rayN Official Site's responsibility regarding project affiliations, software use, technical content, and external resources. By visiting this site, consulting its tutorials, or using its navigation to obtain a client, visitors acknowledge that they have read and understood the information below. These terms do not replace the software's own license files, project documentation, or applicable law.
1. Project Relationships and Site Positioning
This site is an independent Chinese-language resource for general users. It mainly organizes installation links, configuration steps, and troubleshooting guidance for clients such as v2rayN, v2rayNG, and v2flyNG. It is not the official site of V2Ray, Project V, V2Fly, Xray, or any related client project, nor does it issue statements on behalf of their developers, maintainers, or contributors.
Software names, project names, protocol names, and marks shown on these pages belong to their respective rights holders. They are used solely to identify software, cores, and the broader technical ecosystem accurately; their use does not imply an authorized agency relationship, joint operation, commercial partnership, or other organizational connection between this site and any corresponding project. Matters concerning project licenses, feature scope, and release policies should be determined by the licenses supplied with the software and public information from the project maintainers.
2. Software Acquisition and Usage Risks
The download pages provided by this site serve as navigation to version information and file sources. The software is released by its respective projects under their applicable licenses, while installation, updating, configuration, and operation are decided by the user. Operating-system versions, device architectures, security policies, network conditions, and existing software configurations may affect installation results, compatibility, and runtime behavior.
Before proceeding, users should confirm the device platform, processor architecture, installation format, and configuration source, and preserve any necessary personal settings. Users assume all risks arising from choosing the wrong version, incompatible configuration parameters, system permission changes, conflicting proxy rules, third-party subscription content, or other local-environment factors that cause connection failures, lost settings, service interruptions, or device problems. Before changing a production device or important network environment, validate the changes first under conditions that allow recovery.
3. Tutorial Content and Version Changes
The tutorials on this site are compiled from client versions, interface layouts, and common configuration methods available when they were written or revised, with the goal of providing reproducible steps. As clients continue to evolve, menu names, button locations, default values, core options, and system-permission procedures may change. Screenshots and step sequences may therefore differ from the current version.
This site revises major content as versions change, but does not guarantee that every page is complete, current, or suitable for every device at every moment. Protocol fields, routing rules, and sample configurations in the tutorials explain functional relationships and do not replace the actual parameters provided by a service provider. When the interface differs, first verify the client version, current platform, and configuration source, then assess the issue using log information rather than directly applying settings that do not match the current environment.
4. Subscription Configurations and Network Results
Subscription URLs, server nodes, certificate parameters, DNS records, and routing policies are generally maintained by third-party services or users themselves. This site does not control their availability, speed, duration, or data. Tutorials can explain how to import subscriptions, select nodes, configure the system proxy, use TUN mode, and set routing rules, but cannot guarantee the same results for a particular configuration across all network environments.
Users should verify that configuration sources are trustworthy and comply with applicable laws, network-management requirements, and service terms in their jurisdiction. Connection problems caused by expired subscriptions, changed parameters, server status, network-operator policies, device clock differences, or local firewall rules are outside this site's direct control. During troubleshooting, check the logs, system proxy status, core startup result, and parameter consistency one by one.
5. External Links and Scope of Responsibility
Some pages on this site may link to files, project materials, or other third-party resources hosted elsewhere. External pages are managed independently by their operators; their content, availability, privacy policies, license terms, and future changes are outside this site's control. The presence of a link only indicates relevance to the current topic and does not guarantee any third-party content, service quality, or continued accessibility.
Before accessing external resources, users should read the relevant page information and terms and make their own assessment based on the actual environment. To the extent permitted by applicable law, this site is not liable for indirect losses, data loss, service interruptions, or other consequential effects arising from reliance on information here, access to external links, or installation or operation of related software. Responsibilities that cannot legally be excluded or limited are not affected by this provision.
6. Content Revisions and Feedback
This site may revise this disclaimer and related tutorials in response to client release status, changes in technical documentation, or updates to site content. Revised content takes effect when the page is updated, and the date at the top indicates the month of the most recent overall review. Continued use of this site's content is subject to the version shown on the current page.
If the actual interface differs from the tutorial steps, first consult the categorized troubleshooting guidance in Troubleshooting, or return to Getting Started to review the subscription import, mode selection, connection, and verification process. Feedback should focus on reproducible versions, platforms, steps, and log symptoms; do not submit subscription URLs, access credentials, or other sensitive configuration details.