To use a VPN subscription link, copy it from your account, choose “Import from URL” in a compatible client, and update the server list before connecting. It is not a website login or payment link. Update timing depends on the client and system settings, not just the service name.
The difference between a subscription link and a server configuration
A subscription link is an address that a client uses to retrieve configuration. It typically contains access credentials tied to your account. The client uses it to get server names, addresses, ports, protocols, and related settings. The link itself does not accelerate your connection; traffic is routed through the connection between the client and the selected server.
“Updating a subscription” means downloading the configuration again, not renewing a plan. An update may add or remove servers or change settings, but it does not automatically add data to your account. Check your plan status, data balance, and configuration freshness separately.
| Term | What it does | Common misconception |
|---|---|---|
| Subscription link | Lets a client retrieve the server configuration for your account | Copying the link connects you automatically |
| Single-server share link | Imports the settings for one server | It automatically syncs the full server list |
| Local configuration file | Stores a downloaded or manually created configuration | An imported file keeps updating automatically |
| Plan subscription | Defines the service and data available to your account | Updating the configuration renews your plan |
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols or protocol suites, not generic subscription format names. A client that can read a particular subscription format may not support every protocol included in it. Check the client’s supported protocols first, then choose the matching import format provided for your account.
Get your subscription link
Sign in to the VPNNH user panel, find the subscription or connection settings, and use the copy button provided on the page. No email address is required: create an account with a username and password, or sign in if you already have one. See the downloads page for client options. Access requirements differ between iOS and other platforms, so follow the current instructions on the page.
- Make sure you are signed in to the account you plan to use, then check its plan and data status.
- Choose the subscription option that matches the client name or supported format. Don’t select a similarly named format at random.
- Copy the complete address. Don’t include the page title, explanatory text, quotation marks, or trailing spaces.
- Open your client, add the address under subscriptions, configurations, or remote configuration, then update it manually.
- Make sure the server list appears, then select a server and connect.
Opening a subscription link in a browser may download a file or display encoded text or configuration data. That is not necessarily an error, but it does not confirm that the client is compatible. Don’t paste the response into an unfamiliar website to “check” it; review the import result in the client instead.
Importing a subscription in clients on five platforms
The basic steps are the same on Windows, macOS, Android, iOS, and Linux: add a remote configuration, fetch the server list, and enable the connection. Button names vary by client, so the steps below describe what to do rather than assuming every app has the same menus.
Windows and macOS: Import first, then enable the proxy
Add the remote address in configuration or subscription management, give it a recognizable name, save it, and update it. Select the configuration, then enable the system proxy or tunnel mode provided by the client. Seeing server names does not mean system traffic is using the client; some apps also ignore system proxy settings.
Android: Check connection permissions and background restrictions
Add the link in subscription management, or use the import option if it is offered for your account and supported by the client. When Android asks for permission to establish a VPN connection, verify which app is making the request. If updates often stop in the background, check battery optimization and background activity settings instead of repeatedly deleting the configuration.
iOS: Check app support and configuration permissions
First, check the account instructions for client requirements, then select the matching subscription format. After a successful import, iOS usually requires permission to add the configuration. Seeing a VPN configuration in Settings only confirms that it was added; it does not prove that a particular website is accessible. Subscription updates may also be limited when the app is not running.
Linux: Distinguish GUI clients from core configuration
GUI clients usually offer a remote subscription option. If you run a proxy core on its own, configure its remote provider or update mechanism according to the core’s documentation. A subscription URL is not a local configuration file path. If you download a file, check its format, read permissions, and the actual path used by the running service.
If the client reports an unsupported protocol, check its version and core capabilities. Don’t disable certificate verification or change server addresses, transport settings, or encryption options just to clear an error; these settings must match the server.
How often does automatic updating run?
There is no standard interval that applies to every client. Updates may run when the app starts, on a schedule, or when triggered manually. Some clients also use update suggestions from the server. A suggested interval is not a guaranteed schedule; actual timing depends on the app, your settings, and whether the device can connect to the internet.
Check the subscription details to see whether automatic updates are enabled, how the interval is set, and when the last update completed. Sleep mode, background restrictions, network errors, or certificate issues can delay or prevent a scheduled update. After importing, following server maintenance, or when troubleshooting, try a manual update and check the result.
- Update succeeded, but the server list is unchanged: The server-side configuration may not have changed. This is not necessarily a problem.
- Still using an old server after updating: Check which configuration is active. You may have updated one configuration but connected with another.
- Local changes were overwritten: Refreshing may replace the remote configuration. For custom routing, use the client’s supported override or separate rules feature.
Troubleshooting import failures, connection issues, and access problems
First identify where the failure occurs: retrieving the link, parsing the configuration, connecting to a server, or accessing the destination website. Check each stage in order; changing several settings at once makes the cause harder to find.
Can’t retrieve or parse the subscription
Copy the link again from your account and check that it is complete and has not been reset. Make sure your current network can reach the subscription server. A connection timeout may point to a network path issue, while a parsing error is more likely related to the response or format compatibility. A sign-in page returned by the subscription URL cannot be imported as a server configuration.
The server is listed, but the connection fails
Check your account status, client version, and protocol support, then compare with another server available in your account. Converting a subscription format only changes how the configuration is represented; it cannot add support for a protocol the core does not handle. Record the exact error message rather than simply saying it “doesn’t work.”
Connected, but the destination website won’t load
Check whether system proxy or tunnel mode is enabled, whether the target app uses that proxy, and whether routing rules send the destination domain directly. A change in exit IP can help verify the proxy path, but it does not prove that every app uses the proxy or guarantee that the destination service accepts that IP.
A DNS leak means domain lookups are taking an unexpected route; it is not another name for a subscription import error. Check the client’s DNS settings, the browser’s secure DNS, and the system’s DNS resolution path together. A website failing to load alone is not enough to confirm a DNS leak. Don’t delete all your rules indiscriminately, as that may also reroute traffic that should connect directly.
IEPL, relay, and direct connections describe network paths or transport methods; they are not subscription formats. Changing the format does not change the route. See the server list for route details, and test actual access on your own network.
How to reset a leaked link
If your full link or QR code has been exposed, treat it as a leaked credential. Check the user panel for a subscription reset or credential update option, and read the confirmation prompt carefully. Resetting a subscription generally affects its access credentials; don’t assume that changing your login password will invalidate an existing subscription link.
- Remove the public post. If you shared it with someone, don’t assume the risk is over just because they deleted their copy.
- Use the subscription reset option available in the panel. If you can’t find it, ask how to proceed via the support ticket page. Don’t include the full link.
- Copy the new address, replace the old subscription on every device where it was used, and update it manually.
- Confirm that the new configuration loads, check whether the old link has been invalidated, and see if any server authentication credentials also need to be rotated.
Invalidating an old subscription link does not necessarily revoke server settings that were downloaded earlier. Whether the two are linked depends on how the service works; follow the panel’s instructions or ask support. Removing a configuration from your own devices also cannot recall copies others already have.
Post-import checklist
- ✅ The link comes from your own account, and the client supports the selected subscription format and server protocols.
- ✅ The most recent update succeeded, and the configuration you intend to use is active.
- ✅ The connection mode and routing rules meet your needs, and you’ve tested access with the target app.
- ✅ You know where to check automatic update settings and find error messages.
- ✅ Screenshots, support tickets, and shared documents don’t expose the full link or QR code.
If you run into a problem, note your platform, client version, the stage where it occurred, and the error message before contacting support. This is more useful than sending a full configuration containing credentials and helps narrow down the cause.