Package selection and installation
From download to first connection
Check package selection, startup, and import separately. If something goes wrong, identify which step failed first.
Confirm which device you're installing on
Choose a package for the device that will run the client, not the device you're using to view this page. For example, if you transfer an Android installer from your computer to your phone, check the phone's Android version and architecture. For a virtual machine, check its operating system. Even computers in the same home running the same OS may use different architectures, such as x64 and arm64, so don't assume one package fits them all.
Check the downloaded filename and extension. Different package types may use the same client name, so keep installers separate from configuration backups. If the browser says the download was interrupted or is still in progress, let it finish before opening the file with the system's default installer. If the installer has already shown an error, note the exact message; that's more useful than trying every download option.
Back up your settings before updating
If the old client still opens, use its export or backup feature to save your settings. Note your subscription groups, current routing mode, and any manually added nodes. A subscription URL can restore subscription-managed nodes, but not local notes, custom rules, or individually imported nodes. When switching devices or clients, import everything into the new setup and verify it before deleting the old configuration.
Subscription URLs, node links, and backup files may contain access credentials. Keep backups somewhere only you can access. When asking for help, share your operating system, package type, and error message, but redact subscription URLs, node addresses, and QR codes from screenshots. If you're using the system proxy, turn it off in the client before quitting the app to prevent the system from pointing to a local proxy that is no longer running.
Import subscriptions after confirming the client starts
Open the client first and make sure its main window loads. If you have a subscription URL, add it under Subscriptions and refresh the group. If you only have a link for a single node, import it from the clipboard. If the list is still empty after an update, check whether you copied a subscription URL or a single-node link, then review the update log. Reinstalling the client isn't necessary just to retry.
Once the list appears, select a known working node and test it using system proxy settings or the client's connection steps. For your first test, check one mode at a time. If a browser works but another app doesn't, see whether that app follows the system proxy. Once the basic connection works, adjust TUN or routing settings; changing them one at a time makes it easier to identify what caused a problem.
Quick start guide · Installation and connection troubleshooting