A subscription link is an address that compatible clients use to retrieve a list of server configurations. It is not an active network connection. Typically, you copy the link from your service dashboard, add it as a subscription in your client, and update it. Once the client retrieves the server list, you still need to select a server and check the connection status. If the import succeeds but you can’t connect, first determine whether the configuration failed to load or the server connection failed—the troubleshooting steps are quite different.
How a Subscription Link Differs from a Single Server Configuration
A single server configuration describes one connection endpoint and the parameters it requires. A subscription link points to a collection of configurations that can be updated. The client requests the address, parses the response, and displays the included servers. If the service changes its servers, update the subscription to give the client a chance to retrieve the new list. A configuration that still appears in the client does not necessarily mean the service is still using the same endpoint.
A subscription is not guaranteed to use a universal file format. Clients may accept different subscription formats, and even if a link opens in a browser, its response may not work with your client. The protocol used by a server must also be supported by the client. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different protocols or configuration types; renaming one configuration does not make it work as another. Choose a client based on the compatibility notes in your service dashboard and the formats the client actually supports.
| What you receive | What to do | Common misconception |
|---|---|---|
| Subscription URL | Add it as a subscription in the client, then update it | Treating the URL as a server name and trying to connect to it directly |
| Single server configuration | Import the configuration using a method supported by your client | Expecting it to retrieve the full server list automatically |
| Client installer | Install and open the client, then configure the subscription | Assuming installation also imports the servers |
Where to find the link and what to check after copying
Start with your current service’s account dashboard or official instructions to find the subscription page. With VPNUL, sign in to the service dashboard to see available subscriptions and client guides. If the dashboard offers different links for platforms or client types, choose the one that matches your client rather than copying a URL in a different format. VPNUL does not require an email address; keep your account access details secure as instructed in the dashboard.
After copying, make sure you selected the subscription URL—not a webpage URL, installer link, or server sharing link. Extra spaces or line breaks, as well as characters cut off by a messaging app, can cause updates to fail. The safest approach is to use the dashboard’s copy button and paste the link directly into the client’s subscription URL field. There’s no need to send the link to yourself first.
- ✅ Find the subscription link that matches your client in the service dashboard or official instructions.
- ✅ Copy the full URL and paste it into the client’s “Add subscription” field—not the server search box.
- ✅ Give the subscription a recognizable local name, update it, and check that servers appear.
- ✅ After updating, select a server and check both whether the configuration loaded and whether the connection works.
- ❌ Never share the subscription URL in public posts, online parsing tools, or screenshots submitted with support requests.
Some dashboards offer a button to open the link in a client; others provide a URL to copy. Both options are meant to save the subscription source in a compatible client. After following a redirect, check that the subscription was actually added. Simply opening the client does not mean the import is complete. If your browser asks to open an external app, make sure it’s the client you installed.
How to Import a Subscription Into a Client on Different Platforms
Menu names vary by client version, but the process usually involves adding a subscription, importing from a URL, and updating it. Check the client download page for supported software and platform-specific instructions, then follow the menus in your client. The descriptions below are general guidance; not every client uses exactly the same button names.
| Platform | Import steps | What to check afterward |
|---|---|---|
| Windows | In the client’s subscription manager, add the URL, save it, and update manually. | Check that the server list appears, then review the system proxy or client connection mode. |
| macOS | Open subscription management from the menu bar or client window, paste the URL, and update. | Make sure the client retrieved the list and that the connection control is set as expected. |
| Android | Paste the URL into the client’s subscription import field, then refresh the configuration. | Check that the servers have loaded, and approve the connection permission if prompted by the system. |
| iOS | In a compatible client, find the subscription or remote configuration option, paste the URL, and update. | Check the list and system connection permissions. A URL opening in a browser does not mean the import succeeded. |
| Linux | Use a compatible client’s graphical interface or the configuration import method specified in its documentation. | Check that the subscription format can be parsed and that the proxy settings are actually in effect. |
Desktop clients sometimes separate “Save subscription” from “Enable system proxy.” Seeing servers in the list only confirms that the configuration was retrieved; it does not prove that app traffic is using the selected server. Mobile platforms may also require system-level connection permission. Linux clients vary even more: graphical and command-line tools may accept different subscription inputs. Check your client’s documentation, and don’t use a remote URL as though it were a local configuration file path.
If the list is empty after import, first check that the URL is complete, that your client supports the subscription format, and that your current network can reach the URL. If the list loads but only some servers fail to connect, the issue is more likely to involve those servers, protocol support, or your local network. A client that supports VLESS does not necessarily support every transport combination based on VLESS. If parsing fails, check the specific configuration fields and client version instead of repeatedly switching to the same server.
How Often Should You Update It?
There’s no fixed update schedule that works for every subscription. Updating manually is a sensible first step when the service changes its servers, you’ve just imported the subscription, a server suddenly stops working, or the dashboard indicates a configuration change. If your client offers automatic updates, you can enable them to suit your needs. Automatic updates only retrieve the configuration again; they don’t replace checking the actual connection.
It’s important to distinguish between updating a subscription and replacing its URL. Updating makes the client retrieve the saved URL again. Use this when the service still recognizes the URL but the server list has changed. Replacing it means importing a new URL or changing the subscription source after the old one stops working and the service dashboard provides a replacement. Adding the same subscription repeatedly can create duplicate servers in the client and make troubleshooting harder. Before replacing it, check that the new list works, then remove the old subscription according to your client’s instructions.
What to Do If Your Subscription Link Is Exposed
A subscription URL is often treated as a credential for retrieving configuration. Someone with the link may be able to access the server configurations it contains, depending on the service’s permissions and whether the link is still valid. Don’t expose the full URL in public ticket attachments, forum posts, screen recordings, or screenshots of your browser’s address bar. When contacting support, describe the client error and the steps you took. Share information only through official support channels and as requested; don’t send the full link to an unverified recipient.
If you think the link has been exposed, check the service dashboard for an option to reset, regenerate, or revoke it. If one is available, follow the dashboard instructions and import the new URL into your own client. Deleting the local subscription usually does not invalidate an exposed remote URL. If you can’t find a management option, use the contact page to ask how to proceed. Once resolved, check whether the old URL is still saved in your client so you don’t accidentally update from an invalid source later.
Imported Successfully but Still Can’t Connect? What to Check Next
Break the problem down into three layers: configuration, connection, and traffic routing. At the configuration layer, check whether the client can update the subscription and parse the server entries. At the connection layer, check whether the selected server connects. At the traffic-routing layer, check whether the target app is actually using the proxy or connection mode provided by the client. Split-tunneling rules determine which destinations use a server and which connect directly, so one website working while another doesn’t does not automatically point to a problem with the subscription URL.
DNS is also part of traffic routing. Even when the connection shows as successful, the system or app may still use its local DNS settings. If the result isn’t what you expect, check the client’s DNS and routing settings, the system proxy status, and whether the app bypasses the system proxy. A DNS leak occurs when domain queries that should follow a specified route take a different one. Assess this in the context of your connection mode and rules, rather than relying on a single website’s warning. If you’re on a hotel or office network with restrictions, first confirm that the regular network connection works, then compare the results with different servers or connection modes.
When reporting an error, include the error type, the stage where it occurred, and your client version. This is more useful than simply saying “it doesn’t work.” Subscription update errors, protocol incompatibility, failed connections, and apps not using the proxy each call for different troubleshooting steps. For more help, see the troubleshooting guide. If you’re new to the service, you can also follow the Guides to check the setup and connection steps.