Three roles, not one thing
| Part | What it provides | What it does not provide |
|---|---|---|
| Provider | Lines, plans, quota, and the subscription endpoint | The client, or a working local network configuration |
| Client | Reads a configuration, selects nodes, forwards or captures traffic | Any line by itself; an installed client with no valid subscription has nothing to connect to |
| Subscription link | Transfers the configuration from provider to client | Guaranteed compatibility with every client or format |
Most confusing incidents come from mixing these up: assuming an installed client means a working line, assuming a link that opens in a browser is a valid subscription, or assuming “supports Clash” means every client will read it identically.
A subscription link is not an ordinary web page
The link exists so a client can fetch node configuration. After the client reads it, selectable lines appear. A provider's login page, purchase page and subscription endpoint can be three different addresses, and pasting the login page into a client produces exactly the empty or unparsable result you would expect.
Two practical consequences follow. First, a browser opening the address proves reachability and nothing about the payload. Second, the address usually contains a credential, so it must be handled like a password.
Before importing
- Get the client from the project's official release channel, and check the owner, release page and version.
- Read the provider's compatibility note: which clients and which formats it actually serves.
- Confirm the plan has not expired and quota remains.
- Read the provider's setup note once before changing settings.
- Run one proxy client at a time. Two clients capturing traffic is a reliable way to create a fault you then have to diagnose.
Why the link has to stay private
Many subscription links embed an account token. Anyone holding the link can consume your quota, and on some providers can see plan details. Do not publish the full address, do not paste it into a public group, and mask the token and account fields in any screenshot sent to support. If it leaks, rotate it in the provider panel — deleting the message does not revoke anything.
Update, switch, reset
| Action | What it does | When it is appropriate |
|---|---|---|
| Update subscription | Fetches the provider's configuration again | Nodes changed, plan renewed, provider published a new config |
| Switch node | Selects another line already inside the configuration | One node is slow or unreachable and others work |
| Reset subscription | Issues a new token and usually invalidates the old link | The link leaked, or the provider requires it — never as a first response to an update failure |
Resetting to fix a timeout destroys your ability to tell whether the timeout was the network, the provider or the client, because the input changed.
From payment to a working connection
- Buy or receive a plan.
- Get the subscription link from the provider panel.
- Install a compatible client from its official channel.
- Add the subscription and update it.
- Activate the profile.
- Select a node.
- Enable system proxy or VPN/TUN — one of them.
- Verify the exit with an ordinary HTTPS request.
Each step fails differently and belongs to a different page. A failed step three is not a provider problem; a failed step eight with a working profile is not an import problem.
Why the same link differs between clients
Clients differ in supported formats, core versions, request headers and extension fields. A provider saying “supports Clash” means a compatible configuration can be produced — it says nothing about speed, stability or safety, and nothing about whether your particular override, script or rule set will survive conversion. Use the format the provider explicitly supports for your client rather than forcing one into the other.
How to confirm the subscription really updated
- Check the update timestamp on the profile card.
- Compare node count, and quota or expiry if the client displays them.
- Confirm the active profile points at this subscription.
- Select a node, open an ordinary HTTPS site, and compare the exit IP if you need to.
A completed download is not proof that the core loaded. If the provider's content was not supposed to change, an identical node list is the correct result.
When you stop using it
- Turn off the connection, TUN and system proxy.
- Quit the client.
- Remove subscriptions and unknown profiles you no longer use.
- Confirm plain networking returns.
- If you are changing providers, reset or disable the old link in the old panel so the token stops working.
Scope
This page explains the roles and the order of operations, based on the official subscription documentation of the clients referenced. It contains no account or line testing, and no assessment of any provider. Interface names and supported formats follow each client's own documentation.