-
Project V: Why the client and core are separate
Project V is a useful starting point for understanding this ecosystem. Early V2Ray focused on separating inbound connections, outbounds, and routing into composable configuration. Inbounds accept connections, outbounds send them onward, and routing selects between outbounds. This separation means the app initiating a connection, the core forwarding traffic, and the graphical interface managing configuration don’t have to be part of one program. Desktop and mobile clients developed by the community provide a more convenient way to work with these components.
This history helps when troubleshooting. Seeing a subscription entry in the client only means the interface has data. To confirm the configuration loads, check the core’s startup result; to see whether an app’s traffic reaches the core, check how that traffic enters. Confusing these steps often leads to repeatedly importing a subscription when the real issue is that the app isn’t using the proxy at all.
-
V2Fly and Xray: Shared roots, separate development
The V2Fly community continued developing and maintaining the V2Ray core. Xray forked from that codebase, and the two projects have since evolved independently. They share similar configuration concepts, and some protocols and fields may look alike, but a shared origin doesn’t guarantee compatibility. In particular, one core may handle a newer transport or security-layer option differently from the other. Check what the server requires, then confirm which core your client is using.
When moving to a new device, don’t assume you should copy over the entire configuration. The parameters for an individual connection, subscription groups saved by the client, and local listening ports and system proxy settings are separate layers. Start by moving a connection entry and testing it on the new device, then add routing rules back one at a time. If it fails, you’ll have a better chance of telling incompatible parameters from local settings that still need to be configured.
-
Open-source licenses aren’t proxy protocols
VMess and VLESS describe how two endpoints exchange data. Open-source licenses define how code may be used, modified, and redistributed. They address entirely different things. The V2Fly core uses the MIT License; Xray-core uses the Mozilla Public License 2.0. The MIT License has fewer redistribution requirements but still requires preserving relevant copyright and license notices. Under the MPL, obligations mainly apply to covered files; if you distribute changes to those files, you must make the corresponding source available under its terms.
Components are maintained separately, so check their licenses separately too. Don’t assume the graphical client, bundled core, and other components share the same terms just because they came in one installer. You don’t need to read every license before setting up a client, but if you plan to repackage, modify, or publish a derivative version, review the license included with each component. Proxy service accounts, plans, and terms of use are set by the service provider, not by open-source licenses.
-
How three clients fit different configuration needs
v2rayN is an open-source desktop client that brings subscription groups, connection selection, routing, and system proxy settings together in one interface. It suits users who manage multiple configurations or need to troubleshoot traffic from different apps. v2rayNG is an open-source Android client that uses the Xray core; v2flyNG is also open source and uses the V2Fly core. You don’t need to install both just because their names look alike. Choose one based on the server parameters and the core it supports, test a basic connection, then compare the settings if needed.
When describing an issue, include the app name, core, and steps that triggered the error. That’s more useful than a screenshot that only says “connection failed.” Did a subscription update fail to retrieve data? Did the core report an error after you selected an entry? Or does just one command-line tool bypass the proxy? Each points to a different place to check. When sharing logs, include timestamps, steps, and error types, but redact subscription URLs, account details, and sensitive server parameters.
-
Client updates, core updates, and subscription refreshes
A client update may change menus, installation, or how settings are stored. A core update may change supported fields or startup behavior. A subscription refresh simply fetches the latest entries from the provider. These changes aren’t interchangeable. Before updating, note the selected entry, core, routing mode, and local listening port. Back up any custom rules you need to keep. Change one layer at a time and retest with the same app and destination so you can tell what caused the difference.
If every app stops working after an update, check whether the core started and whether the inbound is listening. If only one app is affected, check that app’s own connection settings. If a subscription refresh removes entries, confirm which group you updated and whether the provider actually removed them before overwriting local configurations. For step-by-step help, see the all-platform guide. If the connection works but traffic takes the wrong route, start with the routing and proxy articles in the Help Center.