A Complete VPNBeginner’s Guide: From Subscription to Connection on Day One

Check your plan and account status after ordering

Return to your YiYiVPN account panel and check that the order is complete, the plan is active, and your available traffic is shown. The payment confirmation and plan status may appear on separate pages, so don’t repeatedly import your configuration just because payment went through. If the order and plan status don’t match, keep your order details and contact support through the panel to verify the status—don’t pay twice.

Monthly subscriptions and data packages differ in how long the data lasts. Monthly subscription data resets each month on the activation date; data packages remain valid until used and never expire. There’s no need to guess how much data you’ll need on day one—choose based on your actual usage and budget. See the plans and pricing page for details.

YiYiVPN requires no email address and has no device limit. Keep your account credentials secure, and never share your panel password and subscription link together. Refund policy: You can request a full refund for any reason within 30 days of your first payment. If you upgrade mid-cycle, the price difference is converted into remaining days; it does not simply extend the original term by the same amount.

Get a client: installation and setup are separate

The client reads your configuration and handles traffic; your plan determines your service benefits. Installing a client doesn’t automatically give you a route, and completing payment doesn’t configure your device. Check the download section in the account panel for clients and instructions available for your platform. Don’t install an app based on a similar name alone.

On Windows and macOS, setup often involves system proxy permissions. On Linux, distinguish desktop proxy settings from those used by command-line programs. On iPhone, iPad, and Android, the client usually needs system authorization to create a network tunnel. Prompts vary by client, so verify the app’s source before granting permission. You don’t need to install an untrusted root certificate just to connect.

Whether an iOS client is available may also depend on your App Store region and the app’s listing status; follow the current instructions in the account panel. Also, not every “configuration profile” is a subscription: a subscription provides route configuration, while a system configuration profile may change system settings. They are not the same thing.

Import your subscription and check that routes appear

A subscription link usually points to configuration data that can be updated. It is not a regular website URL or an account panel login page. The link may contain credentials that identify your account, so treat it as sensitive information. Don’t post it in public chats, online conversion tools, or unverified testing sites.

1. Get the configuration from the account panel. Find the subscription or client configuration section, then choose the format for your client. If there’s a dedicated import button, read the instructions beside it first.
2. Add the subscription in your client. Choose the option to import from a link or add a remote configuration, then paste the full URL. Menu labels vary by client; make sure you’re adding a remote configuration, not entering the link as a server address.
3. Update and enable the configuration. After the import completes, check that the route list appears. Some clients can save multiple configurations, so you may also need to set the new one as active.
4. Check the update result. Look for errors such as parsing failures, an unsupported format, or a failed download. If the list is empty, fix the configuration issue before moving on; repeatedly toggling the connection won’t help.

If a subscription update fails, first check that you can reach the account panel on your current network. Then make sure you copied the entire link without spaces or punctuation. If the error mentions an unsupported field or protocol, check that your client version supports the exported format. Keep an older configuration if it still connects, and don’t delete all your configurations without a backup.

If the one-click import button does nothing, your browser may simply be unable to open the client; that doesn’t necessarily mean the subscription is invalid. Open the client and add the link manually instead. When asking for help, share the error text and a screenshot with sensitive details obscured—never send the full subscription URL.

Choose a route, then decide which traffic the client handles

For your first connection, try a route that’s geographically close and suits your needs, then adjust based on how your target app performs. YiYiVPN’s route preview includes Tokyo IEPL, Singapore transit, Hong Kong IEPL, Los Angeles direct, London transit, and Zurich direct. The location tells you where traffic exits; the route type describes how it gets there. Neither guarantees a particular experience.

IEPL usually describes a dedicated transport path; transit routes forward traffic through an intermediate node; and direct routes typically connect from the local network straight to an overseas entry point. Actual performance depends on your local carrier, the route, time of day, and destination service. A “dedicated” label doesn’t mean every site will be faster, and geographic distance alone doesn’t determine latency.

“Global mode” and “routing all traffic through the client” aren’t the same thing

Rule mode uses domains, addresses, or other conditions to decide whether traffic goes through a proxy or connects directly. Global mode typically sends requests that enter the client through the selected proxy. The key phrase is “enter the client”: if an app ignores the system proxy, switching to global mode may not route its traffic.

A system proxy sends requests from compatible programs to the client. TUN or a similar virtual network interface can handle a wider range of traffic, but requires permissions and may conflict with other networking software. Follow the official guide and enable the recommended option; don’t stack multiple proxy clients. Command-line tools may also need separate proxy environment settings, so a working browser connection doesn’t prove that the terminal is configured correctly.

For platform-specific instructions, see the guides. If the labels don’t match, follow the instructions for your current client rather than copying option names from another app.

Verify your connection: exit IP, DNS, and target apps

When a client shows “Connected,” it usually means only that one stage of the connection succeeded. To verify the setup, check whether requests are routed as expected and whether your target app works. Note your exit IP before connecting, then compare it with the same route enabled. Don’t draw conclusions from the location label alone.

• ✅ Before and after connecting, open My IP and compare the exit addresses. The test page itself must follow proxy rules; otherwise, a local exit may simply mean the page is set to connect directly.
• ✅ Open the site you actually plan to use and try a normal action, such as signing in, searching, or loading content. Reaching the homepage doesn’t mean every request in the app is working.
• ✅ Test your browser and standalone apps separately. If only the browser works, first check whether the app follows the system proxy or needs another way to route its traffic.
• ✅ Check the client’s connection log for matched rules and the selected exit route. During troubleshooting, focus on whether traffic used the expected route. Don’t share full logs that expose account details, domains, or browsing activity.

DNS translates domain names into addresses. If you want DNS queries for certain domains to follow your proxy rules, check the client’s DNS and routing settings. Browser Secure DNS, system resolvers, and app-level DNS may each use different paths. Seeing a particular resolver in a DNS test doesn’t, by itself, prove a leak; check whether queries bypassed the intended route.

Likewise, a changed exit IP doesn’t mean all traffic on your device is being routed through the client. In split-tunneling mode, some requests may connect directly by design. When troubleshooting, specify which app and request should use which route; that’s more useful than asking whether the setup “works.”

Common issues: troubleshoot each stage in turn

Routes appear, but none will connect

First confirm that your plan is active, data is available, and your local network is working. Then check that your system clock is accurate; some encrypted connections rely on the correct time, and a clock that’s off can cause certificate validation errors. Next, test a route in a different region or of a different type, and keep the client’s error message. Don’t change DNS, routing, and protocol settings all at once, or you may lose useful clues.

Connected, but some apps still can’t access the internet

First distinguish a routing issue from a restriction imposed by the destination service. If the browser works but a standalone app doesn’t, check whether it supports the system proxy. If only one site has trouble, check the routing rules, cache, account region, and any message from the platform. Streaming and other region-specific services should be tested on the platform itself; a successful connection doesn’t guarantee that the service accepts that exit IP.

Local sites stop working after you exit the client

Check whether the system proxy still points to the local client you’ve closed, then use the client’s option to disable or restore the settings. With a virtual network interface, disconnect using the client’s recommended procedure first, then check whether other networking software has taken over routing. Don’t start by deleting system network components.

Before you call it a day, keep a working configuration you can reproduce

Once connected, note the configuration, route, and proxy mode you’re using, and check that your network returns to normal when you disconnect. Enable startup or adjust split tunneling later if needed; launching the client at startup doesn’t necessarily connect automatically, so check these settings separately. For multiple devices, install a compatible client and test each one independently—a successful setup on one device doesn’t configure the others.