Service Coverage and Cross-Border Connections
Understand accounts, plans, and clients
YiYiVPN is a subscription service for cross-border connectivity, with 120+ countries / 240+ routes and support for Windows / macOS / iOS / Android / Linux. Your account stores orders and plan entitlements; your plan determines your data allowance and billing; and your client routes requests from your device through your chosen route. These parts work together but aren’t interchangeable: installing a client doesn’t give you an active subscription, and signing in to your account doesn’t mean your target app is using the proxy.
Think of everyday use as a sequence: your local network connects to the internet, the client retrieves route settings from your subscription, the right proxy mode handles app requests, and the exit route reaches the destination website. A problem at any point can make a page appear unavailable. When troubleshooting, identify which link in the chain failed instead of repeatedly changing plans, reinstalling apps, or adjusting several unrelated settings at once.
The service provides a network route, not account entitlements on other platforms. Video memberships, AI tool accounts, regional policies, and content rights are determined by each platform. A site loading doesn’t mean every feature will work, and an exit route in a particular region doesn’t change your account’s region. For subscription, identity, or content-access notices, check the platform’s own guidance first rather than assuming there’s a route problem.
Route types and proxy modes are different things
IEPL dedicated lines, transit, and direct routes describe how network paths are arranged, not routing modes in the client. A dedicated line uses a dedicated transmission arrangement along the route; transit routes requests through an intermediate access node before they reach the exit; direct routes connect from the local network straight to the destination exit. A label alone can’t guarantee how a route will perform—results also depend on your local carrier, access network, destination service, and time of day. See the server page and your current subscription for available routes.
Rule, global, and direct modes answer a different question: which requests go through the proxy. Rule mode routes requests based on domains, addresses, or app conditions. Global mode typically proxies all requests the client can handle. Direct mode bypasses the proxy exit. “Global” doesn’t automatically mean every device request is covered: whether apps follow the system proxy and whether the client uses a virtual network interface also affect coverage.
System proxy mode is usually a good first step for checking browser access. Virtual network interface mode can handle a wider range of requests, but may require system permissions and affect local routing. You don’t need to enable every option at the outset. Start with the client’s defaults or the dashboard guide, confirm basic access, then expand one setting at a time. Company networks, campus networks, and managed devices may have additional restrictions; follow the applicable network and device policies.
Privacy commitments and usage boundaries
YiYiVPN describes its privacy commitment as “anonymous, no logs.” This service policy doesn’t mean your browser, operating system, or destination websites keep no records. A site can still associate activity with your account after you sign in; browser history, downloaded files, and app data on your device also need your attention. Consider privacy separately at the service, device, and platform levels—a single proxy toggle can’t replace all security settings.
This service supports unlimited devices, but each one still needs an appropriate client, an imported configuration, and a connection check. Avoid sharing your subscription publicly, as it’s tied to your account entitlements. After this chapter, you should be able to distinguish between “the device is online,” “the subscription is active,” “the route connects,” and “the target app works.” The rest of this guide follows that sequence, with a clear check at each step.
Monthly Plans vs. Data Packs
Choose a billing option that fits how you use the service
Monthly plans suit regular use when you want a recurring data allowance. YiYiVPN offers ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on your activation date—not at the start of the calendar month. To check your current allowance, review your plan status, data usage, and reset date in the dashboard rather than relying on the calendar alone.
Data packs suit occasional use or needs that vary over time. Available options are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They’re valid until used and never expire. The key difference from a monthly plan is how data is used, not how you set up the client. “Never expires” doesn’t mean unlimited data: your balance decreases as you use it. Check the account dashboard for your balance and usage history.
Before choosing, consider how you use the service: mostly web browsing and text-based tools, or long video sessions? Do you sync files to the cloud? Do your devices run background updates? Video, file transfers, and automatic backups can use more data over time than text browsing, though actual usage depends on content quality and app settings. If you don’t have usage history yet, don’t rely on unverified daily estimates. Start with an option that fits your budget and adjust based on actual usage.
| Billing option | Price and data | How data works |
|---|---|---|
| Monthly plan | ¥9.9/month, 60GB included | Resets monthly on your activation date |
| Monthly plan | ¥18/month, 250GB included | Resets monthly on your activation date |
| Monthly plan | ¥28/month, 500GB included | Resets monthly on your activation date |
| Data pack | ¥158/300GB | Valid until used; never expires |
| Data pack | ¥358/1000GB | Valid until used; never expires |
| Data pack | ¥658/3000GB | Valid until used; never expires |
Consider data, devices, and upgrade rules together
Unlimited devices means there’s no device-count limit; it doesn’t give each device a separate plan allowance. When estimating your needs, consider activity across your computers, tablets, and other devices, and check how data is counted in the account dashboard. A device with no visible activity may still be syncing in the background. If usage changes noticeably, check system updates, cloud storage, autoplay, and downloads—not just how many pages you’ve opened in a browser.
If you upgrade a monthly plan mid-cycle, the price difference is prorated into remaining days. Before upgrading, read the change details and final total on the order page. Don’t assume you’ll receive a full month’s worth of extra data or time. This guide can’t calculate your upgraded entitlements; if the result differs from what you expect, keep the order details and check with support before submitting another change. Multiple changes can make your plan status and payment history harder to verify.
Don’t assume separate orders can be combined, or that switching billing options will use old entitlements in a particular order. No combination rules are specified here, so check the options currently available in your dashboard. If you need to plan for different devices or uses, note your requirements and review the supported options. The availability of both monthly plans and data packs doesn’t mean every combination is supported.
What to verify before paying
YiYiVPN accepts Alipay / WeChat Pay / USDT and offers a 30-day no-questions-asked refund. Before placing an order, check the plan name, price, billing option, and payment method. See the refund policy for full terms. A refund policy isn’t a guarantee that other platforms will work, and it’s no substitute for checking your plan details. If you’re paying with an organization’s or another person’s account, confirm you’re authorized and keep the necessary payment records.
Review all pricing and terms on the plans and pricing page. The goal isn’t to choose the largest allowance by default; it’s to know which billing option you’re using, how data resets or gets used, what you’ll pay, and what to check before upgrading. Once you’ve confirmed those details, move on to your account and order. If questions about data or expiry come up later, you’ll be able to tell whether they relate to billing or connection settings.
Creating an Account and Checking Your Order
Manage your account in the user dashboard
YiYiVPN doesn’t require an email address. Create an account with a username and password in the user dashboard, accessible from the site navigation. Your username identifies the account, and your password protects access; keep both safe. Don’t use temporary details you’re likely to forget as long-term login credentials. Use a password that’s unique to this site, ideally stored in a trusted password manager rather than in a public document or group chat.
Before entering your details, check the address bar to make sure you’re on a yiyivpn.com page or a legitimate payment flow. The marketing site and user dashboard have different roles: the former covers the service and guides, while the latter handles sign-in, plans, orders, subscriptions, and support tickets. Their paths may also differ in preview or subdirectory environments, so use links within the site rather than treating any search result with a similar name as an account portal. Never share your full login credentials.
After submitting your details, make sure you can access your account overview before choosing a plan. If your browser asks to save the password, verify that it’s for the current site. If sign-in fails, check the username’s capitalization, input method, accidental spaces, and whether your password manager filled in another account’s details. Don’t create several similar usernames before confirming which account is yours; otherwise, you could end up paying in one account while using another account’s subscription in the client.
From plan selection to payment confirmation
Open the plans section of the dashboard and compare the options with the billing choice you made in the previous chapter. Review the order summary, then choose a suitable payment method: Alipay, WeChat Pay, or USDT. The payment page and dashboard order record should match. If the page is interrupted, first check the order status in your account rather than submitting another payment. A page that hasn’t refreshed doesn’t necessarily mean the payment failed.
Once you’ve paid, return to the dashboard to check that the order is confirmed and your account entitlements have updated. A successful payment notification, a browser redirect, and an active plan in the dashboard are separate signals. If they don’t match, keep your payment records and refresh the order page or reopen your account overview. Don’t rely on an animation to confirm payment, and don’t keep clicking the payment link while the status is unclear. In particular, don’t buy the same plan again to work around a display delay.
For USDT payments, follow the asset, network, address, and amount shown on the current payment page exactly. Don’t use details from an old order screenshot or infer payment details from this guide; no receiving address is provided here. If the payment instructions don’t match your planned transfer, stop and verify them first. For help with a submitted payment, open an account support ticket with the order details and relevant proof. Include what’s needed to verify the payment, but redact unrelated account balances and transaction history.
Order issues and protecting your credentials
If your payment is complete but your entitlements haven’t updated, explain the plan you chose, order status, payment method, and what happened in your support ticket. Attach an order record that can be read. Separately describing “the payment was charged” and “the dashboard still says pending” is more useful than simply writing “it doesn’t work.” Never attach your password, full subscription link, or sensitive payment details. Open a ticket through the user dashboard; there’s no need to look for an unverified contact outside the site.
Once your account is working, get familiar with the overview, orders, downloads, and support ticket sections before retrieving your subscription in the next chapter. If you’re using a shared computer, sign out afterward and check whether configuration details remain in the downloads folder or clipboard. This step is complete when you can sign in, verify the order, and confirm your plan status. That way, if the client won’t connect later, you won’t need to start by checking whether you used the right account.
Getting Your Subscription and Updating Configuration
A subscription link isn’t a regular web address
Once your plan is active, find your current subscription in the overview or subscription section of the user dashboard. The link typically contains information used to identify your entitlements, and the client uses it to retrieve routes and related settings. Pasting it into a browser may show text, start a download, or display a message; none of these alone confirms a successful setup. Check whether the client can read it in a supported format and display routes associated with your account.
Use the dashboard’s copy button and make sure you haven’t copied its label, surrounding instructions, or extra line breaks. If you need to paste the link manually, put it in the client’s subscription URL field—not a route name, proxy port, or web search box. You can give the configuration a helpful local name, but don’t edit the link itself. In particular, don’t remove long query parameters because they look unimportant.
Your subscription link is sensitive configuration data. Don’t post it publicly in forums, screenshots, or shared documents. If you need to show where it goes, use a clearly illustrative example address; it won’t connect to YiYiVPN. Before sharing a screenshot for troubleshooting, hide the full address and any identifying credentials, leaving only the client name, error message, and relevant settings visible. If the link has been exposed, first check whether the dashboard offers a reset option.
https://example.com/sub?token=YOUR_TOKENChoose the import option that matches the client
A client may offer options such as “Import file,” “Add subscription,” and “Add route.” They don’t all accept the same content. Use the subscription setup for a subscription link and the file import flow for a local configuration file. If the dashboard has an import button for your client, first make sure the client is installed on your device, then try opening it from the dashboard. When your browser asks to open an external app, verify its name before allowing it to receive the configuration.
If the client doesn’t open automatically, that doesn’t mean the subscription is invalid. The browser may have blocked the external protocol, or the system may not have linked it to an installed client. Go back to the dashboard, copy the subscription link, and add it manually in the client; this usually makes any error easier to identify. If the format isn’t supported, check for another import option in the dashboard. Don’t send the link to an unverified online converter, which could expose your subscription.
After importing, distinguish between “configuration saved” and “configuration in use.” Some clients can save multiple configurations, but only the selected one controls routing. Check the active configuration, update result, and route list to make sure you aren’t using an old service or test setup. If several names look alike, add a clear local note, but don’t edit fields managed by the subscription. The next update may overwrite manual changes and cause inconsistent results.
When to update, troubleshoot an expired link, or reset
Updating a subscription fetches the latest server-side configuration. It doesn’t restore used data or extend your plan. If the route list is empty, first check your account entitlements, then determine whether the update failed because of a network, address, or format issue. If your local network works but the update still fails, check whether your client needs the current proxy connection to update. Don’t delete your only configuration before backing it up; you may need it to compare errors.
After a subscription reset, the old link may no longer work; follow the dashboard’s instructions. Before resetting, consider every device using the subscription. Then update each client with the new configuration and confirm it’s selected. If importing failed on just one device, there’s no need to reset the whole account subscription first. A safer order is to check the link, format, and local network before making account-level changes. By the end of this chapter, the client should show routes you can select—not just a link you’ve copied.
Set Up Clients on Each Platform
Windows and macOS: check the configuration before enabling the proxy
Download clients from the user dashboard. Once signed in, you can get clients for Windows / macOS / Android / Linux without purchasing a plan, but connecting requires active entitlements and a subscription. See below for iOS requirements. Before installing, check your device’s platform and system prompts; don’t use an installer intended for another platform. Follow the dashboard’s current instructions whenever they differ from the general interface labels in this guide.
After installing and opening the Windows client, go to the configuration or subscription section, add the link from the previous chapter, update it, and set that configuration as active. Select a route, enable the client’s system proxy, and test access in a browser. If you need virtual network interface mode, grant permissions as required by the app. If the system proxy is on but an app still connects directly, first check whether the app follows system proxy settings rather than assuming the route is at fault.
On macOS, follow the same order: add the subscription, update the configuration, select it, choose a route, then enable the proxy. The system may ask permission to run network-related components; check that the requesting app is the client you just installed. If you’ve used other proxy tools, quit them before enabling this one. Closing a window may not quit an app, so check the menu bar to avoid multiple background proxies changing system settings at once.
iOS and Android: check system permissions and background behavior
On iOS, use the App Store link in the dashboard to get the client. This link is available only to users with a purchased, unexpired plan. If the dashboard says you need to resolve a plan issue first, check its status in the account overview rather than looking for an unofficial alternative installation method. App Store availability depends on the current store region. Your store account, device account, and YiYiVPN account are separate identities, so check each one independently.
In the iOS client, add and update your subscription, select a route, allow the VPN configuration when prompted, then connect. Don’t use a configuration profile from an unknown source instead of importing your subscription. A VPN indicator means the tunnel configuration is enabled; you still need to check whether the target app uses the selected exit. If you use automations or shortcuts, first confirm that a manual connection works, then add automatic triggers so they don’t obscure a permission issue.
After importing a subscription on Android, you’ll usually need to approve the system’s VPN connection request the first time you connect. Check that it comes from the client you’re using. If other apps on the device can also manage VPN connections, clarify which ones you need and avoid running them at the same time. If the connection drops when the app goes into the background, check background activity and battery settings, granting only the permissions the client needs to keep running. For more iOS details, see iPhone Clients and Configuration Profiles.
Linux: distinguish desktop proxy settings from service processes
On Linux, install the client according to your distribution and the dashboard instructions, then import your subscription and select the configuration. Desktop system proxy settings may not affect terminal programs or background services, and terminal environment variables may not affect graphical apps. Check your browser, terminal, and actual work app separately. Before enabling a mode that needs elevated privileges, understand what it does; avoid running the entire client with unnecessary permissions over the long term.
On every platform, complete a full connection check after the first import before enabling startup, auto-connect, or per-app routing. Interface labels vary, but the checks are the same: configuration imported, correct configuration selected, route chosen, proxy mode enabled, and target app working. If only one app has a problem, leave working apps alone and check that app’s routing rather than reconfiguring every device. For desktop setups, see Windows Global Proxy and Split Tunneling.
| Platform | After importing | Check these first if something goes wrong |
|---|---|---|
| Windows | Select the configuration and enable the required proxy mode | System proxy settings and app-specific settings |
| macOS | Check network-related permissions | Other proxy tools in the menu bar |
| iOS | Check permission for the system VPN configuration | Plan status, store region, and configuration selection |
| Android | Confirm the VPN connection request | Background activity settings and other apps managing connections |
| Linux | Test desktop and terminal apps separately | Environment variables, app settings, and permissions |
Verify Your Connection and Find the Problem
Start with a baseline you can compare against
Before testing, turn off the proxy and confirm your local network can access common websites. Note whether you’re on a home, public, or other network. Then enable the client and compare using the same browser and destination page. Don’t change networks, clear the cache, and adjust DNS at the same time as switching routes. Even if access returns, you won’t know which change helped—and you’ll have no reliable basis for troubleshooting the next time.
After connecting, visit the IP lookup page on this site to see the exit information for your browser’s current requests. If the lookup fails, follow the page’s instructions; a temporary tool issue doesn’t automatically mean the proxy is down. A changed exit shows that this request took a different path, but doesn’t prove every app is covered. The exit region is a troubleshooting clue, not a guarantee of streaming rights or AI tool access.
Next, open the app you actually want to use and perform a task that tests what you need, instead of stopping at its home page. For a text-based tool, check whether a request completes; for a video service, test playback; for a file app, check a transfer. Static content on a home page may be cached, and the sign-in page may use different domains from the main features. If the home page loads but a key feature fails, note the exact failing step so you don’t misdiagnose the whole network.
Separate DNS, routing, and app errors
DNS translates domain names into addresses. If you see an error such as “server not found,” check whether name resolution succeeds—but a successful lookup doesn’t prove the next connection can be reached. Client DNS, system DNS, and a browser’s secure DNS may all affect requests. System settings alone don’t show which resolution path is actually used. Note the current settings, then coordinate them according to the client’s instructions instead of enabling overlapping DNS options at once.
A command-line lookup can help you inspect your system’s DNS result. The command below looks up example.com; its output only confirms whether that lookup received a response. It doesn’t prove a browser or another app uses the same path. Some systems may need an additional tool; there’s no need to change system settings just to install one for this check. Don’t copy a DNS address into every device’s settings as a fixed value, as the destination platform’s DNS results can change.
nslookup example.comIf just one app can’t connect, check whether it has its own proxy settings, follows the system proxy, or uses a different network component. If every destination fails, revisit subscription status, route selection, and proxy mode. If the same configuration works on another network, local network restrictions or routing differences are more likely. Client connectivity tests are useful clues, but they can’t replace testing the actual app; don’t judge the overall experience by a latency test alone.
Follow the results instead of toggling settings at random
If a webpage shows a certificate warning, don’t bypass the warning to prove that a route works. Check the device’s time, the destination domain, and any additional proxy components on the network. If the destination platform shows an account, region, or permission notice, the request may have reached the platform; investigate its rules and your account status. For timeouts, continue checking the exit, route, and network path. Keep the exact error message—it’s often more useful than “the site won’t load.”
After testing, note the working configuration, route, proxy mode, and target app so you have a baseline for future comparisons. For support, include your device platform, current network, the specific task that failed, and whether changing routes made a difference. Don’t include your full subscription link. For a more detailed per-app check, see How to Verify Your Exit IP, DNS, and Apps. The test is complete when the actual task works—not just when the client shows that its connection toggle is on.
Routine Maintenance and Renewal Checks
Keep a working configuration and check your account status regularly
Once your connection is stable, there’s no need to rebuild the subscription or change advanced settings every day. Keep the client configuration in sync with your account entitlements, and note any recent system, network, or app changes. You can record the configuration name, commonly used routes, and proxy mode on your device, but don’t put the full subscription link in an ordinary note. Make configuration updates, system upgrades, and network changes one at a time so you can return to a known working state if something goes wrong.
When checking your plan, review data, active status, and billing option together. Monthly plan data resets on your activation date; data packs last until used and never expire. Don’t use the same rule to interpret both types of plan, and don’t treat the client’s local usage counter as final billing data. Differences in what’s counted, background requests, and refresh timing can affect the display. Use the dashboard record to verify your entitlements, and send specific details to support if anything looks wrong.
If data usage rises unexpectedly, check device downloads, syncs, and updates first. Video quality changes, cloud storage resyncs, and system updates can transfer data continuously in the background. Pause likely tasks and watch for a change instead of turning off every proxy feature. If certain traffic should connect directly, confirm what it needs to access and configure a rule for it. Lowering the client’s displayed counter doesn’t prove that account usage has stopped.
Handle renewals, upgrades, and client updates separately
Before renewing, check your current plan and order summary in the dashboard. Don’t pay through an old screenshot or a saved payment page. Review the new order’s price, entitlements, and activation terms before confirming. This guide doesn’t assume that your account supports automatic renewal or billing; check the dashboard’s current settings to see whether you need to renew manually. After paying, follow the account steps to verify the order and entitlements rather than closing the page and discovering a problem only when your connection stops working.
For a mid-cycle upgrade, the price difference is prorated into remaining days; check the dashboard for the exact calculation. Upgrading, renewing, and reimporting a subscription are different actions: an upgrade changes plan entitlements, a renewal arranges continued use, and a subscription update syncs configuration. Don’t place repeated orders to refresh routes or reimport a subscription to restore data. If you want to change billing options, read the change details and ask support about anything unclear before proceeding.
Update the client through the dashboard or the client’s trusted update process. Don’t install files from unverified chat messages. Before updating, make sure your subscription link is safely stored and check whether the current configuration includes manual rules. After the update, confirm the configuration is still selected, system proxy settings remain in place, and any required permissions are granted again. Verify basic access before restoring startup or auto-connect, so automation doesn’t keep an incorrect setup running.
Changing devices, exposed subscriptions, and refund requests
When switching devices, install the client and import your subscription on the new device. Test it before clearing the old one. Before handing off or selling a device, sign out, remove the client configuration, and delete leftover files; removing a desktop shortcut doesn’t remove configuration data. If you think your subscription link has been exposed, check the dashboard’s reset instructions, then update every device still in use. Don’t post the old link publicly to prove it was exposed; check its status in the dashboard.
To request a refund, follow the refund policy and the dashboard’s support ticket process. The stated offer is a 30-day no-questions-asked refund. Include your order details and a description of the issue; there’s no need to disclose your password. Routine maintenance is on track when you can find your current plan, identify your active configuration, recall your usual connection method, and distinguish entitlement changes from technical settings. Clear records help more than a pile of unverified configuration screenshots.
Split Tunneling and Advanced Setup
Decide what to route before adjusting rules
Advanced configuration should come only after you’ve verified a basic connection. Start by stating your goal: should only certain sites use the proxy, or should it also handle apps that ignore system proxy settings? Do you need to retain access to local devices, or route terminal tools through a specific exit? Different goals call for different settings. Don’t enable every advanced option just because it’s there—especially virtual network interface, global mode, and an app’s own proxy all at once—then guess how requests are being routed.
Rules are usually checked in a defined order, and a broad rule can prevent later, more specific conditions from taking effect. Before making changes, check where the current rules come from and how overrides work. Prefer the client’s local override feature over editing a downloaded subscription file, which may be overwritten during the next update. Change only rules relevant to your goal, keep a copy of the working setup, and test with the actual app you want to use.
Local printers, file sharing on your local network, and admin pages often need a direct route. If they stop working after you enable broader routing, check how the client handles local addresses and networks rather than disabling system protections. Company intranets and remote-work tools may have their own routing requirements; follow your administrator’s instructions. Don’t copy a rule that works on your home network to a managed network without testing it, as it could disrupt work services or violate usage policies.
Test terminal tools and target apps separately
Terminal programs may use proxy environment variables or only their own settings; graphical apps may follow the system proxy instead. Before configuring a program, check its documentation to see whether it supports an HTTP or SOCKS proxy and where it resolves domain names. These protocol names aren’t interchangeable. If you don’t know the client’s local port, check its settings rather than copying a port from another guide and trying it repeatedly.
A terminal may inherit old environment variables and keep trying to connect to a local proxy that’s no longer running, even after the client is closed. Check whether relevant variables are set, but inspect only their names—don’t copy full values that may contain authentication details into logs or public support tickets. The command below works in shells that support this syntax; it lists relevant variable names without setting a proxy or changing your environment. If it returns nothing, check the program’s own settings.
printenv | cut -d= -f1 | grep -iE '^(http_proxy|https_proxy|all_proxy|no_proxy)$'With AI tools such as ChatGPT, opening the site, signing in, sending a request, and receiving a response may each involve a different step. If you can sign in but requests fail, check the platform’s message, account permissions, and whether the relevant requests match your routing rules. Keeping the exit route consistent can help you compare results, but it can’t guarantee that platform security checks won’t apply. Don’t keep switching regions instead of troubleshooting, or mistake model access, usage limits, or account status for a proxy issue.
Choose routes for each use case and keep useful notes
For streaming, check page access, account region, and actual playback separately. A route reaching a site doesn’t mean every content library will play; buffering can also stem from local Wi-Fi, device decoding, or the platform itself. Compare routes on the same device with the same content, then check whether results change by time of day. See our Streaming guide and guide to route stability during peak sports events. A route label alone doesn’t guarantee viewing performance.
Keep a concise note for each use case: which app you use, how it’s routed, what type of route you choose, how you verify it works, and which setting to revert first if something goes wrong. Don’t include credentials or fill the note with unnecessary parameters. To repeat the full setup, return to the quick-start guide; to check a particular step, use this page’s contents. Advanced use means understanding each setting and returning to a known working state—not simply enabling more options.