Back up before installing or updating
If you already have a client, disconnect first and note the system proxy state and local listening port. Use the client’s backup or export feature to save any configuration you need. Subscription links may contain access credentials, so store them securely and redact them before sharing error screenshots. When switching clients, reimport the original subscription where possible instead of copying database or cache files you don’t understand.
Updating the same client and switching to another client are different operations. Updates usually retain the existing configuration; a different client may support different fields, routing, and core features. After updating, confirm your groups, rules, and configurations still load before testing the connection. Keep your old backup until you’ve verified everything works.
Import a subscription and select a configuration
The client installer doesn’t include a subscription service. Get a subscription link you’re authorized to use, open the subscription group settings, create a group, and paste the full link. Save it and update the group. If the list is empty, check the update log and confirm the response is readable by your client rather than repeatedly importing the same link.
After a successful update, select a configuration and start the connection. Node tests can help check reachability, but they don’t replace testing in the apps you use. If a configuration won’t connect, compare it with one you know works. Avoid changing DNS, routing, ports, and transport settings all at once, or it’ll be hard to tell what fixed or caused the problem.
Test the standard proxy before changing advanced settings
On desktop, make sure the system proxy is enabled and uses the client’s local listening port. On Android, confirm VPN permission is granted. Test a browser on a page that normally loads reliably, then test the target app. If something goes wrong, check the client logs to distinguish a local network issue from a subscription or connection setting problem.
Enable TUN, per-app proxy, and custom routing one at a time, only after the basic connection works. Change one setting per test and keep a configuration you can restore. If the network stops working after you close the client, check whether the system proxy still points to the stopped app before investigating further.
