Project V, cores, and clients
Documentation often uses “V2Ray” as shorthand for the client, core, and protocol. Keep these three layers separate when troubleshooting: the interface manages settings, the core reads them and establishes connections, and the protocol defines how the two ends exchange data. Identify the layer that’s failing before deciding what to change.
Compare the three clients →
Project V and V2Fly
Project V is a good starting point for understanding the ecosystem. V2Ray is its core program for handling proxy connections and routing. The V2Fly community continues to maintain related core software and documentation, while desktop and mobile graphical clients are maintained by their own projects. When following core documentation, don’t expect to find every field under the same name in a graphical interface: a setting may appear under subscriptions, routing, or transport—or may not have a dedicated control at all.
To check whether documentation applies, first see whether it describes a graphical interface or core configuration, then check that its operating system and core family match yours. For example, an inbound port in core documentation is where the client receives requests on your device; it isn’t the remote server’s port in a subscription. Confusing the two can make websites appear unreachable, but the relevant logs differ. For the former, check the local listener first; for the latter, review the connection settings.
V2Fly and Xray compatibility
Xray originated in the V2Ray ecosystem and has since been developed independently. The two core families share support for some protocols and configuration concepts, but each also has its own transport and security features. Configuration names alone don’t tell you whether a setup is compatible: two configurations using the same protocol may still use different transports or require different security fields. Keep the original parameters from the subscription and choose a core based on the provider’s documented combination. Don’t piece together settings from another connection.
If apps still can’t connect after you switch cores, check the first error in the startup logs. An unrecognized field usually points to a compatibility issue; a local address that can’t be bound usually means the port is in use. Check remote connectivity and the handshake only after confirming that the core started successfully and requests are passing through it. This helps distinguish failures at three different stages instead of attributing them all to an expired subscription.
Protocol names and connection requirements
Open-source clients and cores make their configuration fields and protocol implementations available for inspection. VMess, VLESS, Trojan, and Shadowsocks are protocol names, not interchangeable options for any configuration. A connection works only when both ends agree on the protocol, transport, and required security settings. In particular, VLESS isn’t an encryption method; check the specific configuration to determine which security layer it uses.
For your first connection, use the original combination provided with the configuration as a baseline. If the handshake fails, first check the address, port, transport, and security settings, then verify the device’s clock. Switching protocols requires the other end to provide a matching configuration; changing one client setting can’t convert an existing connection to a different protocol. To find an option that fits your device, first compare core support, then consider your network and device requirements.
What sets the three open-source clients apart
v2rayN brings desktop subscription, routing, and proxy settings together in a graphical interface. v2rayNG is a mobile client built primarily around the Xray core and routes traffic through the system VPN interface. v2flyNG is another open-source graphical client for configurations that specifically require the v2fly core. Choose based on what your device can run and what core your configuration requires—not on similar names or icons.
When using the same subscription across devices, import it again and check the proxy setup for each platform. Desktop system proxy settings don’t carry over to a phone, and VPN permissions and per-app settings on a phone don’t carry over to a desktop. If only one device connects, select the same configuration on both and compare the core and network environment. Matching group names don’t prove that both devices are using the same connection.
Clients, cores, and subscriptions update separately
Client releases, core updates, and subscription refreshes are three different things. A client update may move menus or change installation requirements; a core update may change which fields it recognizes; refreshing a subscription rereads the configuration list from its original URL. Back up your groups, routing rules, and other settings before replacing an installer. After updating, test one change at a time: first confirm the program starts, then test a known working configuration, and finally restore your custom routing rules.
If an issue starts right after an update, note when it happened, which platform you’re using, and what action triggered it, then collect the relevant logs. When sharing a log excerpt, include the first error and a few surrounding lines. Remove subscription URLs, identity parameters, and any destination addresses you don’t want to share. If only one subscription group is affected, check that group’s update results; there’s no need to delete other groups that still work. Visit the help center →