Before you install or upgrade
Check the client, core, and configuration separately
The client displays nodes, manages subscriptions, and controls the system proxy. The core establishes connections using protocol parameters. Switching clients doesn't change the protocol used by the server. A configuration may appear in the list but include security-layer or flow-control fields that the current core doesn't support. For a new installation, confirm the protocol with your configuration provider, then choose a package for your device. When migrating from another client, also note the transport protocol and security layer used by a working configuration. For field details, see the protocol handbook.
Back up outside the client directory
If you have a configuration in use, note the client name, current version, and proxy mode, then back up your nodes, subscriptions, and custom routing rules. Subscriptions can usually be fetched again from the server, but manually added nodes, node labels, and rule order may not be restored. Store backups outside the app data directory; on Android, uninstalling may also delete local data. Subscription URLs and node configurations may contain access credentials. Keep backups somewhere you control, and don't post full links or configuration screenshots in public forums.
Know whether you're installing, upgrading, or switching clients
For a new installation, choose a package from the platform table. Before an in-place upgrade, exit the old client and note where it came from. Don't remove the old version just to dismiss an installation prompt. When switching clients, don't assume they use the same database format or rule syntax. Migrate using a format supported by the app, then check that transport-layer fields and routing rules were preserved. If you keep both clients temporarily for comparison, run only one at a time during testing to avoid conflicts over local listening ports or the system proxy.
Troubleshoot by where the failure occurs
If you get a format error before opening the file, first check that you've selected the right platform tab. If the installer won't run, check the OS version, CPU architecture, and installation permissions; on Linux, also check the specific dependency reported by the package manager. If installation finishes but the app won't start, look at the first runtime error instead of switching nodes. If the interface opens but the configuration doesn't work, check the node parameters, selected core, system proxy, or VPN status. Separating installation issues from connection issues makes it easier to compare results between attempts.
Verify one connection path first
After launching the client, import one configuration with clearly specified parameters. Confirm the selected node and local listening status, then choose a connection method supported by the app. On desktop, if you're using the system proxy, test with an app that follows system proxy settings. On Android, check whether the system accepted the VPN connection request. Once the basic connection works, add routing rules, adjust DNS, or enable TUN one change at a time. If you change several settings at once, it's hard to tell which one caused a connection problem.
See how to import a subscription, set up a proxy, and test your connection →