A failed subscription refresh can leave a VPN client showing an empty server list, old entries, or an update error. The cause may be as simple as a temporary network interruption, but an expired account, a copied-wrong link, or an incompatible client can produce similar symptoms. Start by identifying exactly what changed: did the refresh fail, did the list disappear, or can you select a server but not connect? That distinction helps you avoid deleting a configuration that might still be recoverable.
Identify the Subscription Update Error
A subscription link is an address that a compatible client uses to retrieve configuration. It is not necessarily a page you can open in a browser, and it is different from the website address used to sign in to an account. A client can also store imported configuration locally, so an existing server list does not by itself prove that the latest refresh succeeded.
Before changing settings, note the client name, operating system, error message, and time of the failed attempt. Check whether the list is completely empty or whether only newly added servers are missing. If the existing entries remain, avoid removing them until you know whether you can refresh or restore the configuration. If the client reports that the subscription updated successfully but shows no servers, the issue may be parsing or compatibility rather than account access.
- ✅ Check whether the account is active and whether the service dashboard shows a valid subscription.
- ✅ Confirm that the client is online and can access the network you are currently using.
- ✅ Read the update result, including any wording about authorization, format, or connection failure.
- ❌ Do not post a subscription URL, QR code, or configuration file in a public forum; these may contain account access credentials.
- ❌ Do not repeatedly delete and re-import profiles before confirming that you have the correct subscription address.
90+
Countries covered
150+
Available routes
5
Supported platforms
Unlimited
Online devices
These service details describe coverage and supported platforms; they do not diagnose a specific client error. For troubleshooting, the useful question is whether the client can retrieve and understand the configuration associated with your account.
Common Causes and What to Check
Account or access problem
If an update fails with an authorization message, first sign in to the service dashboard and check the account status. A client may still display entries from an earlier successful import even when it cannot retrieve new data. If you recently changed account details, renewed, or switched devices, follow the service’s current instructions for obtaining or refreshing the subscription. Do not assume that an old link is still valid after an account-level change.
Also check whether the client is using the subscription associated with the account you intended. Multiple profiles can have similar names, and it is easy to refresh an old entry by mistake. When possible, compare the profile label and its source in the client with the current setup instructions, without sharing the private address itself.
Network or temporary fetch failure
A client needs a working path to retrieve subscription data. Captive portals, restrictive Wi-Fi, unstable mobile data, DNS problems, or a temporary interruption can prevent that request from completing. Open an ordinary webpage to confirm that the device has general connectivity, then try the update again after reconnecting to the network. If you have access to another trusted network, test there once; success on one network and failure on another narrows the problem to the network path rather than the imported profile.
Check the device date and time as well. Incorrect system time can interfere with secure connections, certificate validation, and authentication. Set the clock automatically, restart the client, and retry. If the client has a request log, look for whether the failure occurred before receiving data or after data was downloaded. A fetch failure and a parse failure call for different next steps.
Client format or configuration compatibility
Not every client accepts every subscription format, protocol, or transport. A subscription may download successfully but still produce no usable entries if the application cannot parse its contents or does not support the configuration’s requirements. Confirm that you are following instructions for the client you actually installed, and check whether its version and core are compatible with the provided configuration.
This matters when moving between an official platform client and a third-party application such as Clash Verge, sing-box, or Shadowrocket. These apps have different import flows and feature support; a generic “add profile” button does not guarantee that a particular subscription format will work. Do not convert a profile using an unfamiliar online tool or paste its contents into a public converter. That could expose sensitive access information and may also produce a configuration that no longer matches the service.
| What you see | Likely area to check | Next action |
|---|---|---|
| Authorization or access error | Account status, subscription access, or an outdated profile address | Sign in to the dashboard and follow the current subscription instructions. |
| Timeout or connection error | Device connectivity, network restrictions, DNS, or a temporary interruption | Reconnect, test a trusted alternate network, and retry the update. |
| Update succeeds but no entries appear | Import format, client compatibility, or configuration parsing | Verify the client-specific import method and check its update log. |
| Old entries remain, new ones are missing | Refresh failure, stale local data, or a profile that was not updated | Confirm which profile was refreshed and inspect the result message. |
Step-by-Step Recovery
Work through these steps in order. Make one change at a time and retry the update after each relevant check. This keeps the diagnosis clear and reduces the chance of losing a profile that still contains useful settings.
- Check the account first. Sign in to the service dashboard using the account associated with the client. Confirm that the account and subscription are in good standing, then open the current setup or client instructions. If you cannot sign in, resolve that access issue before troubleshooting the client.
- Confirm the device connection. Make sure the device is online, complete any Wi-Fi sign-in prompt, and check that automatic date and time are enabled. If the update still times out, disconnect and reconnect to the network or try a trusted alternate connection. Avoid changing DNS, firewall, or routing settings unless you understand how to restore them.
- Refresh the correct profile. In the client, identify the profile linked to the subscription and use its own update or refresh command. Some applications have separate actions for reloading a local configuration and fetching a subscription; choose the action that retrieves updated data. Wait for the client’s result rather than assuming that a button press completed the request.
- Read the update result and logs. Note whether the client reports an access failure, a timeout, an unsupported format, or a parse error. The exact wording varies by application. If logs are available, review only the relevant error lines and redact subscription addresses, tokens, usernames, and other personal information before sharing diagnostic details with support.
- Check compatibility before re-importing. Compare the client’s documented import method with the service instructions. Update the client only through its official distribution channel, then restart it and retry. Do not install an unknown build simply because a search result claims to fix missing servers.
- Re-import only when needed. If the existing profile is damaged or the service instructions explicitly require a new import, obtain the current subscription information through the authenticated dashboard. Keep the old profile until the new one has imported successfully, if the client allows both to remain temporarily. Never send the subscription URL to another person for testing.
If you are setting up a client for the first time rather than repairing an existing profile, the quick start guide can help distinguish account access, client installation, and subscription import. For general service information, Best VPN for China is a useful starting point; it is not a substitute for the client-specific import instructions.
When the Server List Is Still Empty
If the client reports a successful download but displays no usable servers, focus on what happened after retrieval. Check the update log for parsing errors, unsupported fields, or an empty result. Confirm that the correct profile is selected and that the client has not filtered the list by group, region, or connection type. A filter can make entries appear missing even though the imported configuration is present.
Next, test whether the same subscription can be imported using a supported client, but do this only if the service’s instructions permit that client and you can protect the subscription credentials. If another compatible client can read the configuration, the original application’s format support or local profile state becomes more likely. If multiple compatible clients fail in the same way, the account, link, or service-side configuration deserves closer attention.
Do not infer that a missing list means every server is unavailable. A subscription refresh retrieves configuration; connecting to a server is a separate operation that depends on the selected entry, the client’s protocol support, and the current network path. Once entries return, test a single server before changing routing rules, DNS settings, or several profiles at once. If entries appear but connections fail, record that as a separate symptom and troubleshoot the connection rather than repeating subscription imports.
When contacting support, provide the operating system, client name and version, the time of the update attempt, the exact non-sensitive error text, and the steps already tried. Describe whether the client downloaded data, parsed it, and displayed entries. Do not include the full subscription URL, passwords, QR codes, or an unredacted configuration file. Clear evidence helps support distinguish an account issue from a client or network problem without exposing credentials.
- ✅ Check whether a client-side filter or group selection is hiding imported entries.
- ✅ Separate “subscription update failed” from “server connection failed” in your notes.
- ✅ Keep a known-good profile until the replacement has been tested.
- ❌ Avoid resetting all network settings as an early troubleshooting step; it can create new problems unrelated to the subscription.
Frequently Asked Questions
Can I open a subscription URL in a browser?
Not necessarily. A subscription URL is generally intended for a compatible client to retrieve configuration, not as a regular webpage. A browser response that looks blank, unreadable, or like plain text does not by itself prove that the address is invalid. Use the import or update flow described for your client, and treat the URL as private account access information.
Should I delete the old profile before importing again?
Usually, keep it until you know what failed and have confirmed that a replacement imports correctly. The old profile may still contain usable entries or settings. If the client requires removal before re-importing, make a safe local note of non-sensitive settings first, and never copy credentials into an untrusted place.
Why does the update say successful but show no servers?
The client may have retrieved data but failed to parse it, may not support the configuration format, or may be displaying a filtered view. Check the client’s update log, confirm its subscription format support, and remove any active list filters. If the log indicates a parsing or compatibility error, repeating the same import is unlikely to solve it.
What information is safe to send to support?
Share the operating system, client name and version, the time of the attempt, the exact error message, and a concise description of your troubleshooting steps. Redact subscription URLs, tokens, passwords, QR codes, and configuration contents. If a log contains account identifiers or connection details, remove them unless support specifically requests a safe, redacted excerpt through an appropriate private channel.