Complete VPNGL User Guide

Understanding subscriptions and clients

VPNGL is a subscription service for cross-border network access, with coverage in 110+ countries and 170+ routes. Using the service involves an account, a plan, subscription configuration, and a client: your account stores your service status, your plan defines the available traffic and billing method, your subscription provides route settings to the client, and the client handles network requests from your device according to its routing settings. Understanding these roles helps you pinpoint issues instead of repeatedly reinstalling software.

The difference between the service portal and your device

This website’s service information, plans, and guides explain how the service works. The user panel handles your account, orders, subscriptions, and client downloads. Browsing the site won’t connect your device to a route, and paying for a plan doesn’t automatically connect your client. Check your service status in the panel, get the subscription for your client, then import and enable it in the software on your device. If you already have an account, use the login link in the navigation; there’s no need to create another one.

A client is connection software on your device, not a separate plan. VPNGL supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. You still need to install the client, import the subscription, and grant any required permissions on each device. Seeing a connection on your desktop doesn’t confirm that another device is connected. Devices can use the same account, but their local routing, system permissions, and network conditions may differ.

Your local settings determine how requests are routed

Once connected, which requests use a route depends on the client’s rules, system proxy, or tunnel mode. Rule mode typically handles requests by destination; the system proxy mainly affects apps that follow system proxy settings; tunnel mode usually covers more traffic and may require additional system permissions. These are client behaviors, not plan tiers. A connection indicator in the app doesn’t mean every app is using the connection.

VPNGL’s primary security message is quantum encryption. For everyday security, it’s just as important to safeguard your account password and subscription details, check the website domain, and avoid handing your configuration to unknown tools. Route protection and website login security are separate layers. Using a subscription doesn’t bypass a destination website’s account checks, regional rules, or content policies. Check the target service’s response to see whether access is working as expected.

Establish a repeatable baseline

For your first setup, use the device you have at hand and a specific website you want to access. Leave the client’s default settings unchanged for now. First confirm that your basic network can open ordinary websites, then import the subscription, choose a route, connect, and verify the result. Keeping these steps separate makes it easier to identify where something changed. If your basic connection is down, troubleshoot your local internet first. If the subscription won’t load, check the panel rather than changing complex routing rules.

Coverage describes the range of available routes; it doesn’t guarantee the same results for every website in every region. A destination’s regional policies, account eligibility, detection methods, and service status can all affect your experience. Choosing a route means finding a suitable path between your current network and the destination. A country label is one point of reference, not a substitute for testing the connection—and it doesn’t guarantee access to particular content.

You can follow the contents chapter by chapter: start by estimating your traffic needs, set up an account and order, then get your subscription and import it on your device. After verifying the connection, save the working settings before considering split routing or automation. For a shorter step-by-step walkthrough, return to the Quick Start Guide. If you’re troubleshooting a specific step, see the Frequently Asked Questions.

Choose a plan that fits your usage

When choosing a plan, consider how regularly you’ll use it, then how much traffic you need. A monthly subscription suits ongoing use, with traffic resetting each month on the activation date. A traffic package suits users who want unused traffic to remain available: it lasts until used and never expires. Each billing option serves a different purpose, so don’t compare them by price alone. The factual prices are listed below; see the Plans page for full details, and check the order in the panel before activating.

Estimate traffic needs based on what you do

Browsing text, syncing documents, streaming video, and transferring large files use different amounts of traffic. Video quality, viewing time, background updates, and cloud storage sync all affect usage, so it’s not useful to convert a plan tier into a fixed number of viewing hours. Start by reviewing how you use apps on your devices: which tasks transfer data continuously, which you use only occasionally, and which background apps may sync automatically while connected. Then decide how much traffic you need.

Unlimited simultaneous devices means the number of devices doesn’t restrict your plan; it doesn’t mean traffic is unlimited. If multiple devices use the same account, check total usage in the panel rather than relying on one device’s local figures. A client may count only the traffic it handles, while system usage figures may include direct connections. Neither necessarily matches the panel’s billing figures, so check the panel to see your remaining balance.

Understand resets, upgrades, and traffic packages

Monthly subscription traffic resets each month on the activation date, not at the start of each calendar month. Don’t assume your traffic has reset just because the month has changed; check the service period and reset status in your account. Resets and renewals are also different: one concerns your traffic allowance during a billing period, while the other extends your service. If you plan to keep using the service, check your expiration date and traffic details separately to avoid misjudging a temporary interruption.

When you upgrade mid-cycle, the price difference is converted into remaining service days. Don’t try to calculate a fixed additional payment or simply subtract the old plan price from the new one and pay the difference. Choose the upgrade option and review the resulting order in the panel, confirming the target plan and updated service status. If the result isn’t what you expected, contact support before placing multiple orders for different tiers.

“Never expires” describes how long traffic in a package remains valid. It doesn’t tell you how that traffic is deducted when combined with a monthly subscription, how the two are combined, or whether switching happens automatically. These details aren’t specified in the available facts. If you already have an active service and plan to change billing types, check the panel’s guidance first. If it’s unclear, keep your current setup and ask support before making a change; don’t assume different products follow the same rules.

Consider payment and refunds together

Payment methods include Alipay / WeChat Pay / USDT, and the refund policy offers a 30-day, no-questions-asked refund. When choosing a plan, read the Refund Policy and Terms of Service, not just the short label next to the button. Before paying, confirm the currency, amount, and plan name. For digital assets in particular, follow the payment instructions shown for that order; don’t copy payment details from forwarded chats or old screenshots.

Before proceeding, make sure you can answer these questions: Are you choosing a monthly subscription or a traffic package? How much traffic does it include? When should you check for a reset or renewal? Which devices will you use? If anything is still unclear, stay on the plan details page for now. Understanding the service rules first is easier than trying to figure them out by repeatedly changing settings after payment—and it makes it easier to check your order later.

Create an account and get started

VPNGL doesn’t require an email address; you can create an account with a username and password. Your account is where you manage orders, subscriptions, and ongoing service, so plan to keep it accessible rather than treating account setup as a temporary installation step. Check that the address bar shows the official site domain, then use Start Free to open the user panel. If you already have an account, use the login page to avoid leaving your order in a different account.

Keep your username and password safe

Choose a username you can recognize and a password you don’t use on other websites. A password manager can store the full details and help prevent typing mistakes. Once your account is created, make sure you’re on the account page and record your username; don’t rely on keeping a browser tab open. If you share your device, don’t leave your account signed in for others. Sign out and close the relevant pages when you’re done.

Not requiring an email address is a fact about the account setup process; it doesn’t mean you can automatically recover your account in every situation. Keep your login details safe, and follow the recovery options and support process shown in the panel. If you can’t log in, check your username, keyboard layout, capitalization, and whether your password manager has filled in the wrong site’s credentials. Don’t paste your password into a public forum or send a screen recording that shows it when asking for help.

Check your account before placing an order

Open the Plans section of the panel and check your current service status before choosing a plan. Your browser may still be signed in to an old account, especially if you’ve switched devices or are using a shared computer, so confirm the username and existing orders. After choosing a plan, check its name, price, billing method, and traffic against the plan page before continuing to payment. Creating an order only generates a payment request; it doesn’t activate the service.

If the order details don’t match what you expected, go back and make changes or use the cancellation option available in the panel. Don’t try to change the plan by altering the payment amount. The amount requested on the payment page is tied to the order; paying too little or too much, or using details from an old order, may prevent the payment from matching automatically. Follow the payment process shown on the current page. If it redirects, check the destination before continuing and avoid unfamiliar payment pages.

Confirm service status after payment

Once your payment provider confirms the payment, return to the panel to check that the order has updated, then verify the plan and traffic in your account. Payment and service delivery are related but separate steps, so a payment screenshot alone doesn’t confirm that your subscription is ready. If the page hasn’t changed, check your order list again. Keep the order ID and payment receipt, and don’t pay the same order again while its status is unclear; duplicate payments can be difficult to resolve.

If payment is complete but the order is still pending, first confirm you’re checking the right account and order, and that you paid through the flow for that order. If you still can’t match them, submit a request through support tickets in the panel. Describe the plan, the status shown in the panel, and what you’ve already done. Include the necessary payment proof, but cover personal details unrelated to the issue. Don’t share your account password or full subscription details.

Handle refunds and technical issues separately

VPNGL offers a 30-day, no-questions-asked refund. Submit refund requests according to the Refund Policy, and keep the relevant order details available for verification. If your client simply isn’t connecting, first use this guide to check your subscription, permissions, and route. If you’ve decided to request a refund, state that clearly through the panel’s support process instead of burying the request in a long technical description. Keeping the two issues separate helps support staff determine what to do next.

This stage is complete when the panel confirms the plan, order result, and active service status—not just when you see a payment confirmation. Once you’ve checked these details, move on to getting your subscription. If your account status is unclear, resolve the order or delivery issue first; reinstalling the client, changing routes, or adjusting permissions usually won’t fix an account problem.

Get and manage your subscription

A subscription gives your client access to route configuration. Think of it as a source of configuration maintained by the service and updated on your device. It’s not a general information page or a payment link. Before getting your subscription, check your plan and service status in the panel, then follow the import method provided there. Don’t paste the panel’s website address into your client as a subscription; it will usually load a webpage or return a parsing error.

Choose the import method before copying

Find the subscription options in your account overview and check which import methods support your client. Clients may accept different configuration formats, so use the option the panel provides for your specific client. If you copy a link, use the page’s copy button to capture it in full. Avoid missing trailing parameters through manual selection, and don’t paste it into a document editor that might add quotation marks or line breaks.

One-click import usually hands the link to an installed app through your operating system. Your browser may ask whether to open an external app. Check that the app name is what you expect before allowing it. If nothing happens, check that the client is installed and can start on its own, and that the browser hasn’t blocked the external app. You can also add the configuration from within the client. Don’t send your subscription to an unfamiliar online conversion tool to troubleshoot it.

A successful import doesn’t mean the configuration is active

After receiving the link, the client may ask you to name the local configuration, download remote content, or confirm that you want to overwrite an existing configuration. Give it a name that’s easy to recognize; don’t use the full subscription URL as the name. After saving, check that a route list appears, that there are no update errors, and that the selected configuration is the one you just imported. Some clients let you save multiple configurations, and adding one doesn’t necessarily switch to it automatically.

If your client only supports local file imports, first check the guidance from the panel and the client. An imported file is often a snapshot of the configuration at a specific time; whether it can update automatically depends on how it was imported. A remote subscription retains its update source. Avoid repeatedly converting remote subscriptions into scattered local files for convenience; when routes change, it can be hard to tell which file is still valid and which is out of sync with the panel.

Treat your subscription like a credential that needs protection

A subscription link may contain parameters that identify your account or service. Anyone who gets the link may be able to access the associated configuration, so don’t publish it, put it in a code repository, share it in a screenshot, or include it in a document accessible to search engines. The sample address below is fictional and can’t connect to the service; always get your actual address from the panel. If support only needs to identify the type of error, sharing the error message is usually better than sending the full link.

https://example.com/sub?token=YOUR_TOKEN

If you think your subscription has been exposed, check the panel for an option to reset it or update its credentials, and read the instructions. If there’s no clear option, ask through a support ticket. After a reset, you may need to update the configuration on each device; do so one at a time and verify it. Deleting a chat message won’t solve the issue if the link has already been copied elsewhere, and don’t guess whether the old link is still valid.

Trace an update failure back to its source

If an update fails, first confirm your basic network is working, the copied content is complete, and your account status and configuration format are correct. Being able to open the panel doesn’t mean the subscription downloaded successfully; likewise, routes in the client’s cache don’t prove that remote updates are working. If you’re keeping your existing configuration, record the error before making changes. Repeatedly deleting and recreating it may also remove a setup that was working. Always return to the panel for the latest import option.

You’re done with this stage when you can identify the current configuration in the client, see the loaded routes, and know where to update them. You haven’t verified the connection yet; next, grant the required permissions for your platform and enable the connection. To learn more about the differences between copying, importing, and updating, see the account and subscription FAQs.

Import on each platform

The steps are the same on every platform: get the client, import your subscription, select the configuration, and grant permissions. Permission prompts and background behavior vary by platform. Download clients from the downloads section of the user panel, not from search results with similar-looking app names. The instructions below cover platform-specific differences; follow the labels in your actual client. If an option isn’t supported, don’t force-enable another feature just to match the guide.

Windows: Check proxy settings and system permissions

Choose the Windows client in the panel, follow the installation instructions, and launch it normally. Import the compatible subscription and confirm that the configuration has loaded. Then choose a route and connect. If the client offers system proxy and tunnel modes, start with the recommended option. When it requests extra permissions, confirm that the prompt comes from the client you just installed. If you installed the client but didn’t select a configuration, or the client is running but the system proxy is off, your browser may still use its previous route.

When disconnecting, use the client’s disconnect or exit command where possible so it can restore your system proxy settings. If webpages stop loading after you force-quit the client, check for leftover system proxy settings instead of deleting the configuration immediately. To test for interference from other networking tools, exit them normally before testing the current client. Avoid changing the system proxy, tunnel, and app proxy at the same time; it will be hard to tell which one is handling requests.

macOS: Distinguish configuration from network extension permissions

On macOS, installing an app and granting it permission to handle network traffic may be separate steps. After launching it for the first time, import your subscription, check the relevant permissions in System Settings as prompted by the client, then connect. If another window obscures the permission prompt, return to the client and check its instructions rather than importing the same configuration repeatedly. When macOS shows a security warning, verify the app’s source. Don’t disable system protections or run unknown Terminal commands for convenience.

Browsers and terminal apps may handle proxies differently. If webpages work but a development tool doesn’t, first check whether that tool uses the system proxy; don’t assume the subscription is broken. If your connection acts up after sleep or a network change, disconnect and reconnect, then check the selected route. Keeping the existing configuration helps you compare before and after recovery; you don’t need to reinstall the app every time.

iOS: Open the App Store from the panel’s instructions

Follow the panel’s instructions for iOS client availability and eligibility. If a download link is available, continue through the App Store link provided there. App availability depends on the store region and platform rules; don’t use someone else’s shared account. After installation, import through the subscription option. When iOS asks to add a VPN configuration, check the app name and confirm, then return to the client to check the routes and connection status.

The connection icon in the status bar only indicates that the system has a corresponding connection; open your target service to verify it actually works. If a browser works but an app doesn’t, close the app’s existing session and retry, then check for any region or account messages from the app itself. For more on store regions and the difference between app and subscription imports, see the iPhone client and subscription import guide. A configuration profile and a standard subscription aren’t the same thing.

Android: Check background activity and battery settings

After installing the Android client, import your subscription and confirm the system connection request. Then check that the client keeps working when sent to the background or when the screen is locked. If it works in the foreground but stops in the background, check the system’s battery and background activity settings, granting only the permissions the client needs. Menu names vary by device, so don’t worry if they don’t match this guide exactly. If the system reports another active VPN connection, decide which one to keep before continuing to avoid clients replacing each other.

If some apps still don’t use the connection after you switch routes, restart the affected app and check the client’s per-app settings. Don’t add every app to an exception list and then expect them to use the route. For more detailed steps, see the Android setup and connection verification guide. Note whether the problem starts after locking the screen, changing networks, or opening a particular app.

Linux: Check your environment before routing traffic

On Linux, first check that the system architecture matches the client offered in the panel, then follow the relevant installation and import instructions. Desktop proxy settings may not affect command-line programs, while tunnel mode may require additional system permissions. Start by loading the subscription and establishing a basic connection, then configure app-specific proxies if needed. Don’t copy privileged scripts from unknown sources or replace the client’s normal installation process by changing network settings across the entire system.

If a terminal task needs a proxy, use the protocol, listening address, and port actually shown by your client; don’t guess common defaults. Test one task before making the setting persistent, so package managers, background services, and interactive shells don’t all inherit unverified settings. After importing on any platform, continue with the route and app checks in the next chapter rather than judging the result by the client’s color alone.

Connect and verify your setup

Check each of these separately: the configuration is loaded, the client is connected, app requests are using the route, and the destination service allows access. These steps follow one another, but they aren’t the same thing. Choose a route and leave other settings unchanged, then check your exit address, DNS resolution, and target app. Whenever possible, use the same device and basic network throughout testing. Avoid changing the Wi-Fi network, route, and client mode at once; otherwise, you won’t be able to compare results.

Start with a controlled connection baseline

With the client disconnected, first confirm that your basic network can open ordinary webpages. Then connect the client and check for obvious errors. If no webpages load after connecting, check the selected route, system permissions, and proxy status first. If only the target website fails, keep the connection active while you check the site’s response. Record website access restrictions, account issues, or unavailable content separately from a connection that can’t be established at all.

Choose a route based on the region required by the destination, then consider how it performs on your current network. A nearby region isn’t always a better choice; your local carrier’s routing and the destination’s network entry point can also affect results. Before switching, note the current route name and what happens. Then test the same destination again after switching. Don’t judge performance from the region name alone or assume a brief loading failure means the whole service is unavailable.

What your exit address and DNS can tell you

Your exit address shows the apparent source of a request to a website, but it only describes the request you tested. A changed browser exit address doesn’t prove that your terminal, games, or other apps use the same route. Use a diagnostic tool you trust to compare the connection before and after, and check whether the displayed region matches your expectations. Some address databases update slowly, so a different location label alone doesn’t prove that the route label is wrong; consider it alongside other results.

DNS translates domain names into addresses. DNS lookups and service requests may be handled differently. Browser secure DNS, system caches, and the client’s DNS settings can all affect what you see. If DNS appears to take an unexpected path, check your current mode and the client documentation; don’t use a DNS address you found in an online search without verifying it. Resolving a domain doesn’t mean the service connection succeeded, and a DNS failure doesn’t necessarily mean your account or plan is at fault.

Verify apps, not just your browser

Verify the connection in the app you actually use. An AI tool’s website and API, or a video in a browser and a standalone player, may use different network stacks or service endpoints. Open the sign-in page first, then try the task you need to complete. Note whether the failure happens while loading, signing in, or submitting a request. Destination services have their own eligibility, regional rules, and usage policies; connecting to a route doesn’t change them.

If an app still shows the old result after you switch routes, it may be using an existing connection, cached data, or an account session. Close and reopen the app normally, and clear its cache only if its official instructions recommend it. Avoid deleting all local data, which may erase your work. Test the actual content you want to watch on streaming services. With AI tools, check website access and API requests separately; opening the homepage doesn’t prove that your whole workflow works.

Prepare a useful report for support

If you still can’t pinpoint the issue, note whether your basic network works, whether the client loaded the configuration, which route you selected, the routing mode, the target app’s message, and what you’ve already tried. Quote error messages accurately, and redact subscription details, account credentials, and unrelated content from screenshots. You can also consult the guide to exit IPs, DNS, and per-app checks, then add your findings to a support ticket. “It won’t connect” alone doesn’t provide enough detail to troubleshoot.

Ongoing maintenance and renewals

Once connected, day-to-day maintenance means keeping an eye on account traffic and service status, using trusted sources for subscriptions and clients, and rechecking your setup when network conditions change. You don’t need to clear your configuration frequently. Keep settings you’ve verified, and know when to update them or check an order; that’s more useful than continually switching clients. When something goes wrong, reviewing your recent changes can prevent unnecessary troubleshooting.

Check traffic and service periods separately

Monthly subscription traffic resets each month on the activation date. Traffic packages last until used and never expire. When checking your account, review your remaining traffic, service status, and any period information separately. Low traffic and an expired service can cause similar connection symptoms, but they need different fixes: check usage for the former and service continuity for the latter. Don’t blame device permissions or a faulty route before checking your account status.

When using multiple devices, keep an eye on total usage. If traffic increases more than expected, check whether cloud storage, system updates, video autoplay, or background sync is going through the route. Then check for an old device you may have forgotten about. Client counts and panel usage don’t necessarily update in sync, so be mindful of what each is measuring. A low figure in local software alone doesn’t mean the panel’s account usage is wrong.

Review the order details before renewing

To renew, sign in to your original account and check the available options in the plans section. Confirm your current plan and whether the new order extends it, changes it, or handles it another way. Don’t use an old payment screenshot as new payment instructions. After paying, return to the panel to check the order and service status. If an old payment page is still open in your browser, confirm it applies to the current order before starting another transaction.

When you upgrade mid-cycle, the price difference is converted into remaining service days; the panel’s current order shows the exact result. If you’re switching from a monthly subscription to a traffic package, or considering a monthly subscription when you already have a package, don’t guess how traffic will be combined or deducted. Check the panel instructions and ask support if anything is unclear. The price list shows the facts for each tier; it doesn’t explain every transition between service types.

Update subscriptions without overwriting custom settings

When the route list needs an update, update the existing configuration in the client’s subscription manager if possible. Check that the update succeeded, then confirm the route you need is still available. If it fails, don’t delete the configuration immediately; first record the error and check your account status. If custom rules and remote configuration are combined, find out whether an update will overwrite local changes before proceeding. This can prevent routing behavior from changing unexpectedly after an update.

Update your client through a source provided by the panel or a trusted update option within the client. Before updating, check the platform’s prompts and any permission changes. When it’s done, recheck your subscription, proxy mode, and target app. Don’t use an unknown script to “fix” an update or lower system security across the board to solve an issue in one app. If the problem began after an update, recording what changed and the error is more useful than repeatedly uninstalling the client.

Device changes and contacting support

When you switch devices, sign in to the panel on the new device and import your subscription for that platform. There’s no need to pass the full configuration around in chat. Before handing your old device to someone else, sign out, remove subscription and client configurations, and check for saved browser login details. Whether uninstalling the app also removes its configuration depends on the platform. If you suspect someone else has accessed your credentials, follow the panel’s instructions or ask support how to update them.

After switching from home Wi-Fi to an office or travel network, you may need to verify your setup again. First check whether the network requires a web-based sign-in, then start the client. If you need to accept terms or complete a sign-in before connecting, do that first. For problems that only happen in one location, note the network conditions and how to reproduce the issue; don’t assume results from another device apply to this one.

To request a refund, clearly state your request according to the 30-day, no-questions-asked refund policy. For technical help, use the existing support process through Contact Us. The aim of good maintenance is to keep your account status clear, your configuration up to date, and your checks repeatable—not to rely on temporary fixes from unknown sources.

Advanced routing and workflow settings

Only move on to advanced settings after verifying your basic connection. If the default configuration still doesn’t work, return to the connection checks rather than covering up the problem with more rules. Split routing, app proxies, and tunnel mode handle different traffic-routing needs; the available options depend on your client. This chapter explains how to choose, not what every VPNGL plan includes.

Choose routing scope based on your goal

If you want your regular browser to use a route, start by checking the client’s recommended system proxy option. If a standalone tool needs a proxy, check whether it supports its own proxy settings. For broader routing, look into the client’s tunnel mode and its permission requirements. Broader coverage isn’t always better; it may also change access to local networks and DNS behavior. Decide which apps you want to route before choosing an approach.

Rule mode uses domains, addresses, or other criteria to determine where requests go. Rules often match in a specific order. Before adding an exception, read the client’s current rules documentation and confirm where the rule belongs, what syntax to use, and whether it will persist after a subscription update. Don’t mix configuration snippets from different clients. Fields with similar names can have different meanings and scopes; a configuration that saves successfully may still behave unexpectedly.

Test development tools and AI APIs separately

Development tools may not use the desktop environment’s proxy settings. Terminal commands, editor extensions, and tasks running in containers may each use a different environment. Before configuring a tool, check its official documentation for supported proxy settings and use the protocol, listening address, and port shown in your client. Verify one command or task first, then consider saving the settings to your environment. Don’t write unverified parameters into global settings where they could affect other projects and background tasks.

For AI API requests, distinguish connection errors from authentication, quota, and server response errors. Being able to access the website doesn’t prove that your API account is eligible, and an API error doesn’t necessarily mean the route is down. Record the error type and check your account permissions and request format. Follow the service documentation for timeouts and retries; don’t repeatedly submit invalid requests. See the guide to choosing routes and making AI API requests for more details.

Local networks, remote access, and fixed exit addresses

When you route more traffic, changes to routing may affect printers, local file sharing, or internal domains. If that happens, compare the results before and after using a reversible change, then add any necessary exceptions according to the client’s documentation. Don’t combine every private network and destination domain into one broad rule to restore local access; an exception that’s too broad may send traffic directly that you intended to route through the service.

If your workflow requires a fixed exit address, a dedicated IP, or a provider allowlist, first confirm that the product explicitly offers that capability. These aren’t commitments in the available facts, and you can’t infer them from a country label, route name, or subscription price. For development or office tasks that need a consistent source address, explain your use case to support and confirm the available options before changing an external platform’s allowlist. Don’t add an unverified exit address to a critical workflow.

Keep a rollback option and document your changes

Before making changes, note the current configuration name, routing mode, and targets you’ve already verified. Don’t put sensitive links in ordinary notes. After adding a rule, check its syntax and test how it matches a specific target. If unrelated apps start acting up, restore the previous settings to see whether the change caused the issue. Backups may contain credentials, so don’t upload them to a public repository. Keeping a rollback option is better for long-term use than adding a large number of rules at once.

You’ve completed this guide when you can confirm service status in your account, get a subscription from the panel, import it on each platform, verify it in the apps you use, and check again after renewing or updating. For route options, see the route list. Refer to the plan details and legal pages for product terms. Ask before configuring features that aren’t explicitly offered. When an error can be reproduced, keep the evidence and include it in your support request so every change is based on what you can verify.