This reference guide explains why each step matters and includes checks for when something goes wrong. If you just want to get connected, follow the quick path in the Getting Started Guide. Use the contents below to return here when comparing plans, handling system permissions, or managing multiple devices. Client interfaces change, so this guide refers to features rather than specific button labels; check your current dashboard and client for the exact wording.
Understanding Cross-Border Network Subscriptions
What your account, subscription, and client each do
VPNYR is a subscription service for cross-border network access, with coverage in 90+ countries and 170+ routes. Your account identifies which subscription is yours; the dashboard shows plans, orders, and service details; and the client establishes a connection on your device. Creating an account does not connect you, and installing a client does not import routes. Knowing how these pieces differ makes it easier to tell whether an issue is with your account, configuration, or device network—instead of reinstalling everything.
A subscription link lets the dashboard deliver route configuration to a client. The client reads the link to retrieve available routes and related settings. It is not a regular webpage or an installer link. If opening it in a browser shows text, a download prompt, or an error, that alone doesn’t tell you whether it will work in the client. Import it from the client’s subscription or configuration manager, then check the update result and route list.
What happens during a connection
When you visit an international website, a request starts in an app on your device. The client’s connection method and routing rules determine how it is sent. Requests that need acceleration travel over the selected route and reach the service through its corresponding exit; the response returns over the connection. Whether the website itself works also depends on its status, account region, and access policies. Route coverage does not determine a website’s content licensing, so check connection status and service availability separately.
VPNYR describes its security approach as quantum encryption. You should still protect your account password and subscription link, check the dashboard domain, and use clients from trusted sources. Encryption addresses issues related to data in transit; it does not protect your website accounts or tell you whether a page is trustworthy. Before paying, granting access, or entering sensitive information, confirm that you’re on the intended website rather than relying only on the client’s connection status.
Supported devices and usage considerations
The service supports Windows / macOS / iOS / Android / Linux, with no limit on the number of devices online at once. Support means you can configure the service on those platforms—not that they all use the same permission model. Desktop systems may require a network extension or virtual network interface, while mobile systems typically ask you to approve a system connection. System proxy settings, rule modes, and traffic coverage can also vary by client. Check each device individually rather than assuming the controls are in the same place.
Before you begin, make sure your device can access its current network. Home broadband, public Wi-Fi, and workplace networks all have different requirements. If you need to complete a web-based sign-in first, do that before starting the client. Organization-managed devices may restrict network extensions or proxy changes; follow your organization’s usage rules. If device-management policies block a permission, repeatedly importing the subscription is unlikely to help. First check whether the device allows the operation you need.
Treat this guide as a sequence of steps you can revisit. Choose a plan, complete your account and order, get your subscription, then configure your device. If something goes wrong later, return to the step closest to the symptoms; there’s no need to start over. For example, if the route list is empty, check the subscription update first. If the list looks normal but your browser can’t access sites, check permissions, proxy settings, and routes. This preserves the steps that are working, limits unnecessary changes, and helps you explain what you’ve already checked in a support ticket.
Choose a plan for how you use it
First, choose between a monthly plan and a data package
A monthly plan suits regular use when you want to manage data month by month. VPNYR 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 at the end of each calendar month. Before choosing, consider your main activities: document research and messaging, image generation and file transfers, and regular video streaming use data differently. Don’t compare plans by monthly price alone.
A data package suits irregular usage or anyone who wants to use data at their own pace. Options are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Use the data until it runs out; it never expires. This describes the package’s validity, not a promise that devices need no maintenance or that third-party websites will never change their rules. After purchase, check your remaining data and service status in the dashboard. Don’t assume a configuration can be stored indefinitely without updates.
| Plan | Price and data | Data terms | Best for this usage pattern |
|---|---|---|---|
| Monthly plan | ¥9.9/month includes 60GB ¥18/month includes 250GB ¥28/month includes 500GB | Resets monthly on the activation date | Review usage month by month |
| Data package | ¥158/300GB ¥358/1000GB ¥658/3000GB | Use it until it runs out; never expires | Plan usage around your remaining data |
Estimate data needs from your actual activities
Don’t estimate your plan based on the number of devices. Unlimited devices means there’s no cap on how many can connect at once, but activity on each device still uses data. Background sync, app updates, video preloading, and file uploads can all transfer data continuously. Before comparing plans, list the tasks you do regularly and decide which need an accelerated route. Briefly checking text on several devices is different from transferring large files continuously.
When you’re getting started, watch data usage in the dashboard and compare it with your everyday activities to see whether you need a different plan. Note the starting and ending figures, and check whether other devices were connected during that time; otherwise, background activity may be mistaken for usage from the page you’re viewing. The dashboard and device counters may measure usage differently, so don’t estimate account billing from browser download history. Use the dashboard as your reference for actual usage, and keep track of what you were doing if you have questions.
What to check before upgrading, paying, or requesting a refund
If you upgrade a monthly plan partway through its term, the price difference is converted into remaining days. It doesn’t simply add a full new term to your existing plan. Before placing the order, carefully review the upgrade result, amount due, and effective details shown in the dashboard. Don’t calculate your final benefits based only on the original plan price. The available facts don’t specify a universal rule for switching between monthly plans and data packages or combining them, so check the options shown in the dashboard or ask support through a ticket.
Payment methods: Alipay / WeChat Pay / USDT. The service offers a 7-day hassle-free refund policy. Read the Terms of Service for the specific refund terms, and see Plan Pricing for a full comparison. This guide does not promise that a client will install, a particular website will be accessible, or a specific speed will be achieved. Confirm your needs and the terms before paying to avoid relying on assumptions afterward.
Finish by writing down a clear usage plan: which billing option you’ll use, which devices you’ll use most, which tasks need acceleration, and when you’ll check the dashboard again. You don’t need to predict every byte; the plan gives you a way to compare actual usage. If usage changes, check background transfers and routing coverage before deciding whether to upgrade. If you use the service less often, compare how monthly plans and data packages fit your needs rather than sticking with a plan based on its name alone.
Create an account and check your order
Set up your account in the dashboard
Open the account creation page to access the user dashboard at the site root. VPNYR does not require an email address; create an account with a username and password. First, check the website domain in your browser’s address bar, then enter a username and password you can keep secure long term. The marketing pages explain the service; account actions take place in the dashboard. Don’t enter your credentials again on unfamiliar forms, in chat windows, or on pages claiming to repair subscriptions.
Choose a username you can recognize, avoid reusing passwords from other websites, and save your credentials with a trusted password manager. Record the site address and username as well, so you can identify which account a password belongs to later. Since account creation does not require an email address, don’t assume you can recover access through a standard email reset. Before signing out, make sure your credentials are safely stored and know where to find account help in the dashboard. Don’t rely on browser autofill as your only backup.
Check your plan before placing an order
Open the Plans section in the dashboard and check the plan name, price, data, and billing terms. Monthly plans and data packages work differently, so don’t proceed based on the price alone. If you’re changing an existing plan, also check its current status and the change details shown on the page. If the result isn’t what you expected, stop and review the options before confirming. Don’t pay first and expect the system to apply a selection you didn’t submit.
Before paying, make sure you’re signed in to the account you intend to use. Your browser may retain a session for another account, particularly on a shared device or when switching between browser profiles. The order and subscription belong to the account that placed the order. If you later sign in to a different account, its status will naturally look different. If the dashboard doesn’t match your records, check the account and order list first to avoid repeating an action in the wrong session.
After paying, check the order—not just the payment page
Choose Alipay / WeChat Pay / USDT and follow the payment instructions shown in the dashboard. The payment page, the browser’s redirect result, and the order status in the dashboard are separate sources of information. When you return to the dashboard, check your order history and account overview to confirm the plan benefits are displayed. If you close the browser or the redirect is interrupted, sign in again and check the original order. You don’t need to create a duplicate order just because the redirect didn’t complete.
If payment appears complete but the status isn’t what you expected, keep the original order record and payment receipt, then describe the issue through the dashboard’s support ticket page. Include the plan you chose, the status shown in the dashboard, and what you did. Don’t share your account password, full subscription link, or unrelated sensitive information. You can redact irrelevant details from the receipt, but keep what’s needed to verify the payment.
Move on to client setup after confirming delivery
After confirming the order, check your plan, data, and service status in the dashboard before moving on to get your subscription. A successful payment message in a payment app does not automatically give the client any routes; you still need to import the subscription for your account. Handling order confirmation and configuration import separately helps distinguish account entitlements from device issues. If the dashboard status is unclear, resolve that first. If it looks normal but your device has no routes, continue by checking the subscription and client.
To request a refund, use a dashboard support ticket and read the Terms of Service. The service offers a 7-day hassle-free refund policy. Refunds, renewals, and upgrades are account matters; deleting the client from your device is not a substitute for submitting a request. After completing account actions, sign out of shared devices you no longer use and remove saved credentials. Keep necessary order records, but don’t casually share screenshots of the full page if they expose subscription access details.
Get and protect your subscription link
Find the configuration link in your account overview
Sign in and open the account overview. Check your service status first, then look for the subscription, import, or copy-link option. A subscription link gives the client access to configuration, so use the dashboard’s copy function rather than copying it by hand and risking missing characters. If the dashboard offers more than one configuration format, choose the one supported by your client. Similar-looking links are not necessarily interchangeable.
To get a client, open the client downloads section. Sign in to download a client for Windows / macOS / Android / Linux; you don’t need to have purchased a plan. The dashboard checks for an active plan before showing the iOS download option. Getting a client and using a subscription are separate steps: installing the client does not mean your account has an active subscription. If the download is available but the overview shows no active service, return to the account and order steps to check.
Copying a link versus importing directly
Copying a link puts the configuration address on your clipboard; you still need to add a subscription in the client. Direct import typically opens the installed client through a system link and passes the address to it. If a prompt asks to open an app, check that it’s the right one. If nothing happens, open the client to confirm it’s installed, then try copying the link instead. Don’t keep clicking import for the same issue, as that may create duplicate configurations with similar names.
A subscription link is sensitive because it grants access to configuration. Even if it doesn’t display your account password, someone with the link may be able to retrieve your account’s configuration, so protect it like a credential. The example below is clearly for demonstration only and cannot be used to connect. For actual use, copy the address from your own dashboard. Don’t put the full link in public notes, forum posts, screenshots, online conversion tools, or shared documents, and don’t let strangers store it for you.
https://example.com/sub?token=YOUR_TOKENCheck importing and updating separately
Saving an address in the client only confirms that a subscription entry was created. You’ll usually need to update it or fetch its configuration before the client can read its contents. After the update, check whether the configuration is selected, routes appear in the list, and any format or network errors are shown. If the entry saves but the route list is empty, don’t start the connection yet. Check that the address is complete, the format is supported, and the client can reach the subscription source over your network.
If import fails, copy the address again from the dashboard to avoid line breaks, changed punctuation, or leftover spaces introduced by a chat app. Then confirm that the client supports the address format. If the client reports a connection failure, check your device’s basic network access. If it reports a parsing error, check the format and client compatibility first. These errors call for different fixes; changing link parameters at random won’t help, and you should never guess or assemble access credentials.
Updates, backups, and invalid links
If the dashboard lets you reset a subscription link, check what the action affects before proceeding. Once an old link is replaced, each device may need to re-import the subscription or update its address. Clicking Update on an old configuration may not retrieve the new link. If you think the link has been exposed, use the current options in the dashboard or ask support through a ticket; deleting the configuration on your device alone won’t revoke links saved elsewhere.
For a backup, you can note the configuration name, source site, and purpose, but keep sensitive links out of routine backups. Before reinstalling a client, make sure you can still sign in to the dashboard and retrieve your subscription. Don’t rely on an old configuration of unknown origin as your only way to restore access. After importing, clear sensitive information from your clipboard and use recognizable names across your devices to distinguish the current subscription from retired entries.
Import the client on each platform
The basic sequence is the same on every platform: get the client, import the subscription, update the configuration, grant permissions, then select a route. How the system handles network traffic varies by platform. The notes below cover the key differences; button labels depend on the version you’re using. If another network client is already installed, note its settings and disconnect it first to avoid competing changes to system proxy settings. Verify one platform before setting up other devices; don’t copy an untested configuration everywhere.
Windows: check system proxy settings and background status
Sign in to the dashboard to get the Windows client, then install and launch it. In the subscription or configuration manager, add a remote configuration, paste the dashboard link, save it, and update. When routes appear, select the current configuration, choose a route, and enable the connection method you need. If Windows asks for network access, confirm the prompt comes from the client you just installed before granting permission. A system proxy and a virtual network interface work differently; when you’re getting started, don’t change every network option at once.
When verifying the connection, check whether the client is still running in the background. Closing a window doesn’t always exit the app, and force-quitting it may leave the system proxy enabled. If regular websites stop working after you exit, check proxy status in Windows network settings, then reopen the client and disconnect normally. Don’t clear all network settings. For troubleshooting, preserve the original proxy settings and first determine whether the problem affects one browser or the whole system.
macOS: grant network permissions first
When getting the macOS client, choose the installer that matches your device from the instructions in the dashboard; don’t guess based on filenames for another platform. On first launch, macOS may ask you to confirm opening the app or allow a network extension. Check the prompt in System Settings, verify the app name, and grant permission before returning to the client to import your subscription. Until permission is granted, routes may appear in the list even though traffic isn’t going through the client as expected.
After updating the configuration, test a browser first, then check services you normally use, such as iCloud and the App Store. Apps may handle proxies differently, so don’t reinstall system network components just because one app has a problem. For guidance on permissions and chip compatibility, see Choosing a Mac VPN. For setup from installation through authorization, read the macOS setup guide.
iOS: check download eligibility and system connection prompts
Check the iOS client option in the dashboard; download access depends on whether the dashboard recognizes an active plan. In the client, use the import method provided by the dashboard or add the subscription link in the configuration section. If iOS asks to add a connection configuration, check its source and follow the system prompt to grant permission. Return to the client, update the subscription, select a route, and enable the connection. Installing the app without granting system permission does not make the configuration active.
Android: check connection permissions and background restrictions
Get the Android client from the dashboard, install it as prompted by your device, then import and update the subscription. When you connect for the first time, Android may ask you to approve a network connection request; check that it came from the correct app. If the connection drops when you switch apps or lock the screen, check the client status, then review battery management and background restrictions. Change only the settings related to the issue; there’s no need to disable battery management for every app.
Linux: distinguish desktop apps from terminal programs
Get the Linux client and install it according to the dashboard and client instructions, then import the subscription through the configuration manager. A desktop system proxy may not be used by terminal programs or background services, so if a browser works but the command line doesn’t, check how that program handles proxies. If it needs a proxy address or port, use the values currently shown in the client; don’t copy settings from another device. Never paste unknown commands with administrator privileges or expose your subscription link in a script.
| Platform | What to check | Common misconception |
|---|---|---|
| Windows | System proxy, background process, interface permissions | Assuming the connection stopped when the window closed |
| macOS | Network extension permissions, differences between apps | Assuming that seeing the configuration means permissions are granted |
| iOS | Dashboard download eligibility, system configuration prompts | Assuming that installing the app imports the subscription |
| Android | Connection permissions, background activity, battery management | Blaming a route whenever the connection drops on screen lock |
| Linux | Desktop proxy settings versus app-specific proxy settings | Assuming every program works because the browser does |
Once setup is complete, keep the smallest configuration that works reliably. Hold off on custom rules, extra proxy chains, and automatic switching. That gives you a known working state to return to if something goes wrong. If devices behave differently, compare subscription update times, selected routes, and connection modes—not just app names. The same client can have different permissions and network conditions on different platforms.
Verify your connection and choose a route
Check each layer, starting with your basic network
Disconnect the client first and check whether your device can access its current network. Complete any required web-based sign-in. Then start the client and confirm the subscription updates without errors, the right configuration is selected, and routes appear. Select a route, enable the connection, and check the client status and any system permission prompts. This sequence separates basic network access, subscription updates, and the connection itself. It avoids switching routes when the device isn’t online in the first place and helps you focus changes on the right step.
A connection indicator only tells you about the client’s current status; it doesn’t confirm that a service is accessible. First open a website you know how to check, then test the international services you plan to use. Note whether the page loads fully, whether you can sign in, and whether requests return normally. If one website fails, try another. If other services work, consider issues with the website or account before assuming every route is unavailable.
Choose a route for the task, not just its region name
When choosing a route, first check whether the target service requires a particular region, then compare how that route performs on your current network. A closer location doesn’t always mean a better end-to-end experience; local access, transit paths, the exit, and the destination service can all affect results. For meetings, interactive tools, and continuous playback, stability often matters more than a momentary response. Test on the network and at the time you’ll actually use the service rather than relying on results from somewhere else.
IEPL dedicated lines, transit, and direct connections describe how routes are organized; they are not a universal performance ranking. A dedicated line is one way to organize the link, transit uses an intermediate path, and a direct connection reduces those intermediate steps. Actual performance still depends on the entire path. See Global Nodes for route details. For a fair comparison, keep the target app, connection mode, and local network the same, changing only the route.
| Symptom | Check first | Next step |
|---|---|---|
| Subscription list is empty | Subscription address, format, update result | Copy it again from the dashboard and check the error message |
| All websites are failing | Basic network, system permissions, proxy conflicts | Disconnect and test the original network |
| Only the target service is failing | Service status, account region, current exit | Compare while keeping other conditions the same |
| Only one app is failing | Whether the app uses a proxy, app-specific network settings | Check the client’s request log and the app’s settings |
Distinguish network access from platform eligibility
AI tools and streaming platforms may use account details, exit region, risk checks, and content licensing to decide which features are available. Reaching a website does not guarantee that your account is eligible to use it. If you see a region notice, read the platform’s explanation and check the selected exit and your account details. Don’t treat one successful visit as a guarantee of ongoing access, and avoid changing regions repeatedly to test it; that can make account activity harder to assess.
When accessing AI tools such as Claude, distinguish a page that won’t load from a sign-in failure, a rejected request, or interrupted generation. For video, distinguish unavailable content from playback errors and buffering. Each points to a different check. For related guidance, see the AI guide and streaming access guide. During testing, avoid switching between clients so it stays clear which connection is being used.
Keep information you can use to reproduce the issue
When you confirm a problem, record the device platform, network type, route name, connection mode, error text, and comparisons you’ve already tried. Redact subscription links and sensitive account details from screenshots. If switching routes fixes the issue, keep a note of the original conditions for next time. If you need help, submit these details in a support ticket; they’re more useful than saying only “it doesn’t work.” You don’t need to provide your password, and no one needs your full subscription link to troubleshoot.
You’re done verifying when your usual tasks work as expected, your original network works again after you disconnect, and you know where to update the configuration. Once those checks pass, move on to regular maintenance. If things only work temporarily in a particular mode, note which apps it affects and revisit routing rules and permissions instead of applying the temporary setting to every device permanently.
Everyday maintenance and renewal checks
Use configuration updates as a regular check
An imported configuration isn’t a static list of routes. The client should still be able to retrieve updates from the subscription link in the dashboard. If route names, groups, or available options change, update the subscription first, then check that the selected route is still available. Don’t create a new account just because an old route name disappeared, and avoid keeping multiple configurations from the same source that are out of sync. The goal is to know which configuration is current and be able to check its update status.
If the client supports automatic updates, set them to suit your usage, but make sure you also know how to update manually. An automatic update can fail without removing cached routes, so a connection that still works doesn’t prove that updates are working. If the configuration hasn’t changed for a long time or shows an update error, return to the subscription section and check the address and format. After updating, confirm the right configuration is still selected; otherwise, you may have downloaded new content but continued using an older entry.
Check data usage and active status separately
Monthly plan data resets each month on the activation date. Check the relevant status in the dashboard rather than relying on the calendar month. Data packages last until used and never expire, so focus on the remaining balance. Different plans require different checks: interpret a changing data figure based on your plan type. A client that still launches doesn’t prove that your account remains eligible for the service. Check the client’s local status and your dashboard account status separately.
If data usage is higher than expected, first check every device in use and its background activity. File sync, system updates, cloud backups, and video preloading can transfer data even when you’re not actively using the device. Then check whether you’re using a connection mode with broader traffic coverage. Don’t disable essential system services just to reduce the usage figure. First identify which tasks need acceleration, then manage the scope through app settings or an appropriate routing configuration.
Confirm renewals and upgrades in the dashboard
When you want to keep using the service, check your current plan and available options in the dashboard, then review the result shown for the order. Don’t assume every payment automatically extends your existing benefits, or apply data package rules to a monthly plan and vice versa. For combinations or switching rules not specified in the available facts, rely on information clearly shown in the dashboard or a support ticket response. If you upgrade a monthly plan partway through its term, the price difference is converted into remaining days; check the calculation in the dashboard before submitting.
After renewing or changing a plan, check the order and account overview before updating your client subscription if needed. If the dashboard shows the expected status but the client still has old content, update the configuration manually and select the route again. If the dashboard itself doesn’t show the expected result, resolve the account issue first. Don’t keep deleting and recreating configurations to work around an unclear order status. Keep payment records separate from configuration errors so each can be checked at the right step.
Make multi-device maintenance easy to trace
There’s no limit on the number of devices online at once, but you should be able to identify which configuration each device uses, when it was last updated, and which mode is enabled. You can note device and configuration names without writing down the full subscription link. Before replacing a device or reinstalling its operating system, make sure you can still sign in to the dashboard. When you stop using an old device, remove its account credentials and configuration so they aren’t handed over with the device.
Before upgrading the client or system, note the current connection mode, custom rules, and required permissions. After the upgrade, run a basic check before restoring advanced settings. If something goes wrong, first compare permissions, proxy settings, and the selected configuration. Don’t routinely disable security software or system protections, and don’t use repair tools from unknown sources. For more guidance, browse the relevant category in the FAQ, or provide reproducible details in a dashboard support ticket.
Routing rules and advanced troubleshooting
Understand rule mode and global mode
Rule mode uses conditions in the configuration to decide how to route requests. Global mode typically sends requests within its coverage to the selected proxy. That coverage matters: enabling global mode doesn’t necessarily route every app through the client. Apps that don’t use the system proxy, programs with their own network settings, or traffic restricted by the operating system may take a different path. Check actual request logs to see whether a mode is working; don’t rely on its name alone.
Start advanced setup from a configuration you’ve already verified, keep the default rules, and identify the specific issue you want to solve. For example, if an app isn’t using the expected route, check whether the client can see its requests before deciding whether the issue is coverage, rule matching, or route selection. A broad rule may change the path for unrelated apps and mask the symptom temporarily, making further troubleshooting harder. After each change, verify that tasks that already worked still do.
Choosing between a system proxy and a virtual network interface
A system proxy uses the proxy settings provided by the operating system; whether an app follows them depends on how that app is built. A virtual network interface can handle traffic at a different level, but often requires additional permissions, routing, and name-resolution settings. It isn’t a switch that makes every problem disappear. If your browser and target app already work reliably, there’s no need to enable a mode just because a guide mentions it. Configure it only when there’s a clear need, one step at a time, and keep a way to restore the previous settings.
If you need to change name resolution, first check how the client handles it and whether other network tools are still active on your system. A domain that won’t resolve, a connection that times out, and a service that actively refuses a request are different kinds of errors. Don’t enter an unverified resolver address in system settings or change client resolution, system resolution, and routing all at once. Change just one thing while keeping other conditions the same so you can tell whether it fixed the original problem.
Terminal and app-specific proxy settings
Command-line programs may use environment variables or require their own proxy options; desktop settings don’t automatically apply to the terminal. If a browser works but a terminal program fails, read its proxy documentation and check whether it supports the proxy type provided by your client. Get the proxy address and port from the client’s current local listener details, not from a random online article. Never use a subscription link as a local proxy address in an app.
When checking your terminal environment, you can inspect the relevant settings for the current session first, then decide whether to save them permanently. Adding a proxy to your startup configuration can affect software updates, development tools, and background tasks later. If you’ve used another client on the device, check for leftover environment settings. Record the original values before changing them, remove anything you no longer need after testing, and check terminal output for credentials or private directory paths before sharing it.
Automatic route selection and manual comparison
If the client offers automatic route selection, its checks usually cover only the tests it runs; they may not reflect video playback, file uploads, or AI requests. Automatic selection can save time in everyday use, but if a particular service has a problem, select a route manually and compare. Keep the account, task, and local network the same during the test. Don’t treat brief recovery after frequent switching as a stable result, or generalize a single test to an entire region.
For AI tools and streaming, using a suitable, relatively stable exit can make it easier to understand where a problem comes from. The target platform may still change results based on account conditions, regional licensing, or its own policies; network settings can’t replace those requirements. This guide makes no availability promises about dedicated IPs, ongoing authorization for a specific region, or features not listed in the available facts. If you need a specific capability, confirm it through a dashboard support ticket before planning around it.
Close troubleshooting with a reproducible conclusion
After making advanced changes, you should be able to explain the original symptom, what you changed, what you tested, and the final result. If you can’t say exactly what changed, restore the saved basic configuration and try again one step at a time. When contacting support, provide the minimum steps needed to reproduce the issue; don’t submit the full sensitive configuration. Keep a practical recovery path: sign in to the dashboard, get the current subscription, import it into a compatible client, restore a basic connection, then add only the settings you actually need.
The goal of this guide isn’t to turn on as many settings as possible. It’s to help you identify problems independently and restore your connection when things change. For regular use, follow the steps in the Getting Started Guide. For plan benefits, see Plan Pricing; to choose a region, visit Global Nodes. Checking your account, configuration, device, and target service separately makes everyday use and future maintenance easier to manage.