The Complete JujuVPN User Guide

The service, subscriptions, and routes

JujuVPN is a subscription service for cross-border network access. To understand how to use it, start by distinguishing your account, plan, subscription URL, and client app. Your account lets you sign in to the dashboard and view orders. Your plan determines your available data and billing terms. The subscription URL provides the client app with route configurations available to your account. The client app establishes the connection on your device. These are related, but they are not interchangeable. Signing in to the dashboard confirms only that your account login works. Seeing routes in the app does not confirm that your plan is active or that the connection works.

The path from your device to a service

A request passes through the app on your device, your local network, the route selected in the client, and the destination website. A problem at any point can cause slow loading or prevent a page from opening. For example, hotel Wi-Fi may require web sign-in, the client may not have enabled the system connection, or the selected exit location may not meet a service's regional requirements. Each calls for a different fix. Rather than treating every issue as a reason to switch routes, this guide starts by identifying where the problem occurs. Describing what kind of access fails is usually more useful than repeatedly changing settings.

JujuVPN covers 100+ countries with 190+ routes and offers access for Windows / macOS / iOS / Android / Linux. Unlimited devices can be online at the same time. Coverage describes the range of available exit locations; it does not mean every route will work the same way with every website. Regional licensing, a website's risk controls, and your local carrier's routing can all affect access. When choosing a route, consider the destination region, connection performance, and what you need to do. There is no need to prioritize a farther-away location or an unusual route name.

Route types and what to expect

The route list may include labels such as IEPL, relay, and direct. IEPL usually means the path uses a dedicated line; relay means traffic passes through an intermediate entry point; direct means a more direct connection to the exit. These labels describe how the path is arranged, not the speed you will get on a particular visit. The same route type can also perform differently on different local networks. Choose a route in the right region first, then compare other types in that region to see whether differences come from the location, route, or local network. See the global locations page for full regional details.

Privacy policy and account security

This service follows a no-logs policy. That does not mean destination websites will not record account activity, or that your browser accounts, extensions, and site permissions will change automatically. Continue to manage website passwords, authorized devices, and browser sync as usual when using a network acceleration service. A change in exit location does not erase your identity; a website may still recognize you through an account you are signed into. If you use a work device, follow your organization's rules for remote access and device management.

Before setup, make sure your local network can open regular websites and that your device runs a supported platform. Complete any network sign-in first, then open the user dashboard. If you already have another proxy tool on the device, note its current settings to avoid having old and new connections handle requests at the same time. Then proceed in order: plan, account, subscription, client app. These checks may seem like extra steps, but they help prevent mistaking a payment issue for a connection problem or an outdated subscription for a route failure.

Choose a monthly plan or data pack

Before choosing a plan, consider how regularly you will use it. If you work across borders daily, often use AI tools, or stream regularly, a monthly plan may be easier to manage. For travel, temporary projects, or occasional access, compare data packs that never expire. The difference is how you add data and how you use it—not that one option suits everyone. If you are unsure how much data you need, track what your actual tasks use before choosing a capacity. That is more reliable than guessing based on the number of devices.

Estimate data based on your tasks

Data use is not limited to websites you open yourself. Cloud storage sync, system updates, autoplay videos, and background apps can all transfer data. To estimate what you need, track work files, everyday browsing, and streaming separately instead of focusing only on how long a connection was active. Connection time and data use are not the same: staying connected without transferring much uses less data than continuously downloading files. Do not choose a plan based on an unverified claim of a fixed amount used per hour.

Unlimited devices can be online at the same time, but that does not mean data is unlimited. If computers, tablets, and other devices use the same account, keep an eye on total account usage. If devices show different data totals, use the plan details and usage status in the dashboard as your reference. Switching devices does not necessarily mean you need more data; adding ongoing sync tasks may have a more noticeable effect. Work out what you need before ordering so device count and data allowance do not get confused.

Resets, upgrades, and data pack limits

Monthly plan data resets each month on your activation date, not on the first day of the calendar month. After placing an order, check your activation and reset details in the dashboard rather than relying on someone else's dates. If you upgrade mid-cycle, the price difference is converted into remaining days. Do not assume it adds a fixed period or a set amount of data. Review the change shown on the upgrade confirmation page. If it is not what you expect, go back and check the order before proceeding with payment.

Data packs are valid until used and never expire, making them suitable for irregular use. “Never expires” describes the validity of unused data; it does not mean you can keep using the service after the data runs out. Do not assume monthly plans and data packs automatically combine or top each other up. Before changing billing options, review the confirmation details in the dashboard to understand what happens to your current benefits. Do not assume stacking priority, rollover rules, or automatic renewal details that have not been specified.

Keep a record of what you confirm before ordering

JujuVPN accepts Alipay / WeChat Pay / USDT and offers a 60-day no-questions-asked refund. Before paying, check the plan name, price, billing option, and data rules. Review the refund policy in the Terms of Service. Use the pricing page and the order confirmation in your dashboard to verify plan details. Do not rely on an old tutorial screenshot as a record of your current order, or infer processing times, fees, or exchange-rate arrangements from the payment method.

If you are still unsure about capacity, list the tasks you need to complete and distinguish occasional use from regular use. Leave room to adjust for uncertain needs instead of treating a large download that has not happened as your everyday baseline. The goal is to match the plan to your actual usage, not to predict every possible future scenario at once.

Create an account and confirm your order

JujuVPN does not require an email address. Create an account with a username and password using the account link on the site to open the user dashboard, then follow the prompts to set them up. Choose a username you will recognize and a password you do not reuse on other websites. Store it in a trusted password manager. Before creating an account, make sure you are on the official site; do not enter your credentials on a similar-looking address from an unfamiliar message. Because no email address is required, do not assume there is an email-based account recovery process.

Confirm that your account was created

After submitting the form, check that the dashboard shows you are signed in and displays an account overview. Clicking the button, seeing a loading indicator, or saving the password in your browser does not by itself confirm that the account was created. If the username is taken, choose another one as prompted. If the form reports an invalid format, correct the relevant field and try again. If there is a network error, check the page before taking further action. Avoid repeatedly creating similar accounts, which can leave orders and subscriptions split across different usernames.

Once you can access the overview, check the account name and go to the plans section. If you already have an account, sign in to it and check your existing plans and orders instead of creating a new account to restore your connection. Browser autofill may select old credentials, and a public device may still be signed in to someone else's account. Confirm that the account is yours before ordering so you do not have to look for the subscription in another account after paying. It is not necessarily a problem if no routes are available yet; confirm the plan status first.

From plan selection to payment

Select the plan you decided on in the dashboard and proceed to order confirmation. Check the plan name, data, price, and billing option, paying particular attention to the difference between a monthly plan and a data pack. For a mid-cycle upgrade, review the confirmation showing the price difference converted into remaining days; do not calculate the result from the unused data on your old plan. Once everything looks right, choose Alipay, WeChat Pay, or USDT. Payment pages vary by method, so follow the instructions for your current order.

Keep the order reference details during payment and check that the amount on the payment page matches the order. When paying with USDT, follow the network, address, and amount shown on the payment page exactly. Do not reuse payment instructions from another order or send funds to a sample address in a guide. This guide does not provide payment addresses or on-chain transaction details; get those from the current dashboard only. If the page is interrupted during payment, return to your order list and check its status rather than paying again because you did not see a completion animation.

Check payment and plan activation separately

After the payment provider reports completion, return to the dashboard to check the order status, then check whether the plan is active. These are related results, but each needs its own check. If payment is complete but the dashboard has not updated, reopen the order record and make sure you are in the right account and looking at the matching order. Do not immediately place another order or reinstall the client app to try to fix a payment issue. The client app cannot change an order's status, and further changes can make the issue harder to track.

If you need help, describe the issue through the support ticket portal in the dashboard. Include the order reference, selected plan, payment method, and current status. Hide passwords, subscription URLs, and sensitive payment details in screenshots. Do not post full payment screenshots in public comments. Submit refund requests through the process in the Terms of Service and dashboard. Read the 60-day no-questions-asked refund statement alongside the terms; do not assume additional exceptions or promotional conditions.

If an order is missing after you switch browsers, check the username first instead of assuming the order is gone. Keep the links between your account, orders, and plan clear. Store essential account and order references somewhere private so you can find them when renewing, moving to another device, or contacting support without relying on chat history or browser history.

Get and protect your subscription URL

Once you have confirmed your plan status, open the subscription section of the dashboard and look for an option to get your subscription or import it into a client app. A subscription URL is an address that a client app uses to retrieve configuration; it is not a regular information page or an installer. Once the client app reads it, it can load the route details available to you. The URL may contain information linked to your account, so treat it like an account credential even if it looks like an ordinary link. Do not post the full URL on a public website to see whether it opens.

Choose automatic import or paste the URL manually

Automatic import usually works by having the webpage open the client app on your device. If your browser asks whether to open an app, check which app it is before allowing the handoff. After the app opens, confirm that the subscription was imported; the browser's confirmation that it launched the app does not mean the route configuration was saved. If nothing happens, the client app may not be installed, the system may not have an app associated with the import link, or the browser may be blocking external app launches. In that case, use the copy option in the dashboard and add the subscription manually in the client app.

For manual import, copy the full subscription URL, then find an option in the client app to add a subscription, import from a URL, or something similar. Labels vary by platform, so look for the right function rather than an exact button name. After pasting, check that the beginning and end of the URL are intact and that it does not contain extra spaces, line breaks, punctuation added by a messaging app, or a link title. Give the subscription a recognizable local name so you can tell it apart from older configurations; the name itself does not change the subscription.

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

The URL above is only an example of the format and cannot be used to connect. Get your actual subscription from your own dashboard. Do not change its parameters manually or assemble a supposed “universal subscription” from the example. If import fails, copy the original URL again and check that you chose the right import option instead of editing the account identifier. If the dashboard offers different import methods for different client apps, use the one that matches your app; do not assume every platform can read the same format.

How subscription updates work

After importing a subscription, the client app usually keeps a local configuration. If routes change in the dashboard, the app needs to fetch the subscription again to show the updated list. Refreshing a webpage is not the same as updating the subscription in the client app, and reopening the app does not necessarily retrieve the latest configuration. Find the subscription update option, run the update, and check the result message and that the list still belongs to your account. Do not assume there is a universal automatic update schedule; check your client app's settings.

If an update fails but the old list is still there, check your local network and subscription URL first. Do not rush to delete the only configuration that works. Treat a failed update and the status of an existing configuration as separate issues. If the dashboard opens but the subscription request fails, check whether you copied the wrong URL, chose the wrong format, or are using details from an old account. For more on how these steps differ, see how to get and import a subscription link—and what to do if it is exposed.

What to do if a subscription is exposed or you change devices

Do not put your subscription URL in public screenshots, team documents, or shared browser bookmarks. When contacting support, describe the type of error and hide the URL and any QR code in screenshots. A QR code can contain the full subscription details, so it is not safe to share just because the text is not visible. If you think the URL has been exposed, check whether the dashboard offers a reset option. After resetting it, reimport or update the subscription on your devices as instructed. Changing your account password does not necessarily invalidate the subscription URL.

When moving to a new device, sign in to the dashboard on that device and get the configuration there instead of casually sharing a zipped copy of the old device's data folder. Importing routes does not complete the migration; verify permissions and the connection on the new device too. A subscription is meant to deliver a usable configuration securely, not to circulate indefinitely in chat history as a public link.

Import into client apps on five platforms

The general process on every platform is to get the client app, import the subscription, select the current configuration, allow the required system network permissions, and verify the connection. The entry point is in the client apps section of the user dashboard; sign in to get your subscription. Downloads for Android / Windows / macOS / Linux are available after you sign in. The iOS download option is available when your plan is active. Do not download files with familiar names from unknown search results, and do not treat this guide as a public directory of installers. If interface wording changes, identify the action by its function and expected result.

Windows: Confirm that the configuration is active

Get the client app from the dashboard and follow the installation prompts. Open it, import your subscription, and when the route list appears, check that you have selected the newly imported configuration—not an old one or a blank default. Choose a route, then enable the system connection or system proxy using the option provided by the client app. Some apps have their own proxy settings, which may not change just because the desktop client says it is connected. Test with a regular browser first, then check specific apps. If regular websites stop working after you exit the client app, check for leftover proxy settings.

macOS: Approve system permissions

If a system confirmation appears when you first open the app after installation, check the app's name and source before granting the requested permissions. After importing your subscription, select the relevant configuration and update the routes. A menu bar icon only shows that the app is running; check its connection status too. If macOS asks you to approve a network extension, confirm it in System Settings and then check the client app again. Avoid repeatedly granting permissions while switching between tools. Get one client app working on its own first so you can tell whether a problem is due to permissions or configuration.

iOS: Save the subscription and allow the connection

Use the link provided in the dashboard to open the App Store. The link is available based on your active plan status. After getting the client app, return to the dashboard and import your subscription. If the webpage successfully opens the app, complete any in-app save or confirmation steps. The first time you connect, iOS may ask to add a VPN configuration; verify the source and follow the system prompts. Then select the imported subscription and route and turn on the connection. A VPN status indicator still needs to be followed by a website test. Returning to a dashboard that is still open in your browser does not confirm cross-border access is working.

Android: Check background restrictions

Install and open the client app, import your subscription URL, and check that the route list has updated. When connecting for the first time, allow the VPN connection when prompted by Android. If the connection drops when you switch apps or lock the screen, check whether the system restricts background activity or battery settings pause the app's network access. Settings vary by device, so follow the instructions for your version of Android instead of disabling every battery-saving feature. If another VPN app is already on the device, disconnect it before starting this client app to avoid a conflict over connection permissions.

Linux: Distinguish desktop connections from app settings

Get a client app suited to your environment from the dashboard and install it according to the package format and system prompts. Import your subscription, confirm that the configuration loaded, then select a route and enable the connection method provided by the client app. Linux desktop proxy settings, terminal environments, and settings within individual apps may not be shared. A browser working while a terminal task fails does not by itself mean the route is down. Check the client app's status first, then check how the target app reads proxy settings. This guide does not assume a local listening port or provide generic commands with guessed port numbers, which could put incorrect values in your environment.

On every platform, check both “import successful” and “access works in practice.” If you need to switch import methods, note the name of the current working configuration before changing anything so you do not delete it by mistake. For the shortest setup path, see the Quick Start Guide. To learn what to expect at each step, see a first-time setup walkthrough and common sticking points. After this chapter, verify your connection rather than treating the route list as the end of setup.

Check your connection, exit location, and access

Start with a clear baseline when checking your connection: your local network can open regular websites, the client app has a working subscription, and your plan is active. Then choose a route in the target region, connect, and check whether the client app reports success. Next, visit the website or app you actually need. This helps distinguish a connection that was never established from one that works but cannot access a particular service. If you start by guessing from an error on the destination website, it is easy to confuse account restrictions, browser state, and the network path.

Check one layer at a time instead of changing several settings

First check the client app's connection status, then test a regular website and the service you want to use. If no websites load, check your local network, system connection permissions, and conflicts with old proxy settings. If regular websites work but the target service does not, focus on the exit location, service account, and app settings. Change just one thing at a time—for example, switch only to another route in the same region. Do not also update the client app, change regions, clear your browser, and reset the subscription. Keeping before-and-after states comparable helps you identify what actually fixed the problem.

On hotel or public Wi-Fi, complete the network's web sign-in before starting the client app. If the sign-in page does not appear, temporarily disconnect the client and follow the prompts on your local network's sign-in page. Once authenticated, connect to a route and test it. Do not mistake a failed Wi-Fi sign-in for an inactive plan, and never enter your JujuVPN password on an unfamiliar sign-in page. Local network access and your account with this service belong to separate systems and use different credentials.

Check your exit location and target service

Check the exit location in relation to what you need to do. If you want content from a particular region, confirm that the selected route is in that region, then check the content available or account message shown by the service. Website caches, the region set on a signed-in account, and the service's own policies can all affect what you see. After selecting another route, reload the target page to compare results, but do not treat one successful visit as a guarantee of ongoing access. Availability of Netflix, Disney+, and AI tools depends on actual access and each service's account requirements.

Services such as ChatGPT and Gemini may require more than a working connection; account eligibility, service regions, and usage rules can also matter. If a website loads but sign-in fails, do not assume the subscription is broken. If you are signed in but get a request error, note the exact message and circumstances. Keep the exit location stable while checking account and app settings. Switching regions frequently can make the problem harder to reproduce, so once you find a working route, there is no need to keep changing locations just to compare names. For regional limits on streaming, see the streaming access guide.

Test sustained use, not just one successful connection

Once connected, complete a real task from start to finish—for example, open a work page, submit a request, and read the response. For file transfers and video playback, check for repeated interruptions rather than only confirming that the home page loads. A single status icon in the client app does not mean every app is using the connection. If your browser works but a desktop app does not, check whether it has separate network settings. If only background tasks fail, revisit the platform section and check background restrictions and proxy settings.

To compare stability, keep the device, local network, and task as consistent as possible. Note whether the connection works, whether it drops, and what you were doing when it dropped. This guide does not provide unverified speed-test figures or recommend treating results from third-party speed tests as a measure of how a particular service will perform. Download limits, server-side processing, and local Wi-Fi can all affect speed. See how to compare stability by connection success and dropouts to build your own record.

If the test still fails, write a brief note describing the network, platform, failed task, and anything that did work. This can already rule out many unrelated causes. Then move on to advanced troubleshooting rather than starting over with account creation or payment.

Manage usage, renewals, and device transfers

After your first successful connection, routine maintenance is about account status, data usage, and configuration updates—not repeatedly reinstalling the client app. Keep the subscription clearly named on your regular devices, and know where to find the dashboard and your current billing option. When something goes wrong, check the basics first: are you using the right account, is the monthly plan active, does the data pack still have data, and is the client app using the current subscription? A repeatable check helps avoid scrambling for details when you need the service.

Check usage and reset details

Monthly plan data resets each month on your activation date. Confirm your reset schedule in the dashboard rather than assuming it follows the calendar month. If usage seems higher or lower than expected, check background sync, system updates, autoplay videos, and other devices using the account at the same time. There is no device limit, but that does not make usage on each device independent. A device's own usage counter may cover only certain apps or a particular period. Be aware of these differences instead of adding or subtracting figures from different sources as if they were a final account balance.

Data packs last until used and never expire, so keep an eye on the remaining data rather than an expiration date that does not apply. If you reconnect after a long break, sign in to the dashboard to confirm your status and update the subscription so the client app does not keep an old configuration. Do not assume that a data pack that never expires means the client app never needs updating. Nor should you treat an old error shown while the device was offline as a current plan status. Plan benefits and local configuration maintenance are separate things.

Check your order before renewing or upgrading

To renew, sign in to your account and go to the plans section. Confirm your current billing option and the plan you are about to choose. Do not use an old payment page saved in your browser as the starting point for a new order. If you just want to restore access, first work out whether the issue is your plan status, remaining data, or client configuration; do not pay again to fix a configuration problem. After payment, check the order list and account overview, then update the subscription in the client app. A successful payment page does not automatically sync every setting in an old client app.

For a mid-cycle upgrade, the price difference is converted into remaining days. Review the result shown in the dashboard before upgrading; do not assume it adds a fixed amount of data or extends the plan by a fixed period. If you plan to switch from a monthly plan to a data pack, or the other way around, check the confirmation page for how your current benefits will be handled. This guide does not specify how combined billing options are prioritized, so do not apply rules from another service to your order here. If anything on the confirmation page is unclear, pause and check with support through a dashboard ticket before paying.

Update the client app and move to a new device

Before updating the client app, make sure you can still sign in to the dashboard and know which account your current subscription belongs to. Get the client app from the dashboard and follow the installation steps for your platform. Do not overwrite a file from an unfamiliar source just because its name looks familiar. After updating, check that the subscription is still there, the right configuration is selected, and system network permissions remain enabled. If you need to import it again, get the current subscription from the dashboard. Do not upload the full configuration file to a public conversion tool. If the old configuration is still available, test the new setup before removing it.

To switch devices, sign in to the dashboard on the new device, get the client app, import the subscription, and complete a real task as described in the connection verification section. Before handing the old device to someone else, sign out and remove the subscription and other private data; deleting a desktop shortcut does not clear app data. If you think the subscription on the old device has been exposed, check whether the dashboard offers a reset option and update the subscription on any devices still in use. Do not assume changing your password automatically revokes old subscriptions or sessions; handle each according to the available controls.

Keep useful records without collecting too much

Maintenance notes can include your plan type, client platform, the name of a currently working route, and what you were doing when an issue last occurred. Do not save the full subscription details. The goal is to make it easier to restore your setup, not to accumulate sensitive information. If you use a work device, follow your organization's requirements for configuration backups and app installations. For details on how personal information is handled, see the Privacy Policy. To check refund or account rules, see the Terms of Service.

Advanced route selection and layered troubleshooting

Advanced use is not about turning on every option; it is about matching the configuration to the task. Once the basics work, you can explore split tunneling, per-app proxy settings, DNS, and exit locations. For each feature you add, understand which part of the path it changes, which apps it affects, and how to undo it. If you cannot explain what a setting does, keep the default for now so you have a clear baseline to test. For work, it is especially helpful to keep a copy of a working configuration and record its original settings before making changes.

Choose a region first, then compare routes

Choose a region based on what you need to do. For region-specific content, the exit location needs to match. For everyday work, compare connection performance among locations where the target service is available. Then compare IEPL, relay, and direct routes within the same region; route labels are not an absolute ranking. Changing both region and route type at once makes results harder to explain. See the global locations page for more on route types. For warning signs to look for when choosing a service, see the VPN buying checklist.

Understand system proxies and split tunneling

A system proxy usually affects apps that follow the system settings, while apps with their own configuration may use a different path. If the client app offers other connection modes, check its documentation to understand which traffic they handle. Split tunneling controls which requests use a route and which take another path. Before changing rules, check the current mode and where the rules came from. Do not overwrite a working configuration with a large block of rules copied from the internet. Rules may refer to group names that do not exist in your environment, and a successful import does not mean every request will match a usable exit route.

If a website works in your browser but not in an app, first check whether they use the same proxy path. Browser extensions, in-app proxy settings, and terminal environment variables can all change the result. Do not copy commands without knowing your local listening address and port. If you need to configure a proxy for a development tool, check the parameters provided by your current client app, follow the tool's documentation, and note how to restore the previous settings. A successful terminal command only confirms that tool's path at that time; it does not prove every app on the device is connected.

Troubleshoot DNS and browser state in order

DNS translates domain names into network addresses. If a domain lookup fails, note the error and check whether regular websites and the target site are affected in the same way. Your browser may have its own secure DNS setting, and the client app may handle DNS separately. When these settings overlap, the result may not be what you expect. Do not enter DNS addresses at random based on something you found online, and do not assume every problem is a DNS issue. Check the connection and routing rules first, then review DNS settings. Change one thing at a time and test again.

Browser cache, sign-in state, and extensions can also affect what you see. If only one browser has a problem on the same route, compare it with a clean browser profile. Keep in mind that this test helps isolate cache, extensions, and session effects; it does not provide an extra privacy guarantee. If the target service says your account region is unsupported, access is too frequent, or you lack permission, follow that service's rules. A network tool cannot replace account eligibility or guarantee that all restrictions on a destination website will go away.

Submit a support ticket with useful details

If your own checks do not resolve the issue, submit a reproducible description. Include your platform, where you got the client app, local network type, the task that failed, the client app's connection status, whether your plan is active, and what you have already tried. Make clear whether all websites fail or only a specific service. If the result changes on another network or a different route in the same region, include that too. If you are traveling, see the guide to work trips and hotel networks to rule out network sign-in and restrictions in work apps.

After troubleshooting, keep changes that worked and undo experiments that did not, then test a complete task again. For routine maintenance, keep your account details clear, choose a plan that fits your needs, keep the subscription up to date, and maintain a verified client app setup. For common questions, visit the Help Center. To review the first-time setup steps, return to the Quick Start Guide. The same approach applies to new issues: identify the stage, check the facts, and then change the configuration.