VPNRD
Complete Setup Guide

Service & delivery: understanding cross-border connections

What your account, subscription and client each do

VPNRD provides cross-border access and network acceleration subscriptions. Getting started involves more than installing an app: your account, plan, subscription details and client all play a part. The account lets you view orders and manage your service; the plan determines your data allowance and billing; the subscription provides connection details to the client; and the client establishes a connection on your device. Knowing how these pieces fit together helps you avoid mistaking a successful account login for a working connection—and makes it easier to check the right place when something goes wrong.

The user panel and the client app have different roles. Use the panel in a browser to manage your account, payments, plan and subscription details. The client runs on your device, imports connection settings and handles network requests according to the mode you choose. Being able to access the panel doesn’t mean the client is configured correctly, and seeing the client running doesn’t mean your account benefits are still active. Check account status and device connectivity separately instead of treating them as one vague question of whether the service “works.”

What happens along the way when you make a request

When you open a website on your device, the request travels through your local network, the client, your selected route and the destination service. A change at any point can affect the result. For example, an unstable Wi-Fi connection can affect both ordinary websites and cross-border requests, while maintenance at a destination site may affect only that site. To check whether the service is working, compare more than one website and route rather than assuming the entire connection has failed because a single page won’t load.

VPNRD covers 120+ countries and 210+ routes, including IEPL dedicated lines, relay routes and direct connections. Coverage describes the available network resources; it doesn’t mean every location will suit your current network or that every destination platform accepts the same exit point. Check the panel for the available locations, names and options. For an overview of route types, see Global Nodes and Route Types, then choose based on your own results.

Set clear expectations for how to use the service

VPNRD supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. You can use subscription details from the same account on multiple devices, but each device still needs its own client installation and setup. No-logs is the service’s privacy policy; it doesn’t mean you can skip protecting data stored on your device. Browser sessions, downloaded files, screenshots and information you choose to submit are still handled by the relevant device or destination platform.

Before setting things up, make sure your local network can access the websites you normally use, then get your account and client ready. Company, school or managed devices may have additional network policies; follow the relevant requirements rather than disabling organizational settings to try to connect. If another proxy or network management tool is already installed, note its existing settings and let one tool handle the connection at a time. This helps prevent multiple apps from repeatedly changing the same system options.

This guide follows the practical setup sequence: choose a service, complete your account and order, get your subscription, import it on your device, then test and maintain the connection. You don’t need to change advanced settings on your first read. Keep the defaults and establish a repeatable working connection before exploring routing, DNS or traffic interception. That gives you a known-good baseline to return to if something goes wrong, instead of having to guess which part needs fixing.

Choose a plan: monthly subscription or data package

Start with how often you’ll use it, then compare data allowances

When choosing a plan, first consider whether you’ll use the service regularly, then decide how much data you need. Daily browsing, remote work and frequent use of online tools call for a different plan than occasional travel or one-off access to resources. A monthly subscription suits regular use; a data package suits those who want unused data to remain available. Don’t compare prices alone—check how data resets, when it’s used and whether you’re likely to use the allowance within the relevant period. See the plans and pricing page for the full terms.

Monthly plans include ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets monthly on the date you activated the plan, so check the panel for your reset date rather than assuming it falls on the first of the calendar month. Before large downloads, system updates or extended video streaming, check your remaining data. Monthly allowances are meant to be used within each billing period, not stored indefinitely.

What “never expires” means

Data packages are ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They can be used until the data runs out and never expire. This describes how long the data remains available, not a recurring top-up. Each use reduces your remaining balance, so “never expires” doesn’t mean the data replenishes itself. If you haven’t connected for a while, check your balance and subscription status before reconnecting to make sure your device has the current account details.

Data usage depends on what you transfer. Video, cloud sync, background updates and high-resolution streaming can use more data than text browsing. Unlimited devices doesn’t mean each device has a separate allowance; check overall usage in the account panel if multiple devices are connected at once. To estimate your needs, start with the tasks you do most often and monitor actual usage rather than guessing based on app names.

How upgrades, payments and refunds fit together

If you upgrade a monthly subscription mid-cycle, the price difference is converted into remaining days. Before proceeding, read the order summary in the panel and check your current benefits, the new plan and the outcome of the change. Don’t substitute a simple price subtraction for the panel’s calculation. If the summary doesn’t match your expectations, keep a record of what it shows and contact support. Check the panel for the current rules on combining monthly subscriptions and data packages, including which benefit is used first; this guide doesn’t assume a combination that the panel hasn’t confirmed.

Payment methods include Alipay / WeChat Pay / USDT. After choosing a method, check that the order shows the right plan and amount before paying. Once payment is complete through the payment provider, return to the panel to confirm the order status. The external payment record and service activation are separate steps. If the status hasn’t updated, don’t create another identical order right away; duplicate orders can make it harder to match a payment to the correct service.

VPNRD offers a 7-day money-back guarantee. To decide whether the service suits you, test it with your usual network, devices and destination services, and read the refund policy for instructions on how to apply. The guarantee doesn’t promise that a destination website will work, and it doesn’t replace reading the plan terms. Check the plan type, data allowance, payment method and refund policy before moving on to your account and order.

Account & orders: activate your service

Create an account and save your login details

VPNRD doesn’t require an email address; create an account with a username and password. Open the user panel from the site and enter the details requested. Choose a username that’s easy to enter accurately, and use a password you don’t use on other sites. Before submitting, check your input language, capitalization and any accidental spaces, especially when copying details between devices. Once your account is set up, save your login details in a trusted password manager rather than relying on the browser to stay signed in.

Because account creation doesn’t require an email address, don’t assume you can recover your account by email. Check the account page to see what recovery or change options are actually available. On a shared computer, sign out of the panel when you’re done and check that the browser hasn’t saved login details you don’t want it to keep. If you take screenshots of your plan or order, keep passwords, subscription links and other sensitive account information out of view. Troubleshooting shouldn’t expose more data than necessary.

Already have an account? Go to the user panel login; you don’t need a separate account for every device. After signing in, confirm the username and current plan before starting a purchase, especially if your browser may have saved a different account. If the page has been open for a long time, check the account details again before placing an order. Multiple tabs can make it easy to lose track of which account is active, so keep the main task in one tab.

From plan selection to payment confirmation

Choose a plan in the panel and read the order summary before proceeding. Check the plan type, data allowance, price and billing method against what you saw on the pricing page. Plans with similar names can have different data rules, so don’t choose by name alone. If you’re upgrading an existing monthly subscription, read how the panel will handle your remaining benefits and confirm the result of converting the price difference into remaining days.

On the payment page, use only the payment methods and instructions shown for the current order. Alipay / WeChat Pay / USDT have different interfaces, but the checks are the same: confirm which order you’re paying for, the amount and the payment status. Don’t use payment details from another order, screenshots of an old page or instructions from a previous transaction. If you’re redirected to a payment app, return to the panel afterward to check whether the order status has updated to complete.

Even if the payment page says complete, check the panel to confirm your service benefits are active. Review the order, then check your plan and remaining data in the account overview. If the payment is recorded but the order still shows as incomplete, refresh the page or sign in again to check—don’t pay a second time right away. Keep the order ID, payment record and any relevant page messages so support can look into the issue. There’s no need to share your password or full subscription details.

Configure your device after confirming service activation

Once your plan is active, get your subscription and download the client. Installing the app before service activation may leave you without subscription details to connect with. For platforms other than iOS, sign in to download; iOS access follows the active-plan rules shown in the panel. Seeing a download option doesn’t mean the routes are ready to use. Don’t replace the client provided by the panel with an installation file found through a search for a similar name.

For order issues or refund requests, use the support ticket page in the panel. Include the account you used, the order status and what you need help with. Attach only necessary screenshots, with sensitive details obscured. Keep separate issues separate—for example, don’t mix an unverified client problem into a payment question. Describe what you did in chronological order and distinguish completed steps from anything still unresolved so support can check each part.

Account setup is complete when you can sign in and match the order, plan benefits and subscription access to the same account. Once you’ve confirmed this, set up your devices. If you switch devices later, you won’t need to repeat the payment process; just check your account benefits and get the client from the panel. Keeping account, order and device setup separate makes ongoing maintenance easier to follow.

Get your subscription: import it and keep it secure

A subscription link isn’t an ordinary web address

A subscription link lets a client retrieve connection settings and usually contains information associated with your account. It’s not an information page for others to browse, nor a website you need to open manually every time you connect. Once imported, the client uses it to retrieve available routes and settings. Treat the link as confidential access information: don’t publish it, include it in group chat screenshots or submit it to online converters or checkers you don’t trust.

Sign in to the panel and confirm your plan is active, then look for the subscription or import section. Button names and layout may change, so choose based on what you need: copy a link for manual import, open a compatible client from the panel, or update an existing configuration to retrieve the latest details. If several formats are available, choose one your client explicitly supports rather than guessing from a similar-sounding name.

Copy, import and run the first update

To import manually, use the copy option in the panel. This avoids missing characters at the end or accidentally copying extra spaces. In the client, find the subscription, configuration or remote configuration section, choose the option to add a link, then paste and save it. You can give the local configuration a recognizable name, but don’t include a password or other sensitive information in the name. Update it and make sure a route list appears; a configuration name on an otherwise empty page isn’t enough.

If the panel can open a client directly, you’ll need an app installed that can handle that link. If your browser asks which app to use, check the app name before confirming. If nothing happens, open the client first and try again from the panel, or copy the link and import it manually. A failed handoff doesn’t mean the subscription is invalid; the system may not have an app associated with that link, or the browser may be blocking external app launches.

After the first successful update, check that the route list has loaded and that the selected configuration is the one you just imported. If the device has older service details, adding a new configuration may not select it automatically. If its name doesn’t match what you see in the panel, check where it came from and when it was last updated before doing anything with older configurations. Don’t delete everything by default; keep records with identifiable sources until you’ve confirmed the new configuration works.

What to check when a subscription update fails

If the client says the format isn’t supported, check that the client and subscription format are compatible. If it can’t access the link, check your local network and whether the panel opens. If the message points to an account or plan issue, return to the account page and check your plan. A failure while downloading the configuration happens before the route connection stage, so switching routes repeatedly usually won’t help. First get the client to retrieve the configuration successfully.

Updating a subscription doesn’t renew or reactivate your service. It only retrieves the latest delivered configuration; your account balance and service status are managed in the panel. Likewise, deleting a local subscription doesn’t cancel a plan in your account. Keeping these distinctions clear helps you address an outdated device configuration separately from a change to your account benefits, instead of starting a new order just to refresh your routes.

If your subscription link has appeared somewhere public, remove the public copy first. Then check whether the panel offers a reset or replacement option and use it if available; otherwise, contact support through a ticket. After replacing the link, update every device still using the old one—not just the device you’re troubleshooting. For more on subscription links and importing them, see the complete subscription link guide.

At this point, the client should show a working route list, and you should know which account supplied the configuration. Don’t rush to change routing rules, DNS or traffic interception settings. First select a route and connect using the defaults. A successful subscription update is a prerequisite for the tests that follow; keep a record of the update result and any errors to narrow down future troubleshooting.

Set up each platform: configure the client on your device

Get the appropriate client for every platform from the client download page in the panel. For platforms other than iOS, sign in to download; iOS access follows the active-plan rules shown in the panel. Check your operating system and device architecture before installing, then import your subscription. The steps below use general feature names because client interfaces can differ; follow the options in the client currently provided to you.

Windows: install, import and set up the system proxy

On Windows, download the client that matches your system and follow the installation prompts. Open its subscription or configuration section, add the details from the panel and update them. Confirm that the route list appears, select a route, then enable the connection or system proxy as instructed by the client. If the connection stops when you close the window, check whether the app is exiting or minimizing to the background. Don’t rely on whether its window is visible in the taskbar to tell if it’s still running.

If your browser works but other apps aren’t affected, check whether those apps follow the system proxy. Don’t turn on every advanced traffic interception option at once. If you previously set up a manual proxy, note the original settings. After exiting the client, check that the system has returned to the expected state. If you see a permission prompt, confirm it comes from the client you installed and grant access only as needed; don’t run repair scripts from unknown sources.

macOS: network permissions and enabling the configuration

After installation, macOS may ask you to approve network permissions or a configuration. Read the app name and the reason for the request, then grant the relevant permission in System Settings. Return to the client, import and update your subscription, and select the current configuration. If it says a system extension is not enabled, address the permission first rather than repeatedly deleting the subscription. System permissions and remote configuration are separate requirements.

If requests fail after waking from sleep or switching networks, disconnect and reconnect, then check that no other app is handling the same network function. Follow the panel’s download notes for device architecture compatibility rather than making assumptions about the installer. For more on network extensions and using Apple services together, see Mac network permissions and compatibility before changing advanced settings.

iOS: access the client and configure the connection

On iOS, sign in to the panel and confirm your current plan meets the access requirements before getting the client as instructed. After installation, import your subscription from the panel or add the link in the app. If iOS asks to add a VPN configuration, make sure the request comes from the client you’re using. Once permission is granted, return to the app, select a route and connect; approving the system configuration doesn’t select a route automatically.

If the subscription opens in the wrong app, check whether you have multiple clients installed that can handle the same type of link. If needed, copy the link and import it manually. After switching between Wi-Fi and mobile data, test the destination page again. A connection icon in the status bar or Settings can help, but you still need to test the service you want to use. Identify old configurations before removing them; have the administrator handle configurations on managed devices.

Android: import your subscription and keep the client running

During installation on Android, follow the system prompts to confirm the installation source. Open the client and import your subscription. When Android asks for permission to create a VPN connection, check the app name before continuing. Select an exit route after the subscription update has loaded successfully; an empty list before that isn’t a connection failure. If the app reports a parsing or format error, check the compatible subscription format in the panel instead of looking for a replacement configuration on another site.

If the client works in the foreground but stops when you lock the screen or switch apps, check the system’s background activity and battery restrictions for that client. Settings names vary by device, so use the options shown on your system; you don’t need to disable every power-saving feature. If another app using the VPN interface is also running, check which one is currently handling the connection. Competing for the same interface can make the connection status hard to interpret.

Linux: runtime environment and proxy coverage

On Linux, first check your distribution, desktop environment and device architecture, then choose a compatible client from the panel. In a graphical interface, add the subscription, update it and select a route in that order. For terminal-based startup, follow the instructions provided with the client rather than reusing service names or configuration paths from another app. After importing, check which configuration is currently loaded so a background process doesn’t keep using an older file.

Terminal apps may not follow the desktop proxy settings, so a working browser connection doesn’t mean command-line requests use the same route. If the client provides a local proxy address, check the actual listening address and port, then configure each app according to its documentation instead of copying unverified defaults. Be aware of the scope of any environment variables you change, and remove settings you no longer need when you exit the client so new terminal sessions don’t keep pointing to a stopped local proxy.

Connect & test: verify each part of the connection

Test the connection first, then the destination service

Once the subscription is imported, choose an available route in the panel and connect through the client. Note the configuration name, route and connection mode, then open an ordinary website as a basic test. Change one thing at a time—for example, keep the same network and client and switch only the route. If you restart your router, change DNS, switch modes and change routes all at once, you won’t know which step made a difference even if the issue goes away.

After a basic website loads, test the services you use day to day. Check sign-in, file uploads and video playback separately, since they may use different domains or connection methods. A working homepage doesn’t mean every feature works, and a successful login doesn’t mean the content region is the same. If one feature fails, note exactly where: the page won’t load, the account is denied access, or a request is sent but no result comes back.

To check your exit IP, use the site’s IP lookup tool. The result reflects the route taken by that request and may not represent every app. With rule-based routing, some sites may connect directly while others use a proxy; apps with their own proxy settings may use yet another route. Interpret the result alongside the client’s current mode and app settings rather than using a single lookup to infer where all your traffic goes.

Tell DNS, route and destination service issues apart

DNS translates domain names into addresses that can be reached. A DNS failure may show up as a host-not-found message; a failed connection, certificate warning or account-region error points to a different issue. Don’t change every DNS setting just because a page won’t open. Check the client’s error first: did the subscription update fail, did the route connection fail, or did the destination app respond with a restriction after the connection was established? Then follow the relevant troubleshooting path.

On Linux, if the relevant tools are installed, you can use the commands below to check basic DNS resolution and request results. The example uses a documentation domain and contains no account information. A failed command could mean the tool is missing, the network is unavailable or the destination didn’t respond; a successful command alone doesn’t prove the proxy is working. Check what traffic the client actually handles, especially since terminal and browser traffic may use different proxy settings.

nslookup example.com
curl -I https://example.com

If ordinary websites work but a destination platform doesn’t, check your account status on that platform, its supported regions and its service announcements. The platform may make decisions based on account details, payment region, exit characteristics or its own policies; changing routes doesn’t guarantee a different result. For AI tools, see AI access and acceleration, and follow the destination service’s terms. A connection service doesn’t grant permission from the platform itself.

Keep troubleshooting notes you can reproduce

If nothing works, disconnect the client temporarily and check whether your basic network is working. Then check your plan, subscription update and selected route. If only one route fails, compare it with another route on the same network. If all routes behave the same way, check for proxy conflicts, permissions and network issues on your device. Don’t just write “slow” or “not working”; note what failed and what you’ve already tested.

Connection speed depends on your local access, route, destination service and device. A response check in the client usually describes one kind of test result; it doesn’t guarantee large downloads or smooth video playback. Choose a route based on the tasks you actually do: whether pages respond smoothly, uploads complete and video plays without frequent interruptions. Don’t treat a brief test as a long-term verdict, or repeatedly interrupt your work to chase a smaller number on screen.

You’re done testing when you can explain which requests use the connection, whether your main services work and whether the network returns to its expected state when you disconnect. Keep the working configuration as a baseline for future changes. If your environment changes, you can compare against a known-good setup rather than starting over with a fresh installation.

Maintenance & renewals: keep account and device details in sync

Check routine status before problems arise

You don’t need to keep changing your settings, but it’s useful to know what to check from time to time: account benefits, data balance, subscription update status, selected route and whether the client is running. When you open the panel, make sure you’re signed in to the right account before reviewing your plan. A configuration name saved on your device is just a local label; it doesn’t confirm your account status. Seeing routes in the client doesn’t mean you have data left or that your plan hasn’t changed.

Monthly subscription data resets on the activation date, so use the panel’s displayed date to plan your usage. If background sync, video or file transfers increase for a while, check how your balance changes before deciding whether to change your allowance. Data packages can be used until the data runs out and never expire, but you still need to keep an eye on the balance. If usage is significantly different from what you expected, check activity on other devices using the same account and background tasks on your own device before assuming there’s a billing issue.

Handle subscription updates and client updates separately

A subscription update refreshes routes and remote configuration details; a client update changes the software running on your device. One doesn’t replace the other. If the route list is out of date, update the subscription. For compatibility or client issues, check the client information provided in the panel. Before updating the app, note the current configuration and any local settings you need. Afterward, check that the subscription is still selected, permissions are in place and the proxy coverage is as expected.

Don’t download tools from unknown sites that claim to repair your account automatically or unlock every route. Get the client from the panel and the subscription from your current account. If the download page changes, return to the panel to check rather than using an installation link from an old chat. When you stop using a device, remove saved subscription details and check that no browser session still has access to your account.

After a network switch, system update or wake from sleep, your device’s connection environment may have changed. Check the local network first, then the client connection and selected route. If an issue happens only after waking, try disconnecting and reconnecting, and make sure the client is running properly again. Don’t turn a temporary problem into a complex permanent rule. If it keeps happening, note the conditions and check whether it’s triggered by a network change, a background process stopping or a change in system permissions.

Check your current order before renewing or upgrading

If you want to continue your service or add capacity, check your current account benefits before visiting the plans page. Confirm whether the current order is complete so you don’t repeat the same request in multiple tabs. For a mid-cycle upgrade to a monthly subscription, the price difference is converted into remaining days; use the change summary in the panel rather than calculating a new term yourself. If both a data package and a monthly subscription appear in your account, follow the rules shown in the panel instead of assuming they combine or offset each other.

After payment, check the order and account benefits again, then update your subscription in the client and test the services you rely on. You don’t need to delete a working configuration just because you renewed. Whether you need to import it again depends on whether the panel details changed and what the client reports after updating. If your account looks fine but the device still shows an error, check the cached configuration and which subscription is selected first. Treat billing and device setup as separate issues to avoid unnecessary reinstalls and repeated steps.

Keep troubleshooting notes in the order things happened

Maintenance notes can be simple: write down what you did before the issue, which network you were using, what failed and what fixed it. Don’t save the full subscription link. If one change resolves several symptoms, record the exact steps so you can tell whether a future issue is similar. When contacting support, focus on what you observed rather than presenting a guess as a confirmed cause.

If the service doesn’t fit your needs, check the application process under the 7-day money-back guarantee and contact support through the customer support guide or a panel ticket. Keep the relevant order details after submitting a request, and avoid creating new orders that may be hard to distinguish while you wait. The goal of routine maintenance is to keep your account, subscription and devices in sync—not to cover up an undiagnosed issue with ever more settings.

Advanced routing: understand proxy coverage and route selection

Rule mode vs. global mode

Once the basic connection is stable, you can explore routing modes. Rule mode uses the configuration’s matching rules to decide where requests go; some may connect directly while others use a proxy. Global mode generally sends requests the client can handle through the selected proxy policy, but it doesn’t mean every request from your device is intercepted. The actual result also depends on system proxy settings, virtual network interfaces and app-specific settings, so consider the mode and its coverage together.

Before changing modes, note the current mode and route, then test one task with a result you can clearly judge. If a destination works in global mode but not in rule mode, check the rules and how the relevant domains are handled; that doesn’t by itself show that the route quality changed. If both modes fail, return to the basics—connection, DNS, account benefits and destination platform status—instead of adding more rules.

System proxy, app proxy and interface-level routing

The system proxy mainly affects apps that follow the system settings. Some terminal apps, games and standalone network components use their own connection methods. Virtual network interfaces can intercept a different range of requests, but usually require extra permissions and routing setup; use them as described in the client’s documentation. If one app doesn’t change, don’t assume the subscription has failed. First check whether that app falls within the traffic the current client can handle.

If an app has its own proxy settings, check the address, port and proxy type the client is actually listening on before entering them. Don’t assume a port from an online example is the right one for your device, and don’t expose a local proxy to other devices just for convenience. The listening range on a shared network affects who can access that proxy. If only this device needs it, keep the range limited to what you need to avoid extra maintenance.

Route types aren’t a performance ranking

IEPL dedicated lines, relay routes and direct connections describe different ways of routing traffic. A dedicated line uses specific network resources, a relay route passes traffic through an intermediary, and direct connections use a different path to the destination. The name alone doesn’t tell you how well it will work on your network or guarantee that a destination platform will be available. Check the locations and your requirements, then test with the tasks you actually use; don’t assume one route type is always better than another.

Keep DNS and routing changes reversible

DNS and routing rules can affect each other. One app may request multiple domains, and sign-in, static assets and content delivery may use separate services. Adding a rule for just the homepage may not cover the entire service. Before making changes, check whether the client provides connection logs or rule-match information, then use actual requests to guide your diagnosis. Don’t import large rule sets from unknown sources: new rules can change access to your destination and disrupt local services that were working fine.

Change only the settings related to the issue at hand, and keep a way to roll them back. If the client distinguishes subscription content from local overrides, first check which settings will be kept and which will be replaced when you update. Changes made directly to a remotely generated configuration may disappear on the next subscription update. Conversely, local overrides that remain in place may prevent a new configuration from working as expected. Check both the remote details and any local additions during maintenance.

If your work depends on keeping a session active, avoid switching regions or routes frequently. An exit point change may prompt the destination platform to verify your login again, or force an in-progress transfer to restart. Finish the task you’re working on before comparing routes, then keep a reliable option as your usual choice. Test streaming services and AI tools on the destination platform itself; one successful attempt doesn’t guarantee permanent availability, and network changes don’t replace account requirements.

You should now be able to handle the full process yourself: understand the service, choose a billing option, check your account and order, get your subscription, import and test it on your devices, then adjust routing if needed. For unfamiliar terms, see subscription and routing terms: a quick reference. To revisit the shortest setup path, return to the quick start guide. Keeping a working baseline and checking changes one at a time is the key to maintaining a reliable connection over time.