Subscription and Connection FAQs

No email address is required. Create an account with a username and password. Save your login details before you start, and use a unique password for VPNLQ rather than reusing one from another site. Anonymous, no-logs operation is part of this service’s privacy policy; it does not mean account credentials can be shared or that access can always be restored automatically if they are lost. For support, submit a ticket through the user panel. Before sharing a screenshot, hide your password, subscription link and any other access credentials. For your first setup, follow the quick-start guide. Sign in and retrieve your subscription from the user panel.

Your subscription link lets the client retrieve route configurations; it is not a fixed address for a particular route. Get your subscription from Account Overview in the user panel, then update or refresh the existing subscription in your client and check that the route list has loaded. If the original link still works, updating the existing configuration is usually enough; there is no need to add the same subscription again. If the link in the panel has changed, use the current link shown there: replace the old one, then update. Menu labels vary by client. If an update fails, check that your basic internet connection is working, the entire link was copied, and your plan is active with data remaining.

VPNLQ supports unlimited devices and works with Windows / macOS / iOS / Android / Linux. Changing devices does not require another plan. Sign in to the user panel on your new device, get the compatible client and current subscription, then import it. Device limits and data allowances are separate: unlimited devices does not mean unlimited data, and usage across multiple devices is still subject to your plan’s data allowance. If you no longer use an old device, remove its local subscription configuration to avoid unnecessary connections. When sharing across a household, keep in mind that automatic updates, cloud sync and background downloads on each device can affect data use; device count alone is not a reliable estimate.

Your subscription link is an account access credential. Anyone who has it may be able to retrieve the associated route configurations, so do not post it in public chats, forums, shared documents or screenshots that have not been redacted. Unlimited devices is a device-use policy, not permission to distribute your subscription publicly. If the link is exposed, stop sharing it and check whether the user panel offers an option to reset or replace the subscription credentials. If you cannot find the option, ask for help through a ticket rather than guessing at link parameters. After changing the credentials, update the configuration on devices you still use and remove the old subscription. Deleting a public post does not retrieve copies that others may have saved.

First, check that your device can access the internet with the proxy disabled. Then sign in to the user panel and check your plan status and remaining data. Copy the complete subscription link—not the user panel URL in your browser’s address bar—and do not paste it into the client together with explanatory text. After importing, check the client’s update result to determine whether the link could not be retrieved, the configuration could not be parsed, or no route has been selected. If you see a parsing error, use the import method recommended in the panel; do not edit configuration fields you do not recognize. If the routes still will not load, note the client’s error message and your platform, then submit a ticket with a screenshot that hides your credentials.

Browsers and other apps may use different network paths. Some apps follow the system proxy, while others use their own network settings or are affected by the client’s routing rules. First, check in the client whether requests from the app are routed through the selected route, then check the app’s own proxy settings. If the client offers a virtual network adapter or a similar traffic-capture mode, consult its documentation for compatibility and permission requirements. Avoid running multiple traffic-capture tools that could conflict. To narrow down the cause, you can briefly compare results with different routing modes. When troubleshooting is done, restore the settings that suit your everyday use rather than routing every local service through the proxy.

Pause downloads and sync tasks that use bandwidth, then check whether your local connection is stable. If basic websites are also unreachable, start by checking your device’s network, router connection or current access environment. If the internet works normally but the selected route keeps reconnecting, try another route for comparison and note whether the issue occurs only in a particular region or route type. Avoid changing the protocol, routing rules and traffic-capture settings all at once, or it will be hard to tell which change mattered. After reconnecting, open the app you were trying to use; a connected status in the client alone does not confirm that the issue is resolved. If the problem continues, describe how to reproduce it in a support ticket.

Open a ticket from the user panel and include your platform, client name, selected route, when the issue occurred, and whether the failure involved updating the subscription, connecting or accessing a particular app. Mention any recent network or configuration changes and the checks you have already tried—for example, whether switching routes helped and whether your basic internet connection is working. Error messages and redacted screenshots can help identify the cause, but do not send your password, full subscription link or configuration files containing access credentials. Hide account details and link parameters in logs before sharing them. Keep troubleshooting updates in the same ticket so the issue and its history stay together.

VPNLQ offers three route types: IEPL dedicated lines, relay routes and direct connections. To understand the differences, distinguish the access path from the final exit: IEPL dedicated lines use a dedicated transmission path, relay routes forward traffic through an intermediate access node, and direct connections connect to the relevant server directly. Route labels can help you narrow down your options, but they do not guarantee a particular speed across every access network, app or time of day. First check which exit region the service you want to use requires, then compare performance on the same device and app. For more on balancing cost and performance, see our service selection guide. Do not judge whether a route suits your network by its name or the number of available servers alone.

First check whether downloads, backups or other devices are using a lot of bandwidth on your local network. Then see whether the slowdown affects all websites or only the app you want to use. If the service requires a specific region, try a different route within that region first; switching exit regions may introduce new regional restrictions. If no particular region is required, compare routes in other regions and route types. Keep your device and app settings the same, and compare page loading, sustained playback or session stability—not just whether a connection succeeds. Peak-hour performance depends on your local connection, the transmission path and the destination service. Route type alone cannot predict the result, and one successful test is not a guarantee of consistent performance.

Access to streaming and AI tools depends on the exit region, platform rules, account eligibility and service status. VPNLQ’s route coverage does not mean every route works with every service. Check the platform’s regional requirements, choose a suitable exit and test with your own account. If you see a region notice or an access denial, distinguish a network connection problem from an account restriction; switching routes will not solve every issue. Video quality also depends on your platform plan, device and sustained network performance. If an AI website works, that does not necessarily mean API calls will work too. See our Streaming page and related articles for specific use cases.

VPNLQ covers 110+ countries with 170+ routes. See the global server page for regions and route types; use the configuration most recently updated in your client. Coverage gives you a choice of exit routes; it is not a speed guarantee for any individual route, and it does not tell you how many routes are available in a particular region. Choose based on the region required by your app, your local connection and actual performance rather than trying every route. If an app requires a consistent sign-in region, choose a suitable exit and avoid unnecessary region changes. Route selection and app account rules are separate: coverage across multiple regions does not change a platform’s regional requirements.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets monthly on the date your plan starts. This is based on your start date, not the beginning of the calendar month for every account. When choosing a plan, consider your actual usage, including web browsing, extended video streaming, downloads and background activity across multiple devices. There is no need to choose based on device count alone. Before paying, verify your selection on the plans page and in the user panel. After activation, check your plan status, data balance and relevant dates in the panel. Unlimited devices is a device policy; your monthly plan’s data allowance still applies.

Data packages are ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They last until the data is used and never expire. Monthly plans reset data each month on the plan’s start date. The main difference is how long you have to use the data, not a different device limit or route coverage promise. If you use the service regularly and want a recurring data allowance, compare the monthly plans against your actual needs. If you use it less often and want to draw on your remaining data when needed, consider a data package. Never expiring describes the package’s validity; your remaining data still decreases as you use it. Check the billing method and data amount before choosing so you do not mistake a package for a monthly allowance that renews automatically.

When you upgrade a monthly plan partway through, the price difference is converted into remaining days. Before upgrading, check your current plan, target tier and order details in the user panel, and review the updated information before proceeding. Do not calculate the price difference as extra data or assume the original dates and allowance arrangements will all remain unchanged after the upgrade. The panel shows the current status for each account; the help center cannot estimate amounts without the order details. If the order information does not match your expectations, pause and contact support through a ticket with your current tier and the one you want to switch to. Hide access credentials from any supporting material. After the change, check your plan details in the panel and update your client subscription.

VPNLQ supports Alipay / WeChat Pay / USDT. Before paying, confirm the account you are signed into, your selected plan and the billing method. After payment, return to the user panel to check your order and plan status. If the payment provider shows the payment as complete but the panel has not updated, do not pay again just because the page has not changed. Check the original order, refresh the panel and make sure you have not switched to another account. If the details still do not match, submit a ticket with your order information and a redacted payment receipt, and describe the payment method and message shown. Receipts help verify the order; screenshots should not include your password or full subscription link. Check both the order and plan status in the panel to confirm activation.

VPNLQ offers a 30-day no-questions-asked refund policy. See the refund policy for eligibility and full terms. To request a refund, open a ticket from the user panel and provide the relevant order details so the account and payment can be verified. You do not need to complete a full round of troubleshooting before requesting a refund. If you also want help with a connection issue, describe your platform and the problem separately. Keep your order and support correspondence. Redact payment receipts to hide information that is not needed for verification; passwords and subscription links are not required. Track progress through your ticket. The help center does not promise a separate processing time, and uninstalling the client does not count as submitting a refund request.