What is a subscription link? It is an address a client uses to retrieve connection configurations, usually with credentials that identify your account. Import it into a compatible client, and the client can fetch a list of routes. When you update the subscription later, it retrieves the configuration again from that address. A subscription link is not a plan, nor is it an ordinary webpage to share publicly.
How Subscription Links, Routes, and Plans Differ
Think of a subscription as an entry point for retrieving configuration. The server may return route addresses, ports, authentication details, and policy groups or routing rules supported by the client format. The specific contents depend on the subscription format offered by the service; do not assume every subscription includes a complete set of rules.
A plan determines the account’s service benefits; a subscription link lets the client retrieve configuration; a route is a specific entry point selected when connecting. A successful import only means the client accepted the configuration. It does not verify the plan status, current network, or destination website.
| Item | Main purpose | Common misconception |
|---|---|---|
| Plan | Defines the account’s data allowance and billing method | Updating a subscription is not a renewal and does not add data |
| Subscription link | Provides the client with an updateable configuration source | Pasting it into a browser’s address bar does not import it |
| Single-route share link | Describes one connection configuration | It may not automatically update with the full route list |
| Local configuration file | Stores configuration used by the client | A manually imported file may not retain its remote update source |
A subscription format and a connection protocol are not the same thing. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols or protocol variants; subscriptions distribute configuration. A client’s ability to read a particular subscription format does not mean its core supports every protocol and parameter in that subscription. These names are conceptual examples, not a commitment by FTVPN about protocol support. Refer to the user panel and client documentation for current details.
Get the Right Link from the User Panel
Get FTVPN subscription details from the official user panel. Do not use an address found in search results, group chats, or unsolicited messages as the source of your account configuration. An email address is not required to use an FTVPN account, but keep your username, password, and subscription credentials separate and secure.
- Open the FTVPN user panel and make sure you are signed in to the account you intend to use.
- Check your plan and data status in the panel. If your benefits are unavailable, resolve the account status before troubleshooting the client.
- Open the subscription or client configuration section in the panel and choose the format for your current client. Section names may vary by interface.
- Use the copy or import option provided by the panel. If copying manually, make sure you have not included explanatory text, spaces, or line breaks.
- Give the link only to a trusted client you intend to use. Do not paste it into public documents, public code repositories, or online testing pages.
If you are unsure which format to choose, start with the getting started guide and check the client name and version. Do not try to solve format problems by cycling through unfamiliar conversion websites; those services may access the original link and its connection details.
How to Import into Clients on Different Platforms
Windows, macOS, iOS, Android, and Linux have different interfaces, but the core steps are similar: add a remote subscription, enter the address, retrieve the configuration, select it, and enable the connection. If you need a client, use the client download page in the panel and check the platform and system compatibility details.
Desktop: Distinguish Configuration, System Proxy, and Virtual Network Adapter Modes
Desktop clients usually list subscriptions on a page called “Profiles,” “Subscriptions,” or something similar. When adding one, choose a remote address rather than putting the full address into a single-node parameter field. After saving, update it, confirm the route list is not empty, and check that the newly imported configuration is the one currently enabled.
After selecting a configuration, whether apps use the proxy also depends on the operating mode. A system proxy affects only apps that follow the system proxy settings. A virtual network adapter mode can generally handle more traffic, but it needs the relevant permissions and may conflict with routes from other network software. Do not enable multiple clients at once unless you understand how their modes interact.
Mobile: Confirm the Import Handoff and Connection Permission
On mobile, you can paste an address into the app to import it, or a link in the panel may open the client. A successful handoff does not mean the configuration has been saved. Return to the client and check the subscription name, update result, and route list. When the system asks to add a VPN configuration or grant connection permission, first confirm that the request comes from the app you are using.
Background restrictions on some Android devices may affect persistent connections. On iOS, on-demand connection behavior depends on the client and system settings. If a connection drops after the screen locks, check background and on-demand settings instead of repeatedly recreating the subscription. Linux clients may also require separate proxy settings for the desktop environment, terminal, or individual apps.
- ✅ Routes appear after import, with no parsing error or unsupported protocol warning.
- ✅ The active configuration matches the subscription you just imported, and connection permission is granted.
- ✅ Test access with the apps you actually need instead of relying only on the client’s “Connected” status.
- ❌ Do not mistake a chat preview, panel login address, or single-route QR code for a complete subscription.
When to Update and Which Settings May Change
There is no fixed update interval that applies to every client. Retrieve the configuration after the first import. You can update it manually when you receive a route change notice, resume using it after a long break, or encounter problems with existing routes. Whether automatic updates are available or run in the background depends on the client and system restrictions.
Updating a subscription usually downloads the remote configuration again. It does not automatically reset plan data or upgrade the client. FTVPN monthly subscription data resets each month on the activation date. Data packages do not expire and remain available until used. These are billing rules and are unrelated to clicking the update button. Check the plan pricing page for details.
Pay attention to where local changes are saved. Edits made directly to rules in a remote configuration may be overwritten during an update. If your client supports overrides, merging, or separate rules, configure these according to its documentation and recheck policy groups and routing results after an update. Do not assume all clients use the same configuration syntax.
Troubleshoot Import Failures and Connection Issues
First determine whether the issue is a retrieval failure, a parsing failure, or a connection failure. Retrieval failures occur while downloading the configuration and may be related to an invalid address, a network that cannot reach the subscription endpoint, or account status. A parsing failure means the content was retrieved, but its format, fields, or protocols are not supported. A connection failure occurs after the configuration loads and requires further checks of the route and local network.
- Check the source. Return to the panel and copy the format that matches your client. Rule out an old link, an incomplete copy, or accidentally using the login page address.
- Check the client. Review its version and supported core features. If the configuration contains an unsupported protocol or field, do not delete fields at random to force it to run.
- Check the retrieval path. Some clients let you retrieve a subscription directly or through an existing proxy. If the old proxy is unavailable, the latter option may cause repeated update failures. Adjust it according to your network and the official documentation.
- Check the connection environment. Compare results on a trusted network and temporarily rule out interference from other proxies, virtual network adapters, or conflicting rules.
- Collect error details. If the issue persists, contact support through customer support tickets with your system, client version, error text, and steps to reproduce the issue. Redact credentials in screenshots and logs first.
If only certain websites are affected, also check routing rules and DNS. Routing determines whether a request uses the proxy or connects directly; DNS determines how a domain name is resolved. A “connected” status in the client does not prove that every app’s DNS queries follow the expected path. If resolution is not behaving as expected, check the client’s DNS interception settings, secure DNS in your browser, and app-specific behavior instead of blindly switching to a public resolver.
A subscription alone cannot prove that a route uses IEPL, transit, or a direct connection. These describe different network paths or service arrangements, not subscription file formats. Route names are labels for identification. Check the service documentation for the actual type; do not infer guarantees about speed, privacy, or availability from a name.
What to Do After a Link Is Exposed
Treat a complete subscription link as sensitive account information. Someone who obtains it may be able to retrieve the route configuration; the impact depends on the server’s access controls. Even if your plan allows unlimited devices, that does not make subscription credentials suitable for public sharing.
- Remove the link from public posts, shared documents, or repositories and stop it from spreading. Do not assume deletion means the credentials are invalidated.
- Open the official panel and look for an option to reset the subscription link or related credentials. If there is no clear option, contact official support to confirm how to revoke it.
- Follow the panel’s instructions for handling the old credentials, then replace the link on your own devices and retrieve the configuration again. Whether the old configuration becomes invalid immediately depends on the server mechanism; confirm with support.
- If the exposed content also included your account password, change the password and check your account status. Changing the password alone may not revoke a separate subscription token.
When sharing troubleshooting materials, redact the full link, QR code, and authentication fields in the configuration. A QR code is simply another way of representing a link or configuration; it is no less sensitive. Store configuration backups somewhere access-controlled, not in a public sync directory.