If refreshing a VPN subscription fails, or the server list suddenly becomes empty, don’t delete the profile straight away. First determine whether the client can reach the subscription address, whether your account is still active, and whether the app is showing a current configuration. A failed refresh and a failed connection are different problems: the former concerns retrieving configuration, while the latter concerns using a server that has already been imported. Work through these checks in order so you can identify which part needs attention.

Identify What Failed Before Changing the Configuration

Start by noting what the client actually reports. A message such as “update failed,” “network error,” or “unauthorized” points to a different stage of the process than a successful refresh that returns an empty list. If the app reports that no subscription is configured, it may have lost the subscription address or profile rather than failed to contact the provider. Keep the exact error text and the time it occurred; those details are more useful to support than a screenshot of an empty server list by itself.

Check whether the problem affects one device or several. If the subscription updates on another device using the same account, the account and subscription service are more likely to be available, so focus on the affected client’s profile, network permissions, or stored data. If updates fail across devices and networks, check the account dashboard and provider notices before repeatedly reinstalling apps. A temporary service-side issue can look like a local configuration problem.

Also separate subscription retrieval from traffic usage. A client can display imported servers even when a connection is currently unavailable, and a successful connection does not prove the subscription is up to date. Conversely, an account’s data allowance or plan status may affect service use without explaining every subscription-fetch error. Review the account status and any displayed usage or expiration information rather than assuming that an empty list means the allowance has been used up.

  • ✅ Record the client’s exact error and whether the profile still appears in the app.
  • ✅ Compare the same account on another supported device, if available.
  • ✅ Check the provider account page for subscription status, notices, and current usage.
  • ❌ Don’t publish or send an unredacted subscription URL; it may function like an account credential.

A subscription URL can contain an access token or another private identifier. Treat it like a password: don’t post it in a public forum, paste it into an online checker, or include it in an unredacted screen recording. If you need to share diagnostic details, hide the full address and any account identifiers first.

Open the account page or the provider’s official instructions and confirm that you are using the current subscription address for the correct account. A copied address may be incomplete, may contain an accidental space or line break, or may belong to an older profile. If you recently changed a password, reset an account, or replaced a subscription, the old address may no longer be valid. Copy it again from the authenticated account area instead of trying to reconstruct it from browser history or a message.

Read the error carefully. An authentication or authorization response usually calls for checking which account produced the link and whether that account remains active. A timeout, DNS lookup failure, or connection reset is more consistent with a network path problem, although the error alone cannot prove the cause. A response that says the format is invalid may mean that the address was pasted into the wrong field or that the chosen client expects a different kind of configuration.

Test the network without changing several settings at once. If you are on public Wi-Fi, a hotel network, or a workplace connection, first complete its sign-in page in a normal browser. A captive portal can allow the browser to show a login screen while blocking other requests. Then try the update over a different trusted connection, such as your mobile data connection, if available. If the update succeeds there, the original network, its DNS service, or a local filtering rule is a more likely cause than a damaged subscription.

Check whether another proxy, VPN client, firewall, security product, or managed-device policy is interfering. Two clients can compete to change routing or DNS settings, while a firewall may block the app’s connection to the subscription host. Don’t disable endpoint protection or bypass an organization’s controls just to test; ask the device administrator if the computer is managed. On a personal device, temporarily disconnecting another network client for a controlled test can help isolate a conflict. Restore your normal settings after the test.

If you are comparing services or checking which features matter for your own location, the VPN for China overview can provide broader context; it won’t replace checking whether the subscription address itself is valid. For troubleshooting, keep the immediate test narrow: use the same link, make one network change, refresh once, and note whether the error changes.

Refresh the Subscription and Re-Import Only When Needed

Once the account and network checks are complete, try a clean refresh using the client’s normal subscription-update control. The exact label varies: it may be called “Update,” “Refresh,” “Update profile,” or “Update all subscriptions.” Keep the existing profile until you know whether the refresh succeeds. Deleting it first can remove useful information about the URL, selected mode, and previous server list, making it harder to tell whether the problem was a refresh failure or a lost configuration.

Use the following sequence on the device where the problem occurs. Menu names differ between app versions, so follow the client’s own instructions if a control is named differently. The aim is to test one likely cause at a time, not to reset every network setting.

  1. Confirm the active profile. Open the client’s subscription or profile page and make sure the expected entry is still present. If there are several entries, identify the one associated with the account you checked. Avoid editing or deleting profiles until you have identified the correct one.
  2. Check the address privately. If the client allows you to view or edit the subscription URL, compare it with the current address in the provider account page. Do not copy it into a chat or a browser-based diagnostic tool. If the app hides the address, use its supported update or re-import process rather than trying to extract it from local storage.
  3. Test a different connection. Complete any Wi-Fi sign-in page, then switch to another trusted network if possible. Retry the update once and compare the error. A change from a timeout to an authorization message is useful evidence: it suggests the request reached a different stage, but still calls for account verification.
  4. Close and reopen the client. Quit the app fully, reopen it, and run the subscription update again. On mobile, simply leaving the app in the background may not close its network process. Use the operating system’s normal app controls; do not clear all app data as an early troubleshooting step.
  5. Check for an app update and supported format. Use the official distribution channel for the client and review its release notes or provider instructions. A client may not understand a configuration format intended for another application. If the provider offers a compatible subscription option, choose the one documented for that client rather than changing protocols at random.
  6. Re-import if the profile is missing or damaged. Remove or replace only the affected profile, then import the current subscription address using the client’s supported method. Confirm that the profile appears before starting a connection test. If the client distinguishes between a subscription link and a one-time configuration file, select the correct import type.
  7. Verify the result. Check that the server list is populated, select an available entry, and test the connection. If the list returns but connections fail, stop repeating subscription updates and troubleshoot connectivity separately.

The client matters. An official provider app may handle account authorization and profile updates in its own interface. Compatible third-party apps such as Clash Verge, sing-box, or Shadowrocket may require a format or import method specified by the provider. A configuration that works in one app is not automatically portable to another: supported fields, protocol implementations, routing rules, and update behavior can differ. Follow the provider’s current client-specific instructions, and don’t assume that renaming a file or changing a URL suffix converts one format into another.

Cache is another possible source of confusion, but clearing app storage can erase profiles, preferences, and diagnostic evidence. Prefer the client’s built-in refresh or cache-reload option, if it has one. Before using an operating-system “clear data” command or reinstalling, make sure you can retrieve the current subscription again and know how to restore any custom settings. Reinstalling is a later option for a client that repeatedly fails locally after the account and network have been checked, not a substitute for confirming that the subscription address still works.

Bottom line: Refresh the existing profile first, test a different trusted network if the request times out, and re-import only when the profile is missing, outdated, or damaged. If servers return but cannot connect, move on to connection troubleshooting rather than refreshing the same subscription repeatedly.

When to Contact the Provider

Contact support when the account page shows an active subscription but a current link continues to return an authorization error, when the same update fails on multiple devices and networks, or when a supported client repeatedly reports an invalid response. You should also ask for help if the provider’s instructions do not match the options shown in your client. Include the client name and version, operating system, approximate time of the failure, the exact error text, and what you already tested.

Share only the information needed to diagnose the issue. A redacted screenshot can show the error without revealing the subscription URL, account password, or private token. If support needs to verify an account, use the provider’s authenticated support channel rather than sending credentials in an unrelated chat. Don’t upload a full client log publicly: logs may include hostnames, local network details, account identifiers, or the subscription address.

Describe the outcome of each test rather than listing every setting you changed. For example, explain whether refresh works on another device, whether a different network changes the error, and whether the server list returns after a re-import. If you changed several items at once, restore a known configuration where possible and repeat the tests individually. A concise sequence helps support distinguish a server-side authorization problem from a client parser, network, or local cache issue.

While waiting for a response, avoid repeatedly generating new links or replacing profiles unless the provider instructs you to do so. If a link was exposed, say so and ask how to replace it securely. If the issue appears limited to one client, preserve the working configuration on any device that still updates successfully. This gives you a safe comparison point and avoids turning a single-device problem into a multi-device recovery task.

VPN Subscription Update FAQ

Why is the server list empty after a successful refresh?

First confirm that the client updated the intended profile and accepted the response rather than merely reporting that a request completed. Check the account page and the provider’s current instructions, then verify that the chosen client supports the supplied subscription format. An empty list can indicate a profile or parsing issue; it does not by itself establish that the account has no service. If another supported client imports the same current link correctly, report the affected client and its version to support.

Should I delete and add the subscription again?

Not as the first step. Keep the existing profile while checking the account, link, and network. Re-import when the profile has disappeared, is clearly outdated, or the client’s instructions recommend replacing it. Before removing anything, confirm that you can retrieve the current link and restore any settings you need. Never use an old address just because it is still visible in the client.

Does a subscription error mean the VPN server is down?

No. A subscription update retrieves configuration; a server connection uses a configuration that is already in the client. A failed update may involve the address, account authorization, network access, or client compatibility. If the server list is present but a connection fails, troubleshoot the connection separately and check provider notices for relevant service information.

What should I send to support?

Send the client name and version, operating system, exact error text, approximate failure time, and a short summary of the tests you performed. Redact subscription URLs, tokens, passwords, and account identifiers from screenshots or logs. Use the provider’s official support channel and follow its instructions for sharing diagnostic files securely.