Project V and the core ecosystem
Look at the project ecosystem, runtime core, and graphical client separately. Similar names don’t guarantee identical configuration fields, release schedules, or feature sets.
What clients and cores do
v2rayN, v2rayNG, and v2flyNG are all open-source graphical clients, but they aren’t simply the same program with different names for different operating systems. Clients manage subscriptions, display servers, save interface settings, and prepare configurations for the core. The core then uses those configurations to establish connections, handle transports, and apply routing. So a client opening normally doesn’t mean the core started successfully, and a subscription updating successfully doesn’t mean its server settings are suitable for the current core.
v2rayN is designed for desktop systems and can manage configurations for different cores; available features depend on what’s installed and shown in the interface. v2rayNG and v2flyNG provide Android interfaces built around the Xray and V2Fly ecosystems respectively. When migrating, transfer standard share links or subscriptions first, then review device-specific settings. System proxy ports, TUN permissions, per-app routing lists, and file paths usually can’t be copied directly from another device.
Open-source licenses and configuration privacy
Open source means the program’s source code is available under its applicable license for review, use, and contributions subject to that license. The v2rayN, v2rayNG, and v2flyNG client projects use GPL-family licenses; the V2Fly and Xray core projects use MPL 2.0. Clients, cores, and their dependencies are separate licensing matters. When distributing or modifying software, read the licenses provided with each component rather than relying on the name of just one project.
Open-source status doesn’t remove the need to evaluate remote services and configuration sources. Subscription URLs may contain account identifiers, and share links may include authentication details. Before asking for help, hide full URLs, user IDs, passwords, and key fields; share only the error and the relevant setting names. Don’t paste real configurations into unfamiliar websites to convert formats. Our glossary explains parameter meanings without requiring you to submit personal configuration data.
Update clients, cores, and rule sets separately
Updating the interface, updating the runtime core, and updating GeoIP or GeoSite are separate operations. A client update may change menus or subscription parsing; a core update may add field support or change validation; a rule-set update changes category matches. If something breaks, note which layer changed. Updating everything at once makes it difficult to identify the cause.
Back up working configurations before updating, and note the routing profile and proxy entry point you use. After updating, test a configuration that worked before before trying new settings. If the log reports a missing category, check the rule set; if it reports an unknown field, check core compatibility; if only one app has a problem, check that app’s proxy settings. This process can save you from reinstalling components unrelated to the issue.
Connection checks versus speed test results
TCPing, real-connection latency tests, and download speed tests measure different stages. A successful TCP connection to a port doesn’t prove that the proxy handshake, DNS resolution, and destination website are all working. Real-connection tests are also affected by the test endpoint, routing, and DNS. Download tests depend more on transfer duration, the destination service, and current network conditions. Before comparing results, make sure you’re using the same test method under the same conditions.
For a first setup, test access to a specific destination, then check where the logs show an error. A test that returns no value doesn’t prove every configuration is broken, and a successful port test doesn’t explain why an app can’t connect. If you’re unsure what a test measures, read the speed-testing guide before changing servers, DNS, or routing rules.