Complete Setup Guide

International routes and the role of your client

First, understand the account, subscription, and connection

JiaVPN provides cross-border ecommerce acceleration and international route subscriptions. Think of the setup as connecting your work devices to a choice of international exit points: your account identifies you, your plan determines the available data and billing terms, your subscription delivers configuration to the client, and the client handles network requests according to the route and traffic rules you select. These steps are related, but they are not interchangeable. Being able to sign in to the dashboard does not mean the client has imported a configuration. Seeing a configuration name in the client does not mean the target app is using that route.

For cross-border sellers, start by identifying the services you need to access. A store dashboard, media uploads, customer support tools, and research resources may run in different apps, each with its own sign-in session. A network service handles connection and route selection; it does not replace a store platform’s identity checks or change its regional rules, account requirements, or content permissions. Being able to open one website does not prove that every business app is ready to use. Verify the pages and tasks you actually rely on, rather than judging by the client icon alone.

A route name does not tell you how well it will perform

JiaVPN covers 100+ countries and 240+ routes, giving you a choice of international exit points. A region label helps identify the exit location, but it does not describe the full route from your local network to that exit. IEPL, relay, and direct routes use different network arrangements; choose based on the details shown in the dashboard. The routes and types available for each region are those in the current list. Do not assume every region has the same options just because a particular route type appears elsewhere.

Everyday connection quality can also depend on your local broadband, Wi-Fi signal, system network permissions, and the status of the service you are accessing. Having route options does not guarantee the same experience on every network. A useful troubleshooting order is to check your local connection, confirm the subscription is available, make sure the client is handling traffic from the target app, and then compare the exit region and route type. This narrows the issue to a specific step and avoids repeatedly reinstalling software or changing several settings at once.

Connection status is only the first check. Verify account access, configuration import, tunnel status, and access to your work pages separately. The steps below walk you through each check.

Prepare your devices and work notes

Supported platforms are Windows / macOS / iOS / Android / Linux, with unlimited devices online at once. Unlimited devices refers to the number of devices, not a separate data allowance for each one. When devices use the same account, check usage against that account’s plan rather than treating a client’s local statistics as the dashboard balance. Other apps on the same network can use data too, especially cloud sync, media downloads, and system updates. Check these background tasks before relying on the connection for work.

Before you begin, prepare a device with working internet access, a password manager for your username and password, and a private note for your current setup. Record only the platform, selected region, proxy mode, and any symptoms. Do not store subscription links or passwords in a note you might share. JiaVPN’s stated privacy policy is no logging; distinguish client-side connection records used for troubleshooting from the service’s server-side policy. Before sharing diagnostic details, check for account information, business domains, or configuration credentials.

This guide follows the usual setup for personal devices. If your device is managed by an employer, network permissions, certificate installation, and system proxy settings may be restricted by policy. Check what changes are allowed first, and do not remove workplace security settings just to get a client running. Once ready, continue to plan selection. To review the current regions, visit the route list; actual availability is shown in your user dashboard.

Choosing a monthly plan or data package

Choose a billing option based on your usage

When choosing a plan, consider how consistently you use the service and what your work involves. If you use store tools and collaboration apps every day, start by comparing the data allowances in the monthly plans. If you mainly connect while traveling, working through a batch of media, or accessing resources occasionally, consider a data package. This is a difference in billing and data rules, not a promise that one plan is faster. No speed differences between tiers or annual discounts are listed, so do not assume additional benefits that have not been published.

Monthly plan data resets each month on the date you activate the plan, not at the start of the calendar month. Check the dashboard for your actual reset date rather than assuming your allowance renews at month-end. Monthly plans include ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Compare both price and allowance, not just the monthly price. Check your account overview for the current plan, remaining data, and expiration status.

Estimate data from your work, not hours online

Browsing store spreadsheets and uploading video files use very different amounts of data. Time online tells you how long you stay connected, not how much data you need. A better approach is to list your typical tasks: uploading product photos, video calls, cloud sync, streaming, sending attachments to AI tools, and background updates. Check how much data these tasks actually use before choosing a different tier. Other people’s usage patterns are not a guarantee of how much data you will need, and do not base a purchase on conversion estimates that have not been published.

Data packages last until the data is used and never expire, making them useful when your usage is irregular. This applies to the package itself; it does not guarantee that an app will always be compatible, regional rules will never change, or data from different products will combine automatically. If you already have a monthly plan, check how the products and order work together in the dashboard before adding a data package. For details on combining, replacing, or deducting data that are not shown on the page, contact support rather than making assumptions.

Plan upgrades. If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. Do not calculate a daily rate that has not been published or assume an upgrade starts a full new billing period.

Check refund and payment terms together

JiaVPN offers a 30-day money-back guarantee and supports Alipay / WeChat Pay / USDT. A refund guarantee can reduce the risk of trying the service, but it is not a substitute for testing it. After activation, check your usual network, the business pages you need, and the relevant client as soon as possible, and note any issues. Read the refund policy for eligibility and process details. This brief guide is not a substitute for the full terms, and payment method names do not imply a particular processing time or additional service.

Before ordering, review the full pricing and plan details on the plans page. Compare the billing option, data allowance, and account status together to avoid selecting a monthly plan when you meant to choose a data package. If you do not yet know your usage, there is no need to estimate long-term discounts based on untested needs. Track your actual usage first, then use the dashboard to decide what to do next. That makes costs easier to manage than simply choosing the largest allowance.

Set up your account and confirm your order

Create an account with a username and password

Start the account setup process from the user dashboard. JiaVPN does not require an email address; create an account with a username and password. Choose a username you can recognize, but do not include your store name, customer details, or other sensitive business information. Use a unique password and store it securely in a trusted password manager. Do not confuse the client’s configuration name with your dashboard username, or a subscription link with your login password. They serve different purposes and should be kept distinct when troubleshooting.

Before submitting, check your keyboard layout, spaces, and password confirmation. Copying and pasting can introduce leading or trailing spaces, and autofill may enter outdated credentials from another site. If sign-in fails, verify the username and then check the password; do not keep guessing different combinations. Because account setup does not require an email address, do not assume that email recovery is available. Use the recovery process shown in the dashboard, if any. Safely storing your credentials ahead of time is more reliable than looking for a recovery option that may not exist.

If you already have an account, use the dashboard sign-in. Do not create another account to resolve an issue with an existing order, as that could separate your payment history from the subscription you use. After signing in, check the account overview for your username, plan status, and usage. Public devices are not suitable for keeping a signed-in session. If you must use one temporarily, sign out when finished and avoid saving your password or configuration in the browser.

Review your order before paying

Select the relevant product in the plans section of your dashboard, then review the order name, price, billing option, and data allowance. Once these match your selection, use a payment method offered on the page. Alipay / WeChat Pay / USDT are the published payment options, but follow the instructions shown for your specific order. Do not pay using payment details forwarded in a chat, search result snippets, or old screenshots, and never use someone else’s order link as your payment page.

After paying, return to the original dashboard and check the order status instead of relying only on the success message in your payment app. Payment, order, and plan activation statuses may appear in different places, so check each one. If the order has not updated, keep a record of what you see and revisit the order page and account overview. Do not immediately create another identical order, which can make reconciliation harder. A closed browser page does not mean the original order was canceled.

Keep order evidence, not public screenshots. Payment records and order IDs can help support review a ticket. Before sharing anything, hide payment account details, personal information, passwords, and subscription links.

Configure your client after activation

Once you confirm your plan is active, note the billing option, data allowance, and term shown in the dashboard before getting your subscription and client. If the order is marked complete but the corresponding benefits do not appear in your account, start by checking the account linked to the order and its status. Common things to verify include whether you are signed in to the account used for payment, whether the page is out of date, and whether you are viewing a different order. Save the status descriptions you see so support can identify whether the issue is with payment or service delivery.

If you need help, submit a request through user dashboard support. Include the plan selected, payment method, order status, and checks you have already completed. Do not share your password or send a complete subscription link to prove account ownership. Distinguish between “payment did not complete,” “order has not updated,” “plan is not showing,” and “client cannot connect.” These issues require different troubleshooting steps; a vague “it does not work” report means more back-and-forth.

Once your account and order are confirmed, move on to getting your subscription. There is no need to keep changing payment or account details to resolve a network issue. If the plan looks correct in the dashboard but the client still fails, check the subscription, import, permissions, and route in turn. Keeping the transaction process separate from the connection process helps you avoid changing an existing order while troubleshooting the client and makes it easier to review a refund or renewal later.

Get, import, and update your subscription

What does a subscription link do?

A subscription is how your client retrieves routes and configuration; it is not a general information page. The client uses it to fetch available options and retrieve updated configuration when you refresh it. The link may contain sensitive information that identifies your account, so protect it like a credential. Do not post it on public forums, submit it to online conversion tools, place it in shared documents, or include it in screenshots. Never send it to an unfamiliar website just to test whether it works. Marketing pages do not provide live subscription links; get yours from the user dashboard after signing in.

Open the account overview, confirm your plan is active, then find the subscription and import options provided in the dashboard. If the dashboard offers client-specific options, choose the one for the software you are using. Configuration formats are not necessarily interchangeable: a client may recognize route names in a link without fully supporting all its rules. Follow the current setup instructions in the dashboard rather than changing formats based on a tutorial for a similar-looking interface.

Automatic handoff vs. manual import

Automatic import usually relies on the browser opening a locally installed client. After you click, the system may ask permission to open the app. Confirm that it is the right app before proceeding. If nothing happens, check that the client is installed and running and that the browser has not blocked the handoff. No pop-up does not mean the subscription is invalid. You can return to the client’s subscription or configuration manager, follow the dashboard instructions for manual import, and check whether the route list appears.

For manual import, paste the complete link; do not copy only the short text shown next to a button. Give the configuration a clear local name, such as one that distinguishes a work device from a test setup. The name itself does not change your plan or route access. After importing, check that the new configuration is selected. Some clients keep multiple configurations, so a successful import may leave the old one active. Confirm which entry is active; this is usually more helpful than repeatedly importing when the list is there but the old route is still in use.

A subscription is not a single route. It maintains a set of configurations. Copying one route manually may make future list updates less convenient; check the dashboard for supported options.

When an update fails, check downloads and connections separately

Updating a subscription is a network request; connecting through a route is a separate action. A route that is temporarily unavailable may still appear in an older client configuration. Conversely, a failed subscription download does not necessarily mean every saved route is unusable. First identify where the error occurs: configuration cannot be fetched, format cannot be parsed, the list is empty, or a selected route cannot reach the target page. Record the exact error and platform instead of labeling every issue “subscription expired.”

If a fetch fails, first confirm your local network works, then check that the link is complete, your account benefits are active, and the dashboard has no relevant notice. For a parsing error, check that the client supports the subscription format. Do not delete configuration fields you do not understand; that may hide the error temporarily while breaking traffic rules. Also avoid forcing the subscription download through a route that is already failing, which can create a loop where you need a working connection to update the configuration needed to connect.

An update may refresh route groups or overwrite some local edits, depending on the client. If you need to keep personal rules, first understand how local overrides interact with the remote configuration. Do not casually edit route parameters generated by the subscription in the main configuration. A good maintenance approach is to let the remote subscription deliver routes and use supported local overrides for personal preferences. Keeping the two separate makes it easier to understand changes after an update.

If you suspect your subscription link has been exposed, check whether the dashboard provides a reset option and use it if available. If it does not, submit a support ticket. After a reset, replace the old link on every device, not just the one in front of you. Then check the configuration on all work devices and remove any copies stored in public locations. Protecting your subscription is an ongoing responsibility, not something to consider only during the initial import.

Import the client configuration on each platform

Download clients from the user dashboard downloads section. After signing in, clients are available for Windows, macOS, Android, and Linux; the dashboard handles the iOS download option according to your account status. The steps below describe the general setup sequence and do not assume every platform uses the same button labels. After installation, import your subscription, select the active configuration and route, and enable the connection method offered by the client. If the interface differs, follow the dashboard instructions and the options available in your client.

Windows: distinguish system proxy settings from app connections

After installing the client, open its configuration or subscription manager and import using the option provided in the dashboard. Check that the route list appears, select the active configuration, and enable the connection as instructed by the client. If Windows asks for network permissions, first confirm that the prompt comes from the app you installed. A system proxy usually affects only software that follows system proxy settings; it does not automatically cover every program. If your browser works but another business app does not, check whether that app supports proxies before changing route settings.

Other network tools running on Windows may override system proxy settings. To troubleshoot, quit any unneeded tools of the same kind, note the current settings, and test the client again. If webpages stop working after you close the client, check whether the system proxy still points to a local service that is no longer running. Do not solve permission problems by disabling security software, and do not copy another device’s local port. Read the listening address and port from your own client.

macOS: approve permissions and confirm the active configuration

Get a compatible client from the dashboard, then install and open it as prompted by macOS. The system may request authorization or approval for a network extension when the client enables network features, depending on how it is built. Check which app the prompt refers to, then allow the relevant operation in System Settings. After importing your subscription, confirm the new configuration is active rather than an empty default profile. If the menu bar shows a connection status, also check the route and proxy mode in the main window.

If something goes wrong after your Mac wakes from sleep, first confirm that the local network has reconnected, then disconnect and reconnect the client. External network adapters, workplace network settings, and other proxy tools can change the order of network services. Avoid changing several interfaces at once. Before removing an old configuration, keep a record of your subscription source and local rules so you can tell which setup belongs to the current account.

iOS: review the system’s connection permission

Continue through the iOS client option provided in the user dashboard; the dashboard supplies the available link. After installation, add your subscription using the import method provided in the dashboard, then check the route list and selected entry. When you first enable the connection, iOS may ask permission to add a network configuration. Continue only after confirming that the request came from the client you are setting up. A connection indicator in the status bar or Settings only shows that the network feature is enabled; test access in the target app as well.

Other network configurations on iOS may affect the active connection. When troubleshooting, check whether another configuration of the same kind is enabled. After switching between Wi-Fi and mobile data, test your work pages again rather than relying on the previous result. If import fails, determine whether the issue is with the dashboard’s delivery requirements, the system’s app handoff, or client parsing. Do not remove device management settings used for other purposes or share your subscription link publicly for someone else to test.

Android: check background activity and per-app settings

Install the client provided in the dashboard, import your subscription, and confirm the system’s network connection permission when enabling the connection. Android battery management may restrict background activity, causing the connection to drop while the screen is locked and return when you open the app. If that pattern occurs, review the client’s background and battery optimization settings, and adjust them only after understanding the effect. Do not assume the route is constantly failing. For a comparison, see our guide to Android background operation and per-app proxy settings.

Clients with per-app proxy support may require you to check whether the target app is on the include list or exclude list. Read what the current mode actually does instead of relying on the toggle name. If a browser works but a store app does not, first confirm that the app is included as intended, then reconnect. Other network tools on the device may compete for connection access. Keep track of which configuration is active, and avoid repeatedly launching multiple tools while testing.

Linux: distinguish desktop proxy settings from process environments

Get a compatible client as described in the dashboard and import the configuration. A desktop environment’s system proxy, proxy environment variables in a terminal, and other network-handling methods in the client may affect different traffic. A graphical browser working does not mean tools launched from the terminal inherit the same settings; a temporary terminal setting may not affect desktop apps either. When testing, note how the app was launched and which environment is active. Use only connection methods the client explicitly supports.

If you need to configure a command-line tool to use a proxy, read the actual listening parameters from the client first and follow that tool’s documentation. Do not copy a fixed port from another guide. If a local port is occupied, permissions are denied, or a network interface reports an error, save the error text and check for an old process still running. After testing, remove temporary environment settings you no longer need so the command-line tool does not keep trying to reach a local proxy after the client has closed.

Check connection status and access to work apps

Check your local network before the exit route

Start connection testing with the local network. Temporarily disconnect the client and check that websites and local business resources you normally access directly are working. If the basic connection is already failing, troubleshoot Wi-Fi, network authentication, or broadband first. Some public networks require you to confirm access in a browser; the client cannot replace that step. Once the local connection is working, connect to your chosen route so you do not mistake a local outage for an account or subscription issue.

When the client shows a connection, check the current route region, active configuration, and proxy mode. Use a trusted exit lookup to see whether requests appear to come from the expected region, but do not treat any lookup site’s label as definitive proof of location. Databases can describe the same exit differently, and a single lookup only reflects the path used for that request. To verify a store app, test the app itself rather than relying only on a browser lookup.

Break the task into repeatable steps

For a store dashboard, you could check the sign-in page, product list, image upload, and saving a draft in sequence. If the page loads but images do not, the images may come from different domains. If sign-in works but uploads fail, the issue could involve attachment requests, app permissions, or the target service. Keep the selected route unchanged while testing, and note the exact failed action and page message. Do not switch exits repeatedly while an upload is still in progress; that makes it difficult to match the service session with the local connection state.

Verify AI tools and streaming by feature as well. A successful text request does not guarantee that file uploads work, and opening a homepage does not mean content from a particular region will play. The target service may set its own account-region, payment eligibility, or content licensing requirements; route selection cannot replace them. For AI tool access scenarios, see our ChatGPT access guide. For viewing issues, see the streaming guide. The checks in these guides are not guarantees that every feature will work.

Check DNS and proxy scope separately

DNS resolves domain names to network addresses, while proxy rules determine which path a request takes. They are related but not the same. Changing DNS alone will not make every app use a route, and an expected exit region does not prove that every DNS request follows the same policy. If the client has DNS options, first understand its current defaults before changing them. Stacking separate DNS settings in the system, browser, and client can make troubleshooting harder.

On Windows, use the system command below to view network adapters and DNS settings. It only shows local status; it does not confirm that the proxy is working or change any settings. Command output may include device names and local network details, so share only the relevant parts in a support ticket rather than posting the whole output publicly. On other platforms, check the network information provided by the system and review the current settings before drawing conclusions.

ipconfig /all

Change one condition at a time. Keep the app and test action the same while comparing routes, modes, or local networks. This makes it possible to tell which change affected the result.

If the issue persists, collect your platform, network environment, current region, proxy mode, failed action, and exact error message, then submit a support ticket. Avoid sending only a screenshot captioned “doesn’t work,” and never share complete subscription credentials. For a more detailed verification approach, see our guide to checking exit IPs, DNS, and per-app routing. The goal of troubleshooting is not to make every status indicator look normal; it is to confirm that your actual work can follow the intended path.

Routine maintenance, data usage, and renewals

Use the dashboard as the source of truth for account status

After setup, focus on keeping the account, subscription, and device configurations in sync. Check the plan, data, and expiration notices in your account overview regularly, and confirm that the client is still using the subscription for that account. Client-side statistics are useful for tracking device activity; dashboard usage reflects the account allowance. They may cover different activity or refresh at different times, so do not expect them to match at every check or change your account records based on the difference.

Monthly plan data resets each month on the activation date, so plan work around the reset shown in the dashboard rather than the calendar month. Data packages last until used and never expire; they do not follow the same monthly reset schedule. If your balance drops faster than expected, check media sync, cloud backups, streaming, and system updates, then review the traffic rules. Unlimited devices are supported, but background activity on several devices can be easier to overlook.

Save the reasons for local changes before updating

When the route list needs updating, use the subscription update feature provided in the dashboard rather than relying on parameters copied from an old screenshot. Before updating, note the selected route group and any personal overrides. Afterward, check that the configuration is still active. If route names change, do not assume a similarly named route is identical to the old one; review the dashboard details and retest important tasks. Avoid updating while submitting products, uploading files, or attending an important meeting.

Updating the client and updating the subscription are separate maintenance tasks. The former concerns software and system compatibility; the latter refreshes remote configuration. If an issue appears, identify which update you just performed and save the error message. Get clients from the dashboard instead of searching for installation files with a matching name. After an update, check network permissions, auto-start, and the active configuration. A client opening successfully does not mean all previous behavior has been preserved.

Keep only essential maintenance notes. Record the platform, configuration source, selected route, and reason for the change. Do not put passwords, complete subscription links, or payment details in ordinary work notes.

Check renewals, upgrades, and product changes separately

Before renewing, confirm which account you are using and which product is active, then review the order in the dashboard. Do not assume the new order will match your last payment or automatically extend the current term. Check the instructions for that order to understand how it affects your remaining term and data. If the page is unclear, ask support before proceeding, especially when switching between a monthly plan and a data package.

If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. Do not assume the old and new data allowances simply add together or calculate an unpublished daily price yourself. After upgrading, check the account overview for the active tier and term shown in the dashboard. For full pricing, revisit the plans page, not an old screenshot on another device. No annual plans or discounts are listed, so do not infer that JiaVPN offers them from articles about annual subscriptions.

Moving to another device or stopping use

When moving to a new device, get the client and subscription again from the dashboard. Confirm the new device can complete your actual tasks before removing data from the old one. Do not bundle up the entire client directory and send it to someone else; it may contain credentials, local logs, and personal rules. If you are handing off an old device, sign out of the dashboard, remove the client configuration, and check for saved browser credentials. Unlimited devices does not mean you should ignore account access on each one.

If you need a refund, review the refund policy and contact support through the dashboard ticket system. The stated refund guarantee is 30 days, no questions asked. Include the relevant order and what you are requesting. Deleting the client does not replace the refund process, and disconnecting does not cancel an order. As a final maintenance check, confirm the status of your transaction and configuration separately: stopping the software is a device action, while account benefits must be checked in the dashboard.

Traffic rules, route selection, and work environment management

Keep your work conditions consistent before comparing routes

Once the basic connection works, the goal of advanced setup is to avoid unnecessary changes. For store dashboards, ad management, and collaboration tools, keep the account environment and exit selection consistent. Frequently switching regions is not a general optimization strategy: a platform may assess sign-in activity according to its own rules, and a network service cannot replace the platform’s risk checks. If you need to change regions, finish saving and uploading first, then switch and verify the session again. Avoid changing routes repeatedly while a critical request is in progress.

When comparing routes, keep the local network, target app, and test action fixed; change only one factor, such as the region or route type. IEPL, relay, and direct describe different network arrangements, not a definitive ranking. A route that works better for file uploads on your current network may behave differently on another broadband connection, app, or at another time. Recording repeatable results is more useful for future choices than remembering a one-off client test.

When to use rule-based and global modes

If a client offers rule-based mode, it typically selects a request path based on a domain, address, or other condition. Global mode generally sends requests within its scope through the selected exit. The precise behavior depends on the client; mode names are not universal standards across software. Global mode also does not necessarily take over every app, since system proxy settings still have their own scope. Comparing modes can help identify whether rules are involved in an issue, but restore the setting you prefer for everyday work after testing.

If you need custom rules, identify the resources used by the task rather than adding only the homepage domain. Sign-in, images, attachments, and APIs may use different domains, so narrow rules can let a page load while its features fail. Overly broad rules can also route traffic from apps that do not need it. Save the reason for each change, add only rules you can explain, and test their effect on local resources and other work apps.

Local ports, sharing, and router limits

A local proxy listener lets an app pass requests to the client. Use the listener address, port, and protocol shown in your current client. Do not confuse local listener settings with the server details for an international route, or copy another person’s port configuration. If an app has its own proxy settings, check which protocol it expects before entering the details. It may retain those settings after the client closes, so when troubleshooting, check for an old configuration pointing to a stopped local service.

Making a listener accessible across your local network changes which devices can reach the proxy; do not enable it just for convenience. Router setup also depends on the device architecture, system compatibility, storage, and networking capabilities. The platforms confirmed here are Windows / macOS / iOS / Android / Linux; this does not mean every router is supported. If you have a specific need, describe your device setup in a support ticket and confirm what is supported before making changes.

Keep a way to roll back. Advanced settings should have a clear purpose, a way to verify the result, and a recovery path. Without those, the verified default setup is usually easier to maintain.

Turn troubleshooting results into a repeatable workflow

Keep a short record for common tasks: the local network, selected region and mode, and which pages and upload actions you verified. Do not include sensitive parameters; focus on conditions that let you reproduce the result. If something goes wrong next time, check whether the network, client, configuration, or target app has changed, then troubleshoot each factor in turn. This helps distinguish a one-off loading issue from a persistent configuration problem and gives support a clear path to reproduce it.

After reading this guide, you should be able to complete the process on your own: confirm your account and plan, get your subscription, approve platform permissions, select a route, verify your work tasks, and manage usage and updates. For quick steps, return to the guides page. For a specific issue, visit the help center. Complex configuration is not the goal; what matters is understanding why traffic takes its current path and knowing how to return to a verified setup if something goes wrong.