Complete 2BVPN User Guide

Getting Started

Service Coverage & Connection Setup

First, understand accounts, subscriptions, and clients

2BVPN is a subscription service for cross-border network acceleration. Getting started involves more than downloading a file: first you need an account, then your client retrieves the connection configuration associated with that account, and finally the client establishes a connection. Use your account to view plans, orders, and subscriptions; your plan determines the available data and billing method; and the client applies the configuration to your device. Keeping these separate makes it easier to identify what to check when something goes wrong: payment records, subscription updates, or device connection settings—without reinstalling everything.

A subscription link is the entry point for retrieving your configuration. It is not a fixed route or an ordinary webpage URL. The client uses it to fetch available configurations, which then appear as region and connection options. Each route is an available exit point for a connection. You can choose different routes for your computer and mobile devices; they don’t have to use the same region just because they share an account. For services that require a continuous session, however, sticking to a consistent exit region can help avoid interruptions caused by frequent changes.

The service covers 110+ countries and 190+ routes, supports Windows / macOS / iOS / Android / Linux, and allows unlimited devices to connect simultaneously. Coverage indicates which regions you can choose; it does not mean every target website offers the same content in every region. Streaming libraries, regional requirements for AI tools, and account requirements are determined by each service. Before relying on a feature, verify it in the target app rather than assuming everything works just because the client says it’s connected.

Check your device’s existing network setup

Before setup, make sure your device can access the local websites you normally use and sign in to the user panel without the accelerated connection enabled. If your basic connection is down, restore Wi-Fi or Ethernet first. A client can’t connect your device to the internet or fix a failed router connection. Note whether you’re on a home, public, or workplace network so you can compare later and see if an issue is limited to a particular connection.

Check whether other proxies, network filters, or tunneling tools are running on your device. For the initial setup, quit any similar connection apps you don’t need so you can test a clear, reproducible network path. Quitting means more than closing a window: check the menu bar, system tray, and system network settings for active connections. Work-managed devices may have enforced policies, so don’t remove management settings yourself. If you run into permission restrictions, first check whether installing and using this type of client is allowed.

It’s also worth checking your system clock. An incorrect date, time, or time zone can cause secure connection checks to fail, making the panel unavailable, configuration downloads fail, or websites report certificate errors. Correct the setting through your system’s time controls rather than disabling certificate checks to hide the problem. Keep the exact wording of browser warnings; it’s often more useful for diagnosing the issue than “the internet isn’t working,” and helps when you contact support.

Plan your first setup

Start on one device that’s easy to use and check for prompts, then apply the same process to your other devices. This helps you verify your account and subscription separately from any platform-specific permission issues. During initial setup, avoid changing your router, browser proxy, and advanced client settings all at once. Check the result at each stage: sign in to your account, confirm the plan is active, retrieve the subscription, connect to a route, and then test the target service.

Downloads are available in the Client section of the user panel. Sign in to get clients for all platforms except iOS; the actual iOS download link also requires an active plan. You must be signed in to get your subscription. Don’t assume a file with the same name in search results is provided by this service, and don’t import configurations from unknown sources into an existing app. Using the panel as the single download source helps keep each installation tied to the right account and avoids confusion from mixed sources.

The goal of your first setup is a connection process you can repeat—not enabling every advanced option. Keep the default settings, confirm your target app works, and adjust things one at a time.

This guide moves through the setup in stages, but you don’t have to start over every time. If you can sign in and your plan is active, go straight to subscription setup and import. If everything worked yesterday but not today, start with connection checks and everyday maintenance. Identify which stage is failing before you act, so you don’t accidentally delete account details or client settings that are still valid. For a shorter setup path, follow the Quick Start Guide.

Usage & Billing

Choose a plan based on how you use it

Monthly subscriptions vs. data packages

Before choosing a plan, consider how regularly you’ll use it rather than comparing the data amounts on the plan cards. A monthly subscription suits regular cross-border access with a predictable monthly budget. A data package works better if your usage is irregular and you want to draw on a balance when needed. The main difference is how data is allocated and used, not which devices are supported. Unlimited simultaneous devices is a service feature; data tiers do not limit the number of devices you can connect.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on the day you activated the plan, not on the first of each calendar month. Check the actual billing period shown in your account; a new calendar month does not mean your data has reset. If you upgrade mid-cycle, the price difference is prorated by the remaining days. Review the result shown in the panel rather than simply subtracting full-month prices yourself.

Data packages are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They remain valid until used and never expire. This describes how data packages work; it does not mean unused monthly subscription data carries over. Check the panel to see how a data package and an existing monthly subscription are displayed or used together. If the interface doesn’t explain how overlapping plans are handled, ask through a support ticket before holding different plan types at the same time.

Track usage by what you do, not by guesswork

Light browsing, messaging, and research use data differently from hours of video or large file syncs. Video quality, viewing time, background updates, and cloud sync all affect consumption, so the same amount of time online won’t always use the same amount of data. The best way to choose a suitable tier is to check how your account usage changes and consider what you did during that period—not to base your monthly needs on a one-time browser download speed.

When sharing a subscription across devices, remember to account for background tasks. Your laptop may be downloading system updates while your mobile device syncs photos—even if you’ve only opened a messaging app, your account’s data usage may keep changing. Pause nonessential large downloads and observe how much your usual work consumes. Unlimited devices means there’s no device-count limit; it doesn’t give each device a separate data allowance. Check total usage in your account panel.

If your usage pattern isn’t settled yet, don’t choose a large data allowance just in case. First decide whether you need a continuous connection, then compare the billing options you’re comfortable with. A data package that never expires still needs to be managed: leaked links, client misconfiguration, and lost devices all need attention. For a comparison based on different usage patterns, read Choosing Between a Data Package and a Monthly Plan, then check the current details on the plans page.

Check the shared terms and limitations

The service accepts Alipay / WeChat Pay / USDT and offers a 60-day no-questions-asked refund. Read the refund information alongside the Terms of Service. If you plan to request a refund, keep your order records and submit your request through the ticket system in your account. A refund policy does not explain plan data rules: check the relevant pages for data resets, upgrade proration, and order status. Don’t combine short labels from different pages into promises they don’t make.

When comparing plans, look at the price, billing method, and data units together; a larger number doesn’t automatically mean a better fit. A monthly subscription price and the full price of a data package cover different billing periods, so they aren’t directly comparable. Don’t infer renewal discounts that haven’t been stated. If you’re changing plans, check your current account status and order outcome first to avoid creating several similar orders and losing track of what needs to be paid.

By the end of this section, you should be able to explain whether you’re choosing a monthly subscription or a data package, what you’ll mainly use it for, and where to track data usage. Take that information to the Plans page and check the full pricing and terms. If you’re still unsure how your current plan relates to a new one, keep your existing setup and ask support through a ticket how your account will be handled. Don’t place repeated orders just to test the rules.

Account & Orders

Create an account and complete payment

Save your account details so you can sign in again

2BVPN doesn’t require an email address; create an account with a username and password. Open the panel and enter your username and password as prompted. Before submitting, check for accidental spaces or characters you won’t be able to recognize later. Your username and password are the credentials you’ll need to sign in, view your subscription, and manage orders. Skipping the email field doesn’t mean you can skip saving your credentials. Once your account is created, save them with a reliable password manager rather than relying on a browser session that may expire.

Use a password that’s different from the ones you use on other websites, and don’t store it in chat logs or public notes. On a shared device, don’t let the browser save your password indefinitely, and make sure you sign out rather than just closing the tab. If your system offers autofill, check the website domain and username before saving so your credentials aren’t filled in on the wrong site. Keep account credentials separate from route configurations in your client.

After creating your account, make sure you can open the panel and see the account section before choosing a plan. If the page shows an error, note the exact message and check what you entered; don’t keep creating similar usernames to see what happens. If you forget your credentials, use the recovery option currently shown in the panel. Since the account doesn’t require an email address, don’t assume an email-based recovery process is available. Don’t count on recovery options that aren’t explicitly shown—saving your login details securely is the best preparation.

Review your order before choosing a payment method

After choosing a plan, check the plan type, data allowance, amount due, and current order details. Monthly subscriptions and data packages work differently, so don’t rely on the payment amount alone to tell you what you’ve selected. Make sure the panel matches your choice before proceeding to payment. If you’re upgrading, read the prorated amount carefully. If it isn’t what you expected, stop and check before paying rather than trying to work it out from memory afterward.

Payment methods are Alipay / WeChat Pay / USDT. Use the payment option shown on your current order page; don’t use forwarded payment details from unknown sources. For USDT, carefully check the network, address, and amount shown in the order. Don’t repeat a transfer based on a previous payment, or assume a particular network is supported. Follow the instructions on the payment page, which are specific to the order and take precedence over general guidance.

Keep the order page and transaction result open during payment. Once payment is complete, return to the panel to check the order status. A payment app showing success and the panel confirming the order are separate steps. If the panel hasn’t updated, refresh the order section or reopen the order list before taking any further action—don’t pay again straight away. Network changes, browser back navigation, or closing the payment page can interrupt what you see. Check the order and transaction records instead of relying on whether the last page redirected.

Resolve pending orders, duplicates, and status mismatches

If you’ve been charged but the order is still unconfirmed, gather the order ID, payment method, transaction result, and page message, then explain the issue through an account support ticket. Don’t include your password, full subscription link, or unrelated private information. “Payment completed, but the order still shows as pending” is more useful than “my account is broken.” For payment amounts, rely on the actual order details; don’t send an extra payment for a supposed difference.

If you’ve created several similar orders, first identify which one was actually paid. Don’t assume the order at the top of the list is the right one. Keep the details of the paid order and handle unpaid ones using the options currently available in the panel. Don’t assume duplicate orders will merge automatically or that a payment for one order can be transferred to another plan. The panel or support team must confirm what happened to your account; a guide can’t determine the outcome of an individual order.

After your order is confirmed, return to the account overview and check your plan status and data before getting your subscription. If you still can’t see an active plan, resolve the mismatch between your account and the order first. Importing a client can’t fix an unconfirmed plan, and reinstalling the client won’t change the order status. Verify the account, order, and current plan before troubleshooting your connection so you have a reliable starting point and don’t mistake a billing issue for a route problem.

If payment doesn’t go as expected, save the records, check the order, and then contact support. Don’t pay again to see if the order updates, and never share your account password.

At this stage, you should be able to find your account details, the associated order, and your current plan in the panel. You may want to bookmark key pages in your personal browser, but don’t save links containing subscription credentials to a publicly shared sync space. For pricing and refund details, use the marketing site’s plans and terms pages. For your own payment and plan status, use the panel. Keeping these roles separate makes renewals and troubleshooting easier to manage.

Configuration Delivery

Get and protect your subscription link

Get the configuration for your account from the panel

After signing in to the panel, look for the configuration option in your account overview or subscription section. The exact label depends on the current panel; common options include copying a subscription link or importing it into a client. Copying puts the configuration link on your clipboard, while importing tries to open an app on your device. Make sure the client is installed before using the import option. If it isn’t, prepare your device in the download section first rather than repeatedly clicking import and expecting it to install everything automatically.

You must be signed in to get your subscription. The panel’s web address is not the subscription link, and you shouldn’t paste the sign-in page URL into a client. Use the configuration link provided by the panel; it may contain access credentials tied to your account. The client needs the complete link, so make sure you don’t miss any characters at the beginning, in the parameters, or at the end. Sending it through a chat app can introduce line breaks, previews, or character changes. Whenever possible, copy and paste it directly on the same device.

Before importing, check that your client supports the configuration format provided by the panel. Subscription is a general term for the configuration entry point; it doesn’t mean every app can read every format. If the panel offers different import options, select the one intended for your client. If you get a format error, check where you copied the link from and which option you selected before considering compatibility issues. Don’t remove link parameters at random to troubleshoot them; they may be required to identify your account or output format.

Know the difference between importing, updating, and connecting

The first import adds a configuration to the client. An update retrieves the latest content from the same link. Connecting uses the configuration already in the client to establish a network path. These are different actions. If the client doesn’t connect automatically after import, it may simply be waiting for you to choose a route. If you’re connected but the route list hasn’t changed, the configuration may not have been updated. After a failed update, the old configuration may still appear in the list, so seeing a region name there doesn’t prove the update succeeded.

Give the configuration a recognizable local name, such as “2BVPN Daily Connection.” The name is just for your own reference; it doesn’t need to include your username or full link. If your client has subscriptions from multiple sources, check which one is active before changing routes. Don’t import multiple copies of the same configuration at once. Duplicate names can make it look like an update failed when you’re actually viewing a different configuration. Once you’re sure you no longer need an old entry, remove it using the client’s available options so you don’t delete something still in use.

Update your subscription using the client’s update option. If an update fails, first check your internet connection and whether the panel is available, then confirm your account status, and only then consider copying the link again. Don’t assume there’s a fixed update schedule or that you need to import the subscription again every time you start the client. Follow any update prompts shown by the panel or client. After a manual update, check whether it succeeded, whether an error is shown, and whether the routes are still available to select.

Treat your subscription link like an access credential

Don’t post your subscription link in public forums, shared documents, public code repositories, or screenshots. Even if it doesn’t show a password, anyone with the link may be able to retrieve your configuration and use your account resources. When asking for help, describe what you did and the error you saw. Blur the full link, QR code, and account details in screenshots. Don’t send the complete link to an unknown online conversion service; use the panel’s supported options and a trusted local client to resolve compatibility issues.

If you think your link has been exposed, check whether the panel lets you reset your subscription or update its access credentials. If you can’t find the option, ask support through a ticket. Don’t assume changing your login password will invalidate the subscription link; whether those credentials are linked depends on how the panel works. After a reset, retrieve the new configuration on every device that uses the old link. Otherwise, one device may still show the old list while another has already updated.

When transferring a configuration between devices, use a method you control and delete unnecessary temporary copies afterward. Clipboard history, device syncing, and automatic screenshots can all retain the link, so take extra care on shared computers. Anonymous, no-logs is the service’s privacy policy; it doesn’t replace your responsibility to protect account credentials. Protecting the subscription link and protecting your login password address different risks, and both matter in everyday use.

Your subscription link contains account access credentials. Don’t share the full link when asking for help; keep the error message visible and hide the address and QR code.

After setup, you should be able to see the successfully retrieved configuration in your client, know which account it belongs to, how to update it, and where to get help if it’s exposed. For a closer look at how subscription links work, read the Beginner’s Guide to Subscription Links. Next, move on to platform setup. If configuration retrieval is already failing, fix that first rather than testing the connection; otherwise, the symptoms will be mixed together and harder to diagnose.

Device Setup

Import the client on each platform

Windows & macOS: check what’s running in the background

On Windows, download the client from the panel’s download section, install and open it, then return to the panel to copy or import your subscription. If Windows displays a warning, check the file’s source and app details rather than disabling system protection to continue. In the client, find the configuration or subscription section, paste the complete link, wait for it to load, and select the imported configuration. If the window closes but a tray icon remains, the app may still be running in the background; check that during troubleshooting.

After a successful import, keep the client’s default connection method and enable any system proxy or connection feature it requests. If it asks for permission, read the prompt and confirm it matches the action you’re taking. Don’t run another proxy client at the same time. If everyday websites stop working after you quit the app, check whether the system proxy is still pointing to a local service that has stopped. Before restoring default network settings, note their current state so you don’t overwrite settings managed by your workplace or another app.

On macOS, get the client from the panel, install and open it, then import your subscription. If macOS asks for network permissions, check the app name in System Settings and follow the on-screen instructions. The app window, menu bar icon, and system network status may show different information; closing the window doesn’t necessarily end the connection. If the import action does nothing, open the client first and then try copying the link instead. Check separately whether the app is running and whether it has retrieved the subscription successfully.

iOS & Android: check system connection permissions

The actual iOS download link requires an active plan. Check your plan status in the panel first, then open the relevant option in the Client section. After installing the app, return to the panel to get your subscription and add the configuration using a supported method. The first time you connect, iOS may ask permission to add a network configuration; make sure the request comes from the app you just installed. Importing a configuration and granting system permission are separate steps. If you can see routes but can’t connect, check the app’s prompts and the system connection status.

After signing in on Android, get the client from the panel. Install it using the system prompts. If Android asks you to allow installation from a source, make an informed choice for the source you need, then restore your usual restrictions if appropriate. Open the client, import your subscription, select a route, and approve the system connection request. If another tunneling app is already running on your device, stop any connection you don’t need so Android doesn’t confuse the new request with an existing session.

On mobile devices, screen locking, network changes, and background activity can be affected by battery-saving and background-management settings. First check whether the issue only happens after one of these actions; then review the target app’s background permissions rather than changing every battery setting at once. If the target service gets stuck in an old session after switching Wi-Fi networks, reconnect the client and reopen the app. Menu labels vary by system, so the steps here shouldn’t be treated as a fixed path for every device.

Linux & cross-platform differences

On Linux, get a client from the panel that matches your system environment. Before installing, check the system architecture, package format, and runtime requirements. After installation, use the app’s standard import method first. If you see a dependency or permission error, keep the full message and check the download section’s instructions. Don’t run privileged scripts from unknown sources. A desktop environment’s system proxy usually affects only apps that respect that setting; command-line tools and apps with their own network settings may need separate configuration.

On Linux, distinguish between a running process, a loaded configuration, and traffic being routed through the client. The client process being present doesn’t mean a target app is using its network path, and a configuration file loading successfully doesn’t mean your user has permission to enable a particular network mode. For your first test, use a default mode you can verify in the interface, then consider background startup after it works. When troubleshooting command-line access, check the proxy environment used by the command itself rather than assuming browser access proves every terminal tool will work.

Import and verify the setup separately on each device. Don’t skip permission checks on your other device just because the laptop worked. Unlimited devices means you can share a subscription, but each device still has its own system settings. For more detailed Windows installation steps, read Windows Setup: From Installation to Launch at Startup. For every platform, start with the client and configuration provided in the panel; there’s no need to search for public download lists.

Connection Checks

Routes & connection verification

Choose a region first, then compare route types

After importing, choose a route from the client’s current list. If a target service has specific regional requirements, identify the right region first and then compare the available routes there. For everyday browsing, start with an option that works well on your network. A region name indicates the exit location; it doesn’t guarantee the route suits every task. The closest region isn’t necessarily the best-performing option every time, so test it with your current connection and target app.

IEPL dedicated lines, relayed routes, and direct connections describe different ways a connection is routed; they’re not performance ratings. IEPL dedicated lines use dedicated cross-border paths, relayed routes connect through an intermediate node, and direct routes use a more direct path. The routes available to you depend on your current subscription. Don’t assume one type is always faster based on its name, or that a single test proves how it will perform at every time and in every region.

The route list shows regions and route types. For an actual connection, rely on what the client successfully retrieves. If the website and client show different information, update your subscription and check which configuration is active before asking for help. When testing, change only the route and leave other settings alone. If you change networks, modes, and regions at the same time, you won’t know which change affected the result.

Verify the connection with a real task, not just the client status

After connecting, check that the client shows no errors and that the system indicates an active connection. Then open a website you normally use to make sure the basic network settings still work, followed by the cross-border service you need. Don’t stop at loading the homepage; test the action you actually need, such as signing in, opening a work page, loading content, or starting playback. A cached homepage may look fine even when actual requests are still failing.

For streaming services, check the library and playback in the target app. For AI tools, check whether you can sign in, start a conversation, or use the feature you need. A website loading doesn’t mean your account meets regional, subscription, or content requirements. If you see an explicit account restriction, read it and check the target service’s rules rather than treating every access denial as a route issue. For help with specific use cases, see Streaming and AI Tools access.

If only one browser is affected, test other apps on the same device and check for browser-specific proxies, extensions, or stale sessions. If only one device has a problem while the same subscription works elsewhere, start by checking that device’s configuration and permissions. If all devices fail on the same network, compare with another available network. This step-by-step approach is more useful than repeatedly changing regions and helps avoid unnecessary changes to your account setup.

Narrow down the problem based on what you see

If the subscription won’t load, check the link, format, and panel availability. If you can select a route but can’t connect, check your account status, connection permissions, and route selection. If the client says you’re connected but the target app doesn’t work, check whether the current mode routes that app’s traffic and review the service’s own error message. The same “won’t open” symptom can happen at very different stages. When reporting an issue, say what you clicked before it happened and exactly what the page or app displayed.

Don’t disable security checks, ignore certificate errors, or delete unknown system settings to force a connection. For certificate errors, check the system clock and network. For permission issues, check the app source and system authorization. For a single website, note its exact message. If the client can show connection logs, extract only the parts related to the current error. Before sending them, check for subscription links, account information, or other credentials; don’t share the entire configuration file.

If you can’t identify the problem yourself, submit a support ticket with your platform, network type, route name, the stage that failed, the exact error, and what you’ve tried. It’s more helpful to describe what changed after a specific action than to say “none of the routes work.” Don’t include your account password. After testing, keep the configuration and route that you know work as your everyday baseline. You can compare against them later instead of guessing from scratch.

Ongoing Use

Everyday maintenance, data usage & renewals

Maintain your setup instead of rebuilding it

Once everything works, routine maintenance means checking plan status and data usage, updating the subscription when needed, and responding to client prompts—not reinstalling every day. If the route list changes, update your current configuration and check the result. If an update fails but the old configuration still connects, keep the error message and check the panel instead of deleting everything straight away. Removing the configuration loses a useful point of comparison and can turn a problem with the update link into a complete loss of access.

If the client prompts you to update, use the source provided by the panel to check how to get the update, and keep any local configuration notes you need. Before updating, make sure you know how to retrieve your subscription again rather than relying only on an imported entry. Don’t assume every client will migrate all settings automatically, especially custom rules, background startup, or advanced modes. After updating, test a basic connection and your usual target apps before restoring nonessential background tasks.

If your device switches between networks, note whether issues appear after a particular change. If it still won’t connect on a familiar network, reconnect the client first, then check the active configuration and system proxy. A temporary disconnection doesn’t mean you need a new account. Stop connections on devices you no longer use and remove configurations you don’t need. Before selling or servicing a device, sign out, remove the subscription, and clear related autofill entries to reduce leftover credentials.

Read your data usage and plan period correctly

Monthly subscription data resets each month on your activation date. When you check your account, look at your current plan status and data usage together. Plan validity, remaining data, and whether the client is online are related but separate checks. A healthy-looking data balance doesn’t guarantee every account condition is met, and a connected client doesn’t replace checking your panel. If usage differs from what you expected, check the billing period and think back to background tasks and other devices rather than judging by the apps currently open on your screen.

Unlimited simultaneous devices lets you share a subscription between your laptop and mobile devices, but you still need to know which devices have the configuration. If data usage changes unexpectedly, stop connections you don’t need and pause syncing or downloads, then observe how your usual tasks affect usage. If you can’t explain the change, check for old devices, shared records, or possible link exposure. Don’t assume a particular website or client is at fault based only on a change in data usage; rule out possible sources one by one.

Data packages remain valid until used and never expire, but you should still check your remaining balance regularly. If you’re nearing the amount you expect to use, review your plan options ahead of time rather than discovering a billing issue during important work. If you plan to switch from a data package to a monthly subscription, or hold different plan types at once, read the panel details before confirming the order. Don’t infer stacking, offsets, or usage order from the rules of another service when they aren’t stated here.

Renewals, upgrades & refund records

Before renewing, check your current plan and the option you’re considering. Confirm whether you want to continue with the same setup or change your data tier. Don’t confuse creating a new order with completing a renewal; check your account status after payment is confirmed. Whether the panel offers automatic renewal or expiry reminders depends on what’s actually shown in the interface. If there’s no clear notice, don’t assume a future payment has been arranged. Checking your account before important work is more reliable than relying on memory.

Mid-cycle upgrades prorate the price difference by the remaining days. Before upgrading, read the result shown in the panel rather than assuming how data or validity will be combined. Save the order details, complete payment, then check your plan status. If the result isn’t what you expected, stop creating additional orders and contact support with the before-and-after details. Multiple changes make it harder to compare what happened; a clear record helps distinguish a display delay, an unconfirmed order, and an actual plan change.

The service offers a 60-day no-questions-asked refund. To request one, read the Terms of Service and submit a ticket from your account with the relevant order and details. Keep records of the support conversation. Don’t lose your payment receipt while troubleshooting a technical issue, and don’t post a full order screenshot in a public forum. List refund requests, connection issues, and plan upgrades separately so it’s clear what you need help with instead of compressing everything into one vague message.

Keep a configuration you know works as your baseline. Change only what you need, then check the result. This makes it easier to restore your setup and explain what changed before and after a problem.

Everyday notes can stay simple: remember your usual devices, current plan, working configuration, and what you did when a problem occurred. Don’t save the full subscription link or an unencrypted password in your notes. If your setup is stable, leave the defaults in place and focus on the work you need to do. Adjust rules or connection methods only when there’s a clear need or a reproducible issue. Advanced settings should solve problems, not add maintenance overhead.

Adjust as needed

Advanced routing & troubleshooting

Understand split tunneling, global mode, and app routing

Split tunneling typically uses rules to decide which requests use the accelerated connection and which use your regular network. Global mode typically sends all traffic handled by the client through the selected route. The key phrase is “handled by the client”: browser system proxy settings, app-specific proxies, and system-level network modes may cover different traffic. Switching to global mode doesn’t prove that every program on your device uses the same route. Test in the target app rather than relying on the mode name.

For everyday use, start with the client’s default rules. If one target app has a problem while others work, first check whether it follows the system proxy or has its own network settings. Consider changing rules only after that. Temporarily switching modes can help isolate the issue: if the result changes, investigate which traffic is routed and which rules match it. When testing is complete, restore suitable everyday settings so unrelated traffic doesn’t keep taking an unnecessary route.

Before creating custom routing rules, decide whether you need to handle a specific domain, app, or type of traffic. Rule order, matching criteria, and the selected route can all affect the result. If the client shows rule-match details, use them to check actual requests instead of relying on how the rule looks. Keep a way to restore the previous setup, and test both the target task and your usual websites after making a change. If it doesn’t help, revert it rather than adding more rules that may override each other.

Distinguish DNS resolution, app sessions, and exit region

DNS resolution translates a website name into a connection destination, while an app session may retain its sign-in state and previous regional assessment. Either can make an app behave as if nothing changed after you switch routes. If that happens, reopen the page or app, read the specific message, and check any resolution and connection details the client provides. Don’t enter DNS addresses found online at random or disable necessary checks to hide a configuration conflict.

For account tasks that require an ongoing session, it’s generally best to stick to a consistent exit region. Frequent changes may trigger the target service’s sign-in checks or repeatedly reload content. Switching routes isn’t a fix for every problem. If a target service explicitly mentions account, payment, or regional eligibility, check its rules first. The service provides cross-border network routes; it can’t replace authorization from the target platform or guarantee that content in a particular region will always stay the same.

Anonymous, no-logs is the service’s privacy policy. It doesn’t prevent websites from recognizing an account you’re signed in to, and it doesn’t replace browser permissions, device security, or credential management. On public networks, check the domain you’re visiting, use a standard secure connection, and review the permissions requested by apps. For more on privacy claims and account details, read How to Verify a No-Logs Service. Privacy involves the service, your devices, and target apps—not just the name of a route.

Troubleshoot with tests you can repeat or undo

Start by recording your baseline: device, network, active configuration, route, mode, and the action you’re trying to perform. Then change only one thing—for example, keep the device and mode the same and switch to another route in the same region, or keep the configuration and route the same and switch networks. Compare the results before deciding what to try next. You don’t need complex tools; a simple, controlled test can turn “it started working again” into a result you can explain, and helps you remember which settings originally worked.

On Linux or macOS, if the appropriate command is available, you can use the command below to check whether a test site returns response headers. On Windows, call the corresponding executable explicitly if you use this tool. The example doesn’t include a proxy address and won’t automatically route terminal traffic through the client, so it only checks reachability from the current command environment. Getting a response doesn’t prove that other apps use the same path or that streaming libraries or AI features meet their requirements.

curl --head https://example.com/

If the command returns an error, keep the exact text and distinguish name resolution failures from secure connection failures or connections that couldn’t be established. Then compare it with the client’s records. A single line in a screenshot isn’t a complete network diagnosis, and you don’t need to install unrelated tools just to reproduce another guide. Before sharing diagnostic details, check for usernames, configuration paths, full subscription links, or other access credentials. Share only what’s needed to identify the problem.

If troubleshooting reaches system routes, administrator permissions, or workplace network policies and you can’t assess the impact, stop making broader changes. Restore settings you know work and submit a support ticket. A useful request explains whether the issue can be reproduced, which apps are affected, and what comparisons you’ve already made. The goal isn’t to learn how to change every setting; it’s to complete the process from account to connection, know when to update or revert, and send support a clear record when needed.

To repeat the main setup steps, go back to the Quick Start Guide. For billing details, see Plan Details. To report an account issue, open a ticket in the user panel.