This VPN beginner’s guide follows the setup process in order: check your account and plan, get the right client, import your subscription, then select a server and test access. A successful order doesn’t mean you’re connected, and a client showing “Connected” doesn’t guarantee your browser traffic is using the proxy as expected.
Keep things simple for your first setup. Don’t run multiple proxy clients at once or import rules from an untrusted source. Check the result after each step so you can tell whether a problem is with your account, configuration, or local network.
Account and order: Confirm your service is active
VPNKQ doesn’t require an email address. Create an account with a username and password, and keep your username somewhere safe. Choose a unique password you don’t use on other sites. If you already have an account, go straight to the user dashboard—there’s no need to create another one.
After choosing a plan and completing payment, return to the dashboard to check your plan status, available data, and subscription link. The payment page confirms the transaction; an active plan in the dashboard is what you need to get your configuration. If your order is still processing, refresh the dashboard and check the order status rather than paying again.
If you contact support about an order issue, provide the order details and error message. Don’t include your password, full subscription link, or sensitive payment details in screenshots shared publicly.
- Sign in to the dashboard and make sure you’re using the same account you used to place the order.
- Check that the order is complete and your plan is active.
- Find the subscription or client configuration section. Don’t share the link in a chat group or public document.
Choosing a plan: Monthly subscription or data package?
If you haven’t chosen a plan yet, start by considering how regularly you’ll use the service. If you use it often and can estimate your monthly needs, compare monthly subscriptions. If your use is intermittent and you want your data to remain available, compare data packages. Data allowances aren’t speed guarantees: they determine how much data you can use, not a server’s real-time performance.
| Billing type | Price and data | How data works | Best for |
|---|---|---|---|
| Monthly subscription | ¥9.9 / 60GB；¥18 / 250GB；¥28 / 500GB | Data resets monthly on your activation date | Regular use; review your needs each month |
| Data package | ¥158 / 300GB；¥358 / 1000GB；¥658 / 3000GB | Never expires; use it until it runs out | Occasional use; keep your data available |
VPNKQ allows unlimited simultaneous devices, but all device activity uses data from the same account. If you upgrade a monthly subscription mid-cycle, the price difference is converted into remaining days; it doesn’t start a new full billing period. Check current pricing on the plans page.
First-plan tip: Choose the billing type that fits your habits, then compare data allowances. VPNKQ offers a 7-day no-questions-asked refund. Even so, test your connection soon after getting started rather than leaving it unused.
Getting a client: Choose the right platform and configuration format
Open the client downloads in the dashboard and follow the instructions for your device. You’ll need to sign in to access the downloads; the dashboard determines which files are available. Don’t download installers from lookalike sites in search results, and don’t assume every proxy client supports the configuration provided in the dashboard.
On Windows and macOS, you may need to enable the system proxy or grant the required permissions to use TUN mode. macOS network extension permissions and Windows administrator approval work differently, so follow the instructions for your client when prompted.
Android and iOS clients typically route traffic through the system VPN configuration. Seeing a VPN indicator means the tunnel or proxy interface is active; it doesn’t prove that a particular site is reachable. On Linux, desktop proxy settings may be separate from command-line settings, so a working browser doesn’t mean terminal tools are using the same configuration.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are proxy protocols, not client names. Your client must support the protocol used by the configuration. They’re listed here to explain compatibility; this doesn’t mean VPNKQ offers every protocol.
Start with the default setup in the guide. Don’t change protocol settings, DNS, and routing all at once. TUN can cover traffic from more apps, but may conflict with other network software. Enable it only if the client’s instructions and your needs call for it.
Importing a subscription: From link to server list
A subscription link retrieves a set of server configurations; it isn’t a regular web page or an account sign-in link. Once a client reads it, it typically creates a profile and server list. A plan subscription in the dashboard is about billing, while a client subscription updates configurations. The names are similar, but they serve different purposes.
- In the dashboard, choose the subscription format that matches your client and copy the full link.
- Open the client’s subscription, configuration, or profile management section, then choose the option to import from a link.
- Give the profile a recognizable name, save it, and update it.
- Check that the server list appears, then set this profile as the active configuration.
If the import shows a profile name but no servers, the update may not have completed. Check whether the link was truncated, has an extra space at the end, or uses a format the client doesn’t support. Don’t remove query parameters from the link when copying it; they may be needed to identify your account or select a format.
If authentication fails, check your account status and whether the link is still valid. For a parsing error, check the configuration format and client version. If the download times out, check whether your current network can reach the subscription address. Don’t paste the link into an unfamiliar online conversion tool to troubleshoot; it may contain credentials that grant access to your account.
Treat the full subscription link like a password. If it’s exposed publicly, check whether the dashboard lets you reset it or contact support. Then update the configuration on each device; deleting the public post alone won’t invalidate the old link.
Servers and routing: Test with rule-based mode first
After importing the configuration, choose a server suited to the region of the service you want to access, then connect. See the servers page for coverage details, but keep in mind that a server’s listed region doesn’t guarantee every website will accept its exit location. The region a site requires, your account settings, and the site’s own policies can all affect access.
Rule-based mode is usually a good place to start: the client uses domain, address, or other rules to decide whether traffic connects directly or goes through the proxy. Global mode routes as much traffic within the client’s scope as possible through the selected proxy; it doesn’t necessarily cover every app on your device. The actual scope depends on system proxy settings, TUN, system permissions, and app behavior.
If a site won’t open, briefly switching to global mode can help determine whether a rule failed to match. If global mode works but rule-based mode doesn’t, check the rules and DNS before assuming the server is at fault. When you’ve finished testing, switch back to the mode that suits everyday use to reduce disruption to local services.
IEPL, relay, and direct connection describe how a route is structured. A relay forwards traffic through an intermediary server; a direct connection typically skips an extra relay set up by the provider. IEPL uses a dedicated Ethernet link, but that doesn’t mean the entire route is dedicated. A route label can’t replace real-world testing or prove that a server will remain stable.
Checking your connection: Test websites, exit IP, and DNS separately
After connecting, open a site you actually need and check that its pages, images, and sign-in flow work. Then review the client’s connection logs. Rule-match details are more useful for diagnosing issues than a “Connected” icon. When switching servers, leave other settings unchanged so you can make a meaningful comparison.
- ✅ The target site loads its main content, rather than showing only a cached page or blank frame.
- ✅ Check your browser’s current exit IP with My IP, and confirm whether the request should be routed through the proxy according to your rules.
- ✅ Check that the apps you need can connect too—not just your browser.
- ✅ After disconnecting, make sure your local network still works and that no inactive system proxy settings have been left behind.
In rule-based mode, different requests may use different exit routes. If the IP lookup request is set to connect directly, seeing your local IP doesn’t necessarily mean the proxy has failed. To verify the exit IP, make sure the lookup request actually goes through the selected server. IP geolocation databases can also be inaccurate.
DNS translates domain names into addresses. A DNS leak generally means lookup requests are taking an unintended local or external route; a website loading successfully doesn’t rule one out. Encrypted DNS in your browser, system DNS, and the client’s DNS settings can affect one another. Check the client’s documentation and DNS test results together.
If you find a DNS issue, don’t disable every security feature or enter a random DNS address. First check whether the client’s recommended DNS settings are active, whether your browser uses encrypted DNS separately, and whether your rules send DNS traffic along the intended route. An IP lookup checks your exit IP; it doesn’t test DNS.
Common issues: Troubleshoot based on where things fail
No server list? Start with the subscription. Servers listed but no connection? Check client compatibility and your network. Connected but an app still can’t access sites? Check which traffic the proxy is handling. Pinpoint the step that failed and adjust the relevant setting; it’s usually more effective than repeatedly reinstalling the client.
| What you see | Check first | What to try next |
|---|---|---|
| Subscription update fails | Account status, link integrity, configuration format | Copy the matching format again from the dashboard and save the error message |
| No server can connect | Network connection, client support, other proxy software | Close conflicting clients, test another network, and avoid changing several settings at once |
| Browser works, but apps don’t | Whether the app follows the system proxy and whether a rule matches | Check the guide to see whether you need TUN or app-specific settings |
| Local services stop working after connecting | Routing rules, DNS, and whether global mode is enabled | Switch back to rule-based mode and check that local addresses connect directly |
If the issue persists, note your operating system, client name, mode, error text, and when it occurred. Then consult the troubleshooting guide or send a report through the dashboard. Hide the full subscription link in screenshots, and never share your password. Clearly explain which step failed so support has enough information to investigate.
Everyday use: Keep a working setup and verify it when needed
After your first successful test, note your configuration, server, and mode. If something goes wrong after a client upgrade or subscription update, compare it with your original setup. Don’t import a pile of unfamiliar rules just to make your configuration more complex, and don’t let multiple clients on the same device compete for the system proxy or VPN interface.
Video, downloads, and background sync all use data, so check your usage in the dashboard. VPNKQ’s privacy policy is “no logs”; this is a service policy, not a guarantee that websites, your operating system, or local client won’t retain their own data. Handle client diagnostic logs with care.
Your first setup is complete when: your plan is active in the dashboard, the subscription has updated successfully, the apps you need can connect, and you know how to disconnect and restore your local network. When setting up another device, follow the import and testing steps in the Guides again. Don’t assume a setup that worked once will behave the same on every platform.