VPNRich
User Guide

Understanding cross-border network subscriptions

How accounts, plans, subscriptions and apps work together

VPNRich offers subscriptions for cross-border network access, with 90+ countries / 220+ routes and support for Windows / macOS / iOS / Android / Linux. Using the service involves an account, a plan, a subscription and a client app, each with a different role. Your account stores your service entitlements and orders; your plan determines the included data and billing method; your subscription provides route configuration to the client; and the client establishes a connection on your device. Installing the app only gives your device a connection tool—it doesn’t activate a plan or mean your traffic is using a selected route.

Think of the process as a series of handoffs: first confirm your account and plan in the user panel, then get the subscription linked to that account, import it on your device, and finally connect and check that access works. If something goes wrong, check the handoff at that stage rather than starting over. For example, if the panel shows an active plan but the app has no routes, focus on getting or updating the subscription. If routes are visible but websites won’t load, check the proxy mode, route selection and local network. This helps avoid treating an order issue as an installation problem and prevents unnecessary setup changes.

The app’s settings determine which traffic uses the connection

Client apps typically offer modes such as rule-based routing, global proxy and direct connection; the exact names depend on the app version. Rule-based routing directs traffic according to destinations and configuration. Global proxy sends traffic covered by the client to the selected route, while direct connection bypasses the proxy. The key is what the client actually handles: system proxy settings usually affect only apps that follow them, while terminals, development tools and apps with their own network settings may use a different path. So a website opening in your browser doesn’t prove every app on your device is using the same exit route.

Keep route location and route type separate. Location describes where the exit point is and affects the apparent source of a request. IEPL, relay and direct describe how the connection is routed; they aren’t authorization tiers for content services. A nearby location can be a useful starting point, but local ISP routing, your current network and the target service also affect performance. Don’t assume a route is right for every use just because of its location, or treat one connection result as a guarantee of consistent performance. For location details, see Servers and Routes.

Start with a network setup you can restore

Before installing anything, make sure your current network can open commonly used sites over a direct connection. Note any existing proxy apps, browser proxy extensions or managed network settings on the device. You don’t need to remove existing software; the goal is to avoid multiple tools changing system proxy or routing settings at once. If you’re using a work-managed device, check its policies first rather than mistaking a restriction for a service issue. Establish a known-good baseline and test after each stage, so you can return to a working state if something goes wrong instead of making changes across several unknown settings.

Before connecting, be clear about what you want to do: browse websites, maintain a conversation, watch video or use development tools. Each task calls for a different check. A website loading confirms basic access; a long-running connection needs to stay active, and video should be tested during playback. Define your goal, then follow the guide to judge whether setup is complete. To get started quickly, follow the steps in the Quick Start Guide. If a setting isn’t clear, return here for an explanation.

Choose a plan based on how you use data

First, compare monthly plans and data packages

VPNRich monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. They suit ongoing use when you want to manage data month by month. Data resets monthly on the activation date. That date isn’t necessarily the first of the calendar month, so check the plan details in your panel to see when your current allowance changes rather than assuming it resets when a new month begins. Before ordering, review the plan pricing page to make sure the billing method and included data fit your needs.

Data packages cost ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They last until used and never expire. The main difference from a monthly plan is how data is consumed and how long it remains valid; a data package is not a subscription that replenishes every month. The no-expiration rule can suit occasional or irregular use, while frequent users should consider their actual consumption. The available facts don’t specify whether plans can be combined, credited or merged, so if you already have an entitlement, check the final terms shown at checkout instead of assuming how it will work.

Estimate your needs from real tasks, not usage conversions

Browsing text, streaming video, syncing files and downloading development dependencies use data differently, so “hours per day” alone can’t reliably predict which plan you need. A better approach is to list your typical tasks, note any continuous streaming, background syncing or large file transfers, then adjust based on actual usage in your panel. Video quality, app caching and background updates all affect consumption, so don’t convert a data allowance into a fixed number of viewing hours. If you’re unsure, don’t choose a higher tier just because you have more devices: VPNRich allows unlimited simultaneous devices, so device count doesn’t determine your plan tier.

Background activity matters especially when using multiple devices. File syncing may run continuously on a computer, while mobile apps can start downloading when they resume. Not all of this traffic necessarily needs an international route; check the actual routing and panel records to see what counts toward your subscription. Before choosing a plan, list how you expect to use it rather than guessing. Don’t disable system security updates just to save data. Instead, review app network settings and choose an appropriate connection mode so traffic that needs a route is handled separately from ordinary direct traffic.

What to check before upgrading, paying or requesting a refund

If you upgrade a monthly plan partway through its term, the price difference is prorated against the remaining days. This doesn’t mean that paying the difference starts a full new term, and you shouldn’t calculate the final order yourself from the listed prices. In your panel, check the amount due, target plan and activation details before confirming. If the result differs from what you expect, keep the order information and ask through a support ticket instead of placing multiple orders to try to fix it. The plans page explains the public terms; your panel shows the transaction for your account. Check both.

For long-term use, don’t assume other billing periods are available. This guide covers only the monthly plans and data packages confirmed in the facts; it doesn’t add annual billing, discounts or auto-renewal terms. If you’re comparing options for extended use, read How to Evaluate a Long-Term Subscription, focusing on usage frequency, maintenance and refund terms, then decide using the current pricing page. By this point, you should be able to choose a billing method and data tier based on your needs, rather than just remembering a price.

Create an account and confirm your order

Save your account details, then place your order

VPNRich doesn’t require an email address; you can create an account with a username and password. Open the user panel from the site and follow the prompts to set them up. Before submitting, check your keyboard layout, capitalization and any accidental spaces. Your username is important for future sign-ins, so store it securely with your password. A password manager is a good option; use a unique password that you don’t reuse on other sites. Not requiring an email address means you shouldn’t assume email recovery is available, so make sure you can identify and keep your login details before leaving the page.

If you already have an account, use the login page instead of creating another one just because the client can’t connect. Plans and orders belong to the original account; a new account won’t inherit its entitlements. On a shared device, check whether the browser is still signed in to someone else’s panel, especially before paying. Account details, client configuration and browser sessions are separate: signing out of the panel doesn’t remove a subscription from the client, and closing the client doesn’t sign you out of the panel.

Check the order, not just the payment redirect

Choose the plan you want in the panel, then review the plan name, billing method, amount and entitlement details on the order. Make sure they match the option you chose in the previous section, then pay using whichever of Alipay / WeChat Pay / USDT is shown. Open payment pages from the user panel, not from unfamiliar links forwarded by someone else. Reaching a payment page doesn’t mean payment is complete, and returning from a payment app doesn’t prove the plan is active. Go back to your account and verify the order and entitlement status.

After paying, return to the panel and check that the order reflects the payment. Then review the plan and data shown in your account overview. If the payment app shows success but the panel hasn’t updated, confirm your network is working and reopen the order to check its status. The priority is to keep the order reference and payment result, not to pay again. Closing the page, using the browser’s back button or switching apps can leave old information on screen; the current display alone doesn’t confirm the backend result. Check the order record against the account entitlement.

Keep the relevant details if something goes wrong

If the order and payment status still don’t match, explain the issue through a support ticket in the user panel. Include when it happened, the plan you intended to get, the order reference and any on-screen message. Share only the part of a screenshot needed for troubleshooting, and hide your password, full subscription link and unrelated personal information. Don’t post payment records in public comments. If a redirect failed, say whether the payment page never opened, you weren’t returned after paying, or your entitlements didn’t change after returning; each points to a different next step.

To request a refund, first read the application instructions in the Terms of Service, then open a support ticket with the relevant order and your request. VPNRich offers a 14-day no-questions-asked refund, but this guide doesn’t replace the terms or add unconfirmed processing times for any payment method. Don’t place another order to replace the original, and never share payment credentials publicly. If you chose the wrong plan, stop before making another payment, note the current order and the plan you intended to select, and wait for clear instructions before proceeding. This helps avoid entitlements that are harder to reconcile.

At this stage, you should be able to find the verified order in the right account and see the plan you expect. Next, get the client app and subscription. If you can sign in but don’t see the expected entitlement, check the order first. If you can’t sign in, check your username and password rather than confusing an account login issue with a network connection problem. Confirm each state before moving on so the import steps have a reliable starting point.

Get your subscription and complete the setup handoff

A subscription link and an installer serve different purposes

Once your plan is active, find the subscription section in the user panel. A subscription isn’t an app installer; it’s how the client gets route and rule configuration. Downloading an installer prepares the app, while importing the subscription hands the route configuration to it. Get the subscription through your account overview, and get the client from the client downloads section. This page doesn’t provide real subscription URLs or static installer links, keeping account-specific configuration separate from public pages.

Treat your subscription link like an access credential. Anyone holding it may be able to retrieve route configuration for your account, so don’t share it in public groups, online format converters or unrelated diagnostic tools. Troubleshooting usually needs the error message and client name, not the full link. If you need to describe its format, hide the part that identifies your account. A link may look like an ordinary web address, but that doesn’t make it safe to share; what matters is the configuration the service returns.

Use the import option provided in your panel first

If the panel offers one-click import, make sure the client app is installed and has been opened at least once, then select the relevant option. Your browser may ask permission to open a local app; check that the app name is what you expect before continuing. If no confirmation appears, check whether the browser blocked the external app request or the import option doesn’t match the client on your device. Don’t click repeatedly or open several clients at once. Decide which app should receive the configuration, then handle the handoff between your browser and system.

If one-click import isn’t available, copy the subscription link from the panel and add it in the client’s subscription or configuration section. The menu may call this “Configuration,” “Subscription” or “Remote Configuration”; the function matters, not the exact label. Give the configuration a clear name, then fetch or update it and check that a route list appears. Make sure the copied link is complete and contains no extra spaces or line breaks. Check whether the client expects a URL or a configuration file; don’t paste a link into an editor that expects configuration text.

Tell a successful import from a successful connection

Seeing a configuration name in the list only means the entry was created. A route list means the client received configuration; after selecting a route and connecting, you still need to test access. If the configuration is empty, first check that your plan is active and the subscription belongs to the current account, then check whether the client can reach the subscription endpoint. A browser opening an ordinary webpage doesn’t prove the client’s configuration request succeeded. Read the specific error from the subscription update instead of immediately changing system routing or reinstalling the app.

Updating a subscription fetches the latest service configuration; it doesn’t buy data or extend your plan. Route names, rules and available options may change after an update, so check that your current selection is still available. Avoid editing content generated by a remote subscription to save long-term preferences, as the next update may overwrite your changes. If you need customization, first check whether the client supports separate rules or overrides, and keep the original configuration as a fallback. If you’re unfamiliar with those features, use the panel-provided configuration for a basic connection.

If you think your subscription link has been exposed, remove the public post first, then check whether the panel offers a subscription reset. If there’s no clear option, ask support through a ticket. If resetting creates a new link, update the subscription source on every device that uses it; don’t assume the old configuration will keep working. The handoff is complete when the configuration comes from a trusted source, the route list is visible, the client recognizes it and you know which account it belongs to. Then connect on each platform as needed.

Import the client setup on each platform

The steps below are organized by platform. App names and menus can change, so if the wording differs, look for the same function instead of searching for a button that isn’t there. On every platform, get the compatible client and subscription from your user panel, and follow the instructions shown by your system. Import the configuration first, set connection permissions next, then verify access as described in the next section. Don’t copy an installer from one platform to another, or assume permission steps on one operating system apply to another.

Windows: Check the configuration before enabling the system proxy

Choose the Windows client in your panel, download it and install it as prompted. On first launch, import your subscription and make sure the route list appears. Then select a route and rule-based routing mode. If the client uses the system proxy, enable it and test with a browser that follows system proxy settings. Browser proxy extensions can override those settings, and other network tools may change them too; if there’s a conflict, close anything not being used for this test. A standard proxy connection doesn’t automatically cover every program, so test games, terminals and apps with their own network settings separately.

If you need the virtual network interface mode offered by the client, read its permission prompts before enabling it. This mode usually handles a broader range of traffic, so don’t turn it on just because a browser test failed. If direct access stops working after you close the client, check whether its system proxy settings remain in place and use the client’s own disable or restore option where possible. When you see a system security warning, verify the file’s source instead of disabling your security protections to continue.

macOS: Handle installation, permissions and connection separately

Get the macOS client from your panel, install it as directed by the page and system, then open it. Import your subscription and confirm that the configuration and routes are visible before connecting. If macOS asks to add a network configuration or grant related permissions, verify that the request comes from the client you’re using and approve only what’s needed. A system password prompt or confirmation in Settings is for device permissions; don’t enter your VPNRich account password there. If you cancel authorization, check the app to see whether you can trigger the prompt again. Don’t download supposed fix components from untrusted sites.

If the app shows that the configuration was imported but can’t connect, check whether the relevant permissions still need approval in System Settings and whether the app says an extension hasn’t been enabled. Address the prompt, then test the route again. Don’t delete every network configuration to troubleshoot one app. For more installation and permission details, see Mac Setup Guide for Beginners. Once set up, test an actual destination rather than relying on the menu bar icon.

iOS: Open the available client from your panel

Find the iOS client in your user panel and follow the options currently shown for your account; available access depends on your active plan. Don’t look for alternative installation links in articles or search results. Once the client is ready, use the import option in your panel or add the subscription in the app. When you connect for the first time, iOS may ask permission to add a VPN configuration. Verify the app’s identity before approving it. A connection icon in the status bar only shows a change in system connection state; it doesn’t prove the content you want is accessible.

If your device has other network configurations, check which one is active. When you return to the app, make sure the selected route hasn’t changed, then open your target site. If only one app can’t connect, check its own sign-in, regional requirements and network path separately instead of repeatedly deleting system configurations. If a problem appears after the device sleeps or changes networks, reconnect in the client and test again; there’s no need to buy another plan just for that.

Android: Check the import, connection permission and background status

Get the Android client from your panel and verify its source when following the system’s installation prompts. Open it, import your subscription, select the configuration and route, then connect. If Android displays a VPN connection request, make sure it comes from the app you’re using. If another VPN is already active, decide which connection to keep so the apps don’t compete to manage traffic. Don’t enter your account password in the subscription URL field just to get the configuration imported; they serve different purposes.

If the app works in the foreground but often disconnects in the background, check Android’s background activity and battery settings for that app. Menu names vary by device, so follow the prompts and adjust the relevant settings rather than removing restrictions for every app at once. Background permissions affect whether the app can keep running; they don’t improve route quality. Retest the same task after making a change. If it still fails, check whether the issue relates to a network switch or selected route.

Linux: Test desktop apps and the terminal separately

Select the Linux client in your panel. First check that your environment is compatible with the available installation method, then install it as instructed. Import the subscription, confirm that the configuration parses correctly and select a route. Desktop proxy settings and proxy environment variables used by terminal processes can be independent, so test the command-line tools you actually use even if your browser works. Don’t copy unknown ports or startup flags from another guide. If a tool needs an explicit proxy, check the client’s current local listening details and the options supported by that tool.

A failed terminal request can also result from certificates, name resolution or the tool’s own settings; don’t immediately blame the subscription. Note whether the client is connected, whether the browser works and what error the tool returns, then investigate the difference. Don’t change global certificate trust to fix one tool or run privileged commands from an unknown source. On every platform, keep the original subscription configuration after importing it, and know how to disconnect and restore a normal direct connection. This is the foundation for ongoing maintenance.

Verify your connection and troubleshoot problems

Check each layer, from your local network to the target app

Before testing, close other tools that could take over traffic and leave only the client you’re checking. Disconnect the proxy temporarily and confirm that your ordinary direct connection works. Then reconnect with the imported configuration and select a route. Check the client status, webpage access, exit information and target app in order. Don’t change the route, proxy mode and DNS settings at the same time. If you change several things at once, you won’t know what helped—even if you later restore the settings—and you’ll be left guessing again next time.

First, use an ordinary website to confirm that your browser can make requests, then visit the service you actually want to use. The My IP page shows exit information for the current browser request; check whether it matches the selected region. An exit lookup reflects that request only, not the network path used by every process on your device. Terminals and other apps may have their own proxy settings. A failed lookup alone doesn’t mean the connection failed; consider the results from ordinary websites and your target app rather than relying on one tool’s message.

Separate symptoms by troubleshooting stage

If the client can’t retrieve routes, the issue is at the configuration stage: check account entitlements, subscription source and update errors. If routes appear but won’t connect, investigate the route, permissions and local network. If the browser works but one app fails, check that app’s own proxy settings, sign-in state and service requirements first. If the destination’s homepage loads but you can’t sign in or play content, the issue may involve account authorization or content-region rules. Repeatedly switching routes isn’t a substitute for reading the specific message.

Test sustained performance with real tasks

After a quick webpage test, try the task you actually need. AI chats and code completion require a stable connection, video should be tested during playback, and file transfers need to be observed for interruptions. Keep the same exit and mode during each test; avoid changing regions mid-task. Speed tests and client diagnostics offer only a limited view and can’t replace a complete task test. This guide makes no latency, bandwidth or availability guarantees, and a successful visit once isn’t a promise of ongoing support for a content service.

For a name-resolution error, first check what the client and target app report, then look for custom DNS settings or old proxy configuration. Don’t copy unfamiliar DNS addresses from the web or disable certificate checks to hide a connection error. A certificate warning means you should check your device time, destination domain, software environment or network path. Skipping verification can make a security issue look like a successful connection. If ordinary websites are also affected, start by checking your local network baseline.

When asking for support, describe what happened instead of saying “nothing works.” Include your device platform, the client’s current mode, route region, apps that work, apps that fail and the exact error message. You can attach a relevant screenshot after hiding credentials. If changing local networks changes the result, mention that too; it helps distinguish device settings from network conditions. Success means the actual task works as expected and your device returns to its original direct connection when you disconnect—not that every icon looks normal.

Routine maintenance, data and renewals

Keep subscription updates separate from app updates

You don’t need to reimport your subscription every time you use the service. Subscription updates fetch routes and rules; client updates deliver app fixes and feature changes. If route names change or the configuration appears out of date, update the subscription first. If the app has installation, launch or permission problems, check the client’s update notes. Before updating the client, note your configuration name, connection mode and custom settings, and make sure the new installer still comes from your user panel rather than an unfamiliar message.

After updating the subscription, check the route list and current selection, especially whether a route you used regularly is still available. Don’t manually add a route from an old screenshot just because the list changed. Use the current subscription response for service configuration; keep personal preferences in separate client settings where possible. If something goes wrong after an update, save the error and note what changed, restore a known-working setup, then decide whether to contact support. Repeatedly deleting and re-adding configurations creates duplicates and makes troubleshooting harder.

Check data usage against the correct reset rule

Monthly plan data resets monthly on the activation date. Data packages last until used and never expire. When checking usage, first confirm which entitlement you’re viewing, then decide whether the remaining data is as expected. Local statistics in a client may be affected by restarts, the scope of its counter or how the app is implemented; don’t confuse them with account billing records. If usage looks unexpected, check panel records and background tasks rather than relying on a single client counter. Don’t apply the monthly reset rule to a data package.

Unlimited devices means there’s no fixed cap on the number of devices online at once; it doesn’t mean your plan gets extra data when you add devices. With multiple devices, keep track of which ones still use the subscription and which background tasks send traffic through a route. When you replace a device or stop using one, remove the account and subscription details saved on it. Before sharing or transferring a device, signing out of the browser panel isn’t enough. Also check client configurations, clipboard history and saved screenshots so you don’t leave access credentials for the next user.

Check your current entitlements before renewing or changing plans

When you’re ready to continue, check your current plan, remaining data and account status in the panel before opening the plan section to review a new order. A route still appearing in the client doesn’t prove your entitlement is active; old configurations can remain on the device. Don’t assume that renewal happens automatically or that entitlements combine in a particular order—this guide doesn’t confirm either. If you change tiers, remember that the price difference for a mid-term upgrade is prorated against the remaining days. Use the order page’s details for your account to confirm the final terms.

If the client hasn’t recovered after renewal, first confirm the new order and account entitlements. Then check whether the subscription needs updating and whether the client is using the right configuration. Don’t buy another plan while waiting for a payment result. On multiple devices, verify the setup on your main device first, then check the others; this helps distinguish an entitlement issue from a local setting. If only one device fails, revisit its configuration and network status rather than assuming the entire account is affected.

What to do about persistent issues and refund requests

If a problem persists, note what you’ve already checked and report it through the support ticket portal. Explain whether it affects a particular region, app or local network, and don’t paste your private subscription into the message. VPNRich offers a 14-day no-questions-asked refund. To request one, read the Terms of Service and reference the relevant order. Don’t treat troubleshooting as something you must continue indefinitely, and don’t assume an unconfirmed refund processing time. Keep your order and support messages so there’s a clear record to review.

Route selection and advanced routing

Filter by destination region first, then compare route types

Once your basic connection works, you can organize routes by use. First check whether the destination service has a specific regional requirement, then choose a route in an eligible region that suits your current network. If there’s no regional requirement, start with a region you use regularly and test it with real tasks. IEPL, relay and direct are connection types, not a fixed ranking for everyone; results depend on the entry path, local network and destination service. When comparing types, keep the task the same so you can tell what caused the difference instead of mistaking a change in the app for a change in route.

IEPL typically describes a cross-border connection carried over a dedicated line; relay routes use an intermediate node, while direct routes take a different path. These terms explain the route structure, but don’t guarantee a particular speed or acceptance by a target platform. Beginners can read How to Choose a Route by Region, Type and Use, then see the server page for details. The goal is to find a route that suits your current task, not to collect as many route names as possible.

Give split-tunneling rules a clear match target

Routing rules typically have a match condition and an action. A condition identifies a domain, address, app or other target; the action determines whether traffic uses a proxy, connects directly or follows another option supported by the client. Rule order often matters: a broad condition may match before a more specific one. Understand the existing configuration before adding rules. Don’t paste an unknown block of rules just to fix one website; it could change how other apps connect. First identify the affected domain or app, then check whether the client offers separate overrides and match logs.

When customizing routing, prefer separate rules or override features supported by the client, and keep the original service subscription intact. Direct edits to remotely generated configuration may be overwritten during the next update. Before changing anything, write down the intended result—for example, “route a specific development tool through the selected route”—and make sure you can roll back. Direct and proxy are traffic paths, not value judgments. Choose based on the destination service, privacy needs, organizational policies and actual access requirements rather than sending every app through the same path.

Test development tools and long-lived connections separately

Terminals, code editors and package managers may not follow the system proxy automatically. They may use their own environment variables or settings files. If these tools fail while your browser works, check where each tool gets its proxy settings and confirm how the client is listening; don’t copy someone else’s local port. Some processes read environment variables only at startup, so you may need to reopen the relevant process after changing settings—but don’t restart the whole system repeatedly. Read the error first and distinguish an unreachable network, authentication failure, certificate error and a destination service limit.

For a basic request from the terminal, use the command below to inspect the response or error. The example destination only demonstrates how to make a request; it isn’t a VPNRich subscription URL and can’t prove that AI or streaming services are accessible. The command uses the terminal process’s current network environment. If the tool isn’t using the proxy, its result doesn’t represent the proxy route. Keep the error text if the request fails, and don’t add an option to skip certificate verification just to get an apparent success.

curl --head https://example.com

Once an AI chat, code-completion task or remote job starts, keep the exit route stable and avoid switching regions mid-session. If the app reports an account, regional eligibility or quota issue, follow the target service’s guidance; a network route can’t replace account permissions. For development use, see Route Selection and Long-Lived Connections for Cursor and Copilot. Streaming platforms also have their own licensing rules. See Streaming Availability and Testing for practical checks; a region name alone doesn’t guarantee access.

That completes the full process: understand the plan rules, verify your account and order, get and protect your subscription, import it on your platform, connect, test access and restore a direct connection. You also know how to update the configuration and handle issues later. For everyday use, keep settings simple and stable, adding features one at a time when needed. Return to Guides for the main setup steps or compare entitlements on the plan pricing page. This keeps your workflow clear and prevents temporary troubleshooting settings from lingering on your device.