A subscription link is the address a client uses to retrieve connection configuration from a server; it typically includes credentials tied to your account. The basic process is to get the link from your account dashboard, import it into a compatible client, update the configuration, and then verify the connection. Copying a link doesn’t mean you’re connected, and a successful import doesn’t guarantee every app will use the expected route.
How Subscription Links Differ from Plans and Nodes
The word “subscription” may suggest a billing period, but a subscription link and a monthly plan are different things. Your plan determines your account’s data allowance and access; the subscription link delivers configuration to your client. Data packs may also use subscription links to configure a client, so the link’s name won’t tell you whether your plan resets monthly.
When a client accesses the link, it retrieves connection details it can recognize, such as server addresses, ports, protocols, and authentication parameters. The exact contents depend on the server and client formats: some links provide only a node list, while others include proxy groups and routing rules. Don’t assume every subscription includes a complete set of rules, or mistake a node list for an active connection.
| Term | Main purpose | Common point of confusion |
|---|---|---|
| Plan | Sets account billing, data allowance, and access permissions | Renewing or upgrading may not require importing the link again |
| Subscription link | Lets a client fetch nodes or a complete configuration | It’s not an installer or a regular webpage to share |
| Individual node | Contains the configuration needed for one connection | Imported on its own, it may not receive subscription updates |
| Client | Parses configuration and handles connections, proxying, and routing | The same link may not be recognized by every client |
A subscription link only delivers configuration. IEPL dedicated lines, relays, and direct connections describe routing paths or transport methods, not subscription formats. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols. A client that can parse a link may not support every protocol it contains, and that doesn’t guarantee any particular connection speed.
Get the Link from Your Account Dashboard
MeveVPN doesn’t require an email address; you can get started with a username and password. Existing users can sign in through the account dashboard. Once signed in, follow the dashboard instructions to find your subscription and client options. Access is determined by your plan status in the dashboard. This guide doesn’t provide a working subscription URL or direct installer downloads.
- Sign in to your account and check your plan status and available data in the dashboard. If access isn’t available yet, follow the dashboard instructions instead of repeatedly copying the same link.
- Check the installation and import instructions for your device in the client downloads, then choose a compatible client and configuration format.
- Use the copy option in the dashboard to get the complete link. Don’t transcribe it from a screenshot or mistake the regular dashboard URL for a subscription link.
- Paste the link into the subscription URL field in your client, save it, and fetch the configuration. If the dashboard offers direct import, make sure it opens the client you intend to use.
After copying, check that a chat app hasn’t split or truncated the URL and that there are no extra spaces, quotation marks, or explanatory text around it. Query parameters may be needed for authentication or format selection, so don’t remove them just because the link looks long. If your browser displays configuration text, don’t mistake that text for a URL and try importing it again.
A subscription link is an account credential. Don’t submit it to an unfamiliar conversion site or post it in a public forum. Screenshots, QR codes, and exported configuration files may contain the same credentials.
How to Import on Different Platforms
MeveVPN supports Windows, macOS, iOS, Android, and Linux. Platform support doesn’t mean every third-party client can use the same configuration. Follow the dashboard and guides for the correct client, version, and format. The general steps below aren’t tied to menu names in any one app.
Windows and macOS: Add the Configuration, Then Connect
In your client, look for the configuration, subscription, or remote configuration option, add the link, and fetch it. Give the configuration an easy-to-recognize local name, select it, choose a route, and connect. Seeing nodes in a list usually only confirms that the configuration was parsed. If the system proxy or the client’s corresponding traffic-routing mode isn’t enabled, your browser may still connect directly.
iOS and Android: Check System Permissions
After importing, the client may ask to create a system VPN configuration or enable related network permissions. Check the app’s source and the system prompt, then follow the guide to grant access. A VPN indicator in the system status means a network-routing feature is enabled; it doesn’t prove that every app uses the same exit route. Check the client settings to see whether apps are excluded or routed directly by rules.
Linux: Know the Difference Between GUI and Service Modes
Graphical clients usually offer a remote configuration option. Command-line tools and background services may instead require a configuration file path, a subscription-fetching tool, or a reload, depending on the software. Don’t treat a subscription URL as an executable command or apply configuration syntax from a different core. After editing a file, check for parsing errors and service logs to confirm the new configuration has loaded.
- ✅ The client source and version match the dashboard or guide, and the client supports the selected subscription format.
- ✅ After fetching the subscription, you selected the intended configuration rather than continuing to use an old one.
- ✅ You selected an available route and enabled the connection or traffic-routing mode as instructed.
- ❌ Don’t treat visible nodes or a system VPN indicator as complete verification.
Update Frequency and Data Resets
Updating a subscription fetches the configuration again; it doesn’t buy data or reset usage. Refresh it when routes or parameters change, old nodes stop working, or the dashboard explicitly prompts you to update. There’s no single update interval that applies to every client. Follow the client’s instructions to enable automatic updates, and fetch the configuration manually to check when connection issues arise.
MeveVPN monthly plans reset data each month on the activation date, and upgrade price differences are prorated for the remaining days. Data packs remain valid until used and never expire. These are account billing rules, unrelated to when you tap “Update subscription” in a client. Refreshing repeatedly won’t restore used-up data or change the reset date to today.
Before updating, note the route and routing mode you’re using. Afterward, check whether they’re still selected. Some clients retain old configurations, while others replace remote content; an update may also overwrite manual changes. If you need custom rules, look for a supported override or separate rules feature in the client. Don’t assume edits to a remote configuration will be kept permanently.
An automatic update failure doesn’t necessarily mean a node is down. Fetching a subscription and connecting through a proxy may use different network paths: an existing node may connect while the subscription domain is temporarily unreachable, or the subscription may fetch successfully while a particular node won’t connect. Track fetch status separately from connection status to avoid misdiagnosing the problem.
Troubleshooting Import and Connection Failures
First identify the step where the failure occurs. Failing to download content, being unable to parse a downloaded configuration, and seeing nodes that won’t connect are different problems. Record the client name, version, error message, and stage of the failure; that’s more useful than simply saying “the subscription doesn’t work.” Always redact the link and authentication details before sharing a report.
| Symptom | Check first | What to try |
|---|---|---|
| Download fails | Link integrity, account access, and network reachability | Copy the link again from the dashboard and check the error message |
| Format not recognized | Whether the response matches the client’s supported format | Use the compatible option provided in the dashboard; don’t change the file extension at random |
| Some nodes don’t work | Protocol support, client version, and route status | Update the configuration and test another route as described in the guide |
| Apps still can’t access the internet after connecting | Matched rules, traffic-routing mode, and per-app proxy settings | Check the actual exit route and DNS path for each app |
If the response is a sign-in page or an error page, the client usually can’t parse it as configuration. Don’t immediately turn to an unfamiliar conversion tool. First confirm that you copied the subscription link from the dashboard, your account still has access, and the selected format matches your client. If the error mentions a certificate, check your device’s date and the official instructions; don’t disable certificate verification just to import the link.
After connecting, distinguish routing rules from leaks. A rule that sends a particular site directly doesn’t automatically indicate a leak. But if a domain you expected to resolve through the proxy is unexpectedly sent to your local network’s resolver, investigate further. Browser Secure DNS, client DNS settings, and the system’s DNS path can all affect the result; the region of a DNS server alone isn’t enough to draw a conclusion.
Compare the target app’s exit IP before and after connecting, then check the client logs for matched rules and DNS behavior. A browser test only shows the browser’s route at that moment; it can’t verify the route for other apps. If you still can’t identify the issue, send redacted logs through the support ticket portal. Don’t post your full configuration publicly.
What to Do If Your Link Is Exposed
If you find your link posted publicly, first remove any shared content you can control, then check the dashboard for an option to reset the subscription or refresh its credentials. If there’s no such option, contact support to find out how to invalidate the old credentials. Deleting a post can limit further spread, but it can’t retrieve copies others have already made.
- Note where the link was exposed and remove the public content. Keep any information needed for support, with sensitive details redacted.
- Use the dashboard or contact support to invalidate the old subscription credentials and get a new link. Confirm whether the old link is still accessible.
- Replace the subscription on your own devices, remove the old remote configuration, fetch the new one, and verify the connection.
- Check exported files, clipboard sync, and shared notes. Remove any copies that still contain the old credentials.
Changing your account password alone may not invalidate an old subscription link, because login credentials and subscription tokens may be separate. Resetting a subscription may not immediately revoke node credentials that someone has already downloaded. Confirm with the dashboard or support how and when the old credentials become invalid. If your account password was also exposed, secure your account as well.