Check system information, not the device model
A device name can help identify the hardware, but it can't tell you the architecture of the system currently running on it. Devices in the same product line may have different chips, and the same processor may run systems with different bitness. Check the system information on the device you're installing to, not the device you're using to view this download page. If you're transferring the installer from another computer, choose the package for the target device.
If the installer won't open, first check whether the system is blocking installation or doesn't recognize the file format. Fully extract archives, mount disk images, and open mobile installation packages with the system installer. If the system recognizes the format but reports that a requirement isn't met, check the architecture, minimum system version, and dependencies. Don't rename the file extension and try again.
Back up subscriptions, routing, and local settings
Subscription URLs, manually added servers, and local client settings are separate types of data. Refreshing a subscription can restore only the configurations provided by that subscription. It won't restore custom routing rules, DNS settings, proxy ports, or startup options you've set yourself. Before upgrading, use the client's backup or export feature if available. Otherwise, record your custom values and rule order.
Subscription URLs and exported files may contain credentials, so keep them somewhere you control. When asking for help, share only the client name, package variant, system architecture, and where the error occurs. Don't post a full subscription URL or attach an unredacted configuration backup.
Confirm the client launches before restoring connection settings
After installation, open the client and check that the interface loads without missing-component warnings. Don't enable startup launch, system proxy, and TUN all at once. Import a known-good subscription group manually, confirm it refreshes, and select the server you want before configuring the connection. If it still fails, check the subscription or connection logs instead of repeatedly switching packages.
When switching desktop interfaces, exit the old client's background process first; closing its window may leave a process holding a local port. When moving to another device, don't reuse the old device's interface names, directory paths, or local ports without checking them. Establish a basic connection with the new device's defaults, then migrate device-independent routing rules one at a time.
Troubleshoot by stage
A download interruption, installer exit, client startup failure, and subscription refresh failure are different problems at different stages. For an interrupted download, retry the same link. If the installer exits, check the system message. If the interface won't launch, check the desktop runtime. Investigate subscriptions and connection settings only after the client starts normally. The first error is usually more useful than working backward from a later follow-on message.
If the basic connection works but custom routing or DNS causes problems, undo the last change and test it separately. Clients and cores may support different setting names and rule formats. When migrating, review each setting in the new client's interface; matching menu names don't guarantee identical behavior.
See how to import a subscription and connect for the first time · Compare the three clients and their use cases