The installer only deploys the client. Set up configuration, permissions, and connection checks separately so you can pinpoint any issue. There’s no need to change DNS, custom routes, or TUN settings during a first installation.
Install and launch
Check the file format and device architecture first, and note the exact system prompts. On desktop, quit the old client before updating; on Android, allow installs from the app opening the APK. Back up existing settings before making changes, especially manually maintained routes, subscription groups, and local listening settings.
Once the client’s main window opens successfully, move on to subscription setup. It’s normal not to be connected yet.
Import a subscription and select a node
Get a subscription URL from a trusted source and make sure you’re authorized to use it. Add it as a subscription or subscription group in the client, then update it. Importing a shared node link is different from importing a subscription URL, so use the appropriate option. After updating, check that the group contains nodes and select one to test.
Subscription URLs often contain access tokens. Don’t share the full URL in public screenshots or logs, or paste it into third-party conversion sites.
Proxy mode and connection checks
On desktop, start with the system proxy. On Android, approve the connection request. Routing policy determines which connections go direct and which use the proxy; the system proxy and TUN are separate settings. Test the target app first, then adjust routing as needed. Change one setting at a time.
If apps can’t connect after you quit the client, check that the system proxy has been restored and remove any leftover manual proxy settings.
