Download a V2Ray client

Import your subscription, then configure the proxy

In v2rayN, add your subscription URL and update it. Confirm nodes appear in the list, then set the node you want to use as active. A subscription URL and a single-node share link are different: use subscription management for the former and clipboard import for the latter. Saving a URL to a group without updating it may leave the node list empty.

Start by testing system proxy with apps such as browsers that follow system proxy settings. Some apps have their own network settings and won’t use the system proxy; consider TUN for those cases. TUN involves a virtual network adapter and routing, so don’t enable multiple traffic-capture methods just because a page won’t load. Before closing the client, clear the system proxy to prevent other apps from trying to use a local port that is no longer available.

Before switching from WPF to Desktop, back up your subscriptions, routing rules, and custom settings. Don’t run both editions at once on the same local listening ports, and don’t assume separate install directories share a configuration. After migrating, check the active node, system proxy status, and startup options before removing the old installation.

Tell startup restrictions apart from connection issues

If macOS shows a security prompt the first time you open the app, confirm that you downloaded it from the option selected on this page, then check Privacy & Security in System Settings. Address the prompt for this app rather than disabling system-wide protections. An app that won’t launch and one that launches but can’t connect are different problems; track them separately while troubleshooting.

Once the app opens, import your subscription, update it, and choose a node. Whether desktop apps use the proxy depends on whether they follow system settings. Browser proxy extensions may override the system setting. To test a connection, use one proxy method at a time so system proxy, app-specific settings, and other network tools don’t redirect traffic simultaneously.

If you need TUN, follow the client’s prompts to grant permissions. If authorization fails, note the specific error in the logs and check for conflicts with virtual network adapters or existing network extensions. Quit the running client before updating, and keep a backup of the original configuration. After replacing the app, check the menu bar and subscription groups to confirm the new instance is using the expected configuration location.

Install the APK and connect for the first time

When the download finishes, open the APK in your file manager. If Android blocks the installation, check whether the issue is source permission, the system version, or an architecture mismatch instead of repeatedly downloading the same package. Most phones released since 2015 support arm64, but hardware and the architectures supported by the operating system don’t always match. Check what your device can actually install.

After importing your subscription, update it and select a working node. Tap Connect and approve Android’s VPN request. A VPN icon only means the traffic-capture service has started; it doesn’t confirm that the remote node is working. Visit a test page and check the logs for DNS resolution and connection results. If another VPN app is running, quit it before testing.

If the connection often drops when the screen is locked, check battery optimization, background activity, and the device manufacturer’s auto-start settings. Adjust only the settings needed for the selected client; you don’t need to allow all background activity. For per-app proxying, check that the target app is included. Routing exclusions and node failures affect different sets of connections.

See how to import a subscription in v2rayNG →

Keep package manager error messages

Open the downloaded file with a graphical package installer. If it reports dependency errors, check that the distribution and package target match your system; don’t force the installation by ignoring dependencies. The rpm filename includes build environment details, but that doesn’t mean it works on every RPM-based system. The installer’s list of missing components and version requirements is the best way to assess compatibility.

After first launch, import your subscription and update the nodes, then check the system proxy settings in your desktop environment. Linux apps don’t all handle system proxy settings the same way; graphical browsers, command-line programs, and background services may use different proxy settings. If a browser works but another app doesn’t, first check whether that app uses a proxy before changing nodes.

Before enabling TUN, confirm that a virtual network device is available and grant only the permissions the client requires. Save your existing configuration if you use container networking, another VPN, or custom routes. If the network acts up after you turn TUN off, check whether routes and DNS settings have been restored instead of reinstalling the client repeatedly.