Help Center

No email address is required. Create an account with a username and password. Save your login details after creating your account, and store your account password separately from your subscription link. The subscription link gives your client access to route configurations; it cannot be used in place of your account password. If you forget your password, first check your password manager and any login details saved in your browser. If you’re still signed in on another device, check the user panel for account settings, then contact support through a ticket. Since accounts don’t require an email address, don’t assume you can reset your password by email. Follow the user panel’s instructions and any guidance from support. Never share your password or full subscription link in a public discussion.

Sign in to the user panel and find your subscription details in the account overview. Choose an import method for your client; the user panel’s login page URL is not a subscription link. To update an imported configuration, select the relevant entry in your client’s subscription or configuration settings and run the update. Then check that your route list appears as expected. If only the route configuration has changed, you can usually keep the existing subscription entry rather than creating a new one. If the link in the user panel has been reset, stop using the old link and import or replace it with the current one shown in the panel. Menu names vary by client, so follow the options in your current interface.

There’s no device limit, so changing devices alone doesn’t mean you need a different plan. VPNRV supports Windows / macOS / iOS / Android / Linux. Sign in to the user panel, open the client downloads page, then install the client and import your subscription for your platform. Once the subscription is imported on your new device, select a route and check that access works. You don’t need to delete the configuration on your old device before moving. An unlimited number of devices doesn’t mean unlimited data, so keep an eye on your plan’s data allowance and subscription status. Keep subscription configurations secure on all your devices; don’t share files containing credentials through public cloud storage or group chats.

If you think your subscription link has been exposed, sign in to the user panel and look for an option to reset it. If you can’t find one, request help through a support ticket. Deleting the configuration from your device alone doesn’t invalidate the link. After resetting it, update your frequently used devices to the current link and fetch the routes again. If an update is failing, first check your subscription status and data balance. Then make sure the link was copied in full, contains no extra spaces, and uses an import format supported by your client. Retry over a working local network and keep the error message for troubleshooting. Before sharing a screenshot, hide the full link and any credentials it contains. Public screenshots are not a secure substitute for a support ticket.

Disconnect the client first and check whether your local network can reach commonly used websites. This helps determine whether the problem started before the connection. If your basic network access works, return to the client and check that the current configuration is enabled, the selected route is available, and any required system network permissions have been granted. Try another route, then test with both a browser and the affected app. If only one app fails, check its proxy and app settings. If nothing loads, note the client’s error message, update the subscription, and try again. Avoid running multiple tools that take over the system proxy or create network tunnels at the same time; overlapping settings can make the connection status differ from the actual traffic path.

A working browser connection doesn’t mean every app uses the same network path. Some apps follow the system proxy, while others use their own connection method. Client routing rules may also send the app’s domains through a different path. First, make sure the client is in the intended mode, then check whether the app has its own proxy settings or network permissions. After changing rules, fully quit and reopen the app so it doesn’t keep using an old connection. If your client offers system-wide network routing, you can use it to compare results after reviewing the permissions prompt, but don’t blindly override existing work network settings. If the issue persists, include the app name, platform, and specific step that fails in your support ticket instead of simply saying it doesn’t work.

After your device sleeps, you switch from Wi-Fi to another network, or your network address changes, the existing connection may no longer work. First, confirm the new network has internet access, then disconnect and reconnect to the current route in your client. If the route list also won’t update, check whether another network tool’s proxy settings are still enabled on your system. On mobile devices, check whether the system is restricting the client’s background activity and adjust any required permissions as prompted. Once connected again, reopen the app so it can establish a new connection instead of waiting for an old request to finish. If the problem keeps recurring, note whether it happens after waking from sleep or switching networks, and whether it occurs only on the current network or on others too.

Sign in to the user panel and open the support ticket page. Include your platform, client name, selected route, current network, and the step where the problem occurs. Describe connection failures, subscription update failures, and access denied by the target service separately. Include the original error message or a screenshot with sensitive details hidden. If you’ve tried switching routes, updating the subscription, or changing networks, share the results of each attempt; that’s more useful for diagnosing the issue than simply saying the connection is slow. You can include client log excerpts as long as they contain no sensitive information. Check them before sending, and hide passwords, full subscription links, and other access credentials. Don’t post account details publicly to demonstrate the issue. Keep any follow-up information in the same ticket.

First identify what’s affected, then make targeted changes. Pause heavy transfers on your device, check whether only the target service is slow, and compare with other apps. Next, try another route to the same destination region and see whether performance improves. Consider a different protocol or operating mode supported by your client only if similar issues occur across multiple routes. Changing several settings at once makes it harder to identify the cause. Direct, relayed, and IEPL routes use different paths, but their names don’t guarantee the same performance on every local network. Peak-hour congestion can also occur on your local connection or at the target service. Keep a note of when the issue occurred and what changed after switching routes to help with further troubleshooting.

Direct, relayed, and IEPL describe route paths and how traffic is carried, not a universal speed ranking. A direct route takes a more straightforward path, though the experience still depends on your local carrier and the destination network. A relayed route uses an intermediate node. An IEPL route carries the relevant links over a dedicated line, but the target service and your local connection still affect the result. Start by choosing the destination region you need, then compare route types using the same app. Focus on whether the connection stays up and requests complete successfully, not just on the route name. For long-lived connections or continuous playback, keeping a working route is often more useful than switching frequently. For details on network paths, see the protocol guide.

VPNRV covers 90+ countries / 250+ routes. The routes currently available are listed in the user panel and in your client after it updates. Choose a region that meets the target service’s requirements, then compare how it performs on your current network. Distance is only one factor: routes may use different relays and network interconnections, so a nearby region isn’t always faster, and a farther one may still work well. Don’t assume differences between regions mean the client is faulty. For everyday work, keep a region you’ve verified works. For services with regional requirements, switch regions as needed and reconnect the app afterward.

A connected route means the connection was established; it doesn’t mean the target service’s account, region, and content requirements have all been met. AI tools and streaming services may also check the account’s region, session status, content licensing, or their own risk controls. Check the service’s officially supported regions, make sure your selected exit region meets your needs, then sign out of the old session and reopen the app after switching routes. If other websites work, keep the target service’s original error message rather than repeatedly reinstalling the client. VPNRV’s regional coverage doesn’t replace eligibility requirements set by third-party services, and not every route is guaranteed to work with every platform. If you run into an issue, include the service name and the circumstances in a support ticket.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on your activation date, not at the start of each calendar month. Check your account status in the user panel. Choose a plan based on your main use and expected data consumption; having no device limit doesn’t change the plan’s data allowance. Mid-term upgrades are prorated against the remaining days. Check the settlement details in the user panel before proceeding; an upgrade doesn’t mean every part of your plan starts over. If your displayed data doesn’t match your expectations, check your current plan, activation details, and usage records, then explain the difference in a support ticket. Avoid repeating actions that could make the details harder to reconcile.

Data packages cost ¥158 for 300GB, ¥358 for 1000GB, and ¥658 for 3000GB. They last until used and never expire. Monthly subscription data resets each month on the activation date. If you use the service regularly and prefer a monthly budget, compare the monthly plans. If your usage is irregular and you want to keep data for as long as needed, consider a data package. Never expires refers to the data package’s validity period; it doesn’t mean data is replenished automatically or that you can use more than the amount you selected. Before changing billing methods or handling an existing subscription, review the billing and activation details in the user panel. Don’t assume monthly subscriptions and data packages will combine, stack, or be deducted in a particular order.

Alipay / WeChat Pay / USDT are supported. Start the payment process from the order page in the user panel, and check the order details and on-screen instructions before proceeding. If your status hasn’t updated after payment, return to the order list and refresh it, then check whether the payment has completed. If the page hasn’t changed yet, don’t immediately create or pay for another order for the same request. If the payment result and panel status continue to differ, submit a support ticket with the order details, payment method, and a redacted payment receipt so support can check. Don’t share account details from a payment receipt publicly, and don’t act on payment addresses sent in unsolicited messages. Follow the process shown in the user panel.

VPNRV offers a 30-day no-questions-asked refund. To request one, sign in to the user panel, open the support ticket page, clearly state that you’re requesting a refund, and include the order details that need to be checked. Before submitting, review the refund terms in the Terms of Service to confirm the applicable conditions. If you’re also experiencing connection issues, you can describe them for review, but troubleshooting a problem doesn’t count as submitting a refund request. The ticket response will confirm the refund outcome and next steps. This page doesn’t promise a processing time, and payment methods may have different procedures. Keep your order and support records, and add any follow-up information to the original ticket to avoid splitting up the details.