Check OS, architecture, and version separately
The operating system determines which file type can open, the architecture determines whether the program can run on your device, and the version affects upgrade order and configuration compatibility. When switching devices, check the new device instead of reusing the old download. Even if two computers use the same client, different operating systems or chips may require different packages.
When comparing versions, rely on the information shown in the app and the installer prompts. The version listed on the download page comes from a manifest, and the filename may also contain a version number. If they don't match, don't decide whether to install over the existing version based on just one number. If the installer warns that it's downgrading the app or replacing a version from another source, cancel and check the app details and backup status in the old client first.
Back up local settings before upgrading
A subscription URL isn't a full backup. Locally added configurations, custom routing rules, auto-update intervals, and proxy ports may not be restored from a subscription. If the client offers an export feature, use it; otherwise, make a note of the key settings. After backing up, quit the old version and keep a recoverable copy. Delete it only after you've confirmed the new version imports your settings and connects successfully.
Use a connection test to separate installation from configuration issues
First, make sure the main window opens. Then follow the subscription import guide to save the URL and update the group. Once configurations appear, select one to test. “The client opens,” “the subscription updates,” and “app traffic is routed as expected” are three different outcomes. Note where the process fails; that makes troubleshooting easier than reinstalling.
For an initial desktop test, check system proxy settings and use an app that follows the system settings. On mobile, first confirm that the system allows the client to establish a VPN connection. Change one setting at a time, and avoid running two clients simultaneously. If something goes wrong, revert your last change before deciding whether to adjust routing or DNS.
Keep relevant context when sharing error details
Note your operating system, client name, package architecture, and the step where the error occurred. During installation, keep the exact error reported by the system; during connection tests, share only the relevant log entries. Remove full subscription URLs, credentials, and private server addresses from screenshots or logs before sharing them. For core differences, see the core section in the full handbook.