The Quick Start Guide is for readers who want to complete their first connection quickly and covers only the main path from account setup to client configuration. This guide adds the data relationships, platform differences, exception paths, and long-term maintenance behind each step. For first-time use, follow the quick guide for basic setup, then return here when you need help with plans, subscriptions, system permissions, route switching, or renewals.
The overall workflow is straightforward: the account stores plan and order status, the plan determines available data, the subscription delivers the account’s available routes to the client, and the client selects a route and handles network requests. Troubleshoot by checking this chain layer by layer to identify whether the issue lies with the account, subscription, client, system permissions, current network, or destination service—without repeatedly reinstalling software or changing settings at random.
How the service, account, plan, and subscription fit together
What the service provides
vpnLi provides cross-border access and international route subscriptions, covering 90+ countries and 200+ routes, with support for Windows, macOS, iOS, Android, and Linux. The website presents plans, routes, and usage guidance; the user panel handles the account, orders, subscription, and client entry points; the actual connection is made by the client for the relevant platform. Marketing pages do not directly provide installers or public subscription URLs. Log in to the user panel to access the client entry point and subscription details associated with your account status.
A route is the outbound path a client uses when accessing international websites. Choosing a different region changes the route and the region of the exit point; selecting a region closer to the destination service can generally reduce unnecessary cross-region detours. A route name only describes its region and type, and does not mean every website will perform the same way at all times. The destination’s own load, the surrounding network, wireless signal, and local carrier routing all affect the final experience.
An account, order, plan, and subscription are different things
The account is the identity record used to enter the user panel and can be created with a username and password; no email address is required. An order records the selected product and payment status. The plan records available data and its current validity. A subscription is a configuration entry delivered by the panel to the client and contains the routes currently available to the account. Routes appear only after the client reads the subscription, so “payment completed” and “the client has received the latest routes” are two consecutive but separate stages.
When the panel shows an available plan but the client still has no routes, refresh the subscription first instead of placing another order. If the client displays routes but cannot connect, check system permissions, the current network, and route selection. If the panel itself shows no available plan, verify the order result first. Separating these states prevents repeated actions at the wrong stage.
How monthly plans and data packs are measured
Monthly plans are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly from the activation date; when upgrading mid-cycle, the price difference is converted according to the remaining days. “Monthly” means the cycle starts on the activation date, not necessarily on the first day of a calendar month. Use the current cycle and remaining data shown in the user panel as the source of truth.
Data packs are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They remain available until used and never expire. They suit usage that does not follow a fixed monthly pattern and users who prefer to consume data as needed over time. Monthly plans and data packs address different measurement needs: the former resets on a fixed cycle from activation, while the latter does not reset each month. Compare your usage rhythm before choosing rather than looking only at the total amount.
If the panel has no available plan, check the order. If the panel has a plan but the client has no routes, refresh the subscription. If the client has routes but the connection fails, check permissions, the network, and the route. Layer-by-layer diagnosis is more effective than changing several settings at once.
Limits of simultaneous multi-device use
vpnLi supports unlimited devices online at the same time, so one account can be used across multiple supported platforms. Unlimited devices does not mean every device must share one route, nor that every device should use full-system mode. A more reliable approach is to choose by purpose: keep work devices on regions close to the business target, choose content regions for media devices, and disconnect temporary devices when finished. This makes issues easier to isolate and prevents background syncing on one device from continuously consuming data.
Data is measured collectively across the account’s plans. System updates, cloud sync, photo backups, game updates, and long video sessions can all create sustained traffic. If remaining data drops faster than expected, check background tasks on each device before changing plans. For common usage and connection questions, see the Complete VPN Beginner’s Guide.
Choose a monthly plan or data pack based on your usage pattern
Decide whether your usage is ongoing or occasional
When choosing a plan, the key question is not how much one connection might use, but whether your usage is continuous. Daily browsing, document syncing, meetings, or media use generally suit a monthly plan because data resets monthly from the activation date. If usage is concentrated around travel, project delivery, or specific viewing periods and varies substantially between months, compare data packs that never expire. Matching the measurement method to your routine makes ongoing management simpler.
Light browsing, text communication, and code research consume data differently from high-resolution video and large file transfers. Browsing often consists of many small requests that are barely noticeable individually but accumulate over time; video and system images can transfer large amounts in a short period. When choosing a tier, consider foreground activity together with background syncing rather than estimating from the websites you actively open.
Comparing the three monthly plan tiers
| Plan | Price & cycle | Data | Recommended management approach |
|---|---|---|---|
| Basic monthly plan | ¥9.9/month | 60GB | Mostly browsing, text tools, and occasional connections; check background syncing regularly |
| Standard monthly plan | ¥18/month | 250GB | Daily use across multiple devices, including browsing, media, and file transfers |
| High-data monthly plan | ¥28/month | 500GB | Frequent media and large file transfers requiring more data during the cycle |
All three tiers share the same platform support and route coverage; the main difference is monthly data. The lower tier does not restrict which systems you can use, and the higher tier does not change the device limit. Choose based on actual needs, and do not mistake more data for guaranteed faster routes. Connection performance mainly depends on the route, destination, current network, and time of day; plan tiers determine the available data volume.
When a data pack makes sense
Data packs are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB, and remain available until used without expiring. They suit irregular usage and users who want to retain unused data. Because they do not reset monthly, management focuses on the long-term remaining balance rather than the amount left in the current cycle. When multiple devices share an account, monitor background tasks especially closely to prevent unattended devices from consuming data continuously.
Data packs are not automatic top-ups for monthly plans; manage both products according to their actual status in the panel. Before changing measurement methods, review the current plan and orders, confirm that the new choice fits your upcoming usage, and complete the change in the user panel. Do not rely on an old browser-cached page for pricing or status; use the panel’s current display as the final reference.
What changes when upgrading mid-cycle
When a monthly plan is upgraded mid-cycle, the price difference is converted according to the remaining days. The upgrade does not simply add the unused portion of the old plan to a full new cycle; the difference is calculated from the time remaining. Before proceeding, review the order details shown in the panel, confirm the new tier, difference, and activation result, then complete payment. After the upgrade, return to the account overview to verify the plan status and refresh the subscription in the client so it reads the latest available configuration.
If only one website occasionally slows down, do not assume the data tier is the cause. Try another route in the same region, check the local network, pause background downloads, and test again. Adjust the plan only when the panel clearly shows insufficient remaining data or your long-term usage pattern has changed. For a side-by-side comparison of tiers, visit the Plans page.
If you are dissatisfied with your first payment, you can request a full refund within 14 days. Keep the order details and describe the relevant order and issue through the ticket entry in the user panel.
Pre-payment checklist
Before paying, confirm in order that the account is the one you intend to use long term, the product is a monthly plan or data pack as intended, the tier and data amount are correct, and the current page is still logged in. vpnLi supports Alipay, WeChat Pay, and USDT. After choosing a payment method, complete the current order flow and then return to the panel to verify it. Avoid repeatedly creating identical orders during payment, as this makes later identification harder.
If the page does not update immediately after returning to the browser, refresh the order list and wait for the panel to read the status again. If you still have questions, submit the order details through a ticket instead of paying again to test whether the previous payment succeeded. Once the order status is confirmed, proceed to the subscription and client download steps.
Create an account, place an order, and verify activation
Create an account with a username and password
vpnLi accounts require no email address; a username and password are enough. The username identifies the account, while the password grants access to the user panel. Choose a username that is easy to distinguish from accounts on other sites, and store the password in a trusted password manager. Because subscriptions, orders, and tickets are tied to the account, losing login details affects all later management. After creating the account, sign out and sign back in once to confirm access works normally.
Do not keep a login session saved long term in a browser on a shared device. If you must use one temporarily, sign out when finished and clear the browser’s saved session data. A subscription entry should also never be copied into public documents, chat groups, or screenshots; it is linked to the routes available to the account and deserves the same care as login credentials.
Enter the user panel from the Plans page
The marketing site’s plan cards explain the products; the actual order is completed in the user panel. After clicking “Start Free” or “Choose this plan,” the browser opens the plan area in the site root. If you are not logged in, log in first; if you are already logged in, review the product directly. Check the product name, cycle, data, and amount carefully rather than identifying the selected tier only by the button’s position.
Monthly plans are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; data packs are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. The payment page should match the selected product. If the page has been open long enough that its status is unclear, return to the plan list and choose again instead of continuing on an old page.
Create an order and choose a payment method
After confirming the product, create an order and choose Alipay, WeChat Pay, or USDT. Payment may take place on the current page or in a separate flow; either way, let the current order finish confirming before closing the page. A browser notification alone is not sufficient proof of payment. Return to the user panel and check the order and plan status.
If you return, refresh, or switch devices during payment, do not create several orders in succession. Open the order list first and check for pending or completed records. A completed order should correspond to a plan in the account overview; continue processing pending orders according to the status shown in the panel. If the status does not match the actual payment, submit the relevant order details through a ticket rather than making another payment as a test.
How to confirm that a plan is active
Activation checks should cover the account overview, order records, and subscription entry together. The account overview confirms the current plan and remaining data; order records confirm the transaction status; the subscription entry delivers the current configuration to the client. If only the order is complete but the account overview has not changed, continue checking at the panel level. If the overview shows a plan but the client has no routes, refresh the subscription.
Monthly plan data resets each month from the activation date. When recording a usage cycle, rely on the activation and reset details shown in the panel instead of calculating from the first day of the month. Data packs never expire, so focus on the remaining balance. With multiple devices online at once, all device traffic belongs in the account’s data management.
Sign out and back in once to confirm the username and password work, then verify the order, plan, and subscription entry. Completing these checks before configuring the client keeps account issues separate from client issues.
How to store account and subscription information
Store the username, password, and subscription entry separately; do not write all three in notes that anyone can access. After importing a subscription, the client usually stores its configuration locally, so delete the subscription and local configuration before handing over a device, reinstalling the system, or stopping use. If you suspect the subscription was shared improperly, check the available update options in the user panel and import it again.
Tickets are suitable for order status, account access, and service usage issues. Describe the platform where the action occurred, what the panel shows, and the step where the client stopped; include an error message with sensitive content hidden. Full context is more useful than “it does not work” and reduces back-and-forth clarification.
Get the subscription, identify the import entry, and store it securely
Get the subscription from the user panel
After the plan becomes active, open the account overview or client download area in the user panel and obtain the subscription entry associated with the current account. Marketing pages do not publish real subscription URLs, and you should not copy supposed universal configurations from search results, group chats, or unofficial pages. The correct entry must come from the logged-in user panel and match the account’s current plan status.
A subscription lets the client read the available routes and their connection parameters. It is not an ordinary web bookmark or a single fixed route. After importing it, the client parses it into a route list. When route details change, update the subscription to synchronize them instead of entering every parameter manually again.
Copy the link, open the client, or import manually
The panel may offer a direct link to open the client or subscription content that can be copied. Direct opening suits devices where the relevant client is already installed. Manual import after copying is useful when the browser cannot switch automatically, when you need to save the link in a password manager, or when using another trusted device. Whichever method you use, return to the client after importing and confirm that the route list appears.
If the browser says it cannot open the link, the relevant client may not be installed, the system may not associate that link type with an app, or the browser may be blocking external-app navigation. Do not keep clicking. Obtain the client through the panel, install it, and open the entry again; alternatively, copy the subscription and paste it into “Import from link,” “Add subscription,” or a similar function in the client.
Example for understanding the format
The address below only illustrates the structure of a subscription link. It is not associated with vpnLi and cannot be used for a real connection. Actual content must come from the user panel, and example fields must not be replaced with account credentials and shared publicly.
https://example.com/sub?token=YOUR_TOKENA link consists of the site address, subscription path, and account token. The token lets the system identify the subscription content to deliver, so the complete link is sensitive information. If an address must appear in a troubleshooting screenshot, show only the domain and path structure and hide query parameters. There is no need to publish the full link in a ticket; describe the issue using the panel’s secure process.
The difference between the first import and later updates
The first import creates a subscription record in the client; a later update rereads routes through that existing record. If the panel has an active plan and the client already has a subscription but the route list is empty or clearly outdated, use “Update subscription” instead of creating several similar records. Repeated imports can create multiple route groups, making it difficult to tell which group is actually in use.
When an update fails, first check whether the current network can reach the user panel normally, then confirm that the plan is still available. If the browser can reach the panel but the client cannot update, copy the subscription into the client again and check for spaces or line breaks added before or after the content. If it still fails, keep the client’s error text and report it through a ticket.
Subscription names and device management
Use names that reflect purpose in the client—for example, distinguish work, media, and temporary devices—but never put a username, password, or full subscription URL in a name. Unlimited simultaneous devices means each device can import independently and choose routes for its own purpose. If one device has an issue, you can handle that device without affecting the others.
When replacing or retiring a device, delete the subscription from the old client. Uninstalling a browser alone will not remove configuration stored by a separate client, and system backups may copy that configuration to the new device. After migration, check the subscription lists on both devices, keep active records, and remove duplicates and expired entries.
Confirm that the plan is available in the panel, update the client subscription, then choose a route and connect. Do not repeatedly import before confirming plan status, and do not hide an update error under multiple duplicate subscriptions.
Get client entry points only from the panel
Obtain client entry points for Windows, macOS, iOS, Android, and Linux through the user panel. Installation methods and system permissions differ by platform, so the panel provides the delivery path for the current platform. Do not replace the client supplied through the panel with an unknown modified version, and do not mix configurations from other services into an indistinguishable group alongside the vpnLi subscription.
Import on Windows, macOS, iOS, Android, and Linux
The shared workflow across all five platforms is: get the client from the user panel, install it, add the subscription, allow required network permissions, update the route list, then choose a route and connect. Differences mainly involve permission prompts, background behavior, and where system proxy control is enabled. Follow the wording in the client’s current interface rather than forcing every platform to use identical buttons.
| Platform | Import focus | Common permissions | Check after disconnecting |
|---|---|---|---|
| Windows | Update the route list after adding the subscription | Permissions related to network control and the system proxy | Confirm that the system proxy has been restored |
| macOS | Import from the link and allow network configuration | Confirm the system network extension or configuration | Confirm the connection status in the menu bar |
| iOS | Add the subscription through the panel entry | Authorize the system network configuration | Confirm disconnection in system settings |
| Android | Paste the subscription and allow background connections | System network connection and background operation | Check the connection indicator in the status bar |
| Linux | Import through the client interface or configuration entry | Permissions for network management and the proxy environment | Check environment variables and the system proxy |
Windows: update the subscription after installation
Get the Windows client from the user panel and launch it after installation. The first run may require permission for network-related actions; confirm that the prompt comes from the newly installed client before continuing. Open subscription management, choose Add from link or use the panel’s open-client action, save the subscription, and manually update it. After the regional route list appears, select the route you need and enable the connection.
On Windows, confusion often comes from treating “the client is running” and “system traffic is being handled” as the same state. If the client is open but the exit point has not changed, check whether the system proxy or the client connection switch is truly enabled. If websites remain inaccessible after disconnecting, quit the client and check that the system proxy has returned to its previous setting. Do not run multiple similar clients that control the system proxy at the same time, as they may overwrite one another.
macOS: pay attention to network permissions
Get the macOS client from the panel and complete installation. On the first connection, the system may ask you to approve network configuration or extension permissions. After approval, add the subscription and update it in the client. If routes appear but the connection button does not work, open system network settings to confirm the relevant configuration is allowed, then return to the client and connect again.
After sleep, a network change, or a system update on macOS, the previous connection may have expired even though the menu bar icon still shows its old state. When resuming use, check the client status and disconnect before reconnecting if necessary. If you switch from Wi-Fi to Ethernet, reconnect as well so the client can handle traffic through the current interface.
iOS: system authorization and on-demand connections
Use the user panel to access the iOS client and import the subscription after installation. The first activation requires system approval to add a network configuration; the client can establish a connection only after approval. Once the route list appears, choose a region close to the destination service and enable the connection. When switching routes, make the selection in the client first and then check whether the connection is re-established.
Mobile devices switch between Wi-Fi and mobile networks, and a network-interface change can cause a brief interruption. If the interface says connected but websites do not respond, disconnect first, confirm that the underlying network works, and connect again. If on-demand connection is enabled, remember that it automatically takes over when its conditions are met. During troubleshooting, temporarily disable automatic triggering and use manual connection so you can identify the source of each change.
Android: handle background limits and network changes
Get the Android client from the panel, import the subscription, and allow the system to establish a network connection. Some systems restrict background apps and may pause the client after the screen locks. For a persistent connection, allow the client to run normally in battery and background management settings, while avoiding unrestricted background access for every app, which can create unnecessary usage.
Android device models and system interfaces vary widely, so permission names may differ, but the diagnosis is the same: the client must keep running, the system should show a connection status, and the underlying network must work. If the connection does not recover after switching Wi-Fi networks, disconnect the current session and select a route again. If a particular app does not use the route, check whether the client has per-app rules enabled.
Linux: distinguish graphical clients from terminal environments
Configure Linux through the client entry provided in the panel. With a graphical client, the process resembles other desktop systems: import the subscription, update routes, choose a mode, and connect. With a terminal program that relies on environment variables, also confirm that the current terminal reads the proxy settings. A graphical browser working does not mean a newly opened terminal process automatically inherits the same configuration.
When troubleshooting a terminal environment, first check whether proxy variables are currently present, then decide whether to clear them. The following command only reads the environment and contains no account information:
env | grep -i proxyIf the terminal still retains old proxy variables after disconnecting the client, close that terminal session or clear the relevant environment configuration. System-level network management, desktop proxy settings, and per-command proxy parameters may coexist. Keep one clear traffic-control method at a time to prevent requests from bouncing between different settings.
Install first, import next, authorize afterward, and connect last. If routes do not appear, update the subscription; if routes appear but cannot be used, check permissions and the underlying network; if problems occur after disconnecting, check that the system proxy has been restored.
Choose a route, establish a connection, and confirm the traffic path
Choose by destination region, not by name familiarity
Choose routes around the destination you need to access. For content intended for Japan, start by comparing Japanese routes; for services aimed at North America, prioritize the relevant region; for cross-region collaboration, begin with the destination’s region or a nearby route. vpnLi covers 90+ countries and 200+ routes, offering many regional choices, but the number of routes does not mean you need to switch constantly. Once you find a route that suits the task, using it consistently for a while makes actual performance easier to assess.
IEPL dedicated routes, relay routes, and direct routes use different path structures. Dedicated and relay routes focus on how cross-border links are organized, while direct routes depend more on the direct path from the local network to the destination region. Choose based on the current network and destination rather than the type name alone. The routes page explains regions and route types together; see the Servers & Routes List.
The standard order for a first connection
Before connecting, confirm that the underlying network can open ordinary websites. Then update the subscription, choose a route in the target region, and enable the client connection. After connecting, do not open many applications at once. First visit a familiar website in the browser and confirm it loads normally, then open the target service. This makes it clear whether a failure occurs while establishing the connection or inside a specific app.
If the client remains stuck on connecting, wait for the current action to finish instead of repeatedly clicking the switch. Then disconnect and try another route in the same region. If several routes behave the same way, check the system time, network permissions, and whether the current network restricts the connection. Comparing with another underlying network can also show whether the issue comes from the device configuration or the network environment.
Verify through the exit IP
A client showing “Connected” only confirms that it considers the session established. You must also check whether traffic is actually passing through the selected route. Compare the exit IP and its region before and after connecting, and confirm that the result after connection matches the chosen region. Use the same browser environment for both checks to avoid false results caused by one window using the system proxy while another app uses separate network settings.
If the exit point has not changed, check whether the client mode proxies only selected apps, whether the browser has its own proxy, and whether another program has overwritten the system proxy. If the exit point changed but the destination service still reports the wrong region, the cause may be browser cache, account region, location permissions, or the service’s own detection. Clear the relevant site session and reopen it before switching routes repeatedly.
Check DNS and per-app paths
DNS resolves domain names to network addresses. If websites fail to open after connecting, a known address works when entered directly, or different apps produce inconsistent results, check whether DNS is being handled correctly by the current connection. Do not enable multiple tools that modify DNS at the same time. During troubleshooting, keep the client’s default settings, disable extra browser security networking or independent proxy features, and compare again.
Per-app mode sends only selected apps through the route while other traffic stays on the local path. It is useful for precise control but can create differences such as “the browser works, but a desktop app does not.” Global mode is easier for initial verification; once the basic connection works, switch back to per-app mode. For detailed checks, see How to Check Whether a VPN Is Working.
Which variables affect speed
Speed depends on local access, wireless signal, carrier routing, route region, the destination service, and background tasks running at the same time. When downloads or playback slow down, pause cloud sync and system updates, then compare routes in the same region on the same device and underlying network. If only one website is slow, consider the destination service or regional detection first; if every website is slow, inspect the local network and route.
Do not change the route, client mode, DNS, browser, and underlying network at the same time. Change one variable, record the result, and then move to the next. Although this approach takes clearer steps, it prevents a temporary recovery from leaving you unsure which setting helped and makes useful information easier to submit in a ticket.
The client status, exit region, DNS resolution, and target application should all produce consistent results. A connection button alone cannot confirm the path; at minimum, check the exit point and verify the target application.
How to verify streaming and regional content
Streaming services may consider the exit region, account region, cache, and content rights at the same time. After switching routes, fully close and reopen the relevant app; if necessary, sign out of the old session and clear the site cache. Do not switch through several regions during one playback session, as old cache data can distort the result. For Japanese anime and streaming platforms, continue with the Japan VPN Route Selection Guide.
Manage updates, renewals, data usage, and common issues
Build stable daily usage habits
You do not need to import the subscription again every time you open the client. Keep one clearly named subscription and update it when the route list behaves unexpectedly, the account plan changes, or the client has not been used for a long time. Frequently used devices can retain preferred routes, but avoid making automatic connections overly complex; the more rules there are, the harder it is to identify which condition triggered a problem.
Check the underlying network before connecting, confirm the target app after connecting, and disconnect when finished if appropriate. On mobile devices, watch for connection recovery after a network change; on desktop devices, check the system proxy after waking from sleep. When an issue appears, record the platform, underlying network, route region, and error text before changing anything.
Check data usage and understand resets
Monthly plan data resets each month from the activation date rather than uniformly at the start of a calendar month. Use the current cycle and remaining data in the user panel as the reference. ¥9.9/month includes 60GB, ¥18/month includes 250GB, and ¥28/month includes 500GB; choosing a different tier changes the data available during the cycle. Data packs are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB, remain available until used, and never expire.
If data changes faster than expected, check system updates, cloud sync, media playback, and download tasks on each device. Unlimited simultaneous devices means multiple devices can be used together, and their background traffic is counted against the same account. Disconnect devices that are temporarily unused and delete subscriptions from devices that are retired long term.
What to do after renewal or an upgrade
Complete renewals and upgrades in the user panel. For a mid-cycle monthly-plan upgrade, the price difference is converted according to the remaining days. After completing the action, verify the account overview and order record, then update the subscription in the client. If the client still shows old content, clear the cached update result and read it again, but do not start by deleting the entire client configuration.
If routes become unavailable around expiration, check the plan status in the panel first. An unavailable plan is an account-level issue that changing routes cannot fix. If the plan is available but the subscription cannot update, check the network and subscription. If the subscription updates but routes cannot connect, continue with client and network troubleshooting. Following the status order reduces wasted effort.
The client will not start or the connection button does nothing
If the client will not start, confirm that it came from the user panel, check whether the system is blocking it, and restart the device. If the connection button does nothing, check whether another network-control tool is running and whether system permissions are complete. On desktop platforms, inspect the system proxy; on mobile platforms, check whether the system network configuration still contains an old session.
Do not reinstall the client, change DNS, switch the underlying network, and reset system settings all at once. Quit other similar tools first, then restart the current client. If it still does nothing, restart the device; only afterward consider obtaining the client again through the panel. Perform a simple check after each step.
Connected, but a specific website is unavailable
First determine whether the failure affects one website, one app, or all access. For one problematic website, clear its cache, close and reopen the app, and confirm that the route region matches the content you need. For one problematic app, check per-app rules and the app’s own proxy settings. If all access fails, inspect the exit point, DNS, system proxy, and underlying network.
Some destination services judge access using account region, content rights, and the access environment; route region is only one factor. Do not attribute every regional message to a failed connection. If the exit region is already correct, continue by checking the destination service’s account and cache state.
The subscription will not update or the route list is empty
Log in to the user panel and confirm that the plan is available, then use a browser to test whether the panel opens normally. When copying the subscription, avoid including spaces or line breaks. Keep one clearly identified subscription record in the client and update it. If several duplicates exist, identify the one from the current account first and remove the old records.
If an error message contains the full subscription URL, cover the query parameters before saving a screenshot. When submitting a ticket, provide the platform, the action location, plan status, and error text with sensitive content hidden. Never publish the full subscription in a public discussion.
Account status → Subscription update → Client permissions → Underlying network → Route selection → Target application. Confirm each layer in order and change only one variable at a time.
Request a refund and submit a ticket
If you are dissatisfied with your first payment, you can request a full refund within 14 days. Submit the relevant order and issue description through the ticket entry in the user panel. Include the order, platform, and current status, but do not publish the full subscription. See the formal Refund Policy.
Multi-device roles, per-app access, and long-term configuration management
Give each device a clear purpose
Unlimited simultaneous devices make it practical to assign devices by task instead of copying identical settings everywhere. A work computer can use a route near the business system’s region, a media device can follow the content region, a mobile device can use a simple setup suited to network changes, and a Linux device can define its scope based on graphical apps or terminal tasks. Clear purposes keep an issue on one device from disrupting the others.
Use readable names for subscriptions, favorite routes, and per-app rules in the client. Avoid strings of obscure abbreviations and never include account credentials in names. When retiring a device, delete its subscription; when migrating, obtain the current entry again from the user panel rather than copying the entire old system directory, which keeps the configuration cleaner.
Choosing between global and per-app mode
Global mode suits initial verification and tasks requiring a unified exit point. Its advantage is a clear path; its drawback is that all app traffic may pass through the route. Per-app mode suits sending only a particular browser, development tool, or media app through international routes while other apps keep their original path. Before configuring per-app rules, verify the route in global mode so rule issues are not mixed with route issues.
Start per-app rules with a small number of clear targets and add gradually. If an app does not connect as expected, check whether it launches child processes, uses system browser components, or follows rules by app or domain. Do not import a large rule set from an unknown source all at once; the more complex the rules, the more important it is to understand match order and default handling.
Choosing routes for AI Tools and international websites
When accessing AI Tools such as Claude, prioritize regions where the service is available and keep the exit region stable. Frequent regional changes can trigger changes in the account environment and make login sessions and caches harder to diagnose. After connecting, verify the exit point before opening the target tool. If access fails, check the route region, target account status, browser cache, and local time separately.
Development tools may not fully follow browser settings. Command-line programs, editor extensions, and desktop clients may each read the system proxy, environment variables, or in-app proxy settings. If the browser works but a development tool fails, inspect that tool’s network settings instead of assuming the route is unavailable. Linux and terminal environments especially require checking whether proxy variables were inherited by the current session.
Manage media devices independently
Media devices work best with a dedicated subscription name and a fixed regional choice, avoiding frequent route synchronization with work devices. After changing regions, fully quit and reopen the playback app so it can reassess the new network path and content region. If playback fails, reduce concurrent downloads and background syncing before evaluating the route and platform.
Sports streaming places greater emphasis on sustained transfer and peak-time routing. Start with routes near the target region and complete the connection and exit-point checks before the event begins. See Sports Streaming VPN Route Selection for related guidance. Avoid switching repeatedly between distant regions during playback, as this interrupts the current session and increases the need for re-identification.
Configuration backups and privacy boundaries
You can back up non-sensitive client preferences, such as favorite route names and app rules, but full subscription URLs, account passwords, and tokens must not be stored in public code repositories or shared documents. If information must be transferred between devices, use a protected password manager. Check the address bar, notifications, and client details in screenshots, recordings, and ticket attachments to ensure subscription content is not exposed.
The service’s privacy practices and usage boundaries are governed by the Privacy Policy and Terms of Service. At the client level, users remain responsible for device security, system permissions, and browser sessions. The connection service provides a network path; it does not replace account security, device encryption, or the destination website’s own security measures.
Create reusable troubleshooting records
For long-term use, keep a troubleshooting record without sensitive information. Note the device platform, underlying network type, selected region, client mode, symptoms, and steps that ultimately worked. When a similar issue occurs, review the record first instead of starting from scratch. Do not store the full subscription, password, or payment information.
A useful record separates facts from assumptions. “The exit region did not change” is verifiable; “the route is broken” is only an unconfirmed conclusion. “The browser works but the terminal fails” suggests the issue is more likely in the app settings; “it recovered after switching the underlying network” indicates that the original network path needs further checking. This wording also makes tickets easier to handle precisely.
Confirm that the account can log in, the plan status is clear, the subscription updates, the route list is visible, system permissions are complete, the exit region matches your selection, the target app is accessible, and you know how to disconnect and restore the system proxy. After these checks, you have the foundation for independent use and troubleshooting.
When to return to the Quick Start Guide or topic articles
To repeat the main setup quickly on a new device, return to The Quick Start Guide. To compare measurement methods again, see the Plans page. To understand routes by region, see the Servers page. This guide works as a complete index, while topic articles explore specific scenarios in depth. Separating configuration, verification, and maintenance is more reliable than relying on a one-time connection result.
The complete path from account to connection
Choose the right measurement method, log in to the panel to get the subscription, import it on the relevant platform, then verify the exit point, DNS, and target app layer by layer. When issues occur, troubleshoot in the order of account, subscription, client, network, and application.