VPNVJ User Guide

How smart split tunneling works and what the service covers

Understand accounts, subscriptions, and connections separately

VPNVJ is a subscription service for smart split tunneling and cross-border network acceleration. Your account manages plans, orders, and subscriptions. The subscription provides your client with available routes and related settings. The client is what establishes a connection on your device. Signing in doesn’t mean your device is connected to a route, and seeing a plan doesn’t mean the system proxy is enabled. Understand these layers first, and you’ll know whether to check your account, configuration, or device network when something goes wrong—instead of mistaking a connection issue for a payment failure and placing another order.

Smart split tunneling routes traffic based on its destination: domestic websites connect directly, while international sites use international routes. It doesn’t send every request through the same exit, nor does it guarantee the same result for every app on your device. The outcome depends on your current configuration, client mode, and whether an app uses the relevant network path. Even after a website loads in your browser, check desktop apps and command-line tools separately. One successful page doesn’t verify your entire device.

What route names mean and how to use them

VPNVJ covers 100+ countries and 170+ routes. Coverage describes the network exits available to choose from; it doesn’t guarantee that every destination service permits access from every region. First identify the exit region your task requires, then check the route type and notes in your client. Proximity can help narrow down your options, but distance alone doesn’t determine performance. Your local network, transit path, and the destination service’s response all play a part. The real test is whether your task works reliably.

In this guide, “direct” means a request doesn’t pass through a proxy exit; “transit” means it reaches the exit through an intermediate path; and IEPL identifies a route type. A route name isn’t a speed guarantee. “Domestic websites connect directly” also doesn’t mean every Chinese-language site must connect directly. Rules usually match conditions such as domain names, not the language of a page. For available regions and route types, see the route list. The options on your device depend on the latest subscription update.

Check what’s supported before setting up your devices

The service supports Windows / macOS / iOS / Android / Linux, with unlimited devices online at the same time. “Unlimited devices” means you can configure it on your own devices; it doesn’t give each device a separate plan allowance. When checking usage, consider the combined activity across devices on the same account. Large file syncs, video playback, and software updates can continue in the background. Before attributing a change in usage, check whether those tasks are using international routes.

VPNVJ’s core privacy commitment is no logs. To understand what that means, distinguish the route service from the destination website: websites still handle sign-ins, account activity, and regional eligibility under their own policies, and clients may show local connection details for troubleshooting. A change in network exit doesn’t change permissions on third-party accounts. Account security, device updates, and subscription-link handling each need attention. See the Privacy Policy for details.

Complete the full process on one device before setting up others. Keep one verified working route and a clear test destination as a baseline for troubleshooting later.

Before you start, have a browser that can reach the dashboard, confirm your device’s existing network works, and note which proxy tools are currently running. If other network-management software is installed, check whether it has enabled a system proxy or tunnel before deciding whether to pause it. Don’t let multiple tools change the same system setting at once. Next, choose a billing option, then set up your account and import your subscription. Following this order helps avoid redoing your setup because the plan doesn’t fit your needs.

Choose a plan that fits how you use it

Start by comparing monthly plans and data packages

Monthly plans suit ongoing use when you want a set monthly data allowance. VPNVJ offers monthly plans at ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on the day you activate the plan, so don’t assume it resets on the first of each calendar month. Before choosing, think about what you do online: text searches, video calls, developer downloads, and extended video streaming use data differently. Time spent online alone isn’t a reliable way to estimate your needs.

Data packages suit less regular use when you want to access the service as needed. Options are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They last until used and never expire. “Never expires” applies to the data package itself; it doesn’t mean you can keep using the service after the data runs out. Don’t assume a data package automatically adds to a monthly plan or guess how different products are applied at checkout. Before switching billing options, check the dashboard’s billing details or ask through a support ticket.

Choose based on your tasks, not the number of devices

Unlimited devices can be online at the same time, so adding another one of your own devices isn’t, by itself, a reason to upgrade. What matters is the combined data use across your devices and whether large downloads happen at once. Your computer might only occasionally access international sites while your tablet streams video continuously. The same number of devices can use very different amounts of data. When you start, choose a tier based on the tasks you already expect to do, then refine your estimate using actual usage in the dashboard. There’s no need to pay in advance for needs that haven’t come up.

When comparing a monthly plan with a data package, consider both your budget and how consistently you use the service. Monthly plans follow a clear reset schedule, while data packages keep any data you haven’t used. If you barely use the service for a while, a data package may be easier to manage. For regular use, focus on how much you use during the month and when the reset occurs. Don’t budget around unlisted rollover, carryover, or bonus-data rules. Benefits not promised on this page shouldn’t factor into your decision.

Understand upgrades, payments, and refunds

If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. It isn’t simply a fixed amount added to your existing order, and you shouldn’t assume all the original dates will stay the same. Before confirming an upgrade, review the calculation in the dashboard, especially the new tier, amount due, and benefit period. If the result doesn’t match your understanding, stop and ask for clarification rather than creating multiple orders to test how billing works. If you’ve already paid, check the actual order status.

Payment methods are Alipay / WeChat Pay / USDT. Choose a method you can use, then verify the order amount, currency, and instructions on the payment page. For USDT, follow the details shown for the current order; don’t reuse payment information from old screenshots or records. The service offers a 7-day no-questions-asked refund. See the Terms of Service for eligibility details. For a full comparison, visit the plans and pricing page rather than relying on outdated screenshots or descriptions on other pages.

Once you’ve chosen, note the product type and tier you intend to use before setting up your account. This note isn’t proof of an order; it’s there to help you check the billing details you see next. Payment status is confirmed by the order record. If you’re still unsure what you need, you can review the import and verification steps before choosing a plan. Reading this guide, learning about platform differences, and planning your connection doesn’t commit you to long-term use.

Set up your account and check your order

Save your account details, then open the dashboard

VPNVJ doesn’t require an email address; create an account with a username and password. Open the dashboard through the account setup page and enter a username and password as prompted. They serve different purposes: the username identifies your account, and the password verifies it. A quick setup is no reason to choose an easy-to-guess password, and you shouldn’t reuse a password from another important service. Before submitting, check your keyboard input mode so similar-looking characters aren’t entered incorrectly.

After creating your account, save your username and password in a password manager you trust. Since an email address isn’t required, don’t assume there’s an email-based account recovery option. Before leaving the page, confirm you can sign out and back in, then proceed with payment. On a shared device, don’t leave your browser signed in. Sign out of the dashboard when you’re done, and check for order screenshots or copied subscription details that may have been left behind.

Check the product before paying

Open the plans section in the dashboard and select the monthly plan or data package you chose in the previous section. Check the product type, price, included data, and billing terms in order. Don’t rely on the highlighted price alone: monthly plans and data packages work differently. The checkout details should match the public pricing. If they don’t, keep the page open and confirm through a support ticket rather than assuming the difference is a discount, bonus, or automatic upgrade.

Before paying, double-check the username you’re signed in with. When you use multiple browsers, devices, or accounts, it’s easy to choose the right plan but pay from the wrong account. An order belongs to the account that created it; whether a client shows routes doesn’t tell you where the payment went. Once you’ve confirmed the account, choose Alipay / WeChat Pay / USDT. The payment page may open in a new tab or another app. Note where you left off in the dashboard so you can return to the order afterward.

After paying, return to the dashboard and check the order status and account benefits. A charge shown by your payment app is one part of the payment process; check the order status to confirm that the account received the benefits. If the page hasn’t updated yet, reopen your order history first. Don’t repeatedly click the payment button or immediately place another identical order. Keep the order number, amount, and payment receipt. Sharing these details makes follow-up easier than simply saying, “I paid but it doesn’t work.”

Handle order issues separately from connection issues

If an order isn’t complete, resolve the order issue before changing client rules. If the order is complete and the plan appears normally but your device can’t reach a destination, the issue is more likely with subscription delivery or the connection. Check each step in order: order complete, benefits active, subscription available, client loaded, destination reachable. Stop at the first step that fails and troubleshoot there. Changing settings across multiple layers can hide what happened, making it hard to tell whether a configuration update or payment-status change fixed the issue.

If payment is interrupted or you cancel it, return to the dashboard and check whether the original order is still pending. Closing the browser doesn’t cancel an order, and opening the payment page doesn’t mean you’ve been charged. For USDT, compare the current order instructions with your transfer record; if the status is unclear, submit a support ticket. Don’t post a full payment page, subscription details, or account password in a public forum. Share only information relevant to the order, and hide unrelated personal details.

For help, use support tickets in the dashboard. Include the order linked to your username, its current status, and the steps you’ve already taken. Never share your password or full subscription link.

By the end of this section, you should know which account is signed in, which product you chose, whether the order is complete, and whether its benefits are showing. Confirm each point before getting your subscription. If you’re unsure whether you missed a step, check the main flow in the Quick Start Guide, but don’t pay again just to repeat the setup. The next section covers configuration delivery and won’t change an order you’ve already confirmed.

Get your subscription and check delivery

Software downloads and subscriptions are separate

The client is the software that runs your connection; the subscription is the account configuration it reads. You need both. Installing the software without importing a subscription usually leaves you with no usable routes. Copying a subscription without adding it to the right client won’t change your device’s network. Go to the client downloads section in the dashboard and select your platform, then follow the import method provided. The site doesn’t offer direct installer links on promotional pages, and you shouldn’t search for installers from unknown sources.

You can get the Windows, macOS, Android, and Linux clients by signing in; you don’t need a purchased plan. The dashboard determines whether you’re eligible for the iOS client. Getting a client and having usable routes are separate requirements: being able to download the software doesn’t mean your plan includes usable routes. You need to be signed in to get your subscription. If the dashboard shows an eligibility or account-benefit issue, resolve your account status before importing. Don’t try to bypass the dashboard’s checks by switching download sources.

Use the import method provided in the dashboard first

If the dashboard offers one-click import, first make sure the corresponding client is installed on your device, then select the import option. Your browser may ask to open an external app. Check the app name before confirming, then switch to the client and verify that the configuration was added. A message that the action started on the website doesn’t mean the client received it. If the app doesn’t open, check whether the browser blocked the external protocol. Then use the dashboard’s copy-subscription option instead of clicking repeatedly and creating duplicate configurations.

To import manually, look in the client for an option such as Subscriptions, Configurations, or Add from URL. Labels vary by platform, so follow the current interface. Paste the full link copied from the dashboard, check that the beginning, end, and query parameters are intact, then save and update. Don’t paste the link into a regular website search box or try to reconstruct it from a screenshot with line breaks. Line wrapping in an input field is only a display effect; extra spaces or actual line breaks in the link can break it.

A subscription URL contains account-related access credentials, so keep it confidential. Don’t post it in a public repository, online conversion tool, shared document, or group chat, and don’t include the full link in troubleshooting screenshots. To report an import issue, describe the error, the step where it occurred, and your client platform. If you think the link has been exposed, check whether the dashboard lets you reset it. After a reset, every device using the old link needs to fetch and update the subscription again.

Check the imported configuration to confirm it worked

After importing, check the configuration name and route list before connecting. A valid configuration should be selectable in the client and show the content retrieved from the subscription. If you see old routes or an empty list, make sure you haven’t selected an older configuration, then try updating manually. If the update fails, distinguish between an unreachable URL and a configuration parsing error: the former may involve your local network or subscription status; the latter calls for checking the import method and content format. Don’t mistake the dashboard’s web address for a subscription URL.

If you use the same account on multiple devices, import from the dashboard on each one rather than forwarding credential-bearing text from another device. Give the configuration a recognizable name so you can tell it apart from old services or test configurations. Don’t repeatedly delete and re-add the same subscription just to keep it “up to date”; regular updates usually preserve settings and make troubleshooting easier. If you do need to rebuild it, first note the selected route, mode, and any custom local rules so you don’t lose your troubleshooting baseline.

To confirm delivery, check that the client loaded the right configuration and routes—not just that the copy button reported success. It’s normal for the connection to be off at this point.

At the end of this section, you should have a clearly identified configuration and know how to update it manually. Next, follow the import and authorization steps for your platform. If the software is installed but the system blocks it from opening, address the specific system prompt; there’s no need to place another order. If you can’t get the subscription, return to the dashboard to check your account benefits and subscription options. Don’t substitute an unrelated configuration file. Keeping the software download, configuration delivery, and network authorization separate makes the next checks much clearer.

Import the client on each platform

Windows: verify the configuration before enabling traffic interception

Get the Windows client from the dashboard, follow the system’s installation prompts, and open it. Import the subscription from the previous section. Open the configuration list, select the VPNVJ configuration, update it, and confirm that routes appear. Then enable the system proxy or tunnel, depending on what the client supports. Don’t assume both options need to be enabled at once. For your first setup, choose a clear, verifiable path and keep the default rule mode. If the system requests extra permissions, read what they’re for before approving. Don’t run the client with elevated privileges indefinitely without checking why.

After enabling the connection, test a destination website in your browser. If the browser works but a game, office app, or terminal doesn’t, check whether that app uses the system proxy before changing your subscription. Before enabling startup on boot, test connecting and exiting manually, and confirm that your original network works again after you close the client. For a more detailed desktop setup sequence, see Windows: From Installation to Startup on Boot. For compatibility, see Desktop Split Tunneling and App Compatibility.

macOS: check system permissions and proxy status

Get the macOS client, install it using a method supported by your current system, and open it. If the system asks you to verify the app’s source, confirm that the file came from the dashboard before following the prompt. Don’t run commands from unknown sources to disable protections in bulk. Import and update your subscription, select a configuration and route, then grant the network permissions the client needs. If macOS asks to approve a network extension or VPN configuration, make sure the request matches what you’re doing. A running icon in the menu bar only means the app is open; it doesn’t verify that websites are reachable.

iOS: check eligibility in the dashboard and authorize the connection

Sign in to the dashboard and open the iOS client section, then follow the prompts. The dashboard checks subscription eligibility; don’t copy download links from other articles. After installation, return to the dashboard to import your subscription, then check the configuration in the client. When you connect, allow the system to add a VPN configuration if prompted. If the system requires local device authentication, follow your device’s authorization process. Test your browser and commonly used apps separately. The system status indicator means a tunnel is established; it doesn’t mean every request uses the same exit.

Android: check connection permissions and background restrictions

Get the Android client from the dashboard, install it as prompted by your device, then add and update your subscription. The first time you connect, the system may ask permission to establish a VPN connection. Confirm the request comes from the client you’re using, then continue. If browsing works in the foreground but stops when the app goes into the background, check whether your device restricts background activity or battery use for the client. Don’t set every app to unrestricted; change only the settings relevant to this connection. If another VPN app is installed, first check which one is currently controlling the network, then switch as needed.

Linux: distinguish desktop proxy settings from terminal environments

Select the Linux client in the dashboard and install it according to the instructions for your system and the software. Import and update your subscription, select a route, then check how the client handles network traffic. Desktop proxy settings and proxy environments for terminal processes are separate layers: a browser can work while terminal traffic still connects directly. Don’t copy a proxy port from another guide; check the client’s current listening settings. If a program runs in a container, remote environment, or other isolated environment, the local address it sees may differ from the desktop host’s.

On every platform, import the subscription, select a route, authorize network access, and connect before setting up automatic startup or background operation. If a button is named differently from this guide, follow its function and the current client documentation. Don’t install software from another source just to find a button with the same name. You can use the same account on multiple devices, but each device still needs its own system permissions, network mode, and background settings. One device being connected doesn’t mean another is set up.

Connect to a route and verify the actual exit

Start with a consistent test setup

Select a route from your subscription, enable rule mode, and choose a specific international destination to test. Before testing, make sure your local network can still reach websites that normally work. This prevents a disconnected Wi-Fi network or local broadband issue from being mistaken for a route problem. Keep the test destination, app, and local network the same while comparing results before and after connecting. If you change networks, apps, and exits at the same time, you won’t know what made a difference, and the same issue may come back.

Once connected, make sure you can complete a real task on the international destination, not just open its homepage. A sign-in page, document, resource download, or persistent session may use different domains and connections. Browser cache can also make an old page appear to work; reload the destination content if needed. Keep a note of the client’s current mode and selected route while testing. If an error occurs, record its exact wording. Don’t conflate regional restrictions, account permissions, site security checks, and network connection failures.

Check the exit, rules, and app together

Before checking an exit IP, consider the split-tunneling rules. An IP lookup page may match a direct-connection rule and show your local network’s exit; that doesn’t prove the international route has failed. Conversely, seeing an international exit on the lookup page doesn’t prove every app uses the proxy. For a clearer picture, check which rule matched the destination domain, which exit was used, and whether the task worked. If the client shows connection details, use them to inspect the destination request. Hide sensitive information before sharing a screenshot.

DNS checks help you determine whether domain resolution behaves as expected; don’t infer a leak just from the region where a DNS resolver is located. A browser’s encrypted DNS, the system’s DNS cache, and the client’s DNS strategy can all affect the result. First identify the app’s DNS path, then check whether it matches the rules you expect. If you’re not sure what’s causing the issue, don’t change system DNS and client rules at the same time. Save the original settings and test one change at a time. For a full walkthrough, see How to Check Your Exit IP, DNS, and Per-App Connections.

Troubleshoot based on symptoms, not guesswork or reinstalls

If no websites load, first disable the client’s traffic interception and check whether your local network works again. If it does, focus on the current mode, leftover system proxy settings, or conflicts with other tools. If the problem remains after disconnecting, troubleshoot your local network first. If only international destinations fail while domestic websites work, check whether the subscription is up to date, whether the selected route suits the destination, and whether the service shows an account or region message. Don’t delete the configuration before recording what’s happening.

If your browser works but an app doesn’t, check whether the app has its own proxy settings and whether it needs restarting to pick up the new network environment. Developer tools may have separate UI processes, background services, and terminal subprocesses, each with different settings. If a persistent connection drops, test whether the same task stays stable on other candidate routes rather than checking only whether the homepage opens. For AI coding workflows, see Choosing Routes for Cursor, Copilot, and Command-Line Tools.

If streaming playback fails, start with the error from the service, then check account region, content rights, and your current exit. A route covering a country doesn’t mean every title on a service is available there; being able to open a website doesn’t guarantee the playback connection will work. Choose a candidate exit based on the client’s route details and compare results on the same content. For more on streaming scenarios, see the Streaming page. Don’t assume a region name guarantees ongoing access to a particular catalog.

A connection is verified when the configuration is loaded, the destination matches the expected rule, the real task works, and your local network recovers after you turn off traffic interception. The system icon is only one signal.

After verification, note the task, selected route, and current mode; there’s no need to save sensitive links. If something breaks later, restore these known conditions before comparing. This helps you distinguish a temporary route change from a setting changed by other software, and makes support tickets more useful. If you can’t identify the cause, provide your platform, symptoms, exact error, and checks you’ve already done. Don’t upload the entire configuration file publicly.

Maintain your subscription, data, and renewal status

Keep subscription updates separate from software updates

A subscription update fetches the current configuration and routes; a client update changes or fixes the software itself. An unchanged route list doesn’t necessarily mean your software is out of date, and a client that opens normally doesn’t mean its subscription is current. For routine use, first check that the active configuration belongs to the right account, then update the subscription using the client’s controls. If the update fails, keep the existing working configuration, note the error, and check the dashboard status. There’s no need to clear everything immediately. Deleting the configuration can also erase your baseline for comparison.

Get the latest client through the dashboard, not from pop-up ads or search results with similar names. Before updating, note the selected route, traffic-interception method, and any essential local rules, and make sure you can retrieve the subscription again. After updating, check that the client starts, loads the configuration, gets network permission, and restores your connection when it exits. Then set up automatic startup again. If the system asks for permissions, follow the current prompt. Don’t assume an account problem just because an older version didn’t ask you to confirm.

Check usage and reset dates

Monthly plan data resets each month on your activation date. When checking the dashboard, verify both your remaining data and current plan status. Don’t assume you have enough data just because the reset date hasn’t arrived, or that your plan is still active just because data remains. Data packages last until used and never expire, so check the remaining balance. Each billing option follows its own rules: don’t apply a monthly plan’s reset schedule to a data package or assume unused monthly data automatically converts to a data package.

If usage differs from what you expect, first check activity on other devices using the same account. Cloud syncs, app updates, autoplay, and repeated large downloads can all affect usage, even when you’re not watching the relevant window. Unlimited devices means troubleshooting needs to include your other devices, too. Pause known high-usage tasks and then check the dashboard. If usage totals take time to update, follow the dashboard’s guidance. Don’t treat a brief display difference as proof of incorrect billing.

Check the order again before renewing or upgrading

When you want to keep using the service, check your current product and checkout details in the plans section of the dashboard. Don’t assume a renewal will preserve all existing dates, automatically carry over every benefit, or apply a data package in a particular order. Follow the actual checkout details. If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days; check how the dates change before submitting. If you don’t understand the calculation, ask first and pay afterward. Even if your connection works, billing questions should be resolved at the order level.

After payment, check the order and account benefits, then return to the client and update your subscription. If the client still shows old details, check the active account and configuration instead of placing another order. If the dashboard shows the right benefits but your connection doesn’t work, follow the connection verification section. Don’t base long-term plans on unpublished annual prices or discounts. VPNVJ’s published monthly plan and data package terms are listed; for help assessing long-term use, see Long-Term Subscriptions and Service Sustainability.

Manage device sign-out and sensitive information

Before retiring or handing off a device, disconnect, remove the local subscription configuration, sign out of the dashboard, and check whether sensitive content remains in your browser or clipboard. Uninstalling the client may not clear your browser session, and signing out of the website may not remove a configuration already saved in the client. If a device is lost or a subscription may have been exposed, check the dashboard for password and subscription management options, and submit a support ticket if needed. Changing your account password and resetting your subscription are separate actions; don’t assume one automatically does the other.

To request a refund or dispute an order, use a dashboard support ticket and explain the product, order status, and what you’re requesting. The service offers a 7-day no-questions-asked refund. See the Terms of Service for the rules; don’t assume there are additional bonus, extension, or repeat-refund conditions. Keep only the order records you need, and never send support your password. The goal of routine maintenance is to keep your account, configuration, and device status easy to understand—not to reinstall frequently. Knowing what worked last time is usually more helpful than collecting piles of screenshots.

Advanced split tunneling and app troubleshooting

When to use rule mode and global mode

Start with smart split tunneling for everyday use: domestic websites connect directly, while international destinations use the exit selected by your configuration. If your client offers global mode, you can temporarily use it to compare how the same app behaves while troubleshooting. It isn’t a universal fix. Global mode may reroute requests that should connect directly, and can affect data use and access to local services. When testing is done, switch back to the original mode and confirm that domestic websites and the destination app behave as expected. Don’t leave a temporary troubleshooting setting enabled.

Before adding custom rules, check which match conditions your client supports, the rule order, and how changes are saved. Broader rules may take priority over narrower ones, so adding a domain doesn’t guarantee the rule will be applied. First identify the domain used by the actual request, then decide whether a rule change is needed. Sign-in pages, static resources, and APIs may use different domains. Change only settings that serve a clear purpose, and record their original values. Don’t route all traffic associated with an app through one route just for convenience.

Set up the right proxy environment for command-line tools

Command-line tools may read proxy environment variables or use their own configuration files. Before troubleshooting, check whether the current shell already has old proxy settings. The command below only checks common variables on your device. It doesn’t set a port or mean VPNVJ requires any particular proxy protocol. Variable values may contain internal addresses or authentication details, so use the output for your own reference and don’t paste it into a public support attachment. No output means only that these variables aren’t set; it doesn’t prove all traffic connects directly.

printenv | grep -iE '^(http_proxy|https_proxy|all_proxy|no_proxy)='

If you need to configure a proxy for terminal tools, check the protocol, listening address, and port in your current client, then follow the documentation for the tool in question. Environment variables are inherited by processes at startup; terminals, editors, and background services that are already running may not pick up new values automatically. Restart the relevant processes and test again. Restarting only the graphical interface may leave old background processes running. Don’t use a loopback address from another device: it points to the environment running the program, not necessarily your desktop computer.

Distinguish the listener, route, and destination response

Containers, virtual environments, and remote development add more network layers. A client connected on the host doesn’t mean an isolated environment inherits the same proxy. First confirm where the program is running, then check whether it can reach the expected listening address. Don’t expose your local proxy to the entire network just to make a connection work. If you need access from another device, first understand access controls, binding scope, and the network those devices are on. This guide doesn’t provide a one-size-fits-all open configuration without knowing the environment; the same command can expose different things in different setups.

For AI tools, remote work, and long streaming sessions, test with real tasks and check whether the connection stays stable. Loading a webpage briefly only verifies that request; it doesn’t predict how a persistent session will perform. Keep the task and local network consistent when comparing routes, and note the error returned by the destination service. Authentication failures, request limits, regional eligibility, and dropped connections are different issues. If an old session persists after switching routes, reconnect before testing again. Don’t make frequent route switching part of your routine; consistent test conditions are more useful.

Keep a record of changes you can roll back

Make one change at a time to address a specific issue. Note what you changed, what result you expect, and how to revert it. Subscription updates may overwrite some manual changes, so use the client’s supported local overrides or rule-management features where possible. If you’re unsure whether a change persists, check the relevant documentation first. Don’t keep a manually edited copy of the full subscription as a separate configuration. It can drift out of sync with route updates and account status, and may spread sensitive credentials into backups or collaboration tools.

That completes the full process: choose a billing option, confirm your account and order, get your subscription, authorize and connect on your device, verify with a real task, then maintain your configuration and account benefits. If anything changes, return to the relevant section. Still have questions? Start a support request through the Contact Us page. Include your platform, current mode, symptoms, and comparison tests you’ve already run. Keeping the issue reproducible and clearly explained is more effective than piling on more settings.