A VPN subscription update can fail even when your account is active and your internet connection appears normal. The app may be unable to reach the subscription address, the copied link may be incomplete, or a client setting may prevent the refreshed server list from appearing. Start by separating those possibilities instead of repeatedly tapping Update or changing servers at random.
This guide explains five practical fixes for Windows, macOS, Android, iOS, Linux, and compatible third-party clients. First confirm that the subscription link and account are valid; then check the network path, refresh the profile, and re-import only when needed. A subscription update downloads configuration information. It does not, by itself, prove that a VPN connection is working.
Identify what failed before changing settings
Note the exact message shown by the client and what happened immediately before it appeared. “Update failed,” “timeout,” “invalid URL,” and a successful update that adds no servers point to different causes. If the app gives a status code or a brief explanation, record it before dismissing the message. Menu labels differ by client version, but the distinction between a link problem, a connection problem, and a display problem remains useful.
Check the account dashboard separately from the VPN app. Confirm that you can sign in to the account used for the subscription and that the subscription or configuration link is still available there. The dashboard password and the subscription link are different credentials: one gives access to your account, while the other lets a compatible client retrieve settings. Do not paste your password into a subscription field, and do not share the subscription URL in a public forum or screenshot.
120+
countries covered
190+
routes
5
supported platforms
Unlimited
simultaneous devices
These service details can help you set expectations, but they cannot diagnose a failed update. A large server list will not appear if the app cannot reach the subscription service, and a successful profile download does not guarantee that every route will suit every network. Keep the diagnosis focused on the update request first.
- ✅ Record the full error message and the client name before retrying.
- ✅ Check that you are signed in to the account associated with the subscription.
- ✅ Compare the subscription address in the app with the one shown in your account.
- ❌ Do not post or send a complete subscription URL to an untrusted person.
- ❌ Do not delete a working profile until you have confirmed that you can retrieve it again.
Try these five fixes in order
Use one change at a time and try the update again after each one. If you change the network, replace the link, and reinstall the app all at once, you may solve the problem without learning what caused it—and may lose a profile that was still usable. Start with the checks that are easiest to reverse.
Fix 1: Copy the subscription link again
A link copied from a message, note, or screenshot may be truncated or may include an extra space. Return to the account page and use its copy function, if available. In the client, open the existing subscription or profile settings and compare the address carefully. Check that the beginning and end are present, that no punctuation from surrounding text was copied, and that the field contains the subscription URL rather than a website address or account password.
If you have more than one profile, verify that you are editing the one that actually needs updating. Avoid guessing or manually rebuilding a URL. If your account page no longer displays the expected link, use the account’s help or support route rather than trying a link from an old message.
Fix 2: Check the network path
Temporarily test the update on another trusted network, such as switching from Wi-Fi to mobile data or the other way around. This helps establish whether the current network is interrupting the request. If the update works on the alternate connection, the problem may be related to that network’s DNS, filtering, captive portal, firewall, or connection stability—not necessarily to your account or subscription.
Before retrying, confirm that a hotel, campus, or public Wi-Fi sign-in page has been completed. If you already have an active VPN or proxy, disconnect it before testing whether the client can retrieve its subscription. Two proxy applications competing to handle traffic can make the result harder to interpret. When your client provides a proxy setting for subscription updates, only enable it if you understand which existing connection it uses; do not change unrelated routing settings just to clear an error.
Fix 3: Refresh the existing subscription
Use the client’s update or refresh action for the subscription profile, not a button that merely reconnects to the currently selected server. Depending on the application, this action may appear in a profile menu, a subscription management screen, or a context menu. Wait for the result message before starting another request. Repeated rapid refreshes can make it unclear whether the client completed the first attempt or is still processing it.
On Windows and macOS, check whether the app is running and whether a system firewall or security prompt is blocking its network access. If it requests permission to make a system change, confirm that the prompt belongs to the VPN application you installed. On Android, check that the app is allowed to use the network in the background if updates fail while it is idle. On iOS, verify that the app is open and connected to a working network before refreshing; interface names and available background behavior vary by app version.
Fix 4: Re-import the profile when refresh is not enough
If the URL is correct but the profile remains stuck, remove only the affected subscription entry and import it again using the current link from your account. If other profiles contain manual settings, note those settings before removing anything. Some clients treat a subscription as a managed profile and replace its server list during refresh; others may retain a separate manually edited copy. Confirm which entry you are removing so that you do not delete unrelated configurations.
On Windows, macOS, or Linux, a compatible client may offer an “add subscription” or “import from URL” option. On iOS and Android, the import route may be offered by the VPN app or by the system share sheet. Follow the instructions for the specific app rather than assuming that every client uses the same import flow. If you use Clash Verge or sing-box, check that the profile type and import method match the configuration provided for that client. Shadowrocket users should likewise use the app’s supported subscription import option. A client can be compatible with some configuration formats without supporting every provider-specific feature.
For official-client instructions and the current import flow, consult the setup guide. If you are still choosing an access method, the VPN for China page provides the service overview; it is not a substitute for checking that your own client has imported the correct subscription.
Fix 5: Check client version and profile compatibility
If the same link updates in one compatible client but fails in another, the issue is more likely to involve the failing app, its version, or its supported format than the subscription itself. Check whether the app is current using its official distribution channel, and read its import or subscription documentation. Do not install an unofficial modified client just because a search result promises to fix an update error.
Also check whether the client has a profile format, conversion, or subscription-update setting that must match the link. Do not assume that every protocol or configuration option is available in every client. If a client reports that the format is invalid, compare its supported formats with the instructions for that client rather than changing protocol settings blindly. If the app’s documentation is unclear, save the error text and ask support which import method applies to your platform.
Platform-specific checks and a careful retry routine
Once you have worked through the five fixes, make one controlled retry. Close any duplicate proxy or VPN apps, ensure the device has a working internet connection, open the client that owns the subscription, and refresh the correct profile once. Then inspect the result in the app’s server or profile list. If the refresh succeeds, select a route and connect; separately verify that the connection works by loading a website or using an IP-check tool. Do not treat a refreshed server list as proof that traffic is being routed.
- Windows: Confirm the client has network access in Windows security settings and that another VPN application is not controlling the system proxy or adapter. If the client offers both system-proxy and tunnel modes, use the mode described by its setup instructions.
- macOS: Check whether a firewall, network filter, or another proxy utility is interfering. If macOS asks to approve a VPN configuration, verify the app identity and follow the app’s own instructions instead of repeatedly accepting unrelated prompts.
- Android: Check the app’s network permissions and, where relevant, battery or background restrictions. If Android reports that another VPN is already active, close the other VPN app before testing again.
- iOS: Make sure the device is online and the intended app is open. If the profile imports but the list does not change, check that you refreshed the subscription entry rather than only reconnecting to a saved server.
- Linux: Check the client’s own logs and confirm that the account link was entered into the correct profile type. If using a command-line client, avoid placing the full subscription URL in a shared terminal transcript or shell history.
If a route list is present but a connection fails, move to connection troubleshooting rather than repeatedly re-importing the subscription. A profile update and a live tunnel are separate operations. The route list can help you understand the available locations, while the help center may clarify account or client questions. For an account-specific link issue, submit the error details through the account support channel; redact the subscription URL and never include its full access token in a public report.
When the update still fails
Stop repeating the same action if the error remains unchanged. Gather the information that can help isolate the fault: device operating system, client name and version, the approximate time of the attempt, the exact error text, whether another network changed the result, and whether the account page still shows the subscription. This is more useful than reporting only that “the VPN is broken.” Keep the details factual and avoid including passwords, full subscription links, or private account credentials.
If the account page cannot provide a usable subscription link, or if the link fails in more than one compatible client and on more than one network, contact support through your account. If only one client fails while another can update from the same link, include that comparison and ask about the client’s supported format. If the profile refreshes but no route connects, describe that as a connection problem, not a subscription-update problem; the next checks will be different.
Before reinstalling an app, make sure you can access the account and retrieve the link again. Reinstallation can remove local profiles, preferences, and logs, so it is not a harmless first step. Likewise, avoid changing DNS, protocol, routing mode, firewall rules, and subscription settings simultaneously. A small, reversible test provides clearer evidence and reduces the risk of replacing a simple update issue with a broader configuration problem.
Frequently asked questions
Does a successful subscription update mean the VPN is connected?
No. The update retrieves or refreshes configuration information in the client. You still need to select an available route, establish a connection, and check that the device’s traffic is using it. If the list updates but the connection does not start, troubleshoot the connection separately.
Should I keep tapping refresh until it works?
No. Wait for the current attempt to finish and note its result. Repeated requests do not repair an invalid link or a blocked network path, and they can make it harder to tell which attempt produced the error. Change one condition at a time, such as testing another network, then retry once.
Should I delete the old profile before importing again?
Only remove the affected entry if refreshing it does not work and you have confirmed that you can retrieve the current link. Check whether the profile contains manual settings or unrelated servers first. If you are unsure, keep the existing profile and ask the client’s support channel how to replace a managed subscription safely.
What if the link may have expired or been revoked?
Do not try to reconstruct it or reuse credentials from an old screenshot. Sign in to the account and check whether a current subscription link is available. If it is missing or the newly copied link still fails across compatible clients and networks, contact support with the error text and account context, but keep the full link and its credentials private.