What is a subscription link? It is an address a client uses to retrieve route configurations, usually with credentials that identify your account. Copy the link provided in the dashboard, import it into a compatible client, then refresh the configuration and choose a route to proceed to the connection stage. Here, “subscription” means a source of configuration; it does not mean automatic billing is enabled, nor does importing it mean you are already connected.
The Difference Between Subscription Links, Routes, and Plans
Think of a subscription link as an entry point to a refreshable list of routes. The client requests content from this address and reads server addresses, ports, protocols, and authentication parameters. Some configurations also include route groups, routing rules, and DNS settings. The details depend on the format offered by the service and the client’s supported features; not every subscription includes a complete set of rules.
A single-route sharing link generally describes one connection configuration, while a subscription link is used to retrieve a set of configurations over time. After saving it as a “subscription,” “remote configuration,” or “profile,” the client can fetch it again later. When routes change, you usually do not need to re-enter each address manually.
| Item | Purpose | What it does not tell you |
|---|---|---|
| Plan subscription | Defines the account’s billing cycle, data allowance, and usage permissions | It does not mean the client is already configured |
| Configuration subscription link | Lets the client retrieve and refresh route configurations | It does not guarantee that a route is reachable or a destination site is available |
| Single-route configuration | Describes the connection parameters for one route | It generally does not maintain a whole group of routes automatically |
| Routing rules | Determine which requests connect directly and which go through a proxy | They cannot provide valid server credentials on their own |
Remember this distinction: A plan determines how much you can use, a subscription link retrieves configurations, and a client establishes the connection. Refreshing a configuration does not renew an account or reset used data.
Get a Subscription Link from the Dashboard
Open the user dashboard from the site, then check your account and plan status before looking for the subscription or configuration section. VPNWhen does not require an email address; a username and password are enough to create an account. This does not make a subscription link any less sensitive. You must sign in to retrieve it, and should not look for your own link in group chats, screenshots of search results, or configurations forwarded by strangers.
If the dashboard offers different options for different clients, choose the format that matches your app. The same service may provide a general share link, a client-specific configuration, or an in-app import option; these are not necessarily interchangeable. Follow the button labels and requirements shown in the dashboard, and do not mistake a client download link for a subscription address.
- Open the dashboard on a trusted device, verify which account is signed in, and check that the plan is active.
- Choose the client you plan to use, then copy its corresponding subscription address or use the import option provided in the dashboard.
- Open the subscription or remote configuration page in the target client. If your browser asks to open an app, verify the app name.
- After importing, check the update result and route list. Confirm that the new configuration is selected before trying to connect.
A subscription QR code may contain the complete credentials and needs the same protection as the link. Do not post the QR code, address bar, or a screenshot of the full configuration in a public community. When asking for help, share an error message with sensitive details redacted.
Import into a Client by Platform and Check Format Compatibility
Get the app from the client download section in the dashboard. VPNWhen supports Windows, macOS, iOS, Android, and Linux. Clients are available after signing in on platforms other than iOS; check the dashboard for iOS access requirements. Menus and supported protocols vary between apps, so the operating system alone does not tell you whether a configuration can be imported.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols or protocol schemes, not subscription file formats. Being able to import an address does not mean an app’s core supports every protocol it contains. Likewise, support for a protocol does not mean the app can read any client’s configuration syntax. Check the service information, client documentation, and actual error messages.
Windows and macOS: Select a Configuration Before Enabling the Connection
Desktop clients generally let you add a remote configuration and update it. If you continue using an old configuration after importing, the interface may show new routes even though the active connection has not switched. First confirm the selected configuration and route, then enable system proxy or tunnel mode as described by the client. A system proxy usually affects only apps that follow the system proxy settings; it does not route every request from the device.
iOS and Android: Check the Receiving App and System Permissions
When importing through a browser handoff, confirm that the system opens the intended app. Establishing a system-wide connection on a mobile device may require permission to add a VPN configuration. This is part of how the system handles network traffic; it does not mean every imported route uses a traditional VPN protocol. If other networking tools are running, check whether they are using the same connection mechanism to avoid repeatedly overwriting configurations.
Linux: Separate Configuration Files from Service Status
Linux may use a graphical interface or run a configuration file through a core. Do not assume an arbitrary subscription response can be started directly as a core configuration, and never run conversion scripts from unknown sources. Verify the file format, configuration path, and read permissions. Even after the service starts successfully, check that the proxy entry point, routing, and DNS work as expected.
How Often Should You Update? Follow Changes, Not a Fixed Schedule
There is no fixed update interval that works for every service. If your client supports automatic updates, enable them according to its instructions and check the status of the last successful update. After a long period without use, when the dashboard announces route changes, or when several existing routes stop working, you can refresh manually. There is no need to keep clicking update to “speed things up”; refreshing does not improve your local network quality.
If an update fails, do not delete the existing configuration right away. Some clients can still use cached routes. Keep the usable configuration, note the error, and determine whether the subscription address has expired, the request cannot reach its destination, or the returned format is incompatible. Repeatedly deleting and recreating a subscription can lose your existing selections and make the source of the issue harder to identify.
VPNWhen monthly subscription data resets every month on the activation date; it does not reset when the configuration is updated. Data packages remain valid until used and do not expire. Refreshing a subscription does not add data, and a package that does not expire does not mean data can still be transferred after it is used up. Check your remaining allowance and account status in the dashboard.
- ✅ Routes are outdated or the dashboard reports changes: update the existing subscription and check whether it fetched successfully.
- ✅ The client reports an incompatible format: check the import option and app support again instead of repeatedly pasting the link.
- ✅ Routes have loaded but you cannot access a destination: continue troubleshooting the connection and routing rules rather than blaming the subscription address.
- ❌ Using a subscription refresh instead of renewing a plan or managing data: configuration updates and account allowances are separate.
Import Failed or Cannot Connect: Troubleshoot by Layer
Cannot Retrieve the Address? Check Copying and Network Access
Check whether a chat app truncated the link, inserted spaces, or removed query parameters. If needed, copy it again from the dashboard. Never paste the full address into a public search box. If the client reports a certificate error, check the device time and destination address; do not disable certificate verification just to complete an update. If access is restricted, follow the client’s instructions to retry on an available network rather than using a subscription mirror from an unknown source.
Import Succeeded but No Routes Appear? Check the Response and Parser
A successful request only means a response was received. That response could still be a login page, an account status message, or a format the client cannot read. Check the plan status and subscription type, and see whether the app reports a parsing error. Avoid pasting the raw response into an online parsing tool: it may contain server credentials, and a successful conversion does not prove the tool did not retain the content.
A Route Is Selectable but Cannot Access a Destination? Check the Path and Routing Rules
The subscription may already have imported successfully; the problem may be at the connection stage. Try another currently available route, compare whether the issue affects only one destination, and check whether the rules send the target traffic through the intended exit. IEPL dedicated lines, relays, and direct connections describe transmission paths or route arrangements, not subscription formats. A path name alone does not guarantee an access result. See the protocol and route guide for a comparison of terms.
Also check DNS: routing web traffic through a proxy does not necessarily mean domain lookups follow the same path. A DNS leak usually means lookup requests bypass the intended protection path, which may expose information about the domains you visit. Whether this happens depends on the combination of system, browser, client, and rules. Check the client documentation for DNS handling settings; a page loading successfully is not proof that there is no leak.
How to Reset a Leaked Subscription Link
Many subscription addresses let anyone who has the link retrieve configurations. If the address leaks, someone else may obtain its route credentials, use account resources, consume data, or trigger unusual account activity. The link may not provide direct access to the dashboard, but it should still be treated as a sensitive credential. Changing your login password alone may not invalidate an old subscription token.
- Remove any public posts as soon as possible and stop sharing the link. Deleting a message does not retrieve addresses that have already been copied.
- Look in the dashboard for an option to reset the subscription or revoke the old link, and read the confirmation prompt. If the option is missing or unclear, ask through a dashboard support ticket.
- Confirm what the reset affects, including whether the old subscription address and connection credentials in existing configurations will stop working. Do not assume downloaded configurations are revoked just because the address has changed.
- Update the new link on your devices, refresh and test the connection, and remove old subscriptions you no longer use.
- Check usage and account status in the dashboard. If there are also signs that your account password has leaked, change it and review the available session management options.
For everyday use, store subscription addresses in a trusted password manager rather than a public code repository, shared notes, or the clipboard of a shared device. When reporting an issue, provide only the error type, platform, client version, and screenshots with sensitive information removed. Share a full link only when necessary and through a channel you have verified as trustworthy.
For beginners: Get the right format from the dashboard, import and select it in a compatible client, and update it when needed. Troubleshoot configuration retrieval, connection setup, and account data separately. If a link leaks, revoke the old credentials instead of merely deleting the chat message.