Subscription & Connection Help

No email address is required to create an account—just a username and password. Save your login details in a trusted password manager, and make sure you also save the VPNRQ user panel address. If you forget your details, first check your browser’s saved credentials and make sure you’re not confusing a username error with a password error. If you’re still signed in on another device, open the user panel there to find account options. If you need help, contact support with verifiable order information and let them know whether you can still sign in. Never share your password in a public forum or submit your full subscription link as an account identifier. Account recovery is subject to support verification.

Sign in to the user panel and find the subscription options in your account overview. Then import the configuration using the method provided by your client. To sync an existing configuration, open the client’s subscription or configuration manager, select the relevant entry and update it. Once the update finishes, check the region list and select a route again. Repeatedly clicking Connect won’t update your subscription. If the panel shows updated subscription details but the client still has the old list, import the configuration from the panel again and remove the old entry only after confirming the new one works. Your subscription link is sensitive account information. Keep it on your own devices and obscure the full address in screenshots and support tickets.

VPNRQ allows an unlimited number of devices to be online at the same time, so switching devices doesn’t require a new plan. Supported platforms include Windows / macOS / iOS / Android / Linux. On your new device, open the client section of the user panel and follow the instructions for your platform to install the client, authorize it and import your subscription. When using multiple devices, keep an eye on your account’s data allowance; each device does not get a separate allowance. When you stop using an old device, remove its local subscription configuration and sign out of the panel, especially before handing it over or selling it. If the new device shows a device-limit warning, check which client or account is displaying it, then contact support with a screenshot that hides sensitive information. Don’t make another payment to resolve the warning.

Sign in to the user panel and check your plan and data status first. Then make sure the client can reach the subscription update endpoint. When copying the link, include the full address and avoid extra spaces, line breaks or punctuation added by chat apps. Also confirm that you’re editing the VPNRQ configuration, not another subscription entry. Next, check your local connection and see whether the client reports a download failure, invalid format or configuration parsing error. These messages point to different stages, so don’t delete all your configurations straight away. Keep the original configuration and import the panel’s version for comparison. If the update still fails, send the error text and your operating system and client details, but hide any account credentials in the link.

Temporarily disconnect the proxy and check that your local connection can open everyday websites. If your local connection isn’t working, resolve that first. Then sign in to the user panel to check your plan and data status, update the client subscription, and compare a different region or route type. If no routes work, check that the operating system has granted the client the network permissions it needs and that no other proxy, network filter or security software is running at the same time. Change only one setting at a time and note the results before and after each change. That way, you can identify the cause without changing rules, network settings and routes all at once. If you still can’t connect, keep the exact error message and use the troubleshooting guide to organize the details before submitting a support ticket.

A connected status only tells you that the connection state changed; it doesn’t confirm that the site you want to visit is reachable. Try opening an everyday website and the international site you’re having trouble with. Check whether neither site loads or only the target site is affected. Then check whether your browser has its own proxy settings, whether the system proxy is active, and whether the client’s current rules include the target domain. If you see a domain resolution error, check your DNS settings and look for conflicts with other network tools instead of repeatedly switching accounts. After changing settings, reopen the target page and, if needed, restart the app to establish a fresh connection. When reporting the issue, include the website domain and full error message, but don’t send a page address that contains login credentials.

Some apps use their own network settings and may not follow the system proxy. Others connect to several domains, while your current routing rules may cover only some of them. First, check the client’s connection log to see whether requests from the app appear, then check which route the rules select. If your client supports it, briefly switch to global proxy mode for comparison, or follow the client’s instructions to check system-level network routing. Restore your usual app routing settings when you’re done testing. Don’t disable unfamiliar security warnings as part of troubleshooting. If only a specific feature fails, describe what you were doing and the exact error, and say whether the browser works. This can help distinguish app routing rules from account restrictions or an issue with the target service.

First, check whether the disconnections happen when the screen locks, the network changes or the device goes to sleep. If they occur only in the background, review the system’s background activity and battery settings for the client, and keep the network permissions it needs enabled as recommended for your platform. If it disconnects in the foreground too, compare other routes and your current network. After switching between Wi-Fi and a mobile network, you may need to reconnect. Test the target app again instead of relying only on the client’s connection toggle. Also check whether another network tool is taking over the system proxy settings. If the problem continues, note when it happens, which route you’re using and what the client reports. Don’t just report that it won’t connect; see the troubleshooting guide for a step-by-step diagnosis.

These terms describe how routes are set up, but the name alone won’t tell you how a route will perform. An IEPL route may be worth trying when a stable connection is important. A relay route uses an intermediate node, while a direct route can be compared against your local network conditions. The best choice depends on the configurations available in your client, the target service’s region and how your current network performs. Keep the target app constant and compare whether each route completes the same task, then save the option that works best. Meetings, file transfers and web browsing have different requirements, so there’s no need to route every request the same way. The route list shows available regions and types; test a route with your intended task to see whether it suits your needs.

First check whether the slowdown affects only the target app. Pause data-heavy tasks on other devices and make sure your local Wi-Fi connection is stable. If everyday websites are slow too, troubleshoot your local network first. If only international access is slow, keep the target service the same and compare other routes in the current region. Then try a different route type or a region suited to that service. This makes it easier to compare results. Avoid switching regions, rules and clients repeatedly at the same time, or it’ll be hard to identify the cause. For streaming, check playback buffering; for meetings, check whether audio and video stay continuous. When contacting support, include when the slowdown occurred, your network and the routes you tested. An occasional slowdown doesn’t necessarily mean there’s a problem with your plan.

VPNRQ covers 100+ countries and 190+ routes. The options available to you are those shown in the user panel and synced to your client. Japan, the United States, Hong Kong, Singapore and Germany are examples of regions in the route list, but a closer location isn’t necessarily better for every use case. Your experience depends on the target service’s region, your local network and the route taken. For region-specific content, check the platform’s regional rules too. Start by identifying what you need to do, then compare whether routes in relevant regions work for that task. Don’t choose based on the region name alone. The static list on the routes page describes coverage; it doesn’t guarantee that every route will work with every service at all times.

You can start by testing both on the same route, but it’s usually better to set routing separately for each app. For AI tools, check that you can sign in, submit requests and receive responses consistently. Streaming also depends on content availability by region, your platform account and playback requirements. Being able to open a site doesn’t mean every feature has been tested. First check which regions the target service allows, route the relevant requests accordingly, then reopen the app to verify the result. Switching your exit route frequently may trigger additional checks from the platform, so try to keep your setup consistent. VPNRQ provides international routes and quantum encryption-related services. The target platform still determines account eligibility, subscription content and regional policies; a connected route does not override those requirements.

Monthly plans are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on your activation date. Mid-cycle upgrades are prorated based on the remaining days. Choose a plan based on how you use it: everyday browsing, file transfers and extended streaming consume different amounts of data, so the number of connected devices alone won’t tell you which tier you need. Check your current plan and data usage in the panel before deciding whether to switch. Resets are based on your activation date, not the first day of the calendar month. If you have questions about your data or plan status, send the details shown in the panel along with the relevant order information. You can also check the Packages page for current pricing and billing details.

Data packages are ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They last until the data is used up and never expire. Monthly plans are billed monthly, with data resetting each month on your activation date. Choose based on how regularly you use the service, not on unconfirmed price comparisons or promotional claims. If your usage varies, consider how a data package works; for ongoing use, compare your needs with the monthly plan tiers. A data package does not renew with the same allowance every month. If you already have a plan and want to switch billing types, check your orders and plan details in the panel first. For how existing configurations or orders are handled, rely on what the panel shows or confirm with support—don’t assume that plans or allowances stack.

We accept Alipay / WeChat Pay / USDT. Choose a plan in the user panel and open the payment page for the relevant order. Check the order total and payment method before proceeding. If the page doesn’t update after you’ve paid, return to the order list and check the original order. Don’t create another order or pay again right away. Also check whether the payment page still asks you to complete any steps. If the status remains incorrect, open a support ticket with the order ID, plan, payment method and a receipt with sensitive details obscured. Never share your payment password or post complete payment details publicly. Keep the original order record until support has reviewed it; this helps distinguish an incomplete payment from a status sync issue or an order mismatch.

VPNRQ offers a 14-day no-questions-asked refund. To request one, sign in to the user panel and open a support ticket. Say that you’re requesting a refund and include the relevant order ID so support can locate the transaction. Check the Terms of Service for the full refund scope and rules. If you’re also having connection issues, include the client’s error message and the troubleshooting steps you’ve tried. You don’t need to share your full subscription link, password or other credentials to explain your request. Check for replies in the original ticket and add any follow-up information there rather than opening multiple tickets. Refund progress and handling details will be provided in the ticket. This page doesn’t promise a processing time or payment-method rules that aren’t listed.