A subscription link is the URL a client uses to retrieve nodes or configuration from a service. It usually contains access credentials associated with your account. Getting, importing, and updating the link are configuration sync tasks—not plan purchases or renewals. First, choose a format that works with your client, then import the link, enable the configuration, and verify that it works.
How Subscription Links Differ from Nodes and Plans
A subscription link is best thought of as an address for retrieving configuration. When a client requests it, the server may return a node list or a complete configuration with proxy groups, routing rules, and DNS settings, depending on the format provided. The link is not the node server itself, and having the address does not mean a connection has been established.
A regular web link opens a page; a subscription link is mainly intended for software to read. If opening it in a browser displays text, downloads a file, or shows a preview error, that alone does not prove the link is valid or invalid. Check whether the intended client can parse it and whether its update log reports success. Never submit a private link to a public online checker just to test it.
| Term | What it contains | What it does and its limits |
|---|---|---|
| Subscription link | An address and access credentials for retrieving configuration | Updates the local configuration; does not directly change plan benefits |
| Node share link | Connection details for a specific node | Importing a node usually does not sync later server-side changes |
| Configuration file | Configuration data such as nodes, proxy groups, or rules | A local file does not automatically support remote updates |
| Plan | Account billing, data allowance, and usage benefits | Managed through the account panel; refreshing a subscription does not renew a plan |
For example, VPN27 monthly plan data resets on the activation date. Updating in a client only retrieves the configuration again; it does not trigger an early data reset. When troubleshooting, check the plan status in the account panel and the configuration status in the client separately so you don't confuse the two.
Where to Get a Subscription Link
Get your link from the service's official account panel, not from an address shared by someone else. VPN27 users can start by opening the account panel, checking their account status, and following the current client and subscription instructions. Menu labels may change, so follow what the panel currently shows. No email address is required to open an account, but that does not mean subscription credentials are safe to share publicly.
Before copying, confirm the name and version of the software you plan to use. If the panel offers multiple formats, choose the one for your client. If it provides one-click import, your browser will try to open the installed software. The first time, your system may ask for permission to launch the app. Check which app is being opened; a successful launch does not mean you are connected.
- Check the official panel for the currently supported clients and subscription options. If you haven't installed a client yet, see the client download page for platform-specific instructions.
- Choose a format compatible with your client, then use the panel's copy or import option. Don't manually remove or change parameters in the link.
- After importing, check the configuration name, update status, and node list in the client. Don't paste the link into chat groups or public documents.
- If the panel doesn't offer a compatible format, check the usage guide or submit a support ticket. Don't guess compatibility from the link's file extension.
A token in a subscription URL usually acts as a credential for retrieving configuration. HTTPS protects the link in transit, but it can't stop someone who receives the full link from using it. A QR code may encode the same credentials, so treat it as sensitive information.
Choose a Format and Import It into Your Client
Protocols and subscription formats are not the same thing. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC describe different connection methods; a subscription format determines how nodes and rules are delivered to a client. Even if software can read a configuration file, it may not connect if its core version doesn't support a particular protocol or field. This section covers general concepts and does not mean VPN27 offers all of these protocols.
Configurations commonly use YAML, JSON, or collections of encoded share links. A file extension alone doesn't prove compatibility, and software in the same configuration ecosystem may support different fields. Online converters may be able to read your full subscription and node credentials. Prefer formats provided directly by the panel rather than handing your details to an unknown converter for convenience.
General import steps
- In your client, find the subscription, configuration, or remote configuration section. Add a remote URL and give it a descriptive name for local reference.
- Paste the complete link, save it, and run an update. If you see a format error, first check the format, client version, and whether the link was copied in full.
- Set the new configuration as active, then select a node or proxy group. Seeing a configuration name in the list doesn't mean it's active.
- Follow the client instructions to enable the system proxy or system VPN interface, grant any required permissions, and test the target app.
Platform-specific considerations
On Windows and macOS, the system proxy mainly affects apps that follow system proxy settings. Command-line tools and some apps may need separate configuration. Clients using TUN mode involve a virtual network interface, routing, and system permissions; it is not simply another subscription toggle.
On iOS and Android, you may need to approve the system VPN configuration. On Android, also check background activity restrictions: the connection can drop if the system stops the app, even when the configuration has been imported. Linux graphical clients work differently from command-line cores; after importing, check that the client is running, the configuration path is correct, and routing is set up. See the quick start guide for permissions and installation requirements. Check the panel for iOS availability.
How Often to Update and What Changes
There is no fixed update interval that applies to every service. Follow the service instructions and your client's recommended automatic update settings. Refresh manually if the panel announces a route change, nodes remain unavailable, your subscription has been reset, or the local list is clearly out of date. Repeated requests won't improve route quality and may trigger access limits.
An update may replace node addresses, credentials, proxy groups, or rules, or it may simply retrieve the same content again. If you've imported a complete remote configuration, your local edits may be overwritten. Before customizing rules, check whether your client supports overrides or merging, and keep a recoverable copy of your local settings. Don't keep editing a remote configuration without understanding what an update will overwrite.
If your existing connection still works but updates fail, the issue may be with the subscription retrieval path rather than all your nodes being down. Some clients let you choose a proxy for updates; others connect directly by default. If an update depends on a proxy that has already stopped working, you can end up in a loop with no way to recover. Check the client's update connection settings and, if needed, retrieve the configuration over a trusted network.
How to check an update: First review the update result and error message, then check whether the configuration is enabled, and finally test the target app. A changed update timestamp doesn't prove the connection works, and an active plan doesn't guarantee the local configuration is correct.
How to Verify an Imported Configuration
Check the configuration, connection, and routing—not just whether the client icon changes color. First, open my IP to see your browser's current public IP, then check the client's connection log to see which rule and outbound route were used for the target domain. An IP change only shows the route used for that browser request; it doesn't prove all apps use the same route.
- ✅ The configuration updated without errors, the expected nodes or proxy groups are listed, and the newly imported configuration is active.
- ✅ When the target app makes a request, the client shows the connection and applies the expected proxy or direct-connection rule.
- ✅ The browser's public IP matches the selected route; command-line tools, IDEs, and other standalone apps have also been tested individually.
- ✅ DNS resolution matches the routing rules, and test results are not mistaken for a guarantee of privacy or anonymity.
A DNS leak usually means DNS requests did not follow the expected route and instead went to an unintended resolver. System DNS, client DNS, and encrypted DNS in the browser can all affect the results. If the browser uses its own encrypted DNS, it may not follow the client's DNS rules. Check each setting against the client documentation rather than switching everything on or off at random.
Routing rules determine which requests connect directly and which use a proxy; rule order and matching behavior affect the outcome. A node's region doesn't determine the region every website sees. A service may also consider account region, cached data, and its own access rules. Subscription content can't turn an ordinary route into a dedicated IEPL line: dedicated lines, relay routes, and direct connections describe underlying network paths, while actual performance still depends on your local network and the destination service.
Reset and Troubleshoot a Leaked Link
If you suspect a link has leaked, stop sharing it and look in the official panel for an option to reset the subscription or revoke its token. If there is no such option, contact support through a ticket to confirm what to do. Changing your login password may not revoke a subscription token, and deleting the configuration from your client only affects that device—it does not revoke the link on the server.
- Use the appropriate reset option in the panel, or ask support how to invalidate the old subscription credentials.
- Get a new subscription link, replace the old one on every device where it's in use, and update the configuration again.
- Delete screenshots, cloud notes, shared clipboard entries, and chat messages containing the old link. Check whether any automated tasks still use it.
- Confirm that the old link has been invalidated by the server. If node credentials may also have leaked, ask whether they need to be rotated too.
Invalidating a subscription token is not the same as invalidating node credentials that have already been downloaded. If someone has already obtained the configuration, revoking access to the retrieval URL alone may not stop them from continuing to attempt connections. The actual scope of revocation depends on the server-side mechanism; don't assume a reset immediately terminates every existing connection.
How to Triage Update or Connection Errors
For authentication or permission errors, first check your account status and whether the link has been reset. For parsing errors, check the subscription type and client version. For timeouts, check your local network and the subscription retrieval route. If the list loads but a target site won't open, check the node, routing rules, DNS, and the destination service's restrictions. Change only relevant settings one at a time and keep the original error message so you can identify what restored access.
When contacting support, include the client name and version, operating system, error message, and steps to reproduce the issue—but hide the full subscription URL and token. VPN27 supports unlimited devices and offers a 60-day no-questions-asked refund. You can request a full refund for any reason within 60 days of your first payment. Device coverage doesn't change the need to keep subscription credentials secure. For further help, see the FAQ.