JinVPN
Complete User Guide

Understanding cross-border connections and service boundaries

What your account, plan and client each do

JinVPN is a subscription service for cross-border connectivity. Your account manages orders, plans, subscriptions and support tickets. Your plan determines the data allowance and billing method. The client reads your subscription configuration and routes matching requests through the route you select. These parts work together, but they are not interchangeable. Being able to sign in does not mean your plan is active, and an active plan does not mean you have imported the subscription on your device.

Before you begin, follow this sequence: check your plan in the dashboard, confirm the configuration in your client, make sure your device is routing traffic through it, then test access in the target app. Skipping a step can make a client setup issue look like a payment problem, or an account restriction on a website look like a route failure. The rest of this guide follows that sequence. If something goes wrong, you can also work backward one step at a time.

What happens when you access a service

When an app sends a request, your device first resolves the domain name. The client then uses its rules to decide whether the request connects directly or goes through a route. Requests sent through a route reach the target service from its exit point, and the response travels back to your device. Your local network, the way the client handles traffic, the route and the target service all affect the result. That is why the same route can feel different on different networks.

Coverage includes 120+ countries / 150+ routes. This describes the available options; it does not mean every target service works from every location. A location name alone cannot predict your experience. The exit location affects the apparent origin of your connection, while the route and your local network affect performance. The target platform may also decide whether to provide content based on your account region, payment details or its own policies. Consider these factors separately when choosing a route.

What device support and privacy policies mean

Supported platforms include Windows / macOS / iOS / Android / Linux, with no limit on the number of devices online at once. Unlimited devices does not mean each device has a separate data allowance. Check actual usage in your account rather than treating activity on different devices as unrelated. The more devices you use, the more important it is to know which clients are still running in the background, especially on devices downloading or syncing continuously.

Anonymous, no-logs service describes the service’s privacy policy; it does not mean websites cannot identify visitors. A website you sign in to still knows which account you use. Browser sessions, website permissions and uploaded information also serve their own purposes. Changing your network exit does not replace the privacy settings in your apps. On public networks, still check website addresses, system permissions and how account credentials are stored.

Keep a way to restore your original settings

Before installing a client, make sure your device can access your usual websites normally. Note any existing proxy tools, work network settings or system VPN connections. If the network stops working later, you can tell whether the original network was already having trouble or the new configuration changed how traffic is handled. Avoid running several tools that modify system proxy settings at the same time; their controls may override one another, leaving the interface out of sync with the actual connection path.

You do not need to understand protocol details before using this guide. First set up your account and subscription, then verify the connection and adjust settings for your needs. If you just want to get connected, the getting started guide offers a shorter path. This guide keeps the checks and rollback steps for each stage, so you can refer back when switching devices, troubleshooting or adjusting traffic rules.

Choose a plan based on how you use data

First, choose between a monthly plan and a data package

Before choosing, consider whether you use the service regularly rather than starting with the largest data allowance on the page. A monthly plan suits people who prefer to manage spending month by month; its data resets monthly on the activation date. A data package lasts until it is used up and never expires, making it a better fit if you do not want a monthly allowance. The billing models differ, so comparing prices alone will not tell you which option is right for everyone.

Monthly plans include ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data packages include ¥158/300GB, ¥358/1000GB and ¥658/3000GB. The comparison below lists the stated details only, with no unverified discounts or bonus conditions. Check the full plan details and payment options on the plans and pricing page. Choose a plan and manage orders in the user dashboard.

Estimate your allowance based on how you use it

Browsing, file transfers, video streaming and cloud sync all use data differently. If you are unsure how much you need, there is no need to guess an exact figure. Check your device’s data usage to distinguish occasional browsing from sustained transfers, then monitor changes in your account after you start using the service. Video quality, autoplay and background downloads can all affect usage, so the number of times you open the client each day is not enough to estimate your needs.

If you use multiple devices, consider your computer, tablet and any other devices with the subscription imported. While one computer syncs files, streaming quality on another device and your account’s data usage may both change. Unlimited devices removes a device connection limit; it does not make data usage irrelevant. Before upgrading, check for unnecessary ongoing transfers. That can be more helpful than simply increasing your allowance.

Understand resets, upgrades and plan status

Monthly plan data resets on your activation date; do not assume it resets on the first day of each calendar month. Before making changes, check your plan status, usage and relevant dates in the dashboard. If you upgrade mid-cycle, the difference in price is converted into remaining days. Do not simply subtract the old price from the new one and assume you will receive a full new billing period. Before submitting a change, review the order details shown in the dashboard and decide whether to proceed.

A data package never expiring means you use the remaining allowance until it is gone; it does not mean unlimited data. Check the current dashboard rules to see whether a monthly plan and data package can be combined, which allowance is used first and how a change will appear. This guide does not invent stacking rules that have not been specified. If the result of a change is unclear, keep your current order details and ask support through a ticket before making repeated changes.

What else to check besides price

Payment methods include Alipay / WeChat / USDT. Choose one you can use, verify the payment with and provide transaction details for if needed. Do not proceed if you do not understand what the payment page is asking for. Pay close attention to the network and asset type, and follow the details on the payment page. Never copy payment details from chat history or search results.

When comparing cheap VPNs, look at the allowance rules, device limits, refund terms and how subscriptions are delivered—not just the lowest monthly price. Read What to expect from a low monthly budget for help matching your needs to a modest budget. Once you have chosen a plan, move on to your account and order. That way, you will not have to change billing options on the payment page.

Set up your account and check your order

Save your account credentials instead of relying on your browser

JinVPN does not require an email address. Create an account with a username and password. Open the account setup page, follow the prompts and check your entries before submitting. Choose a username you can recognize, but do not include personal details unrelated to using the service. Use a unique password rather than reusing one from another website, so a breach elsewhere does not put your subscription management at risk.

After setup, save your credentials in a trusted password manager and make sure you can sign in again through the regular login page. Do not rely solely on a browser’s autofill or leave your login saved only on a device you are using temporarily. Since an email address is not required, do not assume you can recover your account by email. Use the recovery options and support process provided in the dashboard, and store your credentials securely from the start.

Go from the information site to the account dashboard

The information pages explain the service rules. Manage your account, orders, downloads and subscription in the user dashboard. After clicking Log in, check that you are in the right account before opening the plans section. If your browser has sessions for multiple accounts, verify the username and current plan to avoid placing an order in one account and then looking for its subscription in another.

When choosing a plan, check again whether it is a monthly plan or a data package, along with the price and allowance. The data amount is part of the plan; do not remember only the price. If the item differs from what you expected, go back and choose again instead of paying first and trying to correct it with a note. If your account already has a plan, review the change details, especially how the remaining days are calculated for a mid-cycle upgrade.

Check payment and order status separately

After placing an order, follow the payment page to complete the transaction. Alipay / WeChat / USDT are supported, but use the payment option and details shown for that specific order. Do not reuse payment details from an older order. Make sure the amount matches the plan you selected. If you leave the page midway, check the original order before deciding whether to continue.

A successful message from your payment service only confirms the payment step. Return to the dashboard and check the order status and plan benefits. If the page has not updated, refresh the order or reopen the orders section, and keep your transaction receipt. Do not pay again right away. A lost connection, closed page or blocked browser redirect can interrupt the return flow, but that does not mean the original payment failed.

Tell apart pending orders, completed orders and plan issues

Check both your order history and account overview. An order still pending, a completed order with the wrong plan displayed, and a plan that appears active but does not work in the client are different issues. For a pending order, check the payment and order details. For a completed order with the wrong plan, verify the purchasing account and plan change. If the plan is active but the client cannot connect, check the subscription and client setup. Repeatedly signing in will not resolve these different states.

If you need help, open a support ticket in the dashboard. Say which step you reached, what the page shows, whether payment completed and what you have already tried. Specific details are more useful than saying “nothing works.” Screenshots should show the status and error message, with payment details, login credentials and subscription information hidden. Do not expose everything just to demonstrate the issue.

Sign out on shared devices

After managing your account on a public or borrowed device, sign out and clear any downloaded configuration files, screenshots and clipboard contents. Closing the tab does not end your session, and the browser may still autofill a saved password. If you only need to check an order temporarily, avoid importing your subscription on that device. Protect account access separately from the client configuration it manages.

Once the dashboard shows the right plan, continue to get your subscription. Use this as a checkpoint: you can sign in again, find your order, see the plan you selected and keep the payment receipt. Then, if the client has a problem, you will know the account and subscription delivery steps are complete. You will not need to keep switching between installation, payment and account settings and risk changing something that was already correct.

Get your subscription and verify its source

A subscription is more than a single route address

A subscription lets the client retrieve the routes and rules associated with your account. After import, the client usually stores a local configuration and retrieves later changes when you refresh it. So if the dashboard shows the right plan but the client still shows an old status, check where the configuration came from and when it was last updated instead of repeatedly trying to connect. Seeing routes in the list only means a local configuration is present; it does not prove that it has just refreshed successfully.

Sign in to the dashboard and open the account overview or subscription section. Follow the current instructions to get your subscription. Check the account and plan before copying a link or using the import option. Interface labels may change between clients and dashboard updates. The key is to retrieve the subscription for your account, not to look for a button in a particular screenshot. Never get a supposed universal subscription from search results or public discussions.

Automatic import vs. manual import

Automatic import uses the browser to open the client’s import function. If a prompt such as “Open app” appears, check that it will open the client you expect. Automatic import may do nothing if no app is associated with the link or the browser blocks external app launches. In that case, return to the dashboard, copy the subscription link and use the client’s configuration manager to import from a link. Do not keep clicking and create multiple copies of the same configuration.

For manual import, copy the entire link without leading or trailing spaces, line breaks or punctuation added by a chat app. Before saving, give the configuration a recognizable name, such as the brand and device purpose, so you can tell it apart from older ones. Do not put a password in the name or show subscription fields in public screenshots. After importing, make sure the configuration is selected for use, not just listed in the client.

Get the format your client supports

Different clients may require different configuration formats or import steps. Prefer the method the dashboard provides for your client. Do not simply change a file extension and try to use one format in a different client. If parsing fails, check that the app and subscription type match, then check your network and account status. Changing a lot of configuration options at once can obscure a simple mistake, such as choosing the wrong import method.

If you need to enter a link manually, the example below shows only the format of a link field; it is not a working subscription. Get your actual link from your own user dashboard. The sample domain and label are there to identify the fields and should not be saved as a real configuration. Pasting them into a client will not give you access to JinVPN routes or tell you whether your real subscription works.

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

Tell download failures from parsing failures

A download failure means the client did not receive a usable configuration response. First check that your device can open the dashboard, the link is complete, your account benefits are active and no other proxy setting is interfering. A parsing failure means the content was received, but the client could not interpret it as expected. Check the format, app source and whether the configuration was altered. Do not treat every error as a route connection problem.

Some clients let you view the result of a subscription refresh. You can check the error type while troubleshooting, but do not send the entire response to someone else; it may contain route credentials. In a support ticket, include the client platform, import method, error text and the step where the problem occurred. If you need to attach a screenshot, hide links and key fields while showing enough to identify where it failed.

Refresh, replace or handle an expired configuration

After changing a plan or configuration, try refreshing the existing subscription first, then check whether the route list has updated. If you are still using an old local file, changes to your account may not appear in the client automatically. If you need a replacement subscription, use the management options available in the dashboard and import or update it on your own devices. Do not update only the link saved in your browser and forget that other devices may still have the old configuration.

If you think your subscription has been exposed, stop sharing it and remove the public copy. Use the dashboard’s available options to manage the affected credentials; if there is no relevant option, contact support for guidance. After resolving the issue, check every device so the old configuration is not still in use. For basic guidance on credentials and public networks, see the Subscription Link Security Guide for Beginners.

Import the client on each platform

For every platform, start from the client section in the user dashboard and install using the available method. Static help pages do not provide direct download links. The steps below focus on what to do and do not assume every platform has a button with the same name. If your interface looks different, look for configuration management, subscription import, connection and network permissions rather than following screenshots from another app.

Windows: Confirm the configuration and system routing are both active

After installation, open configuration management and import from the dashboard, or paste the full subscription link in the option for adding a configuration from a link. Wait for the result, check that routes appear, then select the configuration. If configurations from other services are still listed, use their names to verify which one is active before connecting. Next, choose a route suited to the target service’s region and enable the client’s network handling feature.

On Windows, distinguish between the client running and system requests actually being routed through it. The app may be running in the system tray without system proxy enabled. Or the system proxy may be on while the target app ignores that setting. First test a regular website in your browser, then check the specific app. If your chosen routing method needs extra permissions, grant them as prompted by the system. Do not disable system security or change unrelated network settings just to clear an error.

Before closing the client, use its disconnect and exit controls so it can restore the routing settings. If the browser cannot connect after an unexpected exit, check whether the system proxy still points to the local client, then restore the original network settings. On a managed work device, do not override company proxy settings yourself. Confirm which network options are allowed before making changes, so you do not disrupt existing work connections.

macOS: Check the selected configuration and permission prompts

After installing and opening the client on macOS, import your account subscription, confirm it refreshes successfully, then select the configuration and route to use. Even if automatic import opens the client, check that the configuration was actually saved. Sometimes the browser only launches the app and the client is waiting for confirmation. Do not treat “app opened” as proof of a completed import. For manual import, check that the link is complete and refresh after saving.

If the client requests network extension or other system network permissions, verify the app’s source before granting access in System Settings. The permission prompt may appear separately from the app window. If traffic still is not routed after permission is granted, check the client status and system network settings rather than deleting every network service. If you already have work settings, another VPN or a proxy tool, pause conflicting options first and keep a way to restore the original setup before testing the connection.

iOS: Check the connection configuration after importing

Use the installation method currently shown in the dashboard for iOS. After installation, start the import from the dashboard or use a link import feature supported by the client. When switching between the browser and app, check that the subscription appears in the configuration list and that the selected item is not an example configuration. When connecting, iOS may ask you to add or enable a VPN configuration. Make sure the prompt is for the app you expect, then approve it in the system interface.

Even after the connection indicator appears, test access in the target app. If the status changes while switching apps, return to the client and check whether it disconnected or iOS is using a different VPN configuration. If websites work in the browser but not in one particular app, check traffic rules and the app’s own restrictions before deleting the subscription. After changing Wi-Fi networks, verify the connection again rather than relying on the previous test.

Android: Handle VPN permission and background activity

After installing the client on Android, import the subscription, select the configuration and start the connection. When Android asks to authorize a local VPN connection, confirm that the requesting app is the right one. If another tool on the device uses the same traffic handling capability, decide which app should manage the network. Multiple tools competing for control may fail to route traffic even if each app opens normally, causing the connection to switch repeatedly or the target app to use an unexpected route.

If the connection works in the foreground but drops when the screen locks or you switch apps, check the system’s background activity and battery settings for the client. Menu names vary by device; adjust only what is needed to maintain the connection rather than granting every permission. Some clients support per-app routing. If just one app has a problem, check whether it is excluded. If a subscription refresh fails, bring the client to the foreground and refresh manually to rule out background restrictions leaving an old configuration in place.

Linux: Check desktop proxy settings separately from the terminal

On Linux, get the client according to the requirements shown in the dashboard, then import your subscription. A desktop client’s system proxy setting may not be used by terminal commands or every desktop app. Test the browser and target program separately; browser access alone does not prove that all system requests use a route. If you use environment variables to set a proxy, limit them to the programs that need them and keep a way to unset them.

You can check the current proxy environment variables in a terminal, but the output may include private settings, so do not publish it as-is. The command below only lists variables and does not change your network. If you see an old proxy value, check whether the current client still uses it before changing anything. This guide does not specify a fixed local port; use the value shown in the client’s current settings.

printenv | grep -iE '^(http|https|all|no)_proxy='

The completion checks are the same across platforms: the configuration has been retrieved, the right item is selected, traffic handling is enabled and the target app has been tested. If any step is incomplete, fix that step before copying unfamiliar settings from another platform. Once the basic connection works, move on to checking your exit location and traffic rules. This separates installation issues from access issues and gives you a clear starting point for troubleshooting.

Check your exit IP, DNS resolution and app access

A connection indicator is the start, not the final check

When the client says connected, it usually means it has started the connection or traffic handling feature. You still need to verify whether the target app is using that path. Keep your current configuration unchanged at first. Open a familiar website to confirm basic access, then test the service you actually need. Do not change routes, rules and networks all at once; if the result changes, you will not know which change caused it.

Start with the IP lookup page to see the exit information for your current browser request. That result applies to this request only; it does not prove that every app on your device uses the same route. With split routing, the lookup page may connect directly while an international website uses a route. An unchanged exit IP does not necessarily mean the client has failed. Check which rule matched the request rather than relying only on the displayed location.

Interpret test results based on the request path

If the test shows a different region than expected, first confirm that the intended route is selected. Then check whether the client is handling system traffic and whether the test domain is routed according to its rules. Some apps keep a connection open or cache results, so reconnect to the target service after switching routes. Do not conclude that a route is wrong based on one location result, and do not mistake a website account’s region for your current network exit.

DNS resolution converts a domain name into an address that can be reached. It is related to your exit path, but it is not the same measure. Browsers, operating systems and clients may each have their own DNS settings. If a page stalls during resolution, check for conflicts between the client’s DNS status and browser settings. Do not copy DNS addresses from random online sources. Restore the client’s normal settings first, then check custom options one at a time.

Separate account, network and app issues

If the dashboard says your plan is unavailable or the allowance is used up, resolve the account issue first. If the subscription will not refresh, check the link and import process. If routes are listed but every request fails, check traffic handling and the route connection. If only one target app fails, focus on per-app routing, account permissions, regional requirements and the service’s own status. Troubleshooting in layers avoids rebuilding configurations that are already correct.

How to check video services and AI tools

For streaming, check separately whether the page opens, your account can play content, the specific title is available and playback stays stable. Libraries and permissions can change under platform policies, so opening a page does not guarantee access to all content. Start with an exit location that matches your target region, keep other test conditions the same and check actual playback. For more on these limitations, see the streaming access guide.

For AI tools, separate network access from platform eligibility. Reaching the sign-in page does not mean your account has permission to use the service. A dropped long connection, failed upload and account notice may each have a different cause. Check the platform’s current requirements, keep your exit location consistent and avoid switching regions frequently while signing in or working on a task. For Discord and image generation workflows, read Choosing a route for Midjourney and Discord.

How to record a repeatable connection test

Record the device platform, current client configuration, selected region, network type, target app and error message. Then change only one condition—for example, switch to a different network or choose another route suited to the target region—and note whether the result changes. This comparison is more useful than changing several settings in a row and helps support determine whether the issue is with your local network or a specific route.

After testing, restore any temporary traffic handling options and custom settings to the state you intend to use, so test configurations are not left running in the background. For more detailed steps to check your exit IP and DNS, read the Exit IP and DNS Check Guide. When the connection works, keep a settings record without credentials as a baseline for comparison if problems arise later.

Manage usage, configurations and renewals

Check your account and devices separately

Routine maintenance does not require frequent setting changes. It is more useful to check your plan status and data usage in the dashboard from time to time, then make sure the client can refresh its subscription. Your account determines whether your plan benefits are available; your device determines whether it has the right configuration. If both are fine, you do not need to reimport just to change what the interface displays. If something goes wrong, identify which side changed before taking action.

Monthly plan data resets every month on your activation date, not on a single calendar-month reset date. If you are close to your allowance, check background sync, automatic updates, ongoing downloads and usage on other devices first. Data packages are used until their remaining allowance runs out and never expire. Use dashboard records to check usage. Your device’s app statistics can help identify where data went, but the two sources may track different things.

Keep a checklist before renewing or upgrading

When you want to continue using the service, check the available renewal options in the plan and orders section of the dashboard. Confirm the plan name, amount and status after submitting. An order being created does not mean your plan has been renewed. After payment, return to the dashboard to confirm the result, then refresh the client subscription. If the original subscription is unchanged, you usually do not need to reinstall the app; first check whether the configuration and account status have synced.

For a mid-cycle upgrade, the price difference is converted into remaining days. Read the change details in the dashboard before submitting; do not assume you will get an extra full billing period. Do not assume how old allowance will be combined when switching between a data package and monthly plan. If the change details are unclear, ask through a support ticket and keep a record of your current plan before making changes. This helps avoid confusion from switching between orders repeatedly.

Subscription updates and client updates serve different purposes

Refreshing a subscription retrieves changes to the routes and rules associated with your account. Updating the client updates the local app. One does not replace the other. If your route list is outdated, refresh the subscription first. If the app cannot recognize a new configuration or reports a specific compatibility issue, check for a client update using the method shown in the dashboard. Do not download replacement installers from unknown sites or use unfamiliar conversion services to modify a configuration.

Before updating the client, note the configuration name, traffic handling mode and custom rules. Do not write the full subscription link in an ordinary note. After the update, verify the basic connection before restoring any custom settings you still need. If the update causes a problem, record the error and what changed, then contact support. Repeatedly installing old programs from unknown sources makes your system state harder to troubleshoot.

Keep an inventory of configurations across devices

There is no limit on devices online at once, so it is especially useful to know which devices have your subscription. Keep a list of each device’s purpose, platform and whether it is still in use, but do not record passwords or full links. After replacing a subscription or handling an exposure, update each device on the list so an old configuration is not left running somewhere. Disconnect devices you are not using, especially computers that may still transfer data in the background unnoticed.

If usage differs from what you expected, check your own devices and background tasks first. Do not post screenshots publicly; they may reveal account details, subscription content or order information. If the change remains unexplained, open a support ticket with what you observed and which devices you checked. Keep the information shown in the dashboard. Do not blame a specific cause without evidence; let support help investigate.

Prepare refund and support information

JinVPN offers a 60-day money-back guarantee. See the Terms of Service for details. For an order or refund issue, provide the required order information in a dashboard support ticket and follow the support process. Do not treat a refund request, subscription refresh and client uninstall as the same task. Removing the app does not process an account order; check your account status in the dashboard.

Keep support notes brief but useful: when the issue appeared, what happened, whether the account is in good standing, whether the client refreshed and whether changing networks made a difference. There is no need to submit long, unfiltered logs. Logs may contain configuration details and destination addresses, so review them before sharing. A short record that helps reproduce the problem is usually more useful than repeatedly saying “the speed is bad.”

Adjust traffic rules and routes to fit your needs

Choosing between rule-based routing and other traffic handling modes

Consider advanced settings only after the basic connection works. Rule-based routing sends requests along different paths according to conditions such as domain, address or app, which is useful for handling different kinds of traffic separately. Other traffic handling modes may affect a broader range of requests, depending on the client and system permissions. Do not assume what a mode does from its name alone. After switching modes, test the target app rather than relying only on the toggle.

With rule-based routing, local websites, international services and local network resources can use different paths. If an app is not using the expected route, check the client’s rule-matching information to see which condition applied before making changes. Sending all traffic through a route might change the symptom temporarily, but it also changes how other apps connect and does not explain the original rule issue.

Route types offer clues, not guarantees

When choosing a route, consider its location and type. IEPL, relay and direct routes describe different network arrangements, but results also depend on your local connection, destination and current path. A route name alone cannot tell you that every app will be faster, and distance is not the only factor. First narrow your options to regions the target service accepts, then compare actual performance under the same conditions and keep a stable option.

For coverage and route details, see the network page. The region in a route name indicates the direction of the exit, but platforms may not all determine your location in the same way. For streaming or tools with regional eligibility requirements, consider the target website’s account rules and policies as well. Avoid repeatedly switching regions for a particular page; doing so can combine network changes with account risk controls.

Keep local network access available when you need it

When using printers, file shares or local network admin pages, check that requests to those resources still connect directly. If they become unreachable after enabling broader traffic handling, check the relevant rules and local network access settings first. Do not immediately change your router or open unnecessary ports. Check the client’s actual features and permissions for local network access; this guide does not make unsupported promises about network deployment based on desktop connection features.

If a target app has its own proxy settings, it may ignore the system proxy. Before troubleshooting, determine whether the app uses system settings, its own settings or another network interface, then make changes in the right place. Keep a single, clear point of control when multiple configuration layers exist. Do not enter a local address and port in the app at random; check the corresponding values in the client’s current settings.

Keep command-line and custom settings changes to a minimum

Terminal programs may read proxy environment variables, while browsers may use system settings or their own configuration. Different results do not necessarily indicate a problem. If you need custom settings, record the original values, change only what is relevant to the target program, then test and keep a way to roll back. Do not copy settings directly from someone else’s device: local listening methods, permissions and client formats may differ, and identical-looking fields may not work the same way.

For long-running connections or continuous uploads, keep the exit location and traffic handling mode consistent when possible. Switching routes may force existing sessions to reconnect, so avoid repeated tests during important work. If a task fails, first check whether the app supports retrying or resuming, then see whether the network still works. For AI tools, video and file transfers, record network stability separately from platform rules. A single app error does not tell you the status of the whole service.

Turn this guide into a repeatable workflow

If a new setting does not produce a clear improvement, restore the original value instead of adding more unfamiliar parameters. Connection problems need evidence you can compare, not an ever-longer configuration. If the cause is unclear, narrow it down to one layer—account, subscription, client traffic handling, route or target app—and continue troubleshooting there. This is more effective than repeating every installation step and reduces the risk of changing settings that were already correct.

Once you have finished this guide, routine use can stay simple: check your plan in the dashboard, refresh the right subscription, choose a suitable region and confirm access in the app. For a refresher, return to the getting started guide. To compare costs, see plans and pricing. If you still cannot find the cause, open a support ticket with the symptoms and checks you have recorded. Do not include your password or full subscription link.