FAQs and Subscription Help

No email address is required. Create an account with a username and password in the user dashboard, and keep both somewhere safe. After signing in, check your account overview for your plan status and remaining data, then follow the dashboard instructions to get your subscription. The plan status shown in the dashboard determines whether a subscription is available; a client download link on a marketing page does not mean you already have an active subscription. Subscription details are account access credentials. Import them only into your own client, and never share them in public screenshots, group chats, or shared documents. For your first setup, follow a guide to import the subscription, then choose a route to test access.

Sign in to the user dashboard and check your plan status and remaining data in the account overview. In your client, open subscription or configuration management and update the configuration you use. When the update finishes, check that the route list has refreshed and that this is the active configuration, not another one you imported earlier. It is usually best to keep the old configuration until troubleshooting is complete. If the client says the address has expired or cannot be read, return to the dashboard for the current subscription details and replace them according to the client's instructions. Never upload subscription data to a public converter or paste the full subscription link into a support ticket.

VPNFZ supports unlimited devices online at the same time, so changing devices alone does not mean you need a different plan. Sign in to the same account on your new device, use the dashboard links to get the client and subscription, then import the subscription and test the connection. Supported platforms are Windows / macOS / iOS / Android / Linux. Setup steps vary by platform, so a configuration file for one platform may not work as a universal installer. Unlimited devices does not mean unlimited data; keep an eye on your remaining account data when using multiple devices. When you stop using an old device, remove its local configuration to reduce the risk of leaving account access details on an inactive device.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on your activation date. Data bundles are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB; they last until used and never expire. If you use the service regularly, track your data usage to choose a monthly plan. If your usage is irregular, compare it with the data bundle details. Monthly reset rules do not apply to data bundles, and the two product types do not automatically combine or offset each other. Check the plans page before choosing; your account status and usage records in the dashboard are authoritative.

First, pause the proxy and make sure your device can access its current network normally. Then sign in to the dashboard and check your plan status and remaining data. Once the basic connection is working, confirm that the client has the correct subscription configuration enabled, the route list is populated, and any required VPN permissions are allowed. Update the subscription, try another route, and see whether the client error changes. Avoid running multiple tools that can take over network traffic at the same time, or it may be hard to tell which configuration is active. If you still cannot connect, note your operating system, the client's message, the route you selected, and when the issue occurred, then submit a support ticket. You do not need to include your subscription link or account password.

A connected status confirms the connection state; it does not mean every website is using the intended route. Try visiting several websites to see whether all pages fail or just one service. Then check the client's system proxy or VPN status and whether its rules send the site through the proxy. If all pages fail, try another route and compare with your basic connection while the proxy is paused. If only one site fails, also check its account, region, and service status. When checking DNS settings, start by restoring the configuration recommended by the client. Avoid adding settings from unknown sources and mistaking a DNS issue for a route issue.

Browsers and apps may use different network access methods, so a working browser does not prove that an app is using the same proxy route. First check whether the client sets a system proxy or routes device traffic through a VPN. Then check whether its rules send the app or related domains to a direct connection. Some apps have their own proxy settings; check the app's documentation instead of simply switching routes. After changing settings, fully quit and reopen the app so an existing connection does not keep using the old route. If the client offers split tunneling or traffic-routing options, follow its instructions. If the issue persists, include the app name and error message, but never share the app password or login credentials.

Check whether disconnections happen only after the screen locks, the app goes into the background, or the network changes. Mobile operating systems may restrict background activity and pause the client. In system settings, check the client's background permissions, battery management, and VPN permissions, and allow the background activity the system requires. When switching from Wi-Fi to another connection, the client may need to establish the route again. After bringing it back to the foreground, verify that the connection has actually recovered. Do not rely on the notification icon alone; reopen the page you want to use and test it. If the issue continues, note what triggered it and your operating system and client details, and specify whether it also happens in the foreground or only in the background.

VPNFZ covers 100+ countries / 160+ routes. Start by identifying the region your target service requires, then choose a matching route from the options currently available in your dashboard or client. Hong Kong, Japan, Singapore, the United States, and Italy are examples of regions in the route lineup; the current subscription list shows what's actually available to you. Distance alone does not determine performance: your local network, time of day, and target website can all affect the connection. If you need a route for regular use, first confirm that you can sign in and complete the task you need, then keep the configuration that works for you. The global routes page explains the lineup, but route coverage does not guarantee access to every third-party service.

These terms describe how a route is arranged, not whether a particular website will be accessible. IEPL typically refers to a dedicated link. A relay routes traffic through an intermediate connection point before it reaches the exit, while a direct route uses fewer intermediate relays. Choose based on the target region, your current network, and actual performance—not a presumed speed ranking based on the route name. Route types and locations listed in the client depend on your current subscription, and performance may change with time of day. To compare routes, use the same device, network, and target action, and change only the route. Avoid changing rules or DNS settings at the same time, so other changes don't skew the comparison.

First, distinguish local network congestion from changes in cross-border routes. Pause background downloads, cloud sync, and other network-heavy tasks, then compare another route in the same region without changing your device or target service. If the target service supports other regions, you can try another route, but bear in mind that changing regions may affect your account or available content. Video playback can also be affected by quality settings, content servers, and device performance; try adjusting playback quality to see whether it helps. If routes in different regions are all slow, check your Wi-Fi quality and, if possible, compare it with another basic network connection. If the issue keeps recurring, include the time, route, target action, and comparison results in your support ticket. These details are more useful than simply reporting slow speeds.

A successful connection to a route does not guarantee that a third-party platform will work. AI tools and streaming services may also check account region, payment details, exit network, and service availability; the network connection is only one factor. First confirm that the client's rules send the service through your chosen route, then check whether the platform displays a specific region or account message. For regular use, keep your access environment consistent. Frequently changing regions while troubleshooting can make account messages harder to distinguish from network issues. If a webpage loads but a feature does not work, check the platform's official guidance on account access. VPNFZ route coverage does not grant third-party account permissions or replace a platform's own requirements.

VPNFZ supports Alipay / WeChat Pay / USDT. Use the payment options shown on the order page in your user dashboard. After paying, return to the order page to check its status, then check the account overview to see whether your plan has updated. A redirect from the payment page alone does not confirm that an order is complete. If payment went through but the order status has not changed, keep the order ID and payment receipt, then open a support ticket with the payment method and the message shown on the page. Confirm the original order before taking further action to avoid paying twice. Before sharing a screenshot, hide personal information unrelated to the issue, and never send your payment account password. Do not assume a payment method is supported just because you have used it on another site; check the methods listed by the service.

When you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. Before proceeding, check your current plan status in the account overview, then review the target plan and order details on the plans page. Continue only after confirming the details in the dashboard. Data resets monthly on your activation date. Do not assume an upgrade immediately adds extra data or that data allowances from different tiers simply add together. If you have questions about the prorated amount shown in the order, stop before confirming and send support your current plan, the target plan, and the on-screen message for review. Do not use a self-calculated daily price as the basis for payment, and do not apply monthly plan upgrade rules to data bundles. When the change is complete, confirm your status in the account overview and update your client subscription.

VPNFZ offers a 7-day no-questions-asked refund. To request one, sign in to the user dashboard, open a support ticket, say clearly that you are requesting a refund, and provide the relevant order ID, payment method, and receipt that matches the order. You can include your current plan status to help with verification, but you do not need to explain a technical issue for a no-questions-asked refund. Check the refund policy and terms for the full eligibility rules; do not assume this service follows the rules of another provider. Watch for a reply to your ticket and provide any order details requested. Never send your password or full subscription link as proof. Refund processing time depends on the payment channel; follow the actual outcome and the information in your support ticket.

Submit a support ticket if the issue persists after you check your basic network connection and plan status, update your subscription, and try another route. You can also contact support directly if your payment and order status do not match or if you want to request a refund. For connection issues, include your operating system and client details, route name, time of the issue, exact error message, and steps already tried. Specify whether all websites fail or just one app. Before sharing screenshots, hide account access details and keep only information that helps identify the issue. Do not send your account password, full subscription link, or third-party login credentials. Add follow-up information to the original ticket so support can review it alongside the earlier details.