First checks after installation
Once the client opens normally, import an existing subscription or a single node. For the first test, select one known-working configuration and keep its protocol and transport settings unchanged; adjust one setting at a time. This makes it easier to tell whether a problem occurred during import, when the client took over traffic, or while connecting to the remote server.
A node list doesn’t mean you’re connected
A successful import means the client received the node configuration; it doesn’t mean the remote server is available or that the app is routing traffic through the client. First confirm that the selected node is the one you expect, then check the client logs for connection requests. If the subscription updates but app traffic fails, troubleshoot the subscription URL and node server separately—they’re two different connections.
Proxy entry points and routing rules are different
The system proxy directs traffic from apps that honor that setting to the local proxy endpoint, but not every app uses the same proxy settings. Routing rules determine which outbound connection is used by traffic that reaches the client. If one app works and another doesn’t, first check whether the latter sends requests to the local proxy. You don’t need to reinstall the client or switch to global routing right away.
The first time you start a connection through a client on Android, the system usually asks you to authorize a VPN connection. If another app is already using this type of connection, check which app is currently active. Selecting a node in the client doesn’t replace system-level authorization or connection status.
Use the error to troubleshoot before reinstalling
If the startup log points to a local port conflict, check whether an old instance or another app is listening on the same port. If you need to change the port, update any app proxy settings you entered manually. If the log shows the request reached the client, check the remote address, protocol, transport and routing against the error. Don’t change the package, node and routing rules all at once.
For the full import and verification process, see Getting Started. For local port conflicts, see Troubleshooting Port Conflicts. To understand how configuration options relate, consult the JSON Manual.