Using Subscriptions

A subscription URL is the one link that always serves your latest VPN config. Paste it into Clash, sing-box, Surge, Shadowrocket, or QuantumultX and they auto-update when the operator pushes changes. For VLESS-capable clients, the raw vless:// URI works directly.

Your subscription URL is a credential, treat it like a password. Anyone with it can use your VPN.

https://<portal-domain>/api/v1/sub/{your-token}?format=clash

The format parameter selects the output: vless, clash, singbox, surge, shadowrocket, quantumultx (conf is an alias of vless). Omit it and the server answers from your client’s User-Agent, so one URL serves every client. Append ?node_id=<id> to pin a node, or ?region=<label> to prefer a region.

The portal always serves the best available node automatically (load + health + region-aware steering). You don’t need to pick a region manually unless you want to.

Paste the subscription URL into your client’s subscription settings. The client pulls a fresh config on a regular interval, so node changes and capacity adjustments reach you without manual work. The portal’s Subscription page (/console/subscription) also offers one-click import links per client.

Common client subscription entry points:

• Clash / mihomo . Profiles → import URL, or the clash://install-config one-click link.
• sing-box . Outbounds → subscription, or the sing-box://import-remote-profile one-click link.
• Surge . Profiles → download profile from URL.
• Shadowrocket . Add from URL, or scan the per-client QR code.
• QuantumultX . Add the remote resource from the URL or QR code.

Multi-node behavior is airport-style: clash and singbox render every node the account has (best first, with a selector); surge renders the single best node.

If your URL leaks or you simply want a fresh one:

1. Go to the Get connected card on the Console and click Rotate subscription URL (or Regenerate Subscription URL in the Subscription page’s Danger Zone).
2. Confirm. The old URL stops working immediately.
3. Update the URL in every client that uses it.

Rotating only changes the subscription token. Your existing peer connection keeps working until you re-import.

The same subscription URL works on any number of devices, up to your plan’s device limit. To check the limit and current usage:

• Console → Devices (/console/devices) lists the devices seen using your config, with a “last seen” timestamp.
• Counts are approximate on shared networks: NAT can merge or split what the panel sees as distinct endpoints.

To add a device on a new phone or laptop, just import the config there. To remove one, disconnect it from the client; the count drops within a few minutes.

The subscription URL auto-selects the best node. To force a specific node, append ?node_id=<id> to the URL; to prefer a region, append ?region=<label>. Your operator can give you the node IDs and region labels.

• Your account is suspended, traffic stops flowing.
• Your config and data are retained, nothing is deleted.
• The Console shows a renewal prompt.

To renew, go to Console → Shop (/console/shop) and complete payment. The account reactivates immediately, no re-download needed. If your plan doesn’t have self-service billing enabled, contact the operator and they’ll extend the subscription from the admin panel.

If you exceed your data quota, the same suspension applies until quota is added.

• Your subscription URL is your credential. Treat it like a password.
• Rotating invalidates the old URL instantly.
• The operator cannot see your traffic. They manage the infrastructure but cannot decrypt your data.
• The served profile embeds your credential. The subscription token (a 192-bit random value) and the account UUID ride inside the config, so protect downloaded files and screenshots. The portal masks the token in displayed text; copy and QR flows always use the full URL.