Order of work
- Install from the project's own release channel, matching your platform.
- Import the subscription in the form the provider documents for this client.
- Confirm the node count is plausible and update reported no error.
- Select a node, so that a connection has something to use.
- Enable system proxy, then verify with one real request.
- Only if an application needs broader capture, enable the tunnel mode and record the pre-change state.
Format before settings
| Input shape | Produces | If the entry is wrong |
|---|---|---|
| Subscription URL returning a list | Many nodes | Empty list or a parse error |
| Single share link | One node | An unexpectedly short list |
| Configuration file for another client family | Depends on the parser | Empty list, or fields silently ignored |
“Fields silently ignored” is the dangerous case: the list looks populated, but behaviour does not match what the configuration intended. When something behaves unexpectedly, compare the original file against what the client displays.
Capture modes
| Mode | Covers | Notes |
|---|---|---|
| System proxy | Applications that read proxy settings | Fewer variables, simpler rollback |
| Tunnel | Broader, subject to routes and exclusions | Needs a tunnel interface and permissions; can conflict with other VPNs |
The four contrasts when pages fail
- Client off, ordinary site: establishes the base network.
- Another node: separates one node from the whole subscription.
- Another network: separates the current path from the service.
- One app versus Safari: separates capture scope from forwarding.
Why a populated list can still behave oddly
A list with entries proves that nodes were produced. It does not prove that every field in the configuration was understood. Cross-format import is where this happens: a client may accept the file, create the nodes, and ignore a transport option it does not implement. The symptom is a node that connects and carries nothing, or one that behaves differently from the same node in another client.
When behaviour differs from the source configuration, compare the two rather than adding settings: what the file declared for that node, and what the client shows for it. A field silently ignored is not a field you can fix by changing DNS.
What to record
- App version, platform and the time.
- The input shape and what the address actually returned.
- Whether the node list was empty, partial, or complete.
- Mode used, and the result of each contrast.
- Observed exit, if region matters.
Scope
This page describes an order of checks. Interface wording and supported formats follow the installed version and the project's documentation. Nothing here evaluates a provider or claims compatibility with a particular subscription.