JrVPN Complete User Guide

CHAPTER A

How cross-border network acceleration works

What the client, subscription, and routes each do

When using JrVPN, the three concepts most often confused are the client, subscription, and route. A client is the connection tool installed on Windows, macOS, iOS, Android, or Linux. It reads configuration, establishes the connection, and handles network requests according to its rules. A subscription is a set of configuration entry points provided in the user panel, including available routes and their required parameters. A route is the network path that carries your traffic, usually identified by country, region, or city. All three are essential: with a client but no subscription, the software does not know where to connect; with a subscription but no compatible client, the device cannot execute the configuration; and with an imported subscription but no available route selected, no connection is actually established.

A subscription link is not an ordinary webpage address. When a client accesses it, the client reads the configuration associated with the current account plan and organizes the route list locally. If the plan status, route names, or available configurations change, they are usually synchronized by updating the subscription rather than copying every route again. Because a subscription carries account-specific configuration, protect it like a password. Do not post it in public chats, screenshots, or shared documents, and do not submit it to untrusted online conversion tools. If you suspect exposure, manage the credentials in the user panel, then re-import the subscription on every device.

What happens during a connection

Once the connection is enabled, requests from an app are first handled by the local client. Based on the current mode, the client decides which requests use the selected route and which continue over the local network. It then establishes an encrypted connection for forwarded traffic, sends it through the chosen exit region, and lets that exit access the target service. Responses travel back to the client in the opposite direction before being passed to the browser or app. “Acceleration” does not mean every website will mechanically become faster. More precisely, it describes optimizing cross-border paths by reducing unstable detours, switching to a more suitable exit, and keeping connection policies consistent across the same device.

The final experience is shaped by the local access network, selected region, target service, and device state. A nearer route is generally helpful for everyday browsing and interactive use, but some content or work accounts require a specific exit region, making regional matching more important than physical distance. Crowded Wi-Fi, large downloads, or power-saving policies that restrict background connections can also make a “route problem” look like a service failure. Troubleshooting therefore requires checking the local network, client state, subscription state, and specific route separately; a slow webpage alone is not enough to conclude that every route is affected.

Monthly plans vs. data packages

JrVPN offers monthly plans and data packages. Monthly plans are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; data resets monthly on the activation date, and mid-cycle upgrades convert the price difference into remaining days. Data packages are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB; they last until used and never expire. Monthly plans suit steady usage with a fixed allowance each cycle, while data packages suit occasional use where unused data should remain available. They address different billing needs, so do not compare them by headline volume alone.

All plans support unlimited simultaneous devices, but “unlimited devices” does not mean data use will not add up. Video playback on a computer, file syncing on a tablet, system updates, and downloads on other devices all draw from the same plan. When several people or devices share an account, identify the main sources of traffic before choosing an allowance rather than counting installed clients. For a more practical estimate of browsing, work, and video usage, read How to Choose Between Data Packages and Monthly Plans.

JrVPN covers 100+ countries / 160+ routes. This range provides regional choice; it does not mean every situation calls for the farthest or most complex path. For a first connection, choose a relatively nearby route with a clear purpose and confirm the basic path before comparing other regions. Once this is clear, plan selection, platform setup, and fault isolation become easier: the account determines access, the plan determines allowance and validity, the subscription delivers configuration, the client executes it, and the route carries the connection.

CHAPTER B

Choose a plan and route range based on how you use the service

Estimate your use case before guessing your data needs

When choosing a plan, break everyday use into observable scenarios. Light browsing usually consists of webpages, text messages, searches, and a few images. Work may include online documents, code repositories, meetings, file syncing, and AI Tools. Video and audio use depends on quality, viewing time, and autoplay. Avoid judging by vague labels such as “occasional” or “frequent,” because text searches and high-definition video can consume very different amounts of data at the same frequency. A more practical approach is to observe device traffic during a normal work cycle, then decide between a monthly plan and a data package based on whether you need continuous long-term access.

If your habits are steady and each cycle involves similar work or entertainment, a monthly plan makes budgeting easier. ¥9.9/month with 60GB suits light browsing and occasional access; ¥18/month with 250GB leaves more room for sustained work, study, and multi-app use; ¥28/month with 500GB is better suited to frequent video and audio, heavier file transfers, or shared use across devices. The key factors are continuity and concurrent traffic sources, not mechanically matching an allowance to a job or identity.

When to consider a data package that never expires

If your usage has clear gaps—for example, concentrated access during business trips, project collaboration, or specific research, with little connection at other times—a reset-each-cycle allowance may go partly unused. In that case, compare the ¥158/300GB, ¥358/1000GB, and ¥658/3000GB data packages. They last until used and never expire, so the remaining data is not reset at a monthly boundary. They suit users who want a long-term data reserve and work well as a standalone option for irregular usage.

A data package still requires managing background traffic. System updates, cloud syncing, photo backups, and automatic app downloads may continue after the connection is enabled. If you want data limited to specific apps, use rule mode or per-app proxying where supported by the client. If cross-border access is not needed for the moment, disconnect deliberately. Non-expiring data removes time pressure; it does not eliminate the need to monitor background activity. With multiple devices online, check regularly which device is carrying most of the traffic.

How to think about a mid-cycle upgrade

For a mid-cycle monthly-plan upgrade, the price difference is converted into remaining days. Before changing plans, confirm the current cycle, remaining allowance, and upcoming needs instead of changing a long-term plan because of one temporary download. If a large transfer is short-lived, first consider whether it can be split, completed directly over the local network, or truly requires the current route. An upgrade makes more sense when usage will remain higher in every following cycle. The final order details shown in the panel are the reference point; before payment, check the plan name, price, and payment method item by item.

Payment methods include Alipay, WeChat Pay, and USDT. The interface may differ between payment entries, but the logic is the same: confirm the order, complete payment, and return to the user panel to check the status. Do not submit the same order repeatedly after payment. If the page has not updated, refresh the order status or sign in to the panel again before paying again. If the payment status does not match the result, submit the order details through the panel’s ticket entry for support to review.

Evaluate the plan and route separately

An allowance answers “how much can be transferred”; a route answers “where requests exit and how the path is organized.” Buying more data does not automatically make a route better for every website, and switching to a more distant region does not add data to the plan. For everyday webpages and interactive apps, start with a nearer region. When an account, content, or work environment has a specific regional requirement, choose the matching exit. See route types and regions in the server list. When comparing routes, keep the local network and client mode unchanged so you can identify the source of any difference.

All plans include unlimited simultaneous devices and a 7-day no-questions-asked refund. The refund policy reduces uncertainty for a first choice, but you should still match the plan to your actual needs before paying. The soundest decision is not simply the largest allowance; it is the best fit between cycle, data, and usage: compare monthly plans for steady use, data packages for intermittent use, background traffic for multi-device setups, and exit region as a separate condition when a specific location is required.

CHAPTER C

Complete account setup, ordering, and status checks

Create an account you can protect long term

JrVPN requires no email address for account creation; a username and password are enough. On the registration page in the user panel, choose a username used only for this service, then set a password that is not reused elsewhere. The username identifies the login, so avoid confusing character combinations. Store the password in a trusted password manager. Because no email address is required, account recovery cannot rely on the usual email flow, making it especially important to save your login details carefully when the account is created rather than relying on temporary browser memory.

After creating the account, sign out and sign in again once to verify that the saved username and password work. It may seem basic, but this can catch entry or storage mistakes before payment. If several devices need panel access, do not save the login state on a public device or forward account credentials through public messages. The subscription can be imported on unlimited devices, but panel access and subscription links are sensitive information and should be shared only with the person responsible for maintaining the account.

Check the plan and payment entry before ordering

In the Plans area, use the estimate from the previous section to choose a monthly plan or data package. Monthly options are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; data packages are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Before submitting, confirm the plan name, data rules, and final amount. Monthly data resets on the activation date, while data packages last until used and never expire. Do not confuse the two rules.

Payment methods are Alipay, WeChat Pay, and USDT. After choosing an entry, complete payment within the current order flow and retain the necessary record for identifying the order. If payment returns you to the panel, first check whether the order status has updated. A closed browser, brief network change, or delayed page display does not automatically mean payment failed. Most importantly, avoid creating and paying for the same order again before the result is confirmed. If the status remains inconsistent, explain the situation through the ticket area in the user panel rather than repeating actions across multiple pages.

How to tell whether the service is active after payment

After payment, the user panel should show the current plan, data status, and subscription entry. Do not rush to configure every device at once. Start by completing the first import on the device you know best. Once the first connection works, gradually configure the subscription on other devices under the same account. If a problem appears, this makes it easier to distinguish an account-state issue from subscription content or platform permissions instead of facing simultaneous failures on several devices with no clear cause.

If the panel still shows the old status, refresh the page or sign in again before checking. If payment is confirmed but the service status has not updated, use the ticket entry in the panel and submit the relevant order information. Do not post payment records, account passwords, or complete subscription links publicly. Keep the ticket focused on the selected plan, payment method, current panel status, and checks already performed so support can follow the same trail.

Basic checks after initial setup

Once the account is active, check the current plan name, data rules, subscription entry, and client download entry in order. Both client downloads and subscriptions come from the user panel; the marketing pages do not provide static direct links to installation packages. This avoids using configuration that does not match the account state and makes future updates easier. Windows, macOS, iOS, Android, and Linux may use different acquisition methods, so select the entry for the current device in the panel rather than applying one platform’s installation file or import method to another.

For long-term use across several devices, list each device’s role first: the main computer for work, mobile devices for occasional access, and other devices for video, audio, or testing. Then decide which devices need a persistent connection and which should connect only when needed. Unlimited simultaneous devices provide configuration flexibility, but clear roles make traffic control and troubleshooting easier. On devices with heavy cloud syncing, system updates, or media apps, inspect background activity after importing before deciding whether to keep a global connection enabled.

The account stage is complete only after these checks. Next, focus on obtaining the subscription safely, choosing the right client, and verifying the import. For the shortest path, return to Quick Start and follow the main flow. To understand subscription updates, credential protection, and multi-device syncing, continue to the next section.

CHAPTER D

Get, import, and protect your subscription

Get the correct entry from the user panel

Get the subscription from the logged-in user panel, not from chat history, search results, or a third-party sharing page. In the download or subscription area, choose the client and import method for the current device. Some clients can be opened directly with a button; some platforms require you to copy the subscription address and paste it into the client. In either case, confirm that it belongs to the current account and plan rather than an old saved address.

After import, the client will usually show routes organized by region or purpose. Seeing a route list does not mean a connection has been established; it only confirms that the client read the configuration successfully. You still need to choose a route, grant system network permission, and enable the connection. If the list is empty, first update the subscription, then check whether the plan is active, the copied content is complete, and the client supports that subscription format. Do not add several identical configurations before finding the cause, or the client will fill with duplicates that are harder to maintain.

Why subscription links must be handled as credentials

A subscription address usually contains credentials used to identify account configuration. Anyone with the complete address may be able to read the associated routes, so do not publish it as if it were an ordinary download link. Hide the full address in screenshots and do not display it in a public ticket area. To transfer it between your own devices, use a trusted password manager or a secure device-to-device method. After importing, clear the complete value from the system clipboard and temporary notes.

The examples below use non-functional addresses solely to illustrate the format. They show the structure commonly seen in a client input field, do not represent JrVPN’s real subscription domain, and contain no valid credentials.

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

If a subscription accidentally appears in a public group, shared document, or screen recording, treat it as exposed rather than simply deleting the message. Removing public content cannot confirm whether it was copied. Instead, manage the subscription credentials in the user panel, delete the old configuration from your own clients, then obtain and import a new configuration. Check each device afterward so an infrequently used device does not retain the old subscription.

Import, update, and replace: what is the difference?

“Import” creates a new configuration in the client. “Update” rereads subscription content while keeping the local item. “Replace” may overwrite a same-named configuration or remove local changes. Use import for first-time setup and update when the route list needs synchronization. Consider deleting and importing again only after confirming that the old configuration is invalid or duplicated. If the client supports automatic updates, enable a sensible refresh schedule, but still know where manual updates are located so you can sync changes when needed.

Some clients let you rename a subscription. Use a name that identifies its purpose and account, but do not put the password, complete subscription address, or payment details in the name. Across multiple devices, keeping the subscription name consistent makes remote guidance and troubleshooting easier. Do not edit internal route parameters and expect every local change to survive an update; some clients prioritize remote configuration during updates. For custom rules, use the client’s dedicated override or rules area where available.

Troubleshoot import failures layer by layer

First confirm that the device itself can access the user panel normally. If the panel cannot open, fix the local network before changing the subscription repeatedly. Next confirm that the plan is active and the subscription entry is visible. Copy the complete address again, taking care not to include extra spaces, line breaks, or punctuation. Then verify that the client matches the current platform and that you selected an import entry such as “From URL” or “Subscription” rather than a local configuration file. Finally, check the system date and network permissions, since a clearly incorrect system environment can interfere with establishing a secure connection.

If the subscription updates but routes cannot connect, the issue has moved from “subscription delivery” to the “route or system connection” stage; continue with the connection verification section. If only one device cannot update while others use the same account normally, first check that device’s client permissions, leftover system proxy settings, and network environment. If every device cannot read the subscription at the same time, return to the user panel and confirm the plan and subscription status. Separating the scope of the failure quickly shows whether the problem is account-side or device-side.

For the full logic of obtaining, importing, and handling an exposed subscription, read the Beginner’s Guide to Subscription Links. The principle is the same on every platform: get subscriptions only from the user panel, protect the complete address as an account credential, confirm the current configuration before updating, and replace the credentials on every device after exposure.

CHAPTER E

Import client configuration on five platforms

Windows: handle system permissions and leftover proxy settings first

On Windows, open the download area in the user panel and get the appropriate client. On first launch, Windows may request network-related permission; verify that the program came from the panel entry before allowing it. Open the client’s subscription manager, paste the address copied from the panel, and update. Once the route list appears, start with a relatively nearby route, then enable the system proxy or connection switch. Test a website that normally works and a service that requires a cross-border route to confirm local access and proxied access separately.

A common Windows issue is that the system proxy remains enabled after the client closes, causing every webpage to fail. Reopen the client, turn off the system proxy, and then exit normally. If the client will not start, check the proxy status in Windows network settings. Security software may also block virtual network components; review system notices and client logs. Do not install several similar clients and let them compete for the system proxy. During troubleshooting, keep only one client connected.

macOS: confirm network extension authorization

The first time a network client is used on macOS, the system usually asks you to approve a network extension or VPN configuration. If routes are visible after importing but the switch will not stay on, check for an authorization prompt, then confirm in network settings that the related configuration is allowed. Do not keep clicking Connect in the menu bar; without system authorization, the client may briefly show a connecting state even though no network channel has been established.

If other network filters, enterprise security settings, or an old client are enabled on the device, check whether they are using the same system capability. Temporarily quit the other tools and verify JrVPN’s client on its own. Once the connection works, restore the other software one item at a time to identify conflicts. If the network changes after macOS wakes from sleep, disconnect and reconnect. If the route list is outdated, update the subscription manually and choose a route again instead of deleting the whole app.

iOS: distinguish imported configuration from system connection permission

Open the iOS client through the entry provided in the user panel. After obtaining the subscription, use the panel-supported import method to open the client, or add the subscription address inside the client. The first time you connect, iOS asks to add a VPN configuration; this permission is required to create the system network channel. Approve it, return to the client, select a route, and connect. The status bar or system network settings can help confirm that the channel is enabled, but verify the exit region and target service through actual access.

When switching between mobile data and Wi-Fi, the existing connection may need to be rebuilt. If an app still uses its old network state after connecting, fully close and reopen it. With data-saving mode or a managed device, some background activity may be restricted, so complete the first verification under normal network conditions. If the subscription will not update, first confirm that the panel opens in a browser, then check that the copied address is complete. Do not use an untrusted webpage to convert the subscription format.

Android: check background operation and battery policies first

Android interfaces vary widely between devices, but the workflow is consistent: get the client from the user panel, import the subscription, choose a route, allow the VPN connection, and verify access. The most common issue is not import failure but the client being stopped by battery-saving policies in the background. The connection works at first, then drops after the screen locks or the app is switched away. In system app settings, allow the client to run in the background and adjust restrictions using the battery-management options provided by the device.

If you want only selected apps to use the route, use per-app proxying where the client supports it. Check whether the setting means “proxy only selected apps” or “exclude selected apps”; the two options are opposites. After changing it, test the target app in practice rather than relying on the client switch. For detailed handling of background operation, battery-saving policies, and per-app proxying, continue with Android Selection and Configuration Guide.

Linux: confirm the runtime method and environment variables

How you use Linux depends on the client entry in the user panel and your desktop environment. A graphical client can import the subscription through the same general workflow as other desktop platforms. Command-line tools should store configuration in the user directory with restricted permissions on sensitive files. Do not put the complete subscription address in a public script, terminal screenshot, or configuration file that syncs to a code repository. For a temporary proxy test, set the current terminal variables to the address actually listened to by the local client; the example below shows structure only, and the port must match the client interface.

export HTTP_PROXY="http://127.0.0.1:LOCAL_PORT"
export HTTPS_PROXY="http://127.0.0.1:LOCAL_PORT"

curl https://example.com

unset HTTP_PROXY
unset HTTPS_PROXY

After testing, clear the current terminal variables so later commands do not try to use a nonexistent local proxy after the client closes. If system services, containers, or graphical apps also need the connection, do not assume terminal variables will apply to them; check each network configuration separately. Linux troubleshooting especially requires distinguishing system-level routes, desktop proxy settings, and per-process environment variables. They can coexist or override one another.

The five platforms have different interfaces, but the decision flow is the same: confirm the account is active, get the correct client from the panel, import the subscription, allow system network permissions, choose a route, enable the connection, and verify it through actual access. When troubleshooting, do not copy button names across platforms; find the equivalent function in the right place. Configure one device before moving to the next so account issues remain separate from platform issues. Unlimited simultaneous devices make multi-device deployment easier, but each device still needs independent maintenance for client permissions, subscription updates, and background activity.

CHAPTER F

Establish a connection and verify the route

Change only one condition during the first connection

During the first verification, keep the local network, client mode, and target website unchanged; switch only the route. Start with a relatively nearby region suited to the task, confirm that the client reports a connection, and then test in a browser. Do not change the network, modify DNS, enable complex rules, and switch among several regions at the same time. Even if service returns, you will not know which change helped. The key is controlled testing: change one condition at a time, record the result, and decide the next step.

Confirm connection status at three levels. At the client level, check the switch and error messages. At the network level, confirm that ordinary webpages still load. At the application level, check whether the actual target service works. A successful client status only means the local channel was established; it does not guarantee that the target service accepts the current exit region. Conversely, one app failing does not prove the entire route is down; the cause may be account region, cache, app state, or access rules.

How to choose a region and route type

For everyday browsing, searches, and interactive apps, start with a geographically nearer exit to reduce path length. When accessing region-specific content, satisfy the required exit region first, then compare other routes in that region. If a cross-region work account is used from one region long term, frequent exit changes may trigger extra verification, so keep the pattern consistent. See the complete regions and route types on the Servers page.

IEPL dedicated routes, relay routes, and direct connections describe different ways of organizing the path. Dedicated and relay routes focus more on the organization and stability of cross-border paths, while direct connections depend more heavily on the actual network conditions between the local carrier and the exit. No type can be declared universally faster without considering the local network. Compare them on the same device, access network, and target service, while observing webpage response, video buffering, file transfers, and long-lived connections against your main needs.

Do not verify the exit using only one page

Practical verification has two parts: basic access and target access. Basic access confirms that the client has not disrupted the local network; target access confirms the region and application scenario. If all basic webpages fail, check the system proxy, network permissions, and client logs. If basic access works but the target app fails, check the route region, app cache, account state, and rule mode. If the browser works but a standalone app does not, the app may not be handled by the current mode; on Android, also check per-app proxy settings.

After switching routes, a browser or app may retain an old connection. Close and reopen the target page or app, and if necessary clear site sessions related to regional detection before testing again. Do not rapidly switch through many regions and repeatedly sign in to the same account; this can make the target service see an unstable network environment. For AI Tools with stricter regional detection, see Claude Region Detection and Route Selection Tips. The same principle applies to other services that require a stable exit environment.

Layered handling for connection failures

If no route connects, first close the client and confirm that the local network works normally. Then check the plan status and subscription update, restart the client, and grant the required permissions again. If only the current device fails while others work, the cause is usually system permissions, leftover proxy settings, background restrictions, or client configuration. If several devices fail on the same network, compare with another normal access network to determine whether the local network is involved.

If only one route fails, switch to another route in the same region, then try a nearby region. A single route issue does not require deleting the entire subscription or resetting the account. If the connection works but speed is below expectations, pause cloud syncing, system updates, and other downloads on the device before comparing again. Weak Wi-Fi or shared bandwidth affects every route. Rule out local congestion first; only then is a route comparison meaningful.

Find actionable information in the logs

Client logs help identify the layer where a failure occurs, such as subscription read errors, denied network permissions, route connection timeouts, or local port conflicts. When submitting a ticket, include only error details directly related to the current issue, and remove the complete subscription address, account password, and other private content. State the platform, local network type, whether all routes are affected, whether other devices work, and which steps you have already tried. This is usually more useful than simply writing “cannot connect.”

After troubleshooting, remove any temporary system proxy, environment variable, or global mode added for testing, and restore the configuration you actually need. The goal is not to stack settings but to find the smallest stable combination. For most users, one primary route for everyday use, one backup region, a clear subscription-update entry, and a repeatable troubleshooting order cover common situations.

CHAPTER G

Handle daily maintenance, data use, and renewals

Update the subscription regularly instead of reinstalling repeatedly

When the route list changes, update the subscription first. Reinstalling the client clears local settings but may not fix an outdated subscription or account-state issue. Remember where subscription management is located, and update first when route names, regions, or configuration differ from the panel. If the issue persists after updating, check the plan and system permissions. With multiple devices, update each one separately; updating one device does not change the local configuration on others.

If the client supports automatic updates, use them as a supplement rather than relying on them completely. A device that stays offline, restricts background tasks, or has a closed client may not update automatically. Before a business trip or important work, open the client and check the subscription and routes proactively instead of discovering an outdated configuration on site. After updating, there is no need to test every route; confirm only that the primary and backup routes connect normally.

Manage data use across multiple devices

JrVPN supports unlimited simultaneous devices, but every active device may consume plan data. Computer system updates, cloud syncing, automatic video and audio playback, and photo backups on mobile devices often generate more sustained traffic than web browsing. Monthly-plan data resets each month on the activation date, while data packages last until used and never expire. Whichever option you choose, check usage in the user panel and identify high-traffic apps in the device settings.

If a device only needs occasional access to a specific service, it does not need a permanent global connection. Enable it when needed and disconnect afterward. Where supported, rule mode can let local services continue using the original network. Android per-app proxying is especially useful for limiting the connection to the apps that need it. On Windows, macOS, and Linux, watch cloud-sync tools and development environments, which may continuously fetch dependencies or files in the background.

Renewals, upgrades, and data-package management

Monthly-plan users should understand the cycle from the activation date rather than infer resets from the calendar month. Before renewing, review the current plan and usage status to confirm that it still fits the next cycle. If usage remains above the current allowance, compare a higher monthly plan; a mid-cycle upgrade converts the price difference into remaining days. If usage is irregular, reassess whether a data package is more suitable. Base the decision on long-term patterns, not one unusual download.

Data-package users do not face cycle resets, but should still monitor the balance and background tasks. Never-expiring data means the remaining allowance stays available; it does not mean credentials can be neglected. Keep the username and password safe and confirm periodically that the client can still update the subscription. When replacing the main device, import and verify on the new device first, then remove the subscription from the old one so usable configuration is not lost during migration.

Checks after client and system updates

Operating-system or client updates may change network permissions, background policies, and system-proxy behavior. After an update, run a basic connection test: confirm that the subscription can be read, the connection switch works, and the target app behaves normally. On Windows, check that the system proxy follows the client state. On macOS and iOS, confirm that the network configuration is still allowed. On Android, review whether battery-saving policies returned to their defaults. On Linux, check services, routes, and terminal environment variables.

If a problem appears after an update, do not immediately restore a large set of old settings. First quit other network tools and test the default mode with one familiar route. If the default configuration works, restore custom rules one at a time. This identifies whether the client’s core connection is failing or an old rule is incompatible with the new environment. Never upload complete subscription credentials to a public issue platform; when support is needed, submit redacted logs through the user panel.

Account and subscription security habits

Treat the username and password as account-access credentials, and the subscription link as configuration-access credentials. Do not reuse the password on other websites, include the subscription in public screenshots, or save the login state on a public device. If you temporarily connect using someone else’s device, delete the subscription and sign out afterward. Before selling, giving away, or disposing of an old device, clear its client configuration and browser login information.

On public Wi-Fi, first confirm that you are connected to the intended network, then start the client. Do not ignore webpage certificate warnings, suspicious login pages, or files from unknown sources just because a network acceleration service is enabled. For basic principles covering accounts, subscriptions, and public networks, read the Beginner’s Security Guide. These habits add little complexity while reducing credential exposure and configuration confusion.

A stable daily routine can be summarized as follows: check the plan status before use and update the subscription when needed; verify the target app after connecting; monitor background traffic across devices; recheck the basics after system updates; and migrate before cleaning up when replacing a device. If the plan does not suit you after first use, JrVPN provides a 7-day no-questions-asked refund. Handle refunds, orders, and account issues through the appropriate support flow in the user panel; do not send sensitive information through public channels.

CHAPTER H

Master rule mode and advanced troubleshooting

How to choose global, rule, and direct modes

Common client strategies can be summarized as global, rule, and direct modes. Global mode sends most requests through the current route, making it useful for first-time verification and temporary scenarios that need a consistent exit. However, local services, system updates, and apps that do not need cross-border access will also consume plan data. Rule mode chooses a path based on a domain, app, or network target and is better suited to long-term everyday use. Direct mode temporarily pauses proxy handling or supports comparison testing; it does not mean the client has been turned off.

When configuring rules, start with a simple target. Send clearly identified apps that need a specific exit through the route and leave everything else at its default, then add exceptions gradually. Do not begin with a huge rule set from an unknown source; the more rules there are, the harder it is to trace a misclassification. During subscription updates, route content and local rules may belong to separate areas. Confirm that custom content is stored in the client’s supported override layer so it is not lost after an update.

Per-app routing and multi-device roles

Android per-app proxying lets selected apps use the route while the rest stay on the local network. Before configuring it, check whether the client uses an include or exclude logic. Afterward, test both a selected app and an unselected app to confirm the paths. Desktop platforms can offer similar behavior through rules, processes, or system-proxy scope, but support varies by client; follow the client documentation provided in the user panel.

With multiple devices, there is no need for every device to perform the same role. Configure a stable work route on the main computer, keep a nearby region on mobile devices for occasional connections, and choose regions based on content for video and audio devices. This reduces frequent switching and makes traffic sources easier to identify. Unlimited simultaneous devices provide flexibility; sensible role separation turns that flexibility into maintainable configuration. If several people share one account, also decide who handles renewals, subscription updates, and credential management.

Keep stable exits for different purposes

Some services assess the login environment using the exit region, account history, and device state. Frequently switching between far-apart regions may trigger additional verification. For work accounts, AI Tools, and region-specific content, choose a primary exit for each purpose and keep it reasonably consistent during normal use. Before changing regions, sign out of the relevant app or end the old session, then switch routes and enter again to reduce the chance of different exits appearing within one session.

Stability does not mean staying on one route forever; it means switching for a clear reason. Use the primary route for everyday activity and a backup route when the primary has issues, prioritizing another route in the same region before jumping across regions. If content requires a specific region, compare routes within that region. For ordinary browsing, start with a nearby region. Recording a simple relationship between purpose, region, and route is more reliable than clicking around by instinct.

Use the scope of impact to locate faults quickly

Advanced troubleshooting starts with the scope of impact. If one website is affected, check its status, regional rules, and browser session. If one app is affected, check per-app settings and the app cache. If one route is affected, switch to another route in the same region. If one device is affected, check system permissions and leftover proxy settings. If every device on the same network is affected, compare with another access network. Only when every network and device is affected should you return to the plan, subscription, and service-status layers.

This approach is more useful than memorizing many error codes because it narrows the issue to a specific layer first. You can organize a support ticket by impact: state the platform, whether the client can update the subscription, whether all routes are affected, whether other devices work, and what happened after switching networks. Attach only log sections near the failure time and remove the complete subscription address and private content. A clear reproduction path reduces back-and-forth questions.

Build a configuration you can restore

After long-term use, record necessary but non-sensitive information, including the client used on each device, common modes, primary and backup regions, the subscription-update entry, and the purpose of special rules. Do not save complete subscription links or plaintext passwords in the record. When replacing a device, get the client and subscription again from the user panel, then restore only the necessary settings from your notes. Do not copy an entire application directory containing old system paths, cache, and credentials.

If you use many custom rules, save the rule explanation separately from the actual configuration. The notes should explain why each rule is needed, while the configuration stays where the client supports it. When a target service changes or a rule stops working, you can adjust it based on its purpose instead of facing an unexplained list of entries. Check the source and contents of any external rule file before importing it; a filename labeled “recommended” is not a reason to replace your current configuration blindly.

Turn the complete workflow into an executable sequence

Starting from zero, understand the roles of the client, subscription, and route; choose a monthly plan or a never-expiring data package based on continuity and traffic sources; create an account with a username and password and no email address; pay with Alipay, WeChat Pay, or USDT; return to the panel to confirm the plan and subscription entry; import on Windows, macOS, iOS, Android, or Linux; grant system permissions and choose a route; then verify ordinary access, the target app, and the exit region.

Once you use the service day to day, update the subscription regularly, monitor background traffic across devices, manage monthly plans from the activation date, and renew or upgrade as needed. Recheck permissions after system updates. When problems occur, isolate them layer by layer across the local network, account, subscription, client, route, and target app. For a quick refresher, see the Quick Start path. To compare prices, visit the Plans page. To check regions and route types, visit the Servers page.