How the Service Works and the Scope of Cross-Border Connections
Start by distinguishing your account, plan, subscription, and client
VPNFresh is a subscription service for cross-border network access, with 100+ countries and 180+ routes. It supports Windows, macOS, iOS, Android, and Linux. Using the service involves several parts: your account gives you access to the dashboard and order management; your plan determines your current benefits; your subscription delivers route settings to a client; and the client establishes the connection on your device. Keeping these concepts separate makes it easier to tell whether an issue involves your account, configuration, or device—without repeatedly switching routes.
Installing a client does not mean your subscription has been imported. Seeing a subscription in the client does not mean your plan is active. And a connected status does not confirm that the app you want to use is actually going through the selected exit. The full process is to check your plan, import the configuration, enable the appropriate traffic routing mode, then test the destination. Each step can be verified on its own. If an earlier step is incomplete, trying to fix it with a later step will not help. For example, if your plan is unavailable, check the dashboard instead of reinstalling the client repeatedly.
Understand the path your data takes
A typical connection involves your device, its current network, the selected route, and the destination website. Browser requests enter the proxy path only when they meet the client’s routing conditions. System proxy settings, an app’s own proxy settings, virtual network interfaces, and routing rules can all affect the actual path. That is why a browser may work on the same device while another app cannot connect. It does not necessarily mean the entire route is down: the app may not use the system proxy, or the destination domain may be routed through a different exit.
Route coverage describes the range of regions available to choose from; it does not mean every destination service will offer the same content. Streaming catalogs, AI tool account eligibility, website regional policies, and local network conditions depend on different factors. A connection can improve your access path, but it cannot replace a valid account, content entitlement, or compliance with a platform’s regional rules. If you see a region-related message, check the exit, destination account, and platform guidance together. Do not infer the result from a route name alone or treat one successful visit as a permanent guarantee.
Judge your connection by observable results
This guide breaks a successful connection into several checks: the configuration is usable, the tunnel is established, the exit matches expectations, and the destination app works. A usable configuration means the client can parse the subscription and show routes. An established tunnel means the selected traffic-routing mode is active. Check the exit with an IP lookup. Finally, verify the destination app by loading a page or completing a request. These checks are more reliable than relying on a status icon alone, and help prevent account issues on a website from being mistaken for network problems.
Before connecting, make sure the device is yours to manage and understand the rules for your network and the destination service. Work devices may be subject to organizational policies, while other security software may restrict proxies or virtual interfaces. Do not disable all security protections just to get a connection working. Note your existing settings and use permitted configuration options. If administrator access is requested, make sure the prompt comes from the client you are using. VPNFresh uses “military-grade encryption” as a security assurance, but device permissions, subscription access, and account passwords still need to be managed separately.
Choosing Between Monthly Plans and Data Packs
Choose a billing option based on how you use the service
A monthly plan suits ongoing use when you are comfortable managing data month by month. A data pack suits less predictable usage when you want to keep unused data for later. Start by asking whether your use is continuous, then consider your data needs—not just the price. Video, file syncing, and everyday browsing consume data differently, so the same amount of time online will not necessarily use the same amount of data. If you have no usage history, monitor the dashboard after you start and adjust based on actual consumption rather than guessing at your long-term needs.
Monthly plan data resets each month on the day you activated the plan; it does not simply follow the calendar month. After activation, check the expiration details and usage history in your dashboard, and verify the reset cycle separately from the service’s active status. When you upgrade mid-cycle, the price difference is converted into remaining days. The order confirmation page shows the actual calculation. Do not assume an upgrade immediately adds a specific amount of data, or that the remaining-day calculation is a fixed-percentage refund. Review the change details in the dashboard before upgrading or renewing.
| Type | Price | Data | Usage period |
|---|---|---|---|
| Monthly plan | ¥9.9 / month | 60GB | Resets monthly on your activation date |
| Monthly plan | ¥18 / month | 250GB | Resets monthly on your activation date |
| Monthly plan | ¥28 / month | 500GB | Resets monthly on your activation date |
| Data pack | ¥158 | 300GB | Use until depleted; never expires |
| Data pack | ¥358 | 1000GB | Use until depleted; never expires |
| Data pack | ¥658 | 3000GB | Use until depleted; never expires |
Data allowance and device count are separate
Unlimited simultaneous devices removes the limit on how many devices can be used at once; it does not give each device a separate data allowance. Check the usage figures in your account dashboard to understand consumption. Cloud syncing on a computer, video streaming on a tablet, and background tasks on other devices can all generate network traffic at the same time. With multiple devices, pay particular attention to apps running continuously. Pausing unnecessary sync tasks can help identify where data is going more effectively than switching routes repeatedly.
Data packs remain available until used and never expire. This does not imply periodic resets, unlimited data, or any other additional benefit. If you already have a monthly plan and are considering a data pack, check the current orders and change rules in your dashboard first. Do not assume different products can be combined or infer the order in which data will be deducted. If the confirmation page does not explain how the change affects your existing plan, ask support through a ticket before proceeding. A clear answer can help prevent duplicate orders and unintended changes.
Check payments and refunds separately
VPNFresh accepts Alipay, WeChat Pay, and USDT, and offers a 60-day money-back guarantee. Choose a payment method on the order checkout page and verify the amount and currency against your current order. Do not assume payment details forwarded by someone else are an official way to pay for this service. Read the full eligibility details in the refund policy, and review the terms of service before proceeding. If you need a refund, keep your order details and explain your request in a dashboard ticket. There is no need to share your subscription or account password.
Choose based on what you need: ongoing work may call for easier cycle management, multi-device use makes total consumption more important, and occasional access may make it more useful to preserve unused data. No tier is right for every situation. See available benefits and checkout options on the plans page. For more on balancing price and service, read How to Choose a VPN on a Budget. This guide explains how to make a choice; it does not describe any tier as faster or its routes as better without supporting measurements.
Account Setup and Order Confirmation
Create an account you can manage over time
VPNFresh does not require an email address; create an account with a username and password. Open the account setup page, first checking that the browser address belongs to the current site, then follow the on-screen instructions. Choose a username you can recognize, and store your password separately from those for other sites. A quick signup process is no reason to treat your credentials as disposable: your plan, orders, and subscription will all be managed through this account, so keeping your login details safe is the starting point for long-term use.
Before submitting, check your keyboard input, leading or trailing spaces, and anything filled in by your password manager. If the page says your username is unavailable, follow the prompt to choose another rather than submitting the same form repeatedly. After creating your account, confirm you can access the dashboard and save your login details. Since an email address is not required, do not assume there is an email recovery process. If you forget your credentials, use the recovery options shown in the dashboard. Do not trust strangers who claim they can restore your account, and never share an unredacted screenshot that exposes your subscription.
Check your order before paying
Open the plans section in your dashboard and choose the product that matches your needs from the previous chapter. On the confirmation page, check the product type, amount, data allowance, and what the selected action means. Pay particular attention to whether you are starting a plan, renewing, or changing an existing plan. Monthly plans and data packs follow different rules; similar prices do not make them the same product. If the details do not match your expectations, go back and review your selection. Do not assume you can fix it after paying. Resolve any order questions before proceeding to the payment method.
Choose the appropriate payment method from Alipay, WeChat Pay, or USDT, then follow the checkout instructions. For on-chain payments, verify the network, asset, and recipient details against the current checkout page. Do not copy them from an old record or chat. A completed status from the payment provider only confirms the payment step; return to the dashboard to check the order status. A payment screenshot alone does not prove your account benefits are active, and you should not pay again just because the page has not updated yet.
Handling pending or interrupted orders
If an order is still pending after payment, first check whether your browser is showing an old page, then review the order history in your dashboard. Keep the order ID and payment result for support to verify. If payment was interrupted, confirm whether the original order has been paid, closed, or can still be completed before deciding what to do next. Creating another order may make the records harder to follow; paying again can turn a status check into an extra billing issue. Do not make a new order your default troubleshooting step.
If you need help from a person, open a support ticket in your dashboard. Describe which step caused the issue, the order status, and the checks you have already tried. You can provide a redacted payment receipt, but do not send your password, full subscription URL, or unrelated account information. Find contact options and guidance on the Contact Us page. This page does not provide an external contact address; use the support options in your account dashboard.
Check your plan status before downloading
After confirming your order, return to the dashboard overview and check that your plan appears, its data is visible, and its active status matches your expectations. If the order is complete but the overview has not updated, report the discrepancy in a support ticket instead of deleting your account or placing another order. Download access and subscription benefits are separate: supported platforms other than iOS can access the client after signing in; downloading on iOS requires an active plan. Being able to download a client does not replace checking your plan status before connecting.
Getting and Protecting Your Subscription
Treat your subscription as a connection credential
After signing in to your dashboard, get your current subscription from the account overview or subscription section. The exact menu name depends on what the dashboard currently displays. A subscription typically contains route addresses, connection parameters, and settings needed for routing; the client reads it to create a list of routes. It is different from your login password, but it should also be kept private. Do not post the full URL in public documents, screenshots, group chats, or online troubleshooting tools. Avoid sharing it with conversion sites that do not clearly explain how they will use it.
For the smoothest import, use the option provided in your dashboard that matches your current client. When you choose quick import, your browser may ask whether to open an external app; this is how it hands the link to an installed client. Check that the app name is the one you expect before continuing. If the system says no app can handle the link, install the client first rather than repeatedly opening the subscription in your browser. Manual and quick imports are simply different ways to transfer configuration; neither replaces checking that your plan is active and the configuration format is supported.
For manual imports, check the content and format
When copying manually, use the copy function in your dashboard instead of selecting visible text line by line. Before pasting, check that the content does not include extra instructions added by a chat app, extra spaces, or missing characters at either end. Some clients offer separate options for remote subscriptions and local files. Enter a subscription URL in the remote configuration field, not a route server address field or login form. If import fails with a parsing error, check the import type first, then consider network or account issues. Do not edit parameters in the URL.
https://example.com/sub?token=YOUR_TOKEN
The example above is for formatting only and cannot be used to connect. Only copy the content you obtain after signing in to your own dashboard. Subscription parameters identify the corresponding configuration; editing or truncating them, or combining content from different accounts, may make requests fail. If the client asks for a configuration name, choose an easy-to-recognize local label. It only identifies the configuration on your device; it does not change your account benefits or turn the subscription into a different plan. After saving, check that the configuration appears in the list and is selected.
Know the difference between updating and reimporting
Updating a subscription refreshes the content of an existing remote configuration; reimporting may create another configuration in the client. When the route list needs refreshing, use the update option for the existing configuration first. Remove and reimport only if the original source is wrong, the format is incompatible, or it cannot be repaired. Repeated imports can create multiple configurations with similar names, making it easy to think an update succeeded while the client is still using an old one. When troubleshooting, check both which configuration is selected and where the route being tested came from.
A failed update does not immediately mean the entire service is unavailable. Check separately whether the dashboard loads, your account benefits are active, the subscription URL is complete, and the client can reach its source. An existing proxy configuration may sometimes interfere with fetching a new one. After noting the current state, pause traffic routing and try the update again. Do not switch through multiple network modes without recording what you changed; if it starts working, you will not know which change fixed it.
Moving devices and responding to a suspected leak
To move to a new device, sign in to your dashboard there and get the subscription again. Do not send old screenshots through public channels. Before exporting a client configuration, check whether the file includes connection credentials. If you only need to share troubleshooting details, provide the error type and what the interface shows instead of the full configuration. If you suspect your subscription has been exposed, check whether the dashboard offers a reset option and note that the old device may need an update afterward. If there is no reset option or you are unsure what it affects, ask support through a ticket. Do not assume that changing your login password also invalidates an old subscription.
Importing on Each Platform
Get all client downloads from the downloads section in your account dashboard. Supported platforms other than iOS can access the client after signing in; downloading on iOS requires an active plan. Get your subscription after signing in. This chapter covers platform permissions and configuration checks without assuming that menu names are always the same. If you see a menu called “Subscription,” “Configuration,” or “Import,” use the on-screen instructions to identify the right option instead of relying only on its position.
Windows: Confirm the Import Before Enabling Traffic Routing
Select the Windows client in your dashboard, download it for your device, and follow the installation steps. When you open the client, handle any standard system prompt about running the app, then go to its subscription or configuration section. For quick import from the dashboard, confirm that the browser hands the link to the installed client. For manual import, add a remote subscription, paste the URL, and save it. Once the configuration has updated, you should see a list of routes. If the configuration is empty, check the subscription fetch before repeatedly enabling the system proxy.
Select a route, then enable the system proxy or another traffic-routing mode as described by the client. Virtual interface features may need additional permissions; consider using them only when an app that ignores the system proxy needs to be routed. If you have used another proxy tool, turn off its traffic routing first to prevent multiple apps from rewriting the system proxy settings. Before closing the client, check that it restores the system settings. If regular web browsing stops working after you quit, first check whether the system proxy still points to a local process that is no longer running.
macOS: Treat Installation and Network Permissions Separately
Get the macOS client from your dashboard, place the app as instructed, and then launch it. Prompts about the app’s source, network extensions, and proxy settings involve different permissions; read each one before proceeding. Do not lower the security settings for your entire device just because a permission prompt appears. If macOS blocks the app, first check the download source and installation instructions. On a managed work device, confirm whether network extensions are permitted. Repeatedly moving the app or renaming its file will not resolve an organizational restriction.
Import and update your subscription in the client, select a configuration and route, then enable the traffic-routing mode you need. Different macOS network services may retain different proxy settings, so recheck access to your destination after switching from Wi-Fi to another connection. If a browser works but a terminal or desktop app does not, do not assume the route is down. Check whether the app uses the system proxy or has separate proxy settings. For a quick walkthrough, see the macOS getting started guide.
iOS: Confirm the Configuration Request Comes from Your Current Action
First confirm in your dashboard that your plan is active, then open the iOS download option and follow the on-page instructions to get the client. After installing it, return to the dashboard to import your subscription. If the system asks to open the client, check that it is the app you intended to use. The first connection may ask for permission to add a VPN configuration; approve it only when you initiated the connection. This permission lets the system route network connections through the client. It does not give a web page arbitrary permissions, so do not accept a similar prompt from an unfamiliar site.
After importing, confirm that the configuration is selected, choose a region, and connect. A connection indicator in the status bar is only an initial sign; still check the exit and destination app. If access stops working after you switch networks, try disconnecting and reconnecting, then check whether the configuration is still active. Do not immediately delete all your system network settings. For a step-by-step walkthrough, see the Complete Beginner’s Guide to VPN on iOS, and work through installation, import, authorization, and verification separately.
Android: Check Background Activity and Battery Settings
Sign in to your dashboard to get the Android client, install it as prompted by your device, then import the subscription, update the configuration, and select a route. When Android first requests VPN permission, confirm that the prompt comes from the client you are using. If another app is already using the system VPN connection, check for conflicts first. Do not let multiple traffic-routing tools compete for the connection. Confirming the installation source, importing the subscription, and granting VPN permission are separate steps; installing the app does not automatically complete the configuration.
If the connection drops when your screen locks and returns when you reopen the app, check background activity and battery settings. Allow necessary background activity using the options available on your device, while keeping an eye on battery use. For per-app proxy settings, check whether selected apps are routed through the proxy or excluded; clients may describe this differently. For more detail, see Android Background Operation and Per-App Proxy Settings. Do not enable every app permission indiscriminately just to troubleshoot.
Linux: Check Desktop Apps and Terminal Environments Separately
Get the Linux client for your device environment from the dashboard and follow its installation instructions. Do not paste a subscription URL into a terminal as an executable command, and do not run installation scripts from unknown sources. After importing the subscription and selecting a route, test a desktop browser first. Desktop system proxy settings may not automatically apply to terminal programs. If a command-line tool needs a proxy, follow its documentation and use the local listener details shown by your client. Do not guess the port or copy someone else’s settings.
Before changing virtual interfaces, routes, or DNS settings, note the original state and how to restore it after stopping the client. On shared devices, do not let other accounts read subscription files. Set up background operation or launch at startup only after the basic connection works, so an incorrect configuration does not take effect on every startup. When moving between platforms, the same account does not guarantee that configuration files are compatible. Choose the matching import option in your dashboard rather than copying an application folder from another operating system.
| Platform | Check after importing | Common limitations |
|---|---|---|
| Windows | Configuration selection and system proxy status | Another proxy app may change system settings |
| macOS | Network permissions and current network service | App may not use the system proxy |
| iOS | Configuration permission and destination access | Active plan required for the download option |
| Android | Background activity and per-app scope | Battery settings may pause the connection |
| Linux | Test desktop and terminal separately | Proxy settings may not carry over to processes |
Connection Checks and Route Selection
Verify everything from the configuration to the app you need
After importing, check that the current configuration is enabled, routes are available to select, and the client is not reporting a parsing or authentication error. Once these basics are working, enable the connection. If the configuration itself is unusable, turning on the system proxy will only send requests to a local app that cannot handle them. Refreshing web pages at this point may make the issue appear worse. Go back and check the subscription and account benefits instead. Working through configuration, connection, and app checks in order makes each result easier to interpret.
Before and after connecting, use the IP check on this site to compare your current exit, and check the selected route in your client. The result shows the exit used by that browser request; it does not mean every app on your device follows the same path. If the check temporarily fails, do not assume the connection is down based on a tool error alone. Check the destination website and client status too. Once the exit region matches your expectations, open the app you actually need and test the relevant task—such as loading a page, accessing your account, or playing content.
Choose a region for your needs, not just its distance
For everyday browsing, try a nearby region that suits your needs. If a destination service has regional requirements, start by checking its rules. Physical distance is only one factor affecting a connection; your local network, transit path, exit status, and destination website can also make a difference. Do not assume a particular region will be faster for everyone, or treat a label in a route name as proof of current performance. See the routes page for the available list and selection guidance. The dashboard and client show what is currently available.
When comparing routes, keep your device, network, task, and client mode as consistent as possible; change only the selected route. A page’s first load may be affected by caching, and a video may play already-cached content. Observe several consecutive actions instead of judging by the first page load. A client’s latency check mainly reflects that particular test; it does not equal download speed or video stability. A more useful measure is whether the task keeps working, how often it gets interrupted, and whether the same issue consistently returns after switching routes.
Troubleshoot by symptom
If no websites load, pause traffic routing and check your basic network connection. If the network works, check your plan status, configuration update, and selected route. If the network itself is down, address the local connection first. If only one website fails, check the destination service, account region, app cache, and routing path. If a browser works but a desktop app fails, check that app’s proxy settings first. If the connection fails only when the screen locks, check background restrictions. The same “site won’t load” symptom can have very different causes.
If a page displays text but images, sign-in, or playback fail, different domains may be taking different routes. Note which action fails, check whether the client shows the related connection, and then decide whether to adjust a rule. Do not start by clearing all browser data; that also removes your sign-in state and changes the test conditions. You can compare in a separate browsing session if needed, while still accounting for the destination platform’s account and regional rules. Do not generalize one test result to all content.
Keep reproducible details for support
A useful troubleshooting report includes your platform, current client mode, network, selected region, intended task, and error message. Recording what changed after switching routes or pausing traffic routing is more helpful than saying only “it’s slow.” If logs contain subscription URLs, account identifiers, or request parameters, redact them first. For more route selection tips, read How to Choose a Route by Region, Type, and Use. For streaming, see Disney+ Regional Catalogs and Streaming Stability.
Data, Renewals, and Routine Maintenance
Use dashboard records as your starting point
Once your connection is stable, routine maintenance should focus on account benefits, data usage, and configuration updates—not reinstalling the client every day. Check your current plan, remaining data, and active status in the dashboard regularly to make sure they match your usage. Monthly plan data resets each month on your activation date; data packs last until used and never expire. These products do not follow the same usage cycle. If data usage changes, first check the time period and product type, then review what your devices were doing. Local client statistics may not match account billing figures, so do not assume a billing error based on one app’s numbers.
Unlimited simultaneous devices means you need to consider the usage of every device in use. Cloud storage syncing, system updates, video buffering, game downloads, and browser tabs running in the background can all transfer data. To troubleshoot, pause nonessential tasks and see whether usage stops. If it happens only when a particular device is on, check that device’s apps rather than deleting the entire subscription. Local usage figures in a client and cumulative dashboard records may cover different periods or traffic; do not subtract them from each other without confirming what each includes.
Check the product and order details before renewing
To renew, open the plans section in your dashboard, confirm whether you currently have a monthly plan or data pack, and read the confirmation page’s explanation of your existing benefits. Do not treat “renew,” “upgrade,” and “choose a different product” as the same action. When you upgrade mid-cycle, the price difference is converted into remaining days; the dashboard checkout details show the final result. If the page does not explain how remaining data, active status, or another product will be handled, ask support through a ticket. Do not infer VPNFresh’s rules from common industry practices.
After payment, check the order status and account overview again to confirm the change appears in your dashboard. Data or status shown in the client may come from previously fetched subscription information. Update the existing subscription if needed, but do not use a repeated import as a substitute for checking your benefits. If the dashboard has updated but the client still shows old information, note both statuses separately. If the dashboard has not confirmed the change, resolve the order issue first. Distinguishing a display delay from an account benefit issue helps keep billing problems from being misdiagnosed as network settings.
Client Updates and Configuration Backups
Update the client using the download option in your dashboard. Before updating, note the working configuration, traffic-routing mode, and any local rules you need to keep. Do not download installers with similar names from search results. Updating the client and updating the subscription are different: the former changes the software on your device; the latter refreshes the service configuration. If a problem appears after a software update, first check whether permissions, system proxy settings, or the selected configuration changed. Do not assume every route has stopped working. If you need to import again, get a fresh subscription from your own dashboard.
Treat local backups as sensitive configuration files; storing them on your device does not remove the need to restrict access. When backing up custom rules, keep them separate from the remote subscription when possible, and note what they do and how to remove them. Before syncing across devices, check whether the subscription credentials will be uploaded too. Before handing over, repairing, or retiring a device, sign out and remove related configurations. If you are unsure whether someone else may have accessed your subscription, check how to reset it in the dashboard or ask support through a ticket. Deleting a desktop shortcut is not enough.
Keep a short change log
Keep a brief note for a stable configuration: platform, traffic-routing mode, commonly used regions, and any essential local rules. Do not include passwords or full subscription URLs. When something breaks, check whether you recently changed networks, updated the operating system, adjusted routing, or installed other network software. Start with the most recent change. A previously reliable setup can also be affected by changes to the local network or destination service. The goal of maintenance is to reduce unknowns, not to keep adding rules until the setup becomes difficult to understand.
Routing, DNS, and Advanced Troubleshooting
Understand what your settings route before adding rules
Advanced setup is not about turning on more switches; start by identifying which requests need to go through the proxy. A system proxy usually depends on apps choosing to use the system settings. A virtual network interface can cover more traffic, but also affects routing, permissions, and DNS behavior. Available features depend on the current client; similarly named options do not necessarily work the same way on every platform. Verify a basic connection first, then try advanced settings one at a time. This makes it easier to return to a known working state if something goes wrong.
Rule-based modes select a path based on conditions such as domain, address, or app, and can help you manage different use cases separately. Global routing is usually best for temporarily checking whether a rule is affecting a destination, not as a universal fix. Before using it, check which processes and protocols the client actually includes under “global.” A browser working through the system proxy does not mean terminal programs are routed too. After changing modes, verify the exit and destination task instead of relying on the button’s new state.
Understand how DNS resolution relates to the connection path
DNS resolution turns a website name into an address needed for a connection. A proxy chooses the path a request takes. The two are related but not the same. Browsers, operating systems, and clients may each have their own DNS cache or secure DNS settings, so changing routes may not immediately produce identical results. When troubleshooting, first check the current client documentation and DNS mode, then see whether the app has its own settings. Do not paste public DNS addresses found online into every field without checking what they do; that may introduce more differences in the request path.
If you need to check DNS resolution, identify what made the query, which interface it used, and which app used the result. A successful one-off lookup only shows that a result was returned for that query. It does not prove that the subsequent connection went through the proxy or fully describe how every app on your device resolves names. If some resources on a destination domain fail, check the path in the client’s connection log. Clear the relevant app cache and test again if needed, but do not start by resetting all system settings.
| Setting | What to verify | How to revert |
|---|---|---|
| System proxy | Whether the destination app uses the setting | Restore the original proxy state after stopping |
| Virtual network interface | Traffic scope and local network access | Check that routes are restored after disabling |
| Routing rules | Which exit matches the destination request | Remove the added rule and test again |
| DNS settings | DNS source and app behavior | Restore the original mode and check the cache |
Make the smallest possible change to local rules
Before changing the route for a particular app, check whether an existing rule already covers it. Add only the smallest change needed. Rules often have an order, and an overly broad match can make later rules ineffective. Avoid editing a remote subscription directly, as an update may overwrite your changes. If the client supports local overrides or separate rules, use them as documented. Each rule should have a clear purpose, match condition, and rollback method. Do not keep stacking rules that you cannot explain.
If you use local devices, file sharing, or a work network, also verify that local access still works. After enabling broader traffic routing, issues with printers, shared folders, or other local services may have nothing to do with international routes. First return to the original routing mode to confirm the difference, then follow the client documentation to manage exceptions for your local network. Do not force all device traffic through one exit just to get a single app working. Clearer routing and well-scoped permissions make ongoing maintenance easier.
Troubleshoot with reversible tests
Change one variable at a time and record the results before and after. Variables to compare include the route, traffic-routing mode, app proxy settings, and DNS method. Do not change several things at once and rely on memory to identify the cause. After a change works, repeat the original task. If it fails, restore the previous setting before testing another possibility. If logs show an error, share only the relevant excerpt, not the entire configuration. If you cannot identify the issue, bring the differences you have already verified to the Help Center or a dashboard support ticket. This is more useful than sending a large collection of unorganized screenshots.
You should now be able to repeat the full process on your own: check your plan and order, get your own subscription, import it on the right platform, verify the exit and destination task, save a stable configuration, and troubleshoot issues one layer at a time. For a quick refresher, return to the getting started guide. For product details, check the plans page. A configuration you can explain and easily roll back is a better foundation for long-term use than a complicated setup.