Before installing or migrating
For a first install, check the target device and package format. If you already have a client, note your current configuration before deciding whether to update it in place or switch clients.
Choosing an installer
Identify the target system's architecture
Architecture labels describe the instruction set a program was built for, not its feature level. For desktop packages, x64, amd64, and x86_64 refer to the same architecture; amd64 also applies to Intel processors that use it. arm64 and aarch64 refer to 64-bit ARM. Mobile operating systems also use ABI labels to indicate which binary interfaces an app supports.
When downloading for another device, ask its user to check the system information first. This matters especially when the same model has different hardware configurations, the device runs a virtual machine, or the processor supports 64-bit programs but the OS is still 32-bit. A device or product name can't replace the type reported by the system. If the installer reports an architecture error, choose a package that matches the target system rather than renaming files or trying compatibility mode.
Download and installation
Tell download, extraction, and installation errors apart
A download in your browser's history doesn't mean the file finished saving. Check its status, make sure the download completed, then open the file from your downloads folder. If a ZIP won't extract, first confirm the download is complete. If a DMG mounts but the app won't open, check whether you copied the app as instructed and note the specific system message. If an APK downloads but won't open the installer, check whether the app you're using to open it has permission to install apps from that source.
Once the system installer opens, note the first clear error message. Permission issues, an unsupported package format, missing dependencies, and version downgrades are different problems. For example, a Linux dependency error occurs during package management and has nothing to do with whether a subscription can update. On a managed device, check the installation policy first; don't change system security settings to get around restrictions.
Updating in place
Keep your configuration and installation source
Before updating in place, check the client version, where its configuration is stored, and what export options are available. You can fetch subscriptions again, but manually added nodes, rule order, local listening ports, and app exceptions may not be restored with them. Prefer the export option built into your current client, and keep any subscription URLs you need somewhere secure on your device. Don't assume configuration folders can be exchanged between different editions or operating systems.
Before upgrading, quit the app and any background processes, then choose an installer for the same platform, architecture, and source. If an update from another source is blocked because of a signature mismatch, and the old version still opens, export your configuration and confirm the backup is readable before doing anything else. Don't start by uninstalling. Before rolling back, check whether the older version can read configurations saved by the newer one; keep a copy of important rules from before the upgrade.
After installation
Launch the client before importing a subscription
On first launch, confirm the app opens and the interface responds before going to subscription management. Add the URL, save the group, and update it; then confirm the entries appear in the intended group. A single share link and a subscription URL use different workflows: the former usually imports one node, while the latter must be saved and used to update a group. Reinstalling won't fix choosing the wrong input type.
After importing, test the connection with a profile you know works. If only some apps can't connect, check whether they follow the system proxy and whether the local ports match. If the subscription list is empty, check that the subscription is valid, the URL is complete, and the client supports its format. See the user guide for steps, and protocol details for compatibility between protocols and cores.