Back up your settings before upgrading
Before upgrading, note your current subscription groups, routing mode, and local listening ports. Custom routing rules, manually added servers, and interface preferences may not be included in your subscription link, so saving the link alone isn’t a complete configuration backup. Use the client’s export feature or follow the documentation to back up its configuration directory, and store the backup somewhere only you can access. When you’re done, exit the old client before installing or launching the new version.
For your first setup, you don’t need to change a lot of advanced settings just to finish installing. Keep the default local listening settings to avoid conflicts with other network tools. If a port is already in use, check for an old process still running in the system tray or background instead of repeatedly launching more copies. If you’re changing installation methods, keep a backup of the old configuration and wait until the new version starts successfully before deleting the old directory.
Import your subscription and check the update result
Open subscription group settings, enter a label you’ll recognize, and paste the full URL. Remove any spaces or line breaks added during copying, but don’t delete URL parameters. Saving the URL only registers the update source; you still need to update the subscription to download server configurations. If the update fails, check the client’s message to distinguish an unreachable URL, an incompatible format, or an account issue. Reinstalling the client won’t fix a problem unrelated to the app.
Subscription links often contain access credentials, so protect them like account information. When asking for help, hide URL parameters, account identifiers, and other sensitive details; include only the error type and relevant information about your setup. The client being free and the subscription service’s cost are separate matters. Installing the software doesn’t create an account or automatically provide working servers.
Check proxy scope and routing mode
Select a server before enabling the system proxy or connecting on Android. A desktop system proxy affects only apps that use that setting; it doesn’t mean all device traffic is being routed through the client. The routing mode determines whether requests that reach the client go direct, through the proxy, or are blocked. If some sites work but some apps don’t, first check whether their requests reach the client, then check which rules apply. Don’t assume every issue is caused by the subscription.
If you need TUN, read the permission and DNS documentation first. TUN routes more traffic, but it can’t restore an invalid subscription or replace correct routing rules. Change one setting at a time during testing and note the results. If something breaks, revert the last change; that’s usually easier to troubleshoot than switching clients repeatedly.
