From Project V to V2Fly and Xray
Project V is an open-source proxy ecosystem built around V2Ray. It breaks protocols, transports, routing, and other components into configurable parts, providing cores that graphical clients can use. The V2Fly community continues V2Ray’s maintenance, while Xray developed from a fork of V2Ray code and follows its own maintenance path. Similar-looking configuration fields don’t mean the two implementations are identical. When following a guide, check which core its examples use and whether the fields shown are actually generated or read by your client.
What each client does
v2rayN is an open-source desktop GUI client for managing subscriptions, cores, and local proxy settings. v2rayNG is an open-source Android GUI client that uses Xray and routes traffic through the system VPN service. v2flyNG is another open-source Android GUI client; it uses V2Fly and is suited to configurations known to require that core. A client’s name tells you about its interface and installation, but not whether a configuration will work: the protocol, transport parameters, and server requirements still need to match. When comparing screenshots in a guide, distinguish the main screen from subscription editing and runtime settings.
What open-source licenses mean
The V2Fly V2Ray core is licensed under MIT, while the Xray core uses MPL 2.0. The former permits code reuse subject to conditions such as retaining relevant notices; the latter requires source availability for covered files when distributing modified software. Cores, clients, and their dependencies may each use different licenses, so a core’s license doesn’t automatically apply to the whole installer. For everyday use, this distinction helps separate using software from redistributing code. If you plan to modify or distribute software, read the relevant project’s license.
Check the client, core, and rules separately when updating
A client update may change menus or how configurations are saved; a core update may change protocol support or parameter validation; and a routing data update may change how certain destinations are matched. They don’t necessarily update together. Before updating, note your commonly used groups and proxy mode, and save custom local rules. Afterward, test a configuration that used to work before enabling per-app settings or custom routing. If something breaks only after an update, identify what changed most recently. Changing the core, rules, and proxy mode all at once makes the results difficult to compare.
Identify the problem layer from the symptoms
If a subscription update fails, first check whether the client can fetch it. If an imported entry won’t start, check the core’s error. If the core starts but only one app can’t connect, check whether that app is using the proxy. You can also test another app that honors system proxy settings to avoid mistaking an app-level network setting for a server problem. When reporting an issue, include the steps taken, where it failed, and the exact error text. Before sharing logs, remove subscription URLs, credentials, and identifying account details.