For a first install, start with the package type. Before upgrading in place, save your existing configuration and verify each step.
Choose a package for the OS you're running
The host OS, a virtual machine, and a dual-boot system on the same computer may all need different packages. Check system information in the OS where you plan to install the client. The processor model can indicate hardware capabilities, but it can't replace the app architecture reported by the running OS. A processor that supports 64-bit apps, for example, doesn't mean the current OS does too.
Check the OS, architecture, and package format on the download button, then review your browser's download history. If the download contains only an error message, or won't open and has the wrong extension, return to the platform and download it again. Changing a file extension won't turn a webpage into an installer or convert one architecture's package to another.
Back up your configuration, not just the subscription link
Refreshing a subscription can usually restore the nodes in that subscription group, but manually added servers, custom routing, and local listening ports may not be included. Before updating, use the client's configuration backup feature if available. Also note the group in use, selected routing mode, system proxy status, and whether LAN access is enabled so you can compare behavior after the upgrade.
Keep the old backup until you've confirmed the new version can read the configuration. Don't edit the same configuration directory in both versions at once. Subscription URLs, sharing QR codes, and exported files may contain connection credentials. Store backups somewhere secure. When asking for help, share only error excerpts with addresses and credentials removed.
Start the client before restoring proxy settings
On desktop, first confirm that the app opens and can read the server list, then select a configuration you normally use. Avoid changing ports, routing, and DNS at the same time. Restore the previous system proxy settings and test the same app, then toggle the proxy once for comparison. If the toggle makes no difference, check whether the app uses the system proxy before assuming the node is unavailable.
On Android, first check that the configuration imported successfully, then tap Connect and approve the system VPN request. If the configuration list is empty after an upgrade, check whether you opened a different client or the original configuration wasn't restored. A visible app screen doesn't mean it's ready to connect until a server is selected.
Record the error before changing settings
For an installer error, note the OS version, package type, and first missing requirement in the message. For a client error, find the first relevant log entry after the current launch. If a local port is already in use, check whether an old client is still running in the background. For certificate or timeout errors, check the system clock, server configuration, and current network.
Change one variable at a time during testing, and restore its original value if the test fails. For setup from a subscription, see the subscription import steps. To check listening addresses and ports, see the inbound fields reference. Troubleshoot these separately to avoid mistaking a configuration issue for the wrong installer package.