1MVPN / Complete Guide

Complete VPN Setup Guide

Follow the setup process from choosing a plan to verifying your connection, configuring Shenzhen–Hong Kong routes and international routes along the way.

If you just want to get connected on a device you have handy, start with the quick setup guide. This page is a reference manual: alongside the steps, it explains what to expect at each stage, where to go back if something goes wrong, and which settings to check again when you switch devices.

Cross-border network acceleration and routes

Understand the dashboard, client, and destination website

1MVPN is a cross-border network acceleration subscription service for Shenzhen–Hong Kong routes and access to international websites, with coverage in 110+ countries and 160+ routes. The user dashboard manages your account, orders, and subscriptions. The client reads your subscription on your device, lets you choose a route, and handles traffic according to the active configuration. Destination websites independently manage sign-ins, content, and permissions. Each part has its own status. If the dashboard opens, that only means your device can reach the management page. If the client says connected, that does not mean every browser request uses the selected route. And if a website opens, you still need to confirm it was reached through the expected path.

Knowing where one part ends and another begins can save a lot of backtracking. For example, if you have paid but no routes appear in the client, first check that the plan is active in the dashboard, then check that the subscription was imported. If a route connects but a website stays on its account verification page, first check whether the same browser can reach other sites, then distinguish a network issue from a requirement imposed by the destination service. If the message clearly comes from the website—for example, asking you to sign in again—don't assume it's a route problem.

Entry points, exit points, and route types

The entry point is where your device connects to a route; the exit point is where traffic heads toward the destination website. For a Shenzhen–Hong Kong route, Shenzhen entry and Hong Kong exit refer to different points along the connection. A node name may highlight either end, so don't assume the name tells you which region the destination website will see. Learn about nodes and route types on the routes page, then choose from the list currently shown in your client. Route names are mainly there to help you identify them; verify the actual connection on your own network and device.

TypeWhat it meansWhat to check when choosing
IEPL dedicated lineThe cross-border segment uses a dedicated lineCheck that the destination app works reliably at the times you usually use it
RelayedTraffic is forwarded through an intermediate access pointCompare connection stability on your current network
DirectThe device connects directly to the selected nodeFirst check whether a connection can be established, then compare how it performs in actual use

These categories are not a performance ranking. App responsiveness also depends on your local connection, DNS resolution, load on the destination site, and the current route. For meetings or long document-editing sessions, connection drops matter most; for browsing, check whether pages load fully. Before switching routes, keep the device, network, and destination app the same. Otherwise, changing several things at once makes it hard to tell what caused the difference.

Check your local setup before you begin

Before launching the client, make sure your device can reach regular websites. If a guest network requires you to open a sign-in page, complete that network's authentication first. Check that your system clock and time zone are correct so certificate errors aren't mistaken for route issues. If your device is managed by your employer or school, first confirm that you're allowed to install a client, add network configurations, or change proxy settings. If a setting is locked by policy, ask your device administrator—don't remove your organization's configuration. If the device already has a proxy, network accelerator, or system network extension, note its current state so you can spot conflicts and restore it later.

There is no device limit for simultaneous connections. Windows, macOS, iOS, Android, and Linux are supported. For your first setup, start with one device where you can easily check connection details, and verify your account, subscription, and route. Then import the subscription on other devices one at a time. Different results across devices on the same account don't necessarily point to a plan issue: the devices may be on different networks, using different routes, or handling traffic through different system mechanisms. Establish a working baseline first so you can tell account-wide issues from settings on a single device.

Choosing between a monthly plan and a data pack

Compare the prices, then check how billing works

When choosing a plan, distinguish between data that refreshes each month and data that lasts until you use it up. Both are measured in data, but the usage periods differ. Monthly-plan data resets each month on your activation date, not at the start of the calendar month. If you upgrade mid-cycle, the price difference is prorated for the remaining days. A data pack lasts until it is used up and never expires. Compare price, data allowance, and billing method together; don't compare only the two lowest prices. See all options on the plans and pricing page.

Billing typePrice and dataData allowance rules
Monthly plan¥9.9/month, includes 60GBResets monthly on your activation date
Monthly plan¥18/month, includes 250GBResets monthly on your activation date
Monthly plan¥28/month, includes 500GBResets monthly on your activation date
Data pack¥158/300GBUse it until it's gone; never expires
Data pack¥358/1000GBUse it until it's gone; never expires
Data pack¥658/3000GBUse it until it's gone; never expires

Estimate based on your actual usage, not your device count

Start by separating regular usage from occasional bursts. Regular usage might include reading documents, work tools, or online communication. Occasional bursts might include system updates, syncing large files, or heavier use while traveling. If you're unsure how much data you use, check your device's existing network usage statistics, or compare your dashboard balance before and after activation. System statistics may include traffic that doesn't go through the client, so use them to spot data-heavy apps—not as a direct measure of plan usage.

If your usage is steady and similar from one period to the next, a monthly plan makes it easier to track usage by billing cycle. If usage is sporadic or varies a lot, a data pack avoids losing track of a monthly reset when you aren't using it. Even light browsing and text tools can use a lot of data due to background sync; having the client open doesn't mean every app's traffic goes through a route. Check which apps match your proxy rules before deciding whether the plan is too small or the rules cover too much. Don't assume one large transfer reflects your long-term needs, but don't overlook tasks that repeat automatically either.

There is no device limit for simultaneous connections, but that doesn't mean each device gets its own separate data allowance. If you use several devices at home or work, consider their combined usage. For example, a tablet may only be used to read documents while a computer constantly syncs large files. Choose a plan based on actual data use, not on which device stays connected longest. If several people share devices, check background apps and browser settings before deciding whether to change plans.

What to check before placing an order

After opening the dashboard from the plans page, check the current account, plan name, billing type, data allowance, and amount. If you already have a plan, distinguish continuing your current service from changing your allowance, and pay particular attention to whether the order is marked as an upgrade. Mid-cycle upgrades prorate the price difference for the remaining days. The amount due on the order confirmation page is the one to rely on. If the summary doesn't match what you expected, stop at the confirmation page rather than submitting again to see what happens. If you only need extra headroom temporarily, first check which traffic is routed by your split-tunneling configuration; you may not need to add another plan.

Before activation, write down the main things you want to verify, such as a work page in your usual browser or a desktop app you use every day. First check that those use cases connect, then compare longer-term data usage and costs. A single connection test only shows what happened on that route at that moment; it can't predict usage over an extended period. If you're still working out what kind of long-term plan suits you, read How to Decide Whether a Long-Term Subscription Is Worth It. The purchasing strategies discussed there are separate from the plans currently sold on this site.

Create an account, place an order, and confirm it

Create an account, then check that you're signed in

Go to the account setup page from the user dashboard. No email address is required; create an account with a username and password. Choose a username you'll recognize, and use a unique password that you don't reuse for other services. You can save it in your password manager. After creating the account, check that you're signed in to the one you just made before placing an order. If you've used the service before, return to your existing account through the sign-in page to avoid leaving your order and subscription in separate accounts.

If the form won't accept your input, read the prompt for the current field first. If pasting adds unexpected spaces, re-enter the value in the relevant field. When using a password manager, check that it filled in the credentials for your account on this site, not another account. If your browser keeps returning to the sign-in page, reopen the dashboard from the main site and check that you're on the right page. If you use multiple browser profiles, make sure you've opened the one you intend to use to manage the service. Don't send your password to anyone to troubleshoot a sign-in issue, and don't repeatedly create accounts with similar identities across multiple pages.

Pay on the order page

Go to the plans section of the dashboard and choose the plan you checked earlier. Before submitting, verify the account, order amount, and billing type, then choose an available payment method: Alipay, WeChat Pay, or USDT. If your payment method redirects you to another page, check that the details shown there match the order in your account dashboard. For USDT, follow the payment network, amount, recipient details, and instructions shown for that specific order. Don't copy recipient details from an old order or chat history. If anything in the instructions is unclear, return to the dashboard and check before paying.

If submitting the order doesn't take you to a payment page, check your order history first to see whether an order was created. Then decide whether to continue with that order or choose again. A stalled page or closed payment window doesn't mean the payment didn't go through. In particular, don't pay again unless you're sure what happened. After the payment page confirms success, return to your original account and check that the order status matches the payment record. If the payment provider hasn't confirmed the transaction yet, check its status there first rather than assuming the plan hasn't been delivered.

Confirm delivery using your order and account overview

Your order history and account overview answer different questions. The former shows how the transaction is being processed; the latter confirms whether the service is available. After paying, return to the account overview and check the plan and subscription status. If the order is still awaiting confirmation, refresh the order history. If the transaction is complete but the overview hasn't updated, first verify that you're signed in to the right account and keep your order details. Changing routes or repeatedly importing the subscription won't fix a delivery status that hasn't synced.

If payment went through but you chose the wrong plan, keep the order and don't create a reverse order or buy another plan to "replace" it. Check the Terms of Service and Refund Policy, then contact support through the dashboard to ask how to proceed. The 30-day no-questions-asked refund is a service policy; check the application progress and payment status separately. Closing a browser page or uninstalling the client does not mean an order has been processed.

You're done with this stage when you can return to the right account, find the order for your chosen plan, and confirm the service status in the overview. Check all three before getting your subscription so you won't need to repeat the payment process when switching devices. If you only need the client, you can handle installation separately from plan delivery. To import routes for your current account, first confirm that the subscription is available in the overview.

Get, import, and protect your subscription

Get your subscription from the overview, not from an old device

After signing in to the dashboard, open the account overview and choose the import method that matches your client in the subscription section. If the dashboard offers a one-click option for your client, it will hand off the action to the appropriate app. For manual import, copy the full subscription link and choose the option in your client to import from a URL or add a remote configuration. Confirm the app actually received the configuration; a browser prompt alone isn't proof. On a new device, get the link from your current account rather than looking for an old one in a forwarded message.

A subscription is how the client gets route configuration; it isn't an account sign-in page or the name of a single route. Clients usually keep imported configurations locally, so seeing an entry in the list doesn't mean the app has just checked the subscription source. If you select an old configuration, the client may still be using its old route list. After importing, give the configuration a clear local name, then check its source, whether it appears in the list, and whether it's selected. You don't need to put account details in the configuration name as long as you can tell old and new configurations apart.

The address below is fake and only demonstrates the link structure. Copy your actual link from the dashboard after signing in. Don't paste the example into your client or send your own subscription to someone else for testing.

https://example.com/sub?token=YOUR_TOKEN

Where to check when an import fails

If the client says the format isn't supported, first check whether the import option expects a remote subscription, a single route, or a local configuration file. These aren't interchangeable. Then make sure the app received the complete URL, not just its display text. Copying through a chat app, document, or rich-text editor can strip the query string or insert line breaks. Copying the link again from the dashboard is safer than trying to reconstruct it by hand. Don't change parameters you don't understand or paste a real link into a public online conversion tool.

If the client says it can't retrieve the subscription, check each of these separately: whether you can sign in to the dashboard, whether the subscription is available, whether the current network's authentication is complete, and whether the client is trying to update over a connection that's no longer working. If you know how to restore your setup, disconnect the current route and try fetching the configuration again. If the app suggests disabling certificate verification, don't make that your routine fix. First confirm that the address came from the site dashboard, your system clock is correct, and your network isn't still waiting for guest authentication.

If the configuration downloads but no routes appear, check whether you still need to select the imported configuration or whether you're looking at an old list. Don't clear existing configurations just because you see historical entries. First distinguish the new configuration from the old one and verify that the new routes work; then decide whether to remove old entries. Repeatedly importing the same link on one device only makes it easier to select the wrong configuration. If the link is still valid and you need the latest routes, update the existing configuration instead.

Tell subscription updates apart from credential changes

An update usually means the client reads the configuration again from the same address. Changing the subscription address means switching the client to a new source. If the link was exposed in a public document, group chat, or unauthorized device, deleting the entry from your own client isn't enough. Check whether the dashboard offers a reset option; if you're unsure, ask support through a ticket. Once the new address is active, replace the link on each device you still use and verify it. If you're no longer using an old device, delete its saved configuration and sign out of the relevant account.

When submitting a ticket, say "Import reports an unsupported format" or "Update says it can't retrieve the subscription." There's no need to include the full link. For more on the difference between a subscription and a client's local configuration, see the Guide to Getting, Importing, and Updating a Subscription Link. By the end of this section, you should be able to tell whether the subscription on your device is active for your current account or just an old locally cached configuration. Next, check system permissions and how traffic is actually handled on each device.

Import the client on each platform

After signing in, get the platform-specific download from the client section of the dashboard, and get your subscription from the overview. Windows, macOS, Android, and Linux users can access the client after signing in. The iOS download link is shown in the dashboard for accounts with an active, unexpired plan, along with the applicable App Store link. The steps below describe the goal—import, select a configuration, authorize, and connect. Control names can vary between operating systems and app versions; you don't need to find a button with the exact same wording.

PlatformKey checksCommon differences
WindowsCheck whether the browser uses the system proxySome apps have their own proxy settings
macOSCheck whether system network permissions have been grantedDifferent network services may keep separate proxy settings
iOSCheck whether the system allows a connection configuration to be addedCompare the client status with the system status
AndroidCheck whether the system connection request has been approvedBackground restrictions may prevent the app from staying connected
LinuxCheck whether the app's proxy or tunnel is enabled on demandDesktop environments, terminal sessions, and background services may behave differently

Windows: Verify traffic handling in a browser

Get the Windows client from the dashboard and launch it as directed in the installer or download section. Open configuration management, import through the dashboard option or paste your subscription, then select the new configuration and a route. Enable a traffic-handling mode supported by the client, then test with a browser you use regularly. If the browser works but a desktop app doesn't, check whether that app follows the system proxy or has its own proxy address. Some apps need to be closed and reopened after a system proxy change. Don't enable several traffic-handling modes at once at the outset; it makes it hard to tell which one is taking effect.

macOS: Handle permissions and existing settings

Open the macOS client provided in the dashboard, import your subscription, and select the configuration. If the system asks you to approve a network configuration or extension, make sure the prompt comes from the app you just opened, then follow the instructions. The app may still show a route list after you deny permission, but that doesn't prove system traffic is using it. If it still doesn't work after authorization, check the active network service and its proxy settings, and look for settings left behind by other tools. If your device is managed, don't remove your organization's configuration. See the macOS Installation and System Authorization Guide for details on first-time setup.

iOS: Check the app and system connection status

Install the iOS client from the link in the dashboard, then return to the app and add your subscription. If importing from a browser opens the client, switch back to confirm the new configuration actually appears instead of staying on the App Store page. Select a route and connect. Read the system request to add a network configuration and approve it as instructed. Verify the connection on your current network, and test again if you switch to another network. A connection icon in the system status only means the relevant configuration is running; it doesn't tell you which split-tunneling rule a destination app is matching.

Android: Handle connection permission and background limits

Get the Android client from the dashboard, install it as directed in the download section, and import your subscription. The first time you connect, check which app the system request refers to before approving it. If another app is already using the system VPN, check what it's for and, if appropriate, pause it before reconnecting to this service. If the connection works with the screen on but drops in the background, check whether the system restricts the app's background activity and adjust its settings if needed. Don't turn off system-wide battery or security settings to troubleshoot a single app.

Linux: Distinguish desktop apps, terminals, and background services

First, check the dashboard instructions and choose a client that suits your system environment. Import the subscription and select a route. If you're using an app proxy, test in a browser or one app first; desktop proxy settings don't automatically apply to every terminal or background service. If you're using the client's system tunnel, follow its instructions to check permissions, routing, and traffic-handling status. Don't use administrator privileges to bypass an error you don't understand, and don't replace the subscription link with a local listening address. Before changing system-level settings, note how to stop the client and restore your previous configuration.

Verify connections and troubleshoot issues

Compare before and after connecting on the same device

First make sure the configuration you just verified is active, then choose a route and connect. Keep the device, network, browser, and destination page the same, and compare what happens when disconnected and connected. If possible, check your current exit point using a trusted IP lookup tool, and compare it with the client's connection details to see whether a request is using the route. Don't rely only on whether a page opens: it may be allowed to connect directly by a rule or served from the browser cache. A useful comparison includes the client status, whether the destination page actually sent a request, and whether the exit point or path matched your expectations.

In clients that show connection logs, visit a destination domain in your browser and check whether the corresponding request appears and which rule category matched. Viewing cached content or leaving an already-open page idle may not create a new log entry. Reload the page and check for a new request; you don't need to sign out of a work account just to test. If you're testing a desktop app, perform a lightweight action in the app itself rather than relying on browser results. After that, verify with a real task—reading, submitting, or syncing—instead of testing only the home page.

Match the symptom to the right layer

The client can't establish a connection. Go back to the basic network first and check whether regular websites open while disconnected. If you're using a public network that requires authentication, complete that step and try again. If the underlying network works, check the subscription status, selected route, and system permissions. Try another suitable route in the same configuration, changing nothing else. If it only fails on one network, note the network type and exact symptom, then check on another network you're allowed to use rather than repeatedly reinstalling the app.

The client says connected, but apps can't access the internet. First check whether every app is failing. If only one app is affected, check its separate proxy settings, whether the configuration handles its traffic, and whether the destination domain matches the expected rule. If all apps fail, disconnect and check whether the original network works again. If not, look for leftover system proxy settings or another active network tool. A browser's "domain not found" error isn't the same as a connection timeout or a permission message from a website. Recording the exact error is more useful than simply saying it won't open.

The website opens, but an action doesn't work. Pages, files, and sign-in callbacks may use different domains, so a working home page doesn't mean every background request is working. Note whether the failure happens when opening a page, signing in, uploading, or streaming, and compare with as few variables as possible in the same account and app. If the website asks you to verify your identity again, change your account region, or update content permissions, follow the destination service's own instructions. Switching routes can't replace account eligibility or content authorization. For issues limited to specific use cases, see AI tools connection guidance and streaming support information.

Record reproducible conditions; don't share full logs

Briefly record the time, operating system, network, current route name, traffic-handling mode, failure stage, and error message. Include comparisons you've already tried, such as being able to access the site on the same device while disconnected or seeing no change after switching routes. Client logs may contain visited URLs, local file paths, account details, or configuration sources. Review and redact them before sending anything to support. If support needs to reproduce the issue, choose the shortest non-sensitive action you can share; don't send private documents, access tokens, or the full subscription link.

If you can reproduce the issue on the same network and have narrowed it down to a platform or type of task, check the Frequently Asked Questions first. If you need support, submit the minimum information needed to reproduce it through the support ticket form. If the same error occurs when the client is disconnected, check the underlying network or destination service first. If switching networks resolves it, include that comparison in your description. A single clear, verifiable difference is more useful for troubleshooting than a list of attempts with no order or context.

Maintenance, renewals, and refund requests

Update when something changes; don't keep reinstalling

When everything is working normally, there's no need to delete and reimport your configuration just to "stay up to date." Consider updating your subscription if the dashboard announces route changes, a route disappears from the available list, or troubleshooting suggests the client is still using old settings. First note your current route and rule mode, then update the active subscription in the client. Afterward, check that the configuration is still active and review your route selection. If the device was set to choose a route automatically, it may select a different one after an update. Identical names in the list don't guarantee identical routes.

After a system upgrade, client update, or network change, first check whether your existing workflow still works, then make only the changes you need. Before updating the client, note your current configuration name, traffic-handling mode, and custom rules. If the app offers a backup, check whether it contains credentials. Keep any sensitive backup in secure storage, not a public repository or shared drive. If the system asks for permissions again after the update, confirm where the prompt came from before approving it. Before restoring an old configuration, make sure its subscription is still valid. Reinstall only when the installation or app files are actually broken; it's not a prerequisite for routine subscription updates.

Check your balance and billing cycle before renewing

Open the account overview and make sure you're looking at the right account and active service. Monthly-plan data resets each month on your activation date; don't estimate the next reset from the number of days left in the calendar month. A data pack lasts until it's used up and never expires, so the main question is whether the remaining balance will cover your upcoming use. If several devices are connected, keep an eye on apps that sync automatically or transfer data continuously. If usage has increased, first check whether it's related to a new task or a change in mode before deciding to adjust your plan.

If you're continuing your current service or considering a different plan, check the available options in the plans section of the dashboard. If the confirmation page shows an upgrade, check the order against the rule that prorates the price difference for the remaining days. Don't conflate renewing, changing plans, and updating your subscription: the first two affect the service in your dashboard; the last only makes the client read the configuration again. Check payment results in your order history. Only return to subscription updates if the account overview looks right but the client still has an old route list.

When switching devices, first import the subscription and verify the connection on the new device, then deal with the old one. If the old device has been given to someone else and you can't confirm that credentials were removed, check the account and subscription management options in the dashboard and contact support through a ticket if needed. If you simply no longer use the device, sign out, remove its configuration, and check for backups transferred with the device. Retiring a device doesn't cancel the subscription in your dashboard or change the order status.

Keep refund requests separate from troubleshooting tickets

The service offers a 30-day no-questions-asked refund. See the Refund Policy for details. To apply, submit the relevant order and a clear request through a support ticket in the user dashboard, as explained in the policy. There's no need to prove an issue by reinstalling repeatedly or switching routes. If you want to keep using the service but have a connection problem, include reproducible conditions as described in the previous section. Keep the two requests separate so support knows whether to review a transaction or troubleshoot a network issue.

You can reduce routine maintenance to a simple sequence: check the service and order in your account, check the configuration and route in the client, then verify with the app you actually need. That way, if the connection suddenly drops, you won't change system proxy settings before confirming the service status—or mistake one device's configuration problem for an expired plan.

Advanced routing and route selection

Define the traffic scope before changing rules

Rule-based routing uses conditions supported by the client to decide which requests use the selected route and which go through the local connection. Global mode can be useful as a temporary comparison during troubleshooting: if a destination app only works in global mode, check which rule it matches or whether its traffic is being handled. The name "global mode" doesn't guarantee that all system traffic is captured; actual coverage still depends on the client, system permissions, and app behavior. After troubleshooting, restore the mode that fits your needs to avoid sending unrelated background traffic over your subscription route.

Before changing rules, identify the actual domain or request type used by the app instead of writing a broad rule based only on its home page name. Sign-in, static assets, and content APIs may use different domains. After making a change, check whether the affected request follows the expected path, then make sure existing services still work. If the client gives rules a priority order, read its guidance on match order and distinguish specific exceptions from broad rules. Don't import large rule sets from sources you don't understand or trust, especially if they might overwrite local settings you're still using.

Distinguish DNS issues from local network access

When DNS resolution fails, distinguish between "the domain can't be resolved," "the domain resolved but the connection timed out," and "the connection succeeded but the certificate or page returned an error." Browsers and systems may resolve names differently, and a client may use its own resolver for some requests. First check whether the issue affects one app or the whole system, then look for app-specific settings. Avoid changing system DNS, browser DNS, and client rules all at once. If the network requires guest authentication, leave test mode and complete the normal sign-in first, then test again.

If a printer, shared folder, or internal work service suddenly becomes unavailable, first check that your device is still on a network authorized to access those resources. Compare using the app and address that worked before to determine whether the issue is with local discovery, DNS resolution, or the request path. Check the client's local network access settings and understand their scope before making changes. If your device is organization-managed, ask an administrator to handle network policies. Don't forward internal addresses to an external service just to test a connection, and don't disable system security checks.

Compare routes using real tasks and keep a way to revert

To evaluate a route, choose a task that reflects your everyday use. For a long session, watch for repeated reconnects. For websites and app management, check whether sign-in completes. File transfers also depend on the destination service and file size. Test during a time when you usually use the service, repeat the same task on the same network, and record what happens. Don't treat a single connection time as a long-term conclusion. If a route performs poorly, compare it with another route to the same destination region to distinguish differences in access path from differences in exit region.

For apps with regional requirements, first check the service's terms of use, then keep your exit region and connection method reasonably consistent. When troubleshooting sign-in or a long-running session, avoid switching routes repeatedly while submitting forms. To compare routes, save your work, finish the current action, switch, and test again. Keeping your regular work route separate from routes used for temporary testing helps prevent tests from disrupting a session that's already working.

The goal of this guide isn't to enable every mode; it's to understand and reproduce your current setup. You should know how your plan is billed, retrieve your subscription from the dashboard, import it and verify the connection on a supported platform, and know whether to check the account, client, or destination app when something changes. When switching devices, return to Import on Each Platform. If a connection fails, start with Verify Your Connection. For route coverage or plan terms, see Routes and Plans and Pricing.