Install, update, and migrate
An installer determines whether the client can run on your device. Subscription updates and individual node connections depend on your configuration and network, and fail in different ways. Confirm the app starts before importing a configuration to avoid mistaking an installation issue for a node problem.
Check the file type after downloading
Windows downloads are archives containing an installer; don’t run files from the archive preview. macOS downloads are disk images; you can eject the image after copying the app. Open Android APKs with the system installer. On Linux, use the package manager or tool for your distribution to install DEB and RPM files. Avoid converting one format to another just to install it.
If your browser says the download is incomplete, check available storage, your network, and download history. Don’t rename an unfinished temporary file with an installer extension. If the system installer opens but can’t continue, check whether the error mentions architecture, OS version, dependencies, or permissions. Record the full message; it’s more useful for troubleshooting than simply saying “it won’t install.”
Keep a recoverable backup before updating
First, distinguish an in-place update from switching to a different version. For an in-place update, use the same download source and app identity where possible. When changing package, client, or device, don’t assume the data directory can be shared. If the client supports exporting settings, save a configuration it can import again, then separately note custom rules, proxy mode, and app exceptions you need to restore.
After saving a backup, make sure you can open it on your device and note which client and device it came from. Subscription URLs may contain credentials, and configuration backups may include node details. Don’t upload the entire file to an online converter or post it publicly. When asking for help, share your OS version, client name, and an error message with sensitive details removed.
On first launch, test one connection path
Once the app starts normally, follow the subscription import guide to add a configuration you’re authorized to use. Select one node and test it with an app that follows the proxy settings. If you change routing, DNS resolution, and proxy mode all at once, it’s hard to tell which setting fixed the issue.
Before quitting a desktop client, check whether it left a local proxy address configured. If the client has exited but the system still points to a local port, your browser may not load pages. On Android, check which VPN service is active. Installing two clients on your phone doesn’t mean you need to run both at once.
Check permissions on managed devices
Company computers, school devices, and phones with work profiles may restrict app sources, installation permissions, or system proxy changes. Ask your device administrator which apps and distribution channels are approved; don’t assume a policy restriction means the package is corrupted. If only apps in the work profile can’t connect, compare with the same app in your personal profile to help distinguish a device policy issue from a node configuration problem.