7xVPN / HANDBOOK

Complete VPN Setup Guide

Setting things up for the first time? Follow the chapters to go from choosing a plan to verifying your connection. If your client is already installed, jump to renewal, split tunneling, or troubleshooting. For the basic setup flow, start with the Guides. Return to this manual for platform-specific steps or help identifying where something went wrong.

SERVICE / ROUTES

Cross-border network service and routes

What accounts, subscriptions, and routes do

7xVPN is a subscription service for cross-border network acceleration. The user panel manages your account and orders and provides your subscription. The client retrieves that subscription, lets you choose a route, and handles the traffic assigned to it. The route determines the path those requests take. These are separate steps: successfully signing in to the panel means your account can access it; importing a subscription means the client has received its configuration. Only after connecting and sending a test request can you tell whether this device is using the selected route.

The path from your device to a website also depends on your local network, name resolution, and the website itself. Connecting a client does not mean every request goes through the tunnel; split-tunneling rules may leave some apps or sites on their usual path. Even when a request uses a route, the destination service may decide whether to respond based on account region, content licensing, or its own access policies. Check in this order: the client handles the traffic, the request matches the route, and the service is available. This is more useful than relying on a single connection indicator.

Consider region and route type separately

The service covers 120+ countries / 180+ routes. Start with the exit region your task requires. For a work service you use regularly, check which regions it accepts, then consider options closer to your current network. A city name alone does not tell you everything about a route: routes in the same region may have different entry paths and intermediate hops. See Global Nodes for regions and route types, then note your candidates in your test log.

Route types and what to check during a trial
Route typeDescriptionWhat to check during a trial
IEPL dedicated lineUses a dedicated line for the cross-border segmentWhether sessions stay connected during your usual usage hours
RelayTraffic is forwarded through an intermediate node to the exitLatency changes before and after switching on the same network
DirectDoes not use a separately designated relay nodeWhether the client can connect directly and maintain a steady transfer

Choose a route based on the task

Route categories describe the transmission path, not a speed ranking. A dedicated-line label says nothing about the quality of the connection between your device and the entry point, and a relay does not necessarily make every test faster. Video calls for work, for example, are more sensitive to latency spikes and brief packet loss, while large file transfers depend more on sustained throughput. For video, check whether the same content starts smoothly and resumes loading after you seek. For interactive tools, focus on whether consecutive requests work reliably, not just how quickly the page opens the first time.

For a fair comparison, keep the device, network, and destination service the same, then perform the same task on each candidate route. If you test one route on your home network and another on public Wi-Fi, you cannot tell what caused the difference. Browser caching can also speed up repeat visits. Treat page loading as a connectivity check and an actual download or call as an experience check; there is no need to combine them into one score. For more comparison tips, see How to Choose a VPN Route.

Usage boundaries and configuration permissions

Windows / macOS / iOS / Android / Linux are supported, and there is no limit on the number of devices connected at the same time. System permissions, network access, and client settings still need to be handled separately on each device. Work-managed devices may have additional requirements for network extensions or proxies. If you see a management prompt, check with your device administrator; do not remove work configurations just to connect. If a public network requires a sign-in page, complete that step before connecting the client.

7xVPN follows a no-logs policy. This describes the service's privacy practices; it does not change how browser extensions, website accounts, or your device keep records. Before choosing a route, identify the traffic that needs to use the service, rather than sending every unrelated app through the same path. For a first setup, start with one device you manage, one repeatable destination, and one backup route. Verify the result before applying the configuration to other devices.

Define the test task before comparing routes. For your first setup, verify one device; import to other devices after confirming the connection path.

BILLING / TRAFFIC

Plans, data, and billing periods

Estimate data usage from past activity

When choosing a plan, start with your usage patterns, then consider the price. Your device's network statistics can help, but system counters often combine direct traffic with traffic handled by the client and may cover different time periods. First, identify which apps typically use the route, then estimate their total usage over a billing period. Reading documents and messaging usually involve occasional requests, while ongoing video, cloud-drive syncing, and large uploads can change your usage significantly. A short period of light use is not a reliable estimate for a whole billing period.

When multiple devices are in use at once, treat them as sharing one data allowance. “No device limit” does not mean each device gets the plan's full listed allowance. Track work, personal, and always-on devices separately. If usage is unusually high, first check whether it came from a one-off file transfer or recurring background activity such as system updates or autoplay. Then decide whether to move to a higher plan or adjust automatic tasks on individual devices.

Monthly plans: check the reset date; data packages: check the balance

Billing options and prices
OptionTierHow usage works
Monthly plan¥9.9/month includes 60GB · ¥18/month includes 250GB · ¥28/month includes 500GBData resets monthly on the activation date
Data package¥158/300GB · ¥358/1000GB · ¥658/3000GBUse it until it's gone; it never expires

A monthly plan suits people with fairly consistent needs each billing period. Pay attention to the period starting from your activation date; do not assume the allowance resets on the first of each calendar month. If your work changes next month, for example with more regular video calls, compare capacities on the Plans page, then check your current billing status in the panel. Mid-cycle upgrades are prorated by the remaining days, so subtracting the listed prices of two tiers will not give you the amount currently due.

A data package suits occasional or irregular tasks. Compare how much data you get separately from how long it will take to use it. “Never expires” means it does not expire monthly; usage still comes out of the balance, and service will not continue once the balance is depleted. If you mainly need it for occasional travel or cross-border collaboration, review whether similar tasks involved concentrated downloads and whether several devices need to connect during the same trip.

Turn your budget into a choice you can verify

Use your task history to choose a billing option, then estimate the total data needed to choose a tier. Do not start by picking the highest or lowest tier and looking for a reason afterward. Estimate one-off tasks, such as a time-limited project or file migration, separately. For regular work, count the apps you know will use the route as your baseline. Not all uploads and downloads use the same path. After installing the client, compare its request records with changes in the panel's data usage, then adjust your budget. Do not make a long-term decision based on one unusual spike.

If your estimate falls between two tiers, first check whether backups, updates, or syncing that do not need the route can stay on your regular connection. Separating those background tasks is more reliable than adding a blanket buffer based on guesswork. If you are not yet sure how you will use the service, track actual usage on your primary device for a while and see how the balance changes over the billing period. Do not rely on other users' estimates from different apps, video quality settings, or split-tunneling rules.

What to check before checkout

Use the plan name, billing option, and amount due shown on the current order in the panel as your reference. Even products with the same data allowance may be a monthly plan or a data package. Payment methods: Alipay / WeChat Pay / USDT. The page offers a 30-day no-questions-asked refund; see the Terms of Service for details. Before checkout, make sure this is the account you intend to use for renewals and subscription access, then proceed to the order page. This helps avoid activating a plan on an account you only meant to use temporarily.

By the end of this chapter, you should be able to answer three practical questions: whether you bought an allowance for a billing period or a data balance, where to check what remains, and when to reassess your needs. Keep those answers in your own notes; there is no need to save a full screenshot of the payment page. Once you have confirmed the billing option, create or sign in to your account in the panel and check that the order has activated successfully.

PANEL / ORDER

Create an account and confirm your order

Create an account and keep your login details safe

Go to the user panel from this site. No email address is required to create an account; just choose a username and password. Save them in a password manager you control, and make sure the saved entry points to the 7xVPN panel. Do not reuse a work password or one used for another service. If you already have an account, continue through panel login. You do not need another account just to install the client on a second device.

If the page says your details do not match, check for spaces around the username, symbols changed by your input method, or a password manager entry for a different account. Reopen the page from the usual panel entry point and verify the account separately rather than pasting your password across multiple pages. On a shared device, do only what is necessary and sign out when finished. Do not let the browser save credentials in a profile you do not control, and never include your password in an order screenshot or support request.

Choose a plan and proceed to checkout

After signing in, open plan selection in the panel. Use the billing option and tier you chose in the previous chapter, then start checkout for that tier. The page may create an order before asking you to choose a payment method. Check the account, product, and amount due on the order, then continue to payment from that order page. If your browser blocks a window, make sure the prompt is part of the current panel and payment flow. Do not use a payment link found through a search instead.

For Alipay or WeChat Pay, follow the payment instructions on the current order and return to the panel to check its status once payment is confirmed. For USDT, compare the network, receiving address, and amount shown for this order before confirming in your wallet. The same asset name does not mean you can use a different network. If information is missing or the payment screen does not match the order, stop and verify before proceeding. Do not reuse payment details from an old order.

Payment confirmation is not the same as plan activation

A successful payment status only confirms the result shown by the payment provider; it does not confirm the order in the panel. Return to the original account and check the order history, then open Account Overview to confirm that the expected plan, available data, or active status appears. If an order still shows as pending, keep your payment record and check that same order again. Do not pay for the same tier a second time just because you no longer see a prompt after reopening the plans page.

If the expected plan is missing from your overview, first check whether the order is still awaiting confirmation, you are signed in to the wrong account, or the page is out of date. Verify the username and refresh the overview. Clearing the client configuration will not fix a payment issue; the client does not determine which account owns an order. If the payment page has closed, do not recreate the order from memory. Check the original order's status in your order history and follow the panel's instructions.

Problem orders and refund requests

If an order has not reflected payment for a long time, you were charged twice, or the plan does not match your notes, sign in and open a support ticket. Include the tier purchased, payment method, order ID, status shown in the panel, and the sequence of events. Before attaching an image, cover payment details that are not needed to identify the issue. Never share passwords, wallet keys, full subscription URLs, or other account information. If you can describe the status clearly in text, there is no need to upload a full-screen screenshot.

To check eligibility for the 30-day no-questions-asked refund, review the Terms of Service first, then submit the related order and a brief explanation through the user panel. Payment, activation, and refunds are separate processes: deleting the client does not cancel an order, and changing routes does not alter its payment status. Once you have confirmed the order, move on to setting up your subscription. If Account Overview does not show an active service, resolve the order or account issue first.

After payment, rely on the order and Account Overview in the panel. Keep the original order record to check your plan and avoid duplicate payments if you need support.

PROFILE / IMPORT

Get and verify your subscription

Get your client and subscription from the panel

On the device you are setting up, sign in through this site's entry point and open Client Downloads and Account Overview to handle installation and subscription access separately. You must be signed in to retrieve a subscription. Downloading and installing a client does not add routes to it. If the client launches but shows an empty configuration list, do not adjust routes or connection modes yet. First check the subscription option and account status in the panel.

After signing in, you can get clients for Windows, macOS, Android, and Linux; a purchased plan is not required. On iOS, the panel provides the client link through the App Store when you have a purchased plan that has not expired. Eligibility to download a client and having an available subscription are separate matters. Installing the app or downloading it from the app store does not replace checking your plan and subscription in the panel.

One-click and manual import

If the panel offers an import action for your client, install the client first, then click the action in the panel on the same device. If your browser asks to open an app, check the recipient's name and confirm it is the client you just obtained from the panel. After the app opens, check whether the remote configuration was added. Switching to the app's home screen alone is not proof of a successful import: the browser may only have opened the app, or the client may not have received the configuration.

For manual import, copy the subscription URL for your client from the panel, switch to the client, and choose the option to add a link under subscriptions, remote configurations, or configuration management. The label varies by platform and client. The key is that the form retrieves a remote configuration, rather than asking you to enter a route's server details. After pasting the URL, check for extra spaces or line breaks, save it, and refresh once. Make sure the list populates correctly. If renaming is supported, add a source or purpose so you can identify it later.

Tell the URL, configuration, and selected profile apart

The subscription URL retrieves a configuration; the downloaded configuration is a local copy stored in the client; the selected profile determines which configuration the client uses for this session. Adding a remote subscription may not replace an older copy or select the new one automatically. If the client shows multiple configurations, check the current configuration name against the subscription entry. Do not assume a matching route name in the list means the right profile is selected. If you refreshed the wrong entry, switch back to the correct configuration first, then decide whether the old one should remain.

When an import fails, separate the error by where it occurs. If no request can be sent, check that the device's regular network can reach the panel and, if needed, pause an old connection before trying again. If the request succeeds but the client cannot parse the response, check that you chose the subscription format for that client rather than copying the panel page URL. If the client says the configuration was saved but shows no routes, check whether it switched to the new entry and whether the panel shows an active plan. Change one thing at a time so you can identify what helped.

Treat your subscription link as private

Never submit a URL that retrieves your account configuration to a public conversion site, or share it in group chats, public documents, or screenshots. To set up another device, sign in to the panel directly on that device instead of passing the link through a shared clipboard or collaboration document. After pasting it, check whether your system keeps clipboard history. On a shared device, do not leave the subscription where others can access it. A support request can describe the import method, error type, and when it occurred without including the URL.

If you think your URL has been exposed, check the panel for available subscription management actions and follow its instructions. If there is no relevant option, confirm what to do through a support ticket. Afterward, refresh and verify the configuration on any device you still use. The starting point for the next chapter is: the device has the client, the account status is confirmed, the panel can retrieve the remote configuration, and you can identify it in the client.

CLIENTS / SYSTEM ACCESS

Client imports by platform

Start by connecting on the platform you use most. Note the configuration name, selected route, and verification result, then move on to other devices. The basic steps are the same on each platform: install the client, import the remote configuration, select it as current, grant the required network permissions, and send a test request. The table highlights platform-specific permission checks; it does not imply that every client has the same mode switches.

Pre-connection checks by platform
PlatformGet the clientCheck first
WindowsSign in and download from the panelWhether system proxy, app proxy, or tunnel mode is set as expected
macOSSign in and download from the panelWhether system network permissions have been approved
iOSOpen the App Store when the panel confirms eligibilityWhether the expected VPN configuration is enabled
AndroidSign in and download from the panelVPN authorization and background activity
LinuxSign in and download from the panelSystem installation method, proxy scope, and routing mode

Windows: Check system and app proxy settings

Install the client provided by the panel, open configuration management, import the remote subscription, and select it. Before testing for the first time, check system network settings for proxies left by other tools, and see whether your browser has its own proxy configured. With system proxy mode, you can start by testing in a browser that respects the system setting; command-line tools and some apps may not. If the client supports tunnel mode, try it only when you need broader app coverage and are authorized to do so. Note the original mode before switching.

If your browser works but your meeting app does not, first check whether both use the same network settings instead of switching routes right away. Disconnect, then check whether the system proxy returned to its original state. If the browser still points to a local proxy that has been shut down, quit the client and check system settings. Restore the values you recorded. For managed software and system settings, do not clear them; ask your administrator for help.

macOS: Check system prompts and the active configuration

Get the client from the panel and install it by following the on-page instructions, then import the matching subscription entry. If macOS prompts you about a network configuration or extension when you connect, check that the app name and action match what you just did, then approve it as prompted. Do not disable system security checks just to complete installation. If the app opens but cannot establish a connection, check Network settings and related permission pages for pending approval prompts or device management restrictions.

On macOS, a browser extension can send one site through a different proxy, and existing network configurations can affect your test. To isolate the variables, record a baseline on your regular network, open the current client, and test the same site. If something goes wrong after waking from sleep, first make sure the network connection is back, then check whether the client has reconnected. A problem after every wake does not necessarily mean the subscription has expired.

iOS: Check the subscription, system authorization, and active profile

If you meet the download requirements, follow the panel link to the App Store and install the client. Open it to prepare for the subscription import. Return to the panel on the same device and choose the import method for the client. To add a link manually, open the client's remote configuration options, save the entry, and select the right one. The first time you connect, approve the VPN configuration when prompted by iOS and confirm in Network settings that this is the active configuration. If older configurations remain, trust the one actually enabled in the system and client, not a similarly named list entry.

Android: Distinguish connection permission from background restrictions

Get and install the client from the panel, import the subscription, select the configuration, and connect. The system VPN permission should be requested by the client you just opened. If another tool is already using a similar connection, check the system prompt and pause the old connection if needed, or ask your administrator. If the connection works at first but often drops when you switch to another app, check whether the system restricts background activity. Adjust only the permissions this client needs; do not disable power-saving and security settings across the whole device. For more detail, see Android Setup Guide: Starting from Scratch.

Linux: Check which proxy method the app actually uses

Use the panel's download page to get a client suited to your environment. Confirm that it matches your operating system and processor architecture, then follow the installation instructions for that download. Once it starts, import the appropriate subscription and select the configuration. Desktop proxy settings may not apply to terminal tools or background services, so test with the app you intend to use rather than relying on another program's result. Before enabling tunnel mode, which may require additional permissions, check the client documentation and device management requirements. Do not leave a troubleshooting program running as an administrator.

CHECK / EGRESS

Connection checks and interpreting results

Record a baseline while disconnected

Before testing, use the same device, browser, and network. Disconnect the client, open My IP to check your current exit IP, then try a site that normally works for you. If the browser cannot access the internet, check your regular network, sign-in requirements, or leftover proxy settings first. Keep the baseline in your own notes. Compare the exit before and after connecting, whether the lookup succeeds, and whether the destination is reachable; there is no need to share your address. If you switch networks, record a new baseline for that network.

Keep your test browser setup simple. If it has its own proxy enabled, your baseline may not reflect your local network's exit. If several apps manage tunnels at once, it may also be unclear which one handled the request. Use a browser profile with known settings and temporarily quit proxies you are not using for the test, but do not change managed settings. Note the client's mode, especially if the lookup site may be set to connect directly by a split-tunneling rule.

Verify the requests you send after connecting

In the client, select the imported configuration and destination route, connect, and make sure no error appears. In the same browser, reload the IP lookup page rather than relying on its previous result, then try a real work destination. Check whether the client shows the route or rule matched by that request. Some clients only show useful connection records after a request is made. An unchanged idle log does not by itself mean the connection failed.

If the lookup shows a changed exit that matches your current rules and selected route, that is evidence that this request used a new path. It does not prove that every app on the device is covered. If the exit has not changed, first check whether the lookup site is set to connect directly, then test with a destination you know should match the route. Region names may not match the city shown in the client word for word. IP geolocation databases and client labels can differ, so focus on whether the expected path is being used and the destination works.

Diagnose lookup, name resolution, and destination services separately

If a lookup page fails, first determine whether the entire network is down or only that page cannot return data. Try another ordinary website as a reference and check the client's records to see what requests were sent. If only a particular domain fails, note whether the browser reports a name resolution error, a connection timeout, or a clear rejection from the website. These point to different layers: check the name resolution path for lookup failures, the route and destination reachability for timeouts, and the service's own access requirements for rejection messages.

An exit IP lookup shows the exit used by that lookup request; it does not tell you where every DNS query went. System resolution, browser secure DNS, and client-side resolution may all be active and use different paths. When testing DNS, note which app reported the error and check whether it has its own resolver settings. Do not change DNS system-wide just because the reported region differs from the route label. In a work environment with internal domains, changing system resolution may break internal apps. Keep the existing settings and check with your administrator first.

Establish repeatable trial results

Once basic connectivity is confirmed, test the tasks you actually need. For video, check continuous playback and recovery after seeking. For online collaboration, see whether requests intermittently time out. For calls, check whether a long session repeatedly drops. When comparing another route, keep the app, network, and test content the same. Record the time and result; do not treat one performance snapshot as a long-term guarantee. For help distinguishing latency, jitter, and throughput, see How to Test VPN Speeds and repeat your observations in the same way.

At the end of your test, disconnect deliberately and confirm that your regular network works again. Reconnect and check whether the same destination is reachable. If it only works immediately after connecting but fails every time you switch networks, note which switch occurred, which app was affected, and what message appeared. Follow up in the maintenance and troubleshooting chapters. Once you have a repeatable result, set up other devices; verify each device's active configuration and the apps you actually use.

“The client is connected,” “the test request used the selected route,” and “the destination service responded normally” are different conclusions. Check them in order to identify which layer needs troubleshooting.

CARE / RENEWAL

Everyday maintenance, renewals, and device changes

Check your current billing period before investigating data changes

Check the active plan and available data in Account Overview. Monthly plan data resets each month on the activation date. When usage changes, check how much of the current period has elapsed instead of guessing the reset date from the calendar. For a data package, check the remaining balance when planning ahead; it does not expire and lasts until used up. If the panel's availability status differs from what you expect, first make sure you are signed in to the account that made the purchase, then check the relevant order.

Device statistics and Account Overview may count usage differently. Some device-level counters cover only the current connection, while system statistics may include regular network traffic. If usage is unexpectedly high, check each device for syncing, autoplay, downloads, or updates. Pause background tasks you know you do not need and see whether usage continues to change. Do not try to attribute exact usage to an app by simple subtraction unless the time period, device, and traffic path all match.

Check your current status before renewing or upgrading

Before extending your service, work out whether the issue is an approaching expiry date or a data allowance that does not meet your current needs. Check Account Overview and order history for expiry-related actions. If usage has increased and you are considering an upgrade, compare allowances on the Plans page, then check your current checkout details in the panel. Mid-cycle monthly plan upgrades are prorated by the remaining days; the checkout page shows the amount due. Keep the purchased tier, current charge, and next reset date as separate details.

After completing the transaction, check that the related order appears in the panel, then confirm that Account Overview shows the expected status. Do not assume that renewal always requires a new subscription URL or that an old configuration will always remain valid. First update the current configuration in your existing client and try connecting. If the panel's subscription link or requirements have actually changed, follow its instructions. Checking Account Overview and sending a real request is more reliable than just counting how many routes remain in the client.

Keep a working baseline when updating configurations and clients

If the route list changes, refresh the remote configuration you currently use and check whether your previous preferred route is still there. If requests take an unexpected path after the update, see whether the client selected a default route or reverted to its default mode. Avoid changing your network, updating the client, and editing split-tunneling rules all at once; otherwise, even if things work again, you will not know why. Record working routes, the selected mode, and any necessary exceptions. Do not store the full subscription URL in maintenance notes.

Get client updates through the relevant user panel entry. First check whether the new version recognizes your existing configurations, permissions, and rules. If you created complex rules, save a separate copy without credentials and note which configuration they apply to before updating. After the update, verify the default workflow, then restore custom settings one at a time. Do not send someone a full export containing your account configuration for troubleshooting.

Changing devices, stopping use, and keeping issue notes

When changing devices, sign in to the panel on the new device, install the appropriate client, and import your subscription. Complete a round of checks before clearing the old device. There is no limit on the number of devices connected at the same time, so you do not need to remove a configuration that is still in use just to free up a slot. If you no longer manage the old device, sign out of the panel, remove your personal subscription from the client, and delete any local backups you created. If you think the device still has a copy of your subscription, check the panel's subscription maintenance options.

Keep maintenance notes to details you can check later: platform, network, active configuration name, route, and the last change made before the issue. A route that stopped working after an update and a regular connection that does not recover after disconnecting are separate issues; do not combine them into one vague report. Start with Support and look for the relevant account, connection, route, or billing topic. If you still need help, open a ticket with the checks you have already performed and the expected result, so troubleshooting does not have to start from installation again.

POLICY / DIAGNOSTICS

Split tunneling rules and advanced troubleshooting

First decide which traffic should stay on its regular path

Split tunneling selects a path for requests based on matching conditions. A typical setup sends services that need a particular exit through a selected route, while keeping local devices, internal work services, or everyday apps on their usual connection. Clients differ in the conditions they support, which may match by domain, address, or app. Do not assume that every rule works on every platform. Write down the destination and expected path first, then configure it using the options actually available in your client. For work networks, follow the access method specified by your administrator.

A webpage may request login, static assets, media, or API domains in addition to its main domain. The page loading only shows that some of these requests worked. If a page loads but an action fails, check the client's connection records and verify the matched path for each request in order. Do not add a broad set of unrelated domains to fix one API endpoint. First confirm that a specific exception is necessary and works before keeping it.

Test rule order instead of piling on rules

Before making changes, write down what you expect: the test site should use the selected route, local network devices should keep their usual access, and requests without a specific rule should follow the default. Check how your client handles rule priority. If it uses the first matching rule, a broad rule placed before a specific one can prevent the latter from applying. Change one rule at a time and send a new request to compare results. Existing long-lived connections may still be using the previous path; close the old session in the test app before checking a new connection.

For diagnosis, if the client offers modes with different coverage, you can temporarily switch modes on a device where you are allowed to do so, then restore the original setting. If the request works after switching, that only shows the issue is related to the original path or coverage; it does not mean broader traffic handling is the right permanent solution. Next, check whether the original mode failed to handle the app, the rule did not match, or the destination used an unexpected resolution path. Isolate one setting at a time before applying the same approach to other devices.

Use system checks to help identify the problem layer

On a Linux device with the relevant system tools installed, run the read-only commands below once on your regular network and again with the connection enabled. The first line shows the system's IPv4 default route; the second checks whether system name resolution can return an IPv4 address for the example domain. These commands do not submit subscription or account credentials, and the public example domain is not a subscription entry for this site. Their output may contain local network details, so keep it for your own reference.

ip -4 route show default
getent ahostsv4 example.com

An unchanged default route does not prove that an app proxy is inactive; a tunnel may use another routing table or handle traffic per app. Successful resolution does not prove the browser uses the same resolver, or that the destination service is reachable. Read command results alongside the client's connection records and the browser's exit check. If the system resolves names but the browser fails, check the browser's own settings. If the browser works but a terminal does not, first check whether the terminal app uses the expected proxy.

Roll back based on the first point of failure

If the regular network is down, restore network access first. If the regular network works but the configuration will not update, check the account, subscription format, and download result. If the configuration is updated but the client cannot connect, check system permissions and route selection. If the client connects but one app fails, check split tunneling, name resolution, and app-specific policies. If another device works on the same network, compare the devices' permissions and client modes. If the same device works on another network, note what differs between the two connections. This preserves more useful evidence than reinstalling, resetting the network, and switching routes all at once.

Before opening a ticket, reproduce the issue with as few steps as possible. Note the starting state, what you did, the first error message, whether the regular connection recovered after disconnecting, and the individual checks you have already tried. For a path you verified, record the test site, backup route, and rules that need to stay in place as a baseline for future device changes or updates. Return to the Guides to reinstall step by step, or see Global Nodes to compare available regions.

When troubleshooting, find the first step that does not match expectations. Change one thing at a time, confirm the result, then keep or undo the change.