L7VPN
Complete User Guide

Service overview and app routes

Understand the service, subscription, and client

L7VPN is a subscription service for cross-border network acceleration. Using it involves three distinct parts: your account stores your plan and orders, your subscription provides route settings for client apps, and the client establishes a connection on your device. Being able to sign in to the website does not mean your device is using an international route. Installing a client does not mean you have imported the subscription for your current account. Understanding the difference helps you work out whether to check the dashboard, refresh your configuration, or review the device's connection settings—instead of repeatedly creating accounts.

A route is the path your data takes; the exit region is the network location seen by the destination website. App routing determines whether a request uses a specific route and which exit it uses. Browsers, desktop apps, and system processes may use different network settings, so one app may work while another on the same device does not. Check which traffic the proxy handles and whether the rules match. A page loading successfully does not prove that every app is using the same exit.

Coverage does not guarantee app access

L7VPN offers 120+ countries / 180+ routes and supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. Coverage indicates the range of routes available; it does not mean every region will work with every app. A platform may check account region, payment details, sign-in history, and exit location when determining access. A network connection can change the data route, but it cannot grant account permissions on another platform or guarantee that the same library or feature will always be available to an account.

IEPL dedicated lines, relay routes, and direct routes describe connection types; they are not a fixed ranking of performance. Your connection also depends on your local ISP, network conditions, the destination service's location, and the selected exit. For your first setup, choose a route in the dashboard that suits the target app and verify it before comparing other types. Avoid changing the exit, proxy mode, and app account region all at once. Even if access returns, it will be difficult to tell which change made the difference.

Encryption and responsible use

Quantum encryption is a service trust marker for L7VPN. Still, distinguish between connection security, website account security, and device security: route encryption does not identify fake sign-in pages or manage your browser extensions, system permissions, or local files. This guide makes no claims about encryption algorithms or audit results that have not been provided. When handling passwords, payments, or work files, check the website address, keep your system up to date, and be cautious about granting apps access to your clipboard or network traffic.

The service is accessed through the user dashboard. Get subscriptions, client apps, and support tickets from the dashboard—not from attachments in unsolicited messages or so-called shared configurations. For coverage and route types, see the server locations page. To compare billing, visit plan pricing. This guide follows the journey from account to connection. Check that the service meets your needs before choosing a plan, so you don't mistake a destination platform's eligibility rules for a plan capacity issue.

Choose a plan and understand billing

Compare how you use the service before comparing data allowances

Monthly plans suit regular use. Data packs suit variable usage when you want spending to track actual consumption. The main difference is how data is managed, not the number of devices: this service supports unlimited simultaneous devices. When choosing a plan, consider how you use your computer, tablet, and other devices—especially for video streaming, file syncing, and software updates. These tasks can use data in the background, so browsing frequency alone is not a reliable way to estimate usage. Client-side data totals may also differ from the dashboard's final billing figures.

Monthly plan data resets each month on the activation date; it does not reset at the start of each calendar month. Check the billing period and status shown in your dashboard rather than relying on your local calendar. A data pack remains valid until used and never expires; that describes its validity, not unlimited data. If you already have a plan, check the checkout page to see how a new order will work and what options are available. Don't assume allowances stack or that a particular pack will be used first automatically.

When upgrading, check the remaining days instead of estimating the credited data

For mid-cycle upgrades, the price difference is converted into remaining days. This is not the same as paying a fixed amount to top up, nor does it mean you receive a full new billing period. Before proceeding, check your current plan, the target plan, the amount due, and the details of the updated benefits. If the page doesn't match your understanding, stop and confirm through a support ticket before submitting. Don't place multiple orders and then try to infer the billing outcome from the client's data display. Check your account and order status in the dashboard; the client manages network settings.

When choosing a data allowance, start with how you use the service. Streaming high-resolution video and downloading large files make total usage over the billing period more important. Text-based work, reading code, and occasional AI tool use also depend on session continuity and a consistent exit. A larger allowance won't necessarily fix local Wi-Fi interference or change a platform's regional rules. If you experience buffering or disconnects, verify the connection first to see whether you really need a different allowance. Don't use a billing change as a substitute for troubleshooting.

Payments, refunds, and checks before checkout

Payment methods include Alipay / WeChat Pay / USDT, and the refund policy offers a 60-day no-questions-asked refund. Read the Terms of Service for the full eligibility details. Contact support about order issues through a dashboard ticket. Experience-related wording on buttons does not imply extra data, automatic bonuses, or other unlisted plan benefits; rely on the stated price and data allowance when confirming an order. If you still have questions about a plan, review the comparison on the plan pricing page before checkout.

Before paying, make sure you're signed in to the account you intend to keep using. Otherwise, you could place an order under a different username in another browser and leave it on an account you rarely use. Keep a record of the plan name and order status; there's no need to share payment details publicly. For duplicate orders or a status that hasn't updated, check your order list before deciding what to do next. By the end of this section, you should be able to describe the plan's data allowance, reset rules, and payment route—not just its price.

Create an account and check your order

Save your account credentials before choosing a plan

L7VPN doesn't require an email address. Create an account with a username and password. Open the user dashboard from the free trial page and enter the details requested. Choose a username you can recognize later, and don't reuse a password from another site. Before submitting, check your keyboard layout, leading or trailing spaces, and any autofill from your password manager. This helps prevent saving temporary test text as your real credentials. Once your account is created, make sure you can sign in to the dashboard before moving on to a plan.

Since no email address is required, don't assume your inbox will be the default way to recover your account. Store your credentials securely and make sure you can access them when you're away from your current device. This guide does not promise account recovery options that haven't been listed. If you lose your credentials, check the help options actually available in the dashboard. Don't share your password with strangers or send your subscription link as if it were a login password. Both need to be protected, but they serve different purposes.

Confirm your sign-in and plan details

After signing in through the login page, check that the account overview looks right. If you've used the service before and the overview is empty, don't pay again right away. First verify your username and check whether your browser autofilled a different account. Sign-in status is separate across browsers and devices. Confirm which account you're using before deciding that a plan hasn't taken effect; otherwise, you could mistake an account switch for a failed payment and create a duplicate order.

Open the plans section in the dashboard and check the product name, price, data allowance, and billing terms. Monthly plans and data packs work differently, even if their allowances look similar. Before placing an order, check whether the confirmation page is for a renewal, upgrade, or another change. If your account already has benefits, pay particular attention to how they carry over. Don't guess what an unspecified change will do. Keeping the current state and asking support is less likely to cause a billing dispute.

Return to the dashboard after payment

Choose one of the payment methods shown for the order: Alipay / WeChat Pay / USDT. Follow the instructions for that order. For USDT, check the network, recipient details, and amount shown on the current payment page. Don't reuse information from an old order screenshot or chat message. Payment details may be tied to a specific order; this guide does not provide fixed recipient details. Before leaving the payment page, save the order record for reference, but don't publicly share a full screenshot containing account or payment details.

After your payment tool confirms completion, return to the dashboard and check the order status and plan overview. Payment completion, order confirmation, and getting an updated client configuration are connected but separate steps. If the expected benefits aren't shown, refresh the order list and make sure you're in the right account. Don't place the same order again. If the order is successful but the client still has old settings, update the subscription next. If the order hasn't been confirmed, resolve the billing status first rather than repeatedly changing proxy settings.

If something goes wrong, gather details that can be checked

If you can't sign in, check your username, password autofill, capitalization, and keyboard layout. Avoid repeatedly trying passwords you can't remember. If the page won't load, note the error and reopen the dashboard on a working network. Avoid running multiple network interception tools at the same time. If you can access your account, describe the problem through the support ticket page. If you can't sign in, follow the help options shown on the login page. Don't guess at unpublished support addresses.

For an order-related ticket, describe the step you were on, the plan name, the order status shown in the dashboard, and the result from your payment tool. Share any necessary proof only through the dashboard's private support channel. Full passwords, subscription URLs, and browser session details are not normally needed for troubleshooting. “Payment complete, but the dashboard still shows the order as pending” is more useful than “nothing works.” Once your account benefits and order status are confirmed, move on to getting your subscription to keep troubleshooting in order.

Get and protect your subscription settings

A subscription link is for setting up a client, not a webpage bookmark

A subscription link lets a client fetch routes and related settings. It's different from the website login page and usually isn't meant to be read in a regular browser. Once imported, the settings are stored locally on your device. So if route details change in the dashboard, your device may still be using a cached version. Understand the relationship—link fetches settings, the client saves them locally, and the connection uses the selected settings—to work out whether to refresh the subscription, switch configurations, or check your account status in the dashboard.

Sign in to the user dashboard and check your plan status, then find the subscription section for your account's current configuration link. The page may offer options to copy a link or send it to a client for import; use the labels shown in the interface. For your first setup, keep the dashboard open while importing into the client, then return to the dashboard to verify. Don't copy a subscription from someone else's screenshot or paste a marketing page URL into the subscription field. The marketing page describes the service; the subscription link provides data for the client.

Before copying, check the destination and client type

If the dashboard offers client-specific options, choose the one that matches the client you've installed. Different clients may accept different configuration formats. Being able to copy a link doesn't mean every app can parse it. If importing opens another app, confirm it's the one you expect before proceeding. If nothing happens, make sure the client is installed and opens on its own, then use its built-in subscription import option. There's no need to create another account.

When pasting, make sure you've copied the complete link by itself—without explanatory text, line breaks, or punctuation. The path and query parameters may be required, so don't remove them to “tidy up” the link. After import, give the local configuration a recognizable name, such as “L7VPN daily setup,” and make sure it's selected. Seeing a name in the configuration list only confirms it was saved. Check that routes have loaded before connecting; an empty configuration is not a usable subscription.

If an update fails, tell fetching apart from parsing

An update can fail because a request never reaches its destination, a server returns an error, or the client can't parse the configuration. Start by checking whether the error points to the network, account status, or format. If the dashboard opens but the client reports an unsupported format, check the import type first. If neither is accessible, check your local network. Don't send your subscription to a stranger to import, and don't assume a screenshot is safe after hiding only part of a real link—the rest may still expose the configuration.

Subscription updates may also depend on the client's current network settings. Some clients let you choose a route for update requests; others use the system's current network. If updates fail while connected but work after disconnecting, the client may be trying to fetch its settings over a route that isn't working. Note your existing settings first, then adjust the update route using the client's own options. Don't delete the configuration while also changing the system proxy, or you may lose a working state you could restore.

If a link is exposed or you're moving to another device

Treat your subscription link like sensitive credentials. Don't put it in public notes, code repositories, shared screenshots, or chats visible to others. If you think it has been exposed, check whether the dashboard offers a way to reset it. If so, follow the instructions and update the link on your devices. If there is no such option, ask through a support ticket. Don't assume that changing your account password automatically revokes the subscription link; check how the dashboard actually handles this instead of guessing.

When moving to a new device, sign in to the dashboard and get the configuration again instead of sharing client files through a public cloud drive. Check local configurations, clipboard history, and synced notes on the old device too. Deleting a local configuration doesn't revoke its link, and signing out of the website doesn't clear the client's cache. For more background, read the guide to getting, importing, and updating subscription links. Once you have the right configuration, follow the next section to set up each platform.

Set up the client on each platform

Before you start: get the client from the dashboard

Download clients from the download section in the dashboard. Sign in to download for Windows / macOS / Android / Linux; the iOS download link requires an active plan. Download access and connection benefits are separate: installing the app doesn't mean you have a working subscription. Check your operating system and device architecture before selecting the corresponding download. This guide doesn't provide direct installer links or specify a particular version. Refer to the client itself for current interface labels and permission prompts.

Windows: check which traffic is routed after import

Install and launch the client, then choose Import in the subscription or configuration section and paste the complete link copied from the dashboard. Wait for the routes to load, select the configuration and exit you want, then connect. If Windows asks for network permissions, check the app name and its source. Don't disable all system protections just because a permission prompt appears. Once connected, test a regular browser request, then try the app you need. This helps rule out interference from browser extensions or a separate proxy setting in a developer tool.

On Windows, distinguish the system proxy, virtual network adapter, and an app's built-in proxy. The system proxy usually affects apps that follow system settings; don't assume every process does. If a browser works but a command-line tool doesn't, check whether that tool reads the system proxy or still has old environment variables set. If regular websites stop working after you quit the client, check whether the system is still pointing to a local proxy that has stopped instead of repeatedly reinstalling the client.

macOS: allow the required network extension

Download the macOS client for your device from the dashboard, then install and open it by following the system instructions. Import your subscription, select a configuration and exit, then enable any required network extension or connection permissions when prompted by the app. macOS may ask you to confirm in Security settings; check the software source and the permissions requested first. Until permissions are granted, the client may show the configuration even though it hasn't taken over system traffic. Verify by making an actual request rather than relying on the appearance of a toggle.

If other network tools are running in the menu bar, pause any that you don't need so their settings don't conflict. If the app can't reconnect after waking from sleep or changing networks, check the current network and client status, then try disconnecting and reconnecting. Don't clear system DNS, delete configurations, and change network service order all at once. Keep a clear record of what you changed so you can tell whether the issue came from a network switch, permissions, or the subscription.

iOS: make sure the configuration goes to the right app

On an account with an active plan, open the dashboard's download section and follow the iOS instructions to get the client. If you import from the dashboard, make sure iOS is about to open the app you expect. To import manually, paste the subscription into the client's configuration section. The first connection may ask permission to add a network configuration; verify the source before approving it. After saving the configuration, select it and connect. Being redirected from the browser to the app does not mean setup is complete.

On iOS, check which network configuration is active and whether another app replaces it on launch. If a problem starts after switching between Wi-Fi and cellular data, verify the underlying connection first, then check that the client still has the intended route selected. If a video app shows an old region, don't delete the subscription right away. Fully quit and reopen the app, then consider the account region and the platform's own message. The issue may be cached platform data, not a failed installation.

Android: manage connection permissions and background activity

Sign in to the dashboard to get the Android client. During installation, read the system's information about the app source and permissions. Open the client, import your subscription, wait for the configuration to load, select a route, and allow the network connection. If the client supports per-app routing, start with the default rules so they're easy to understand; avoid adding lots of exceptions straight away. If an app isn't included, its traffic may still use the original network even when the client shows as connected.

If the connection drops when the screen locks or you switch apps, check the system's background activity and battery restrictions for the client, then see whether the issue improves. Settings names vary by device, so don't rely on screenshots from another model. Grant only the permissions needed to keep the connection working. When troubleshooting, first check whether the client is still running, then look at route errors. This helps distinguish the system stopping background activity from a remote route problem.

Linux: distinguish desktop apps from terminal tools

Choose a Linux client for your system from the dashboard and install it using the interface or the supplied instructions. Import your subscription and select the configuration before connecting in the mode you need. A desktop proxy setting may not be passed through to terminal programs, and proxy environment variables in a terminal won't automatically control every desktop app. Check the actual route for each browser, developer tool, and command-line request. Don't assume the whole system is routed just because you see a tray icon.

If network permissions are required, follow the client's explicit instructions. Running an unknown script with elevated privileges is not a general-purpose fix. For command-line proxy settings, use the listening address shown by your local client; don't guess the port from a tutorial. The final checks are the same on every platform: make sure the configuration is selected, routes are loaded, and the connection is active before moving on to the layered checks in the next section. For a shorter walkthrough, return to the quick start guide.

Check your connection and troubleshoot

Check one layer at a time, from the network to the target app

Start by checking your underlying network with the client disconnected. Make sure your device can access the current network and complete any sign-in required by a public hotspot. Then connect the client and check the configuration, selected route, and connection status. Visit a familiar website and the international service you actually need. This sequence helps distinguish an unavailable local network, a client that isn't routing traffic correctly, an issue with the exit, and a destination platform that is refusing access. Don't label every problem “a slow route.”

The connection icon, route tests, and requests from real apps indicate different stages. A successful test may only show that its test destination is reachable. An app session also depends on DNS resolution, transport protocols, account permissions, and platform security checks. Reproduce the task you actually need to do—for example, open the relevant page, make a normal request, or start playback—instead of stopping at the home page. Keep the app and test action consistent while troubleshooting so you can compare changes accurately.

Match symptoms to the right checks

If regular websites load but one app doesn't, start with the exact message from that app. Expired sign-in, an unsupported region, too many requests, and a network timeout all need different responses. For a sign-in issue, check the account with the target service. For a region message, check the exit and the platform's supported regions. For a timeout, revisit the route and DNS. If a security check appears, don't keep switching regions and retrying. That may make account activity less consistent and make the issue harder to diagnose.

Trying another route in the same region can help distinguish a single-route issue from a regional one, but keep all other conditions the same. Note the current route type, network, and error before switching to another suitable route. Don't also change the browser proxy, clear all site data, and switch accounts. Even if access returns, you won't know why. A useful performance comparison starts by controlling variables—not just looking at which test result has the biggest number.

Command-line checks only answer specific questions

If curl is already installed, use the command below to check the response headers from an example website. It contains no credentials and doesn't use a real subscription link. Whether the request goes through a proxy still depends on your terminal environment and how the client routes traffic. A successful response only means that request completed; it doesn't guarantee access to a particular AI tool or video platform. If you don't have curl, use a browser for the same basic check. There's no need to run an installer script from an unverified source.

curl --head https://example.com

Understand DNS errors, certificate errors, and connection timeouts separately. A DNS error points to the domain lookup path. For a certificate error, first check the system time, website address, and any unexpected interception. Don't disable certificate verification as a lasting workaround. A connection timeout needs further checks of the underlying network and current route. Before sharing terminal output, remove proxy credentials, internal addresses, and work project details. Include only what's needed to diagnose the problem.

Write a reproducible report before opening a ticket

A useful support ticket names the platform, current network type, target app, route region and type, the action that caused the problem, and the client's original error message. You can also say whether it happened before connecting, while updating the configuration, or during use. Don't publicly attach a full subscription link, password, or logs containing sensitive work information. If an action consistently reproduces the problem, list the steps. If it happens only after switching networks, say so. A clear report preserves more troubleshooting clues than repeated reinstalls.

Ongoing maintenance and renewals

Keep your account records and local configuration in sync

Routine maintenance doesn't require frequent configuration resets. The key is to keep your dashboard benefits, subscription contents, and selected client configuration in sync. Route details may change, and importing multiple links can make local configurations hard to identify. If the dashboard and client show different information, first check which configuration is selected, then update it. Keeping obsolete or unknown configurations isn't useful for troubleshooting. Before deleting anything, make sure you can get a working subscription again from the dashboard.

Updating a client app and updating a subscription are different tasks. The first updates the software on your device; the second refreshes route and configuration data. After a software update, check whether system permissions, routing behavior, or configuration compatibility have changed. After a subscription update, make sure your usual routes and app rules still work as expected. Don't treat updates as background chores that need no follow-up. Before a long session, meeting, or file transfer, test a normal task first.

Understand your data allowance and billing period

Monthly plan data resets each month on the activation date. Check the billing period shown in the dashboard when reviewing your remaining data. A client's local usage total may accumulate by app session, configuration, or device, so it doesn't override account billing records. Unlimited simultaneous devices means multiple devices can connect; it doesn't mean each gets a separate plan allowance. When planning usage, consider the tasks on all connected devices under the same account.

If your remaining data changes more than expected, check whether autoplay, cloud sync, system updates, or download tools are using the proxy. App routing affects both where traffic goes and which background tasks use international routes. Check the client's connection logs for possible sources, but don't block essential system services just to save data. Identify the task first, then decide whether direct routing or pausing it makes sense. This avoids turning data management into a connectivity problem.

Review the confirmation page before renewing or upgrading

To keep using the service, open the plan section from your current account and check the product, price, and type of change. Don't assume that a payment will keep your existing plan, or treat a data pack as a universal way to top up a monthly plan automatically. A data pack is valid until used and never expires. Monthly plan data resets on the activation date. Check the confirmation page to see how products work together in your account. Don't guess at priority, rollover, or reset behavior unless it's clearly stated.

For a mid-cycle upgrade, the price difference is converted into remaining days. Check both your current benefits and the target plan benefits before confirming. If you're changing how you use the service, first see whether the change reflects a genuine need for more data—for example, adding regular video streaming or a one-off background update. A brief network problem doesn't mean your allowance is too small, and changing plans doesn't replace connection troubleshooting. After paying, check your order and account overview, then update the client subscription if needed. This keeps billing and network setup as separate steps.

Device changes, stopping use, and privacy cleanup

When switching devices, sign in, import the subscription, and verify the connection on the new device before clearing the old one's local configuration. Before handing over or selling a device, also check saved website accounts, password manager access, clipboard history, and screenshots. Signing out of the user dashboard doesn't automatically remove configurations from a client, and uninstalling the client doesn't prove that subscription credentials have been revoked. If you suspect a link has been exposed, use the options available in the dashboard and update the link on any devices you keep using.

If you're taking a break, disconnect the client normally and check that your system network returns to its expected state. You don't need to delete your account to stop using the service. L7VPN offers a 60-day no-questions-asked refund; see the Terms of Service for application details and contact support through a dashboard ticket. Refer to your order and the issue you encountered; don't share your password or subscription link. Read the Privacy Policy for information about data handling, and consider account information alongside network configuration when managing your privacy.

Advanced routing and app exits

First, understand how rules determine the route

App routing can match requests by process, domain, address, or other conditions supported by the client, then apply a specified policy. Rule capabilities and matching order vary by client, so this guide does not provide a configuration assumed to work on every platform. Read how your client handles rule priority and default behavior before making changes. In particular, confirm where unmatched requests go. A rule that appears to affect only one app could change the route used by other services too.

Keep the working configuration provided by the dashboard, then add only the rules you actually need. After each change, test the target app and check regular websites and commonly used local services too. Domain rules may look precise, but an app can use different domains for sign-in, content delivery, attachments, and live connections. Matching the home page doesn't mean every part of a task uses the same route. Process rules can also miss helper processes. If only some features fail, check which policy the actual request matched instead of routing all traffic through the proxy.

Choose exits for your apps instead of chasing list metrics

AI tools often rely on persistent sessions, streaming responses, or long-lived connections in developer tools. For these tasks, a consistent exit and stable connection are often more important than switching routes frequently. Before starting a session, confirm that the platform supports the selected region and avoid unnecessary exit changes while using it. If the platform reports an account or region issue, check eligibility according to its guidance. Switching routes is not a general solution to account restrictions. For more background, read how Claude determines regions and handles account risk.

Verify video by playing it, not just by opening the home page. Library listings, sign-in checks, playback authorization, and content delivery may use separate requests. The platform may consider both account region and network location. If your rules are incomplete, the home page and video requests may take different routes. To troubleshoot, keep the exit consistent and note exactly when playback fails. Don't conclude that a route will always work based on one successful load, or treat the number of covered regions as a promise of library access.

Check developer tools and DNS routes separately

Terminals, editor extensions, and background tasks may each have their own proxy settings. After configuring a route for your browser, check whether developer tools use the system proxy, environment variables, or a separate setting. Use the local parameters shown by your client for the proxy listening address; don't copy a port from another device. When working on projects, don't share full request headers, access keys, or private repository contents with unrelated support channels. For more on long-lived connections, read route selection for Cursor and Copilot.

DNS resolution turns a domain name into a destination address; proxy rules determine how the request is sent. The two work together. A browser may use its own DNS settings, and an app may cache old results, so changing client rules may not immediately change what the app does. Don't disable checks or replace your entire DNS setup just to get a particular result on a test page. First check the client's recommended settings and see whether the target app works as expected. Then decide whether deeper changes are necessary.

Make changes you can roll back

Advanced settings should make traffic paths clearer, not make the configuration longer for its own sake. Document what each custom rule is for, note the configuration and exit used when everything works, and keep a comparison record without credentials before changing anything. If something goes wrong, return to the basic configuration provided by the dashboard and verify it first. Then restore custom rules one at a time. To compare regions and route types for different uses, read the beginner's guide to choosing a route. When you can check the account, subscription, client, and app exit independently, everyday use and troubleshooting have clear boundaries.