VPNAct
Complete Setup Guide

Understand accounts, subscriptions, and clients

VPNAct provides a subscription service for cross-border connectivity. Your account manages plans, orders, and support tickets. A subscription delivers available routes and related configuration to your client, which handles connections and traffic routing on your device. These are related, but not interchangeable. Creating an account does not connect you, and installing a client does not give you access to working routes. Follow the sequence: account, plan, subscription, client, verification.

Think of a subscription as the way a client retrieves its configuration, not a website you need to keep opening in your browser. The client uses it to get route information, then connects according to your current selection. Updates may change route names or configuration, so routine maintenance should focus on refreshing the existing subscription rather than relying on manually copied route settings. If settings are missing, return to the panel for the complete configuration.

Service coverage includes 100+ countries / 150+ routes, with support for Windows / macOS / iOS / Android / Linux and unlimited simultaneous devices. This describes the service's scope; it does not guarantee access to every website in every network environment. Your device's network, client settings, and the target platform's policies can all affect the result. A repeatable verification process is more reliable than relying on the connection icon alone.

A connection handles the network path, not platform account permissions

When you access international services, requests pass through your local network, client rules, selected route, and the destination server. A route can change the path and exit region for some requests, but it cannot change the permissions the destination service grants your account. A page may load while account features remain unavailable due to account region, eligibility, or platform risk controls. Further changes to local proxy settings may not help.

Likewise, a region label does not guarantee access to particular media. Platforms may assess the exit region, account, and session history, and their content catalogs can change. First check whether ordinary websites load through the route, then test playback or sign-in on the specific platform. Separating network issues from platform permissions helps avoid switching routes at the wrong layer.

A client showing “Connected” usually means the connection feature is active; it does not prove every app uses the same network path. Some apps follow the system proxy, others use independent network settings, and rules may send certain requests direct. To check whether an app is covered, make a request in that app instead of assuming a successful browser test verifies every app on the device.

Before setup, keep a way to restore your connection

Before you begin, confirm that the device can access the internet normally with the client disconnected, and note your current network environment. If the underlying network is unavailable, first troubleshoot Wi-Fi, access authentication, or your local router. Otherwise, subscription errors, inaccessible websites, and app timeouts can blur together, making it hard to tell whether the issue is network access or incomplete client setup.

You may want to keep a local note of your operating system, client name, import method, and current mode, but never put your password or full subscription URL in a public note. This non-sensitive information is enough to reconstruct the setup when troubleshooting. Record existing settings before changing them, then check the result before making another change. Avoid changing several options at once, so you can identify the cause and restore the original setup if needed.

This guide is organized around common client features and does not assume every platform uses the same button names. An interface may say “Configuration,” “Subscription,” “Proxy,” or “Connect.” Follow the function and the panel's instructions rather than looking for a fixed location. If a feature is missing, first check that you have a client suitable for the platform before moving on.

Choose a billing option that fits how you use the service

Before choosing a plan, consider how regularly you connect. For daily work, research, or streaming, focus on the monthly plan's data allowance and reset schedule. If you connect only occasionally or at irregular times, compare the data packages. Base your choice on actual use and frequency, not just the price. A lower-tier plan does not necessarily mean worse routes, and a larger plan does not guarantee easier access to a particular platform.

Monthly plans: ¥9.9/month includes 60GB, ¥18/month includes 250GB, and ¥28/month includes 500GB. Data resets monthly on the activation date. Mid-cycle upgrades are prorated against the remaining days. Check the current term and upgrade details in the panel. The reset date is not the start of a calendar month; do not estimate the post-upgrade amount or remaining term yourself.

Data packages: ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Use the data as needed; it never expires. The key difference from a monthly plan is how you use the data, not any promise of additional connection capabilities. If you already have a plan, check the panel's terms before adding another billing product. Do not assume allowances will combine or that one plan will take priority.

Understand data use in everyday situations

Web pages, video streaming, file sync, and large downloads use very different amounts of data. Even within a browser, streaming video is a different workload from reading documents. When you start, check data usage in the panel and compare it with the apps running on your device. Connection time alone is not a reliable estimate: background sync and automatic updates may keep transferring data when you are not actively using the device.

Unlimited simultaneous devices means there is no limit on the number of connected devices; it does not give each device a separate plan allowance. Consider usage across all devices on the account together. If data usage keeps changing after you close a page on your computer, check other connected devices and background tasks before assuming a billing error. Do not compare panel and client statistics as if they use the same measurement method without checking first.

Traffic rules determine which requests use a route. Direct requests and proxied requests are not equivalent, so understand your rules before comparing usage. If you temporarily change modes to troubleshoot, restore the original settings when you finish. That prevents unnecessary downloads or sync tasks from continuing over the proxy. Consider your plan and client settings together rather than focusing on a larger allowance alone.

Check the details before confirming an order

Check the current prices, billing options, and refund terms on the Plans page, then choose a plan in the panel. The marketing page explains the available terms; confirm the actual order details again before paying. If you are unsure about an upgrade, an existing order, or when a change takes effect, describe your current situation in a panel support ticket and wait for a clear answer before proceeding. Do not assume an unfamiliar rule is a default promise.

VPNAct supports Alipay / WeChat Pay / USDT and offers a 30-day refund policy. See the Terms of Service for refund details; submit requests through a panel support ticket. A refund policy does not mean every transaction is automatically reversed. Do not place duplicate orders to test whether a payment went through; keep a record of both order and refund processing.

By the end of this section, you should know whether you chose a monthly plan or a data package, its allowance, and where to check your resources. If you are still deciding, keep your options open and read the next section about accounts and orders. You do not need to pay before continuing; the same steps apply while you are preparing.

Get started with account details you can keep safe

VPNAct does not require an email address; you can create an account with a username and password. Go to the account creation page to open the user panel, then enter the requested details. Choose a username you can save and enter accurately. Use a unique password and store it with a trusted password manager. Never share your account password and subscription URL together in a chat group or shared document.

After submitting, check that the panel opens your account before choosing a plan. If the page stays where it is, read the message and check required fields and your network. Do not submit repeatedly just because there is a brief delay. Confirm that the account was created by checking that you can enter the panel, then save your username before placing an order.

Not requiring an email address does not mean you can ignore your account credentials. You will need your account to sign in, check your subscription, and manage orders. Do not assume a particular recovery method is available; account recovery depends on the features and identity checks provided by the panel. Verify your credentials before changing devices so you do not discover you cannot sign in after clearing the old device.

From choosing a plan to confirming payment

Open the plans section in the panel and choose the product you checked earlier. Review its price, allowance, and billing option before submitting. In particular, do not confuse a data package that never expires with a monthly plan that resets each month. If you see an existing unfinished order, check its status and details before deciding whether to pay or follow the options shown on screen.

Choose Alipay / WeChat Pay / USDT as appropriate and follow the payment page instructions. Check the amount and payment details for the current order; do not use payment details from an old screenshot in place of the current page. For transfers, follow the instructions for that order. Do not guess the amount, network, or settlement rules; pause and ask through a support ticket if anything is unclear.

After paying, return to the panel to check the order status and plan resources. A completed status in your payment app only confirms the payment side. You can proceed to get your subscription once the panel shows that the order has been processed and the resources are active. If the redirect fails, keep the original order and check it in the panel. A browser error does not mean the payment failed, and it is not a reason to pay again.

If payment is complete but the panel has not updated, refresh the order record and check that you are signed into the correct account. If the status still does not match, use a panel support ticket to provide the order ID, payment method, and a description of what happened. Keep only the details needed for verification in screenshots, and hide unrelated personal information. Support does not need your account password or full subscription URL to investigate an order issue.

Check account and device status separately

Once your plan is active, check your resources in the panel before installing or opening a client. This makes it easy to rule out “no resources available on the account” if import fails. If the account has resources but the client has no routes, check subscription retrieval and configuration import. If the panel shows no resources, resolve the order or activation status first; reinstalling the client repeatedly will not help.

After using the panel on a public or borrowed device, sign out and clear subscription details from the clipboard. Whether your browser retains a signed-in session depends on the device and its settings; closing the tab does not necessarily sign you out. Use a suitable screen lock on your regular devices too, to prevent others from opening pages with subscription, order, or account information.

You are ready to move on when you can sign back into the same account, find the relevant order, and see available resources in the panel. Confirm all three; the next section covers subscription delivery. If you run into an account or billing issue here, check the relevant guidance in the Help Center before attributing it to a route problem.

Get a configuration that works with your client

Once your plan resources are available, look for subscription options in the panel overview. Decide which client you plan to use, then follow the import method provided in the panel. Clients may accept different formats; the same subscription resource cannot necessarily be read from any text by every app. Use the import option the panel identifies for your client to avoid format issues.

Automatic import usually opens the client from your browser and passes it the subscription details. If prompted to open an app, confirm that the intended client will receive them before continuing. If nothing happens, the client may not be installed, the system may not have an app assigned to open the link, or the browser may have blocked it. Go back and check the download and installation steps before assuming the subscription is invalid.

For manual import, copy the subscription URL from the panel and paste it into the client's remote subscription or import-from-link feature. Check that the beginning and end are intact, with no extra text, line breaks, or spaces. Give the configuration a recognizable local name, save it, and update it. Confirm that the route list appears, then select this configuration as the active one.

Tell retrieval, parsing, and connection errors apart

“Retrieval failed” usually means the client could not get the subscription. Check your underlying network, the URL, and resource status in the panel. “Parsing failed” means the client received content but cannot read it in the current format. Check the subscription type and client compatibility. “Connection failed” occurs after routes appear; focus on the selected route, permissions, and proxy settings. These errors need different fixes.

If the client says the subscription is empty, first make sure you imported a subscription URL, not a marketing page or the panel sign-in page. A URL opening in a browser does not mean it contains configuration the client can read. If the browser shows a sign-in screen, error message, or ordinary webpage, the client cannot turn it into a route list. Return to the signed-in panel and get the correct link.

If an update succeeds but routes do not appear on the current screen, check whether the client still has an older configuration selected or whether you are viewing a filtered or favorites list. Some apps store multiple configurations. A successful import means it was saved, not necessarily activated. Confirm which configuration is active, then check its routes. Do not create repeated copies to compensate for selecting the wrong one.

Treat your subscription as a credential that needs protection

A full subscription URL may contain information identifying your account resources, so protect it like a credential. Do not paste it into an unfamiliar conversion website, post it on a public forum, or share an unredacted client screenshot. Anyone who can read the subscription may use your account resources. Even when asking for troubleshooting help, use a redacted screenshot and describe the error in text.

If you suspect your subscription has been exposed, check whether the panel offers a reset and review the impact described there. After a reset, the old URL may stop working, and you may need to retrieve or update the configuration on your devices. Follow the panel's instructions. Update every device still in use; changing the setup on your computer alone could leave an old configuration on another device and make the issue look like an unstable network.

This guide does not show real subscription URLs. Always get yours from the panel; do not copy purported generic configurations from articles, search results, or chat history. If support needs to investigate, start with the error type, client platform, and stage where it occurred. Share any additional information only through a panel support ticket and only to the extent requested, keeping unrelated credentials out of it.

Update regularly without losing your existing setup

When routes change, update the existing subscription instead of deleting it and rebuilding all your settings. Then check whether your selected routes are still available, rules still work, and commonly used apps connect. If an old route name disappears, choose an available one from the updated list. Repeatedly deleting configurations can erase local groups or selections and turn a simple update into a full reconfiguration.

At this point, you should be able to confirm that the client has loaded the configuration for your account and tell whether an update succeeded. The next section covers installation, permissions, and activation for each operating system. Importing a subscription only gives routes to the client; to confirm they work, connect and check the exit region and app results in the verification section.

The general sequence on each platform is: get a client, import your subscription, select the configuration, grant required permissions, and enable the connection. Find the client in the panel downloads section. After signing in, you can get a client for all platforms except iOS. The panel handles the iOS entry point and available permissions; follow its instructions and do not look for installation files shared from unofficial sources.

Windows: Check the active configuration and system proxy

Get the Windows client from the panel and install or launch it as directed by the system. Import the subscription and confirm that routes appear before selecting the active configuration and a route. If Windows asks about network access or related permissions, verify the app's source and name before responding. If installation succeeds but no routes appear, the issue is still at the subscription stage; you do not need to change network adapter settings yet.

After connecting, check whether the client uses the system proxy or another method to route traffic. The system proxy affects apps that follow that setting; it does not mean every program is covered. Verify with a browser first, then test the apps you actually use. If webpages still behave strangely after disconnecting, check whether the client turned off the system proxy and exit other network tools. Do not remove system networking components unless you know what they do.

macOS: Handle installation approval and connection permissions separately

Get the macOS client from the panel, put it in the appropriate location as directed, and launch it. macOS may ask you to approve opening the app or grant network-related permissions. Only authorize it when you can verify its source; do not lower system security settings across the board to resolve a launch issue. Once the client opens, import the panel subscription, confirm the configuration has updated, and enable the connection.

If the menu bar shows a connection but an app still fails, check the active configuration, route, and proxy mode first. Then check whether the app needs a new network session. Reopening it after changing settings can rule out an old connection. If a system permission was denied, check the relevant authorization in System Settings rather than repeatedly importing the subscription.

iOS: Get and import through the panel

On iOS, first check the Downloads section in the panel for the options available to your account, then get the client as instructed. After installing it, return to the panel and try the relevant import method. If your browser asks whether to open the app, confirm that it is the correct client. In the app, check that the subscription has been saved and updated; opening the app alone does not mean the configuration is active.

The first connection may require system approval for network configuration. Verify the app before allowing it. If other network configurations are present on your device, check that the active one is the one you expect and avoid interference between tools. Even after the system shows a connection, verify in both a browser and the target app. If platform content does not change after switching routes, first distinguish an old session from an account-region issue.

Android: Check background activity and network switching

Sign in to the panel and get the Android client, then follow the system's installation instructions. Import the subscription and select a configuration and route. Read the system permission prompt the first time you connect. If the system says another app is using network access, check which tools are running before deciding what to close. Do not let multiple apps compete to manage network traffic.

If the connection works in the foreground but drops after you lock the screen or switch apps, check the system's background activity and battery restrictions for the client. Settings locations vary by device; follow the system's own guidance rather than disabling power management for every app. If the connection fails after switching between Wi-Fi and mobile data, check that the underlying network works, then reconnect instead of clearing the configuration.

Linux: Check the runtime environment before routing

Get the Linux client from the panel and check its system requirements and permissions as instructed. For a graphical client, import the remote subscription. If you use command-line features, check the configuration format and actual startup parameters; do not assume a configuration for another client is compatible. If you see a permissions error, read the logs rather than continually raising privileges without investigating the cause.

Desktop proxy settings, terminal environments, and background services may use different network paths. A working browser does not prove terminal commands use the proxy, and the reverse is also true. Identify the program you need to test, then check how it reads proxy settings. Keep existing environment variables and service settings; record their values before changes. Remove temporary settings after testing so they do not affect later software management tasks.

After setting up a platform, hold off on adding custom rules. First verify the default configuration, then handle special apps one at a time. That way, if something goes wrong later, you can return to a known-working baseline.

Start with a clear before-and-after comparison

Start verification with your underlying network. Disconnect the client and confirm the device can access the network as usual. Then enable the imported configuration, select a route, and reopen the test page. Use the same app and type of request before and after so you can tell whether the connection made a difference. Do not change networks, rules, and browsers all at once; even if things work again, you will not know which change helped.

Client logs can help show whether a request used a route, but interpret them alongside the actual page result. A successful connection log only confirms that one request connected; it does not guarantee that later requests will work. A failed log may also come from a background app unrelated to the site you are testing. Note what you did, then check logs for the matching time and destination to filter out noise.

To check your exit address, use the same app environment you plan to work in to look up the current address and region. Record the results with the client disconnected and connected, then compare them with your client rules. In rule mode, a lookup site may be set to connect directly, so an unchanged result does not necessarily mean the connection failed. Check which rule matched the request before switching temporarily to a clearer test mode.

Distinguish exit region, DNS, and app sessions

The exit address shows where a request leaves the network. DNS translates a website name into a connection destination. They are related but not interchangeable: your exit address can change while DNS still fails, and successful DNS resolution does not prove the request used the expected route. If a webpage will not load, identify whether the failure is in name resolution, connection setup, or sign-in. Do not label every issue a route failure.

Do not draw conclusions about DNS based only on the region of a particular DNS server. System caches, browser settings, and client DNS policies may all affect the process. Consider the active rules and actual request path, and compare them with a known-good setup. Before you understand how the client handles DNS, do not enter unfamiliar addresses or enable multiple DNS configurations at once; that can create new inconsistencies.

Apps may keep old connections, region checks, or sign-in sessions. After switching routes, reopen the relevant page first; if the result is still inconsistent, start a new session using the app's own options. Consider which accounts will be signed out before clearing browsing data, and do not treat clearing everything as the default fix. Repeatedly changing regions to retry a sign-in may prompt the platform for extra verification.

Narrow down the issue by what you observe

If no apps can connect, check the underlying network and client permissions first. If the browser works but other apps do not, check whether they follow the system proxy. If ordinary websites work but a particular platform does not, check its account, region requirements, and the selected route. Only if one route is failing should you compare it with another using the same configuration. Do not treat a local issue as an account-wide failure.

If performance differs between peak hours and daytime, note the results on the same device, network, and destination, then compare other route types. Do not treat route names in the client list as a performance ranking or draw lasting conclusions from a single connection test. Choose based on repeatable checks in the situations that matter to you. See the Routes page for route types and region details.

If an AI tool opens its sign-in page but fails when you send a request, check page loading, account sign-in, and the actual feature call separately. They may use different domains and connection methods. For streaming, test catalog loading and playback separately too. Reports like “it opens” or “it doesn’t work” are hard to diagnose; describe the specific action that failed.

Keep useful details before opening a support ticket

If the issue persists, note your operating system, client name, selected route, proxy mode, exact error message, and checks you have already run. Redact passwords, subscription URLs, and unrelated account details from screenshots. After submitting a panel support ticket, keep the issue in a reproducible state. Avoid repeated reinstalls and major setting changes while waiting, or the advice you receive may no longer match the problem.

Use a verified working setup as your maintenance baseline

After your first successful checks, note the client, active configuration, commonly used routes, and proxy mode. Do not include credentials; these notes are just for restoring your setup if something changes. Maintain the state you have verified instead of changing unfamiliar settings on sight. A setup that completes your tasks is usually easier to maintain than one that keeps accumulating untested options.

After updating a subscription, confirm that the configuration loaded, then check whether your commonly used routes are still available. If route names or groups have changed, choose an available option and test your usual apps. Do not assume all routes are broken just because an old favorite no longer responds. Clients and subscriptions have separate update processes; test after each one before proceeding so you can identify what changed.

Before updating a client, save any necessary notes about non-sensitive settings and confirm that you can sign in to the panel to get your subscription again. After the update, check whether system permissions, the active configuration, and proxy status are still in place. Do not upload a full configuration file to a public backup service; it may contain subscription information. When moving to another device, get the subscription from the panel instead of relying on unverified cloud sync to manage credentials.

Manage data and billing periods using the panel

Monthly plan data resets on the activation date each month. When checking the panel, review resource status, data usage, and the current billing period together. Do not confuse a data reset with the service's active status. If the client suddenly shows no available routes, check your resources and subscription update before troubleshooting the local network. An exhausted allowance, invalid configuration, and connection failure occur at different stages and need separate fixes.

Data packages last until used and never expire. Even if your usage is irregular, check your remaining data periodically so you do not find yourself short when you need it. Do not assume that renewing will necessarily restore an old configuration or that new resources will be consumed in a particular order. Check the panel and ask support how an existing plan relates to additional resources if anything is unclear.

If usage is much higher than expected, check other devices and background tasks first. File sync, autoplay, and app updates can all keep using data. Client statistics can help you spot trends, but use panel records and a support ticket to check account billing. Do not compare a momentary reading from one app directly with the account's cumulative total.

Handle renewals, upgrades, and orders separately

When you want to continue, choose a suitable product from the plans section in the panel and confirm the order's billing option, price, and activation details. Check for unfinished orders before renewing to avoid submitting a duplicate. After paying, verify the account resources and order record instead of relying on whether the payment page closes automatically. If resources do not change as expected, keep the order and ask through a support ticket.

Mid-cycle upgrade differences are prorated against the remaining days; use the panel's confirmation details. Do not calculate this as a discount yourself or assume an upgrade gives you a full new billing period. If your usage pattern is changing, for example from regular use to occasional use, compare the billing terms rather than just the total data. See the Plans page for prices and data package details.

Handle refund questions according to the 30-day refund policy and the Terms of Service; submit requests through a panel support ticket. Include the relevant order and what you are requesting, and avoid submitting different versions in multiple places. Orders, plan resources, and refund requests each have their own status. Keep details consistent to make them easier to check and avoid mistaking in-progress processing for completion.

Move to a new device and clear the old one

There is no limit on simultaneous devices, but sign out of your old devices and remove subscriptions when appropriate. Before giving away, repairing, or retiring a device, clear client configurations, browser sign-in sessions, and clipboard contents. If a device is lost or may have been accessed by someone else, use another available device to check account-related options in the panel and ask support what to do. Closing the local app does not necessarily stop access to your resources.

The goal of ongoing maintenance is not to check every setting daily, but to know where to look when something changes. If the network changes, check your connection. If routes change, update your subscription. If resources change, check the panel. If one app changes, check its rules and session. Following this order means you do not have to start over with installation every time something goes wrong.

Understand the modes before changing rules

Consider advanced settings only after the basic connection works. Rule mode uses the destination, app, or other matching conditions to decide whether requests connect directly or use a route. Global proxy mode generally sends requests handled by the client through the proxy. Direct mode sends the relevant requests without a proxy. Mode names vary by client; what matters is which traffic is handled and how rules match, not where a particular switch is.

Global proxy mode cannot automatically handle apps the client does not cover. If a program does not use the system proxy and no other traffic-handling method is active, switching modes may not change its path. Before changing modes, check whether the request reaches the client, then see how rules route it. Distinguishing “not handled by the client” from “matched a direct rule” helps avoid ineffective changes.

To test a rule, keep other conditions unchanged and check the logs for the target request's match and final route. If there is no matching request in the logs, check whether the app is covered. If it matched an unexpected rule, then inspect rule order and scope. Do not expand proxy coverage for all requests just to get one website working; this could change how other apps appear and how much data they use.

Consider route type and destination region separately

IEPL dedicated lines, relay routes, and direct connections describe different ways of organizing network paths, not a fixed ranking that applies to every network. A direct path is more straightforward, but performance still depends on the network between your location and the destination. Relays add nodes to the path, so results depend on those links. IEPL routes also need to be checked with your actual network and target app; the name alone cannot predict every result.

When choosing a route, first identify the region the target platform requires, then compare available routes in that region. For apps that need a stable session, try to keep the exit environment consistent instead of switching just because other regions are listed. For general browsing, compare actual availability. For region-specific content, also consider the platform's account and catalog requirements.

Streaming pages, media, and account services may use different domains. If a page opens but playback fails, check the rules for playback requests instead of looking only at the homepage domain. AI tools may also use different connections for authentication and feature requests. Custom routing needs to cover the full workflow, but do not add broad rules based on guesses or assume platform restrictions are caused by local rules.

Start small when customizing a configuration

If your client supports local overrides or separate rules, use the features it provides rather than directly editing the main content generated by a remote subscription. A remote update may overwrite manual edits, making a setting seem to “revert on its own.” Before you start, understand merge order, conflict handling, and rollback. If the interface does not explain these, check the client help or ask through a panel support ticket.

Change only one setting at a time when you understand its purpose, and note why you changed it and what happened. If it fails, restore the original value before trying another approach. DNS, traffic handling, and rule selection are related; changing them all at once can produce results that seem random. You do not need to enable every advanced feature. Settings are worth keeping only if they suit your device and task and produce repeatable results.

Coordinate multiple devices and keep useful troubleshooting notes

Devices can use different rules and preferred routes, but verify apps on each device separately. A browser working on your computer does not mean background traffic works on your phone; a terminal command connecting successfully does not verify a desktop app. For multiple devices, give local configurations clear names and note their platform and purpose. Do not put full subscription URLs in configuration names or shared notes.

For complex issues, keep a concise record: whether the underlying network works, whether the subscription updated, whether the app is covered, which rule matched, which route was used, and the exact action that failed. This helps with self-troubleshooting and gives support the context to make a useful suggestion. Do not submit unfiltered full configurations and large volumes of unrelated logs. Protect credentials and keep only information needed to reproduce the issue.