From getting started to ongoing maintenance

The Complete MSGVPN Guide

To connect a device first, follow the Guides for a quick walkthrough. This manual follows the setup process in order, explaining what to expect at each step and where to check if something goes wrong. If you’re already using MSGVPN, jump to the relevant section from the contents.

Service and use cases

What your account, subscription, and client each do

MSGVPN is a network acceleration subscription service for access to services in mainland China and cross-border access. It covers 120+ countries and 190+ routes, with no limit on the number of devices connected at once. Use the account panel to view your account, orders, and subscription; use the client on your device to import the subscription, choose a route, and connect. They serve different purposes: being able to open the panel in a browser doesn’t mean your device traffic is using the selected route. Likewise, a client still showing a previously selected region doesn’t mean your account still has active benefits. Before troubleshooting, identify which layer the information comes from.

Think of the subscription as the way your client retrieves route configuration. Once imported, the client usually keeps a local copy, so logging out of the panel won’t automatically remove the client’s list. Similarly, uninstalling the client won’t cancel an order in the panel. A node is a selectable connection point in the configuration; a route is the path your traffic actually takes. Switching nodes may change your experience, but it won’t fix an inactive order, an incomplete subscription copy, or an inactive account.

Choose a route based on what you need to do

For access to services in mainland China, first check where the website or app provides its service, then see whether the client offers a route for that region. When using work systems or online tools across borders, focus on whether you can log in, use the site, and transfer files without interruption—not just the response time shown in the list. For video calls, check for choppy audio; for large transfers, watch for stalls. On organization-managed devices or networks, check the applicable policies first and don’t replace the organization’s prescribed connection method with a personal configuration.

Coverage indicates how many regions and routes are available; it doesn’t mean every route in a region supports every feature of a service. Streaming libraries, account eligibility for online tools, and regional payment requirements are determined by each platform. If you see a regional restriction, check whether it refers to your access region or account eligibility. If a page opens normally but the platform rejects an action, don’t assume the network connection failed. See the node page for available regions, then check the panel and client for the options available to your account.

Establish a baseline you can reproduce

For your first setup, use your most frequently used device and a familiar destination. Before connecting, note whether you can open it, how far you get, and whether other network tools are running on the device. Then compare before and after on the same device, network, and destination. If you change your browser, network, and route all at once on setup day, even an improvement won’t tell you which change made the difference. When a problem comes back, you’ll likely have to test each condition separately anyway.

Keep your account password in a secure password manager and your subscription URL on the device where you’ll import it. They serve different purposes, so there’s no need to store both in the same note. On shared devices, first check who can access the local user account. The unlimited simultaneous device limit describes how many devices can connect; it isn’t a recommendation to share your account credentials. For your first setup, keep this order in mind: check your benefits in the panel, confirm the configuration in the client, then verify access in the app you want to use.

Choosing a monthly plan or data package

Choose a billing option that fits how often you use it

A monthly plan suits people who need the service every month and want to track data by billing cycle. Data resets monthly on the day you activate the plan—not necessarily on the first of the month—so don’t count any remaining data toward the next cycle’s budget. A data package stays available until used and never expires. If your usage is concentrated around work trips, family visits, or a specific project, with little use otherwise, compare the data packages. The main difference is when data resets and what happens to unused data—not that one option is always better value.

Plan data allowances and prices
Billing optionPriceDataData terms
Monthly plan¥9.9/month60GBResets monthly on the activation date
Monthly plan¥18/month250GBResets monthly on the activation date
Monthly plan¥28/month500GBResets monthly on the activation date
Data package¥158300GBNever expires; use it whenever you need
Data package¥3581000GBNever expires; use it whenever you need
Data package¥6583000GBNever expires; use it whenever you need

Estimate by app usage, not device count

When estimating usage, consider browsing, video streaming, cloud storage sync, and app updates separately. Text browsing is usually easier to estimate; long streaming sessions, automatic backups, and one-off downloads can make two sessions of the same length use very different amounts of data. If your device tracks network usage, review a representative recent work period to identify the apps using the most data. If the stats include traffic that doesn’t go through the client, treat them as a guide, not as your account usage in the panel.

There’s no limit on simultaneous devices, so don’t choose a higher tier just because you plan to install the client on a computer and mobile devices. Consider whether they’ll stream, sync, or download at the same time. For example, while your computer is in a video meeting, another device might be uploading photos in the background. Looking only at the meeting’s usage misses activity from other devices on the same account. If you occasionally download large files, first check whether they need to use the accelerated route before including them in your regular budget. A plan’s listed data allowance is a billing quota, not a speed rating for one device.

Compare upgrades and refunds without placing duplicate orders

If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. It isn’t simply a matter of paying the difference between list prices and keeping the original expiry date. Before upgrading, check your current benefits and carefully review the result shown on the panel’s confirmation page. Don’t substitute your own per-day calculation for the checkout total, and don’t apply monthly-plan upgrade rules to a data package. If the option shown doesn’t match your expectations, keep your current plan, exit the confirmation step, and check whether you selected the wrong billing option or tier.

MSGVPN offers a 7-day no-questions-asked refund. See the Terms of Service for the specific conditions. After activation, test your main use case first—for example, play something you watch regularly or complete a typical work task. Don’t stop at seeing “Connected” in the client. If you’re considering a different tier, note your current balance, typical use, and any high-usage tasks coming up. That way, you can choose a plan to address a specific data need instead of buying more data because of a one-off slowdown.

On the plans page, first decide whether you want data to reset monthly or remain available until used. Then compare tiers within the same billing option. In the panel, rely on the plan name, price, and data allowance shown on the confirmation page. Don’t remember only the price—the billing period also matters. Once you’ve made your choice, follow the ordering steps in the next section rather than comparing several options during checkout.

Account setup and order checks

Create an account and confirm which one you’re signed in to

MSGVPN doesn’t require an email address. Create an account with a username and password on the account setup page, then save them securely. Use a password you haven’t reused with another service, and associate the saved entry with this site’s domain. If your password manager stores credentials for multiple sites, check the current address and username after autofill instead of repeatedly submitting details that clearly don’t match.

If you already have an account, go straight to the login page. If your browser still has an earlier session, open the account overview and confirm it’s the account you intend to use for your purchase and subscription. On shared family browsers or profiles used for both work and personal activity, it’s easy to place an order in one account and then look for the benefits in another. Don’t switch between multiple checkout pages until you’ve confirmed which account is signed in.

Complete payment for the same order

In the panel’s plans page, find your chosen option and check its name, billing method, data allowance, and price before proceeding to checkout. Payment methods are Alipay / WeChat Pay / USDT. Follow the instructions shown for this order. Don’t use payment details copied from old screenshots, forwarded chats, or saved bookmarks. For USDT, use the currency, network, and payment details displayed on the current order. If you can’t confirm the network is correct, stop and check before paying; don’t guess at missing information.

Before switching payment methods, check whether the current order can still be completed or needs to be canceled. If you submitted payment but the result page didn’t load, don’t assume the payment failed just because you weren’t redirected. Return to the panel in the original browser session and check the same order against the payment provider’s record. Refreshing the order status and clicking Pay again are different actions: the former checks the status, while the latter may initiate another payment. If the connection drops or the page closes, keep the original order number; it makes reconciliation easier than creating a new order.

Check the order and benefits separately

After paying, check the order status, then review your current benefits in the account overview. Check both separately: the order shows which transaction your payment applies to, while the overview shows the plan and data currently available to you. If the order has updated but the expected benefits aren’t showing, first make sure you’re signed in to the original account, then reload the panel. Don’t use the client’s region list to confirm a new order; it may be showing a locally cached list.

If the billing details still don’t match, use a support ticket in the panel to include your chosen plan, order number, payment method, payment provider result, and what the panel shows. In screenshots, keep only the information needed to check the transaction and hide unrelated account details and reusable payment credentials. To request a refund, start with the original order: identify the order to be handled, review the Terms of Service, then explain the request in a ticket. While billing is being reviewed, don’t place a replacement order just to get the client working again.

Getting your subscription and updating your configuration

Get the import option that matches your client from the panel

After signing in, open the account overview and look for the import or copy option in the subscription section. Import methods can vary by device. If the panel offers a direct import option for your client, follow the prompt to open the app. If you need to import manually, copy the subscription URL provided for that client. Downloading, installing, signing in, and importing are separate steps: installation puts the app on your device; importing gives the client your account’s configuration.

Your subscription URL may contain credentials used to retrieve configuration. Copy the entire address, including its beginning and end; don’t copy just the domain or remove parameters after the question mark. If you need to move it to another device, sign in to the panel on that device and copy it there, limiting how often it passes through chat history, public documents, or a shared clipboard. Don’t paste the URL into a search engine or submit it to an unknown online conversion tool. This guide doesn’t provide usable subscription URLs; only use the one in your own account.

Tell an import failure from a list that hasn’t switched

For manual import, find the client option for accepting a remote subscription URL. Don’t paste it into a server field for a single node or choose an option that only accepts a local file. After saving, check whether the subscription entry appears, the refresh completes, and the route list loads; these may happen at different times. Some clients also require you to select the new configuration as the active one. If you still see the old region after refreshing, first confirm that the new entry is active rather than assuming the panel didn’t provide any routes.

If the client says the link is invalid, check that the full URL was entered, there are no extra spaces, and the import option matches the client’s format. If it times out while retrieving the configuration, check whether the panel opens on the same network, then see whether another proxy or network tool on the device is affecting the client. If parsing fails, note when the error occurs and check that you haven’t used the panel’s webpage address as the subscription URL. If you already have a working configuration, keep it for comparison rather than deleting everything straight away.

Use recognizable names to manage multiple devices

Give each device configuration a recognizable local name so you can distinguish the account you’re using from older saved configurations. Names are for identification only; don’t include passwords or subscription parameters. After changing plans, check your account in the panel, then refresh the existing subscription on each device and see which ones still use an old copy. Avoid repeatedly adding the same entry: otherwise, it’s hard to tell which configuration a region belongs to and easy to test the wrong one while troubleshooting.

If you think the URL has been exposed somewhere it shouldn’t be, remove it from shared locations first and check whether the panel offers an option to replace the subscription URL. If you’re unsure, ask how to proceed in a support ticket. If you replace it, update each device in use and verify access with a real destination. Deleting the configuration from one device won’t revoke a URL that was already copied elsewhere. Before sending an error screenshot, check whether it displays the URL in full; if in doubt, describe the stage where the error occurred in text instead.

Import the client on each platform

Supported platforms: Windows / macOS / iOS / Android / Linux. Start at the panel downloads page to get a client. After signing in, you can get a client for Windows, macOS, Android, and Linux without a purchased plan. On iOS, the download option depends on the plan status shown in the panel. The steps below describe the results to look for and don’t rely on button names that may vary by version.

Windows: import first, then check whether apps are using the connection

Get the Windows client from the panel, install and launch it, then open configuration or subscription management to add and refresh the subscription from the panel. Once the route list appears, select that configuration, choose a route, and enable the appropriate connection mode. If your browser works but a work app still behaves as if it’s offline, check whether the app uses the system proxy, has its own network settings, or needs a restart to pick up changes. Don’t keep entering different proxy values in both the client and system settings. See the Windows client selection guide for more on connection modes.

macOS: approve the prompt and confirm the connection is active

Open the client and use the direct import option provided by the panel, or add the remote subscription in the app. If macOS asks to add a network configuration, confirm the request comes from the client you just launched, then follow the client’s instructions to approve it. Once the configuration syncs, select a route and open a familiar page in your usual browser. If you’ve granted permission but still can’t connect, check for an old configuration or a management policy that may be affecting access. Don’t remove network settings from a work device without approval. After quitting the client, you can also check whether the system’s network settings have returned to the expected state.

iOS: check your plan status, then allow the connection

In the panel, confirm that your plan is still active, then use the App Store link on the downloads page. Once the app is installed, start the import from the panel or paste the matching subscription URL into the app. If iOS prompts you to add a VPN configuration when you first connect, confirm the app and follow the system instructions. In the client, select the current configuration and a route, then verify access in the app you want to use. If the installation option isn’t available, check that your benefits are active instead of looking for an unknown installation file. If the connection drops after switching networks, wait for the network to recover and test again.

Android: manage connection conflicts and background restrictions

Download and install the Android client from the panel, import the subscription, refresh the list, and choose a route. Then approve the system prompt allowing the app to establish a VPN connection. If another app on your device already uses the VPN interface, decide which one should manage the current connection to avoid conflicts. Only if the connection regularly drops when the screen is off, check whether the system restricts the client’s background activity and adjust that app’s battery settings. Don’t disable all device protections to fix a problem with one app. See the Android setup guide for details.

Linux: check the installation method and traffic coverage first

On the downloads page, check which installation methods are offered for your device and follow the relevant instructions. Don’t run commands from unknown sources with administrator privileges if you don’t understand what they do. Open the client, add the remote subscription, and select the refreshed configuration. With an application proxy, desktop browsers and terminal programs may use different settings. Even if a graphical app works, separately check the terminal tools that need network access. If the configuration involves system routes or network interface permissions, save the original settings and check device management requirements first to avoid disrupting other users or services during testing.

Settings to check after importing and selecting a route
PlatformCheck firstWhen to check
WindowsActive configuration, system proxyOnly some apps behave unexpectedly
macOSNetwork configuration permissionsApp runs but no connection is established
iOSSystem VPN configurationOn first connection or after switching networks
AndroidVPN control, background restrictionsDisconnects when the screen is off or the connection is replaced
LinuxApplication proxy and routing scopeDifferent results in graphical apps and the terminal

After setting up each platform, test connecting and disconnecting once. On shared or remotely accessed devices, especially check that the network works again after disconnecting. If enabling the client disrupts your management connection, restore the original settings locally before deciding whether to expand its routing scope. When testing several devices, note each device’s active configuration and mode; don’t assume that the same subscription means they’ll behave identically on the network.

Connection and access checks

Check the configuration, route, and destination—in that order

First open the client and confirm that the active configuration is the one you imported or refreshed from your account, not a default left over from installation. Choose a region that suits your needs, connect, and watch whether the client stays connected, prompts for system permission, or repeatedly returns to a disconnected state. Finally, open the actual website or app you want to use and complete a normal task. Seeing a homepage doesn’t mean the whole service works. Reading an article, submitting a normal request, or starting a legitimate stream tells you more than the homepage title alone.

Keep other conditions unchanged while testing. Compare results on the same device and network you used before, changing only the connection status or route if possible. Browser cache may make a previously opened page look accessible; reload it or open a public page you haven’t viewed yet so you’re not mistaking local content for a new response. For video, check that playback continues—not just the cover image or search results. When you’re done, disconnect and confirm that local apps that don’t need acceleration still work as before.

Narrow down the problem by where it fails

If familiar websites stop opening after you disconnect, troubleshoot the local network first. Public networks may require you to accept their access terms, and a home network can also go offline. If the basic network works but the client can’t load the list, return to subscription import and check the URL and your account benefits. If the list loads but the connection won’t establish, check permissions and other network tools, then try another available route in the same destination region. If only one destination fails, note whether it returns a timeout, login error, certificate warning, or a regional notice from the service itself.

Local route latency, response time to a node, and the target service’s response speed are different things. A probe to a node reflects only part of the connection; it can’t tell you whether an app will complete a task without interruption. If things slow down during peak hours, compare whether the same destination works over another available route at the same time. If you change both the network and region, it’s hard to tell which made a difference. If an app asks you to log in again, first consider whether your account session or a region change might be involved, rather than repeatedly switching routes for the same task.

A terminal check only tests requests from that program

If curl is installed on your device, you can use the command below to send a public request that doesn’t include account information. It requests response headers, doesn’t use your actual subscription URL, and doesn’t configure a system proxy. An HTTP response means the program can reach the test site with its current settings; it doesn’t prove that the request used your selected route. If it fails, keep the error type as a clue. Don’t disable certificate verification just to make the command succeed.

curl -I https://example.com/

If the browser and terminal give different results, first check whether they use the same proxy settings. The terminal may use environment variables, while the browser may follow system settings or its own configuration. Mobile apps don’t necessarily behave like desktop browsers either. During troubleshooting, note the app, network, mode, selected region, and stage where the error occurs. If reproducing the issue requires signing in, describe the step that fails without sharing session details from the page. That way, even if you switch devices later, you can repeat the key test under the same conditions.

Routine maintenance and renewals

Use the panel to check billing; use the client to check connectivity

For routine checks, review billing and connectivity separately. In the account overview, check your plan, remaining data, and active status; in the client, check the current configuration, route, and last refresh result. The traffic count shown in a client may apply only to the local device or current session, so it isn’t measured the same way as the remaining data in your account. If several devices are online at once, check background backups, file sync, and app updates first, then decide which apps need to use the client based on what you’re doing.

Monthly plan data resets each month on the activation date. Use the billing period shown in the panel to schedule tasks that involve transferring a lot of data. Don’t confuse the data reset with an extension of your plan’s validity; before renewing, check both your remaining data and your current benefits. A data package never expires and remains available until used, so keep an eye on the balance rather than estimating when it will run out based on the calendar. Even if you use it only occasionally, check that your configuration can still refresh on the device you’ll need before an important task, and leave time to handle any issues.

Renew on the original account, then check your devices

Before renewing, make sure you’re signed in to the original account, then check your current benefits and plan options in the panel. After choosing a renewal or upgrade, review the billing method, data allowance, and total on the confirmation page. If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days; don’t assume the result based on the expiry date of your previous order. If you have questions about the terms, don’t confirm payment yet. Review the plan details or use a panel support ticket to describe your current benefits and the plan you’re considering.

After payment, follow the same checks as when you first activated: confirm the order, check the account overview, then refresh the subscription on your devices. If one device works again but another still says it’s unavailable, compare whether both are using configurations from the same account and whether the client refreshed successfully on each. Don’t place another order because one device still has a cached configuration. If you stop using a device, disconnect it and remove its local configuration. Before handing it over, also clear sensitive content from browser sessions and configuration backups.

Keep a recoverable copy of your settings before updating

If the client behaves unexpectedly, first save a record of the settings without credentials, including the connection mode, frequently used regions, and any necessary app exceptions. Update the client from the panel downloads page, and finish any active calls or transfers first. After updating, check that the right configuration is still active, system permissions are as expected, and your usual apps can connect. Avoid changing the proxy mode and system network settings at the same time as updating the client; otherwise, if something goes wrong, it’s harder to identify the cause.

When reporting a problem, say when it started, whether it followed a renewal or app update, and whether it affects just one device or network. Describe steps that reproduce it—for example, the refresh succeeded, but the app request timed out after switching to the destination. Don’t just say the connection is bad. Include the original order details for billing issues and the relevant error text for connection issues. There’s no need to submit unrelated account details, subscription parameters, or other transaction information. Changes to work network policies should be reviewed by the appropriate administrator.

Split tunneling and advanced troubleshooting

Understand the limits of each mode before changing settings

If your client offers rule-based and global modes, rule-based mode uses conditions such as destination or app to decide whether traffic goes through the proxy or connects directly. Global mode sends traffic within the client’s control to the selected route. The key is which traffic the client controls. If only the system proxy is enabled, some apps may ignore that setting entirely; even with global mode selected in the client, their traffic may not pass through it. Modes that use a virtual network interface or system routes typically cover more traffic and are more likely to affect workplace networks or local services.

Before setting up split tunneling, list the specific destinations: which apps need acceleration, and which local sites, printers, or work resources should keep their usual route. Add only clearly necessary exceptions; don’t replace your current configuration with a large set of rules from an unknown source. If the client shows rule-matching logs, use them to check which rule a request actually matched and whether a broad rule near the top matched first. A subscription refresh may replace client-managed configuration, so check whether the app offers a separate way to save custom rules you want to keep.

Check DNS resolution, the app, and the route separately

DNS resolution looks up the network address for a destination name; a successful lookup doesn’t mean the connection will succeed. If access fails, keep the original error from the browser or app and don’t rush to change system DNS. If only one domain has a problem while other sites and routes in the same region work, check whether the issue is with that domain’s resolution, a split-tunneling rule, or the remote service. If changing a system setting also stops local network names from resolving, undo the change and restore the original network environment rather than layering on more DNS configuration.

If an app connects but a specific action fails, distinguish a network interruption from a rejection by the remote service or insufficient account permissions. A work app may contact several domains during sign-in, and a streaming service’s page and media requests may not use the same host. If the homepage opens but later actions fail, compare the app’s behavior with a configuration that previously worked, then check the rules. Don’t route unfamiliar domains through the client by default. For workplace intranets, online banking, or managed systems, follow the connection method required by the service.

Make advanced troubleshooting a reversible experiment

Start with a working configuration and note the current mode, route, test destination, and expected result. Change one thing at a time, then repeat the same action. If it doesn’t help, undo the change before trying something else. For example, try another route in the same region on the same network and in the same app; don’t reset DNS or change the system-wide routing mode at the same time. If the original route still fails after you switch back, other conditions may have changed during testing. Recheck the basic network, remote service, and account status instead of assuming the route you just tested was the cause.

If a local service suddenly becomes unreachable, first restore the last working mode and confirm that essential resources use the expected routes. Then identify the affected scope step by step. If you ask someone for help, include the affected app, steps to reproduce the issue, what you’ve ruled out, and whether restoring the previous setup helped. Keep only the relevant parts of logs and check for destination addresses, account details, or subscription parameters before sharing them. If you’re unfamiliar with route types, protocols, or split-tunneling terms, check the VPN glossary before changing settings.

Start Free