How do you use a VPN? After placing your order, confirm that your plan is active, get your subscription or account configuration, install the right client, import a route, and connect. Then check whether the app you want to use is going through the selected exit. Completing payment does not connect a device, and a successful connection message does not mean every app is using the proxy.
This guide follows the steps a first-time user will typically take and explains what to expect at each stage. Menu names vary by client, so follow the download instructions and guides in your VPNDV user panel. If something goes wrong, identify the step where you got stuck before changing settings. Adjusting the route, proxy mode, and DNS all at once makes it harder to find the cause.
Confirm your plan and account after purchase
Open the user panel to check your current plan, available data, and order status. If the payment page says your payment is complete but the panel has not updated, refresh the page and check the order. Do not pay again just to confirm the status. For Alipay, WeChat Pay, or USDT, verify the result using the payment steps shown in the panel.
VPNDV does not require an email address. Create an account with a username and password. Keep your account credentials separate from your client configuration: your password is for signing in to the panel, while the subscription link retrieves routes. They are not interchangeable. If the download instructions tell you to sign in to the client, follow those steps; there is no need to look for a separate subscription link.
Monthly plans reset data on the day you activated them, not at the start of each calendar month. If you upgrade partway through a billing period, the price difference is prorated for the remaining days. Data packages last until used and do not expire. Before troubleshooting data usage, check which billing option you purchased.
You can request a full refund for any reason within 30 days of your first payment. For help with an order or account, submit a ticket through the panel. Do not post payment details or account configuration in a public discussion.
Get your subscription link and protect your configuration
A subscription link is usually how a client retrieves its configuration. It may return route addresses, connection parameters, and routing information; it is not necessarily a webpage you can read in a browser. Use the option currently available in the panel. If you see choices such as Copy subscription, Import, or Download configuration, choose the one that matches your client.
Copy the full address and make sure it has no extra spaces, line breaks, or punctuation added by a chat app. Do not mistake the regular website URL for a subscription link, or a short link title for the complete configuration. If the client reports an unsupported format, first check what you copied and which import option you used instead of assuming the route is down.
A subscription may contain account-related access credentials. Do not share it for someone else to test, upload it to an unfamiliar online converter, or include it in a public screenshot. If you think the link has been exposed, check whether the panel offers a reset option. If there is no clear option, contact support. After a reset, you may need to update the link in your client.
Subscription updates and software updates are different. Updating a subscription retrieves the service configuration again; updating software installs a newer client version. The former cannot add protocol support that an older client lacks, and the latter cannot fix an expired account configuration.
Install a compatible client for your device
Check the user panel download page for installation instructions for Windows, macOS, iOS, Android, and Linux. Do not download software just because its name looks familiar, and avoid installers from unknown mirrors. Before installing, check your operating system, device architecture, and any compatibility requirements listed in the panel.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are common proxy protocols or protocol families, not different names for the same configuration format. Whether a client can import and connect depends on its core, version, and the parameters provided by the server. These names are included to explain compatibility; their mention does not mean VPNDV supports each protocol.
| Platform | First-install checks | What to verify after connecting |
|---|---|---|
| Windows | Check the download source and system proxy settings | Whether the target app follows the system proxy |
| macOS | Follow the guide to review system permissions and network extension prompts | Whether the proxy or tunnel is actually enabled |
| iOS | Install the client as directed and allow the required VPN configuration | Whether the selected configuration is connected |
| Android | Check VPN permissions and background restrictions | Whether app exclusions or per-app routing are enabled |
| Linux | Check the architecture, dependencies, and how the client runs | Whether terminal and desktop apps use the same proxy configuration |
On mobile, VPN permission is typically used to create a local tunnel interface; it does not mean the client necessarily uses a traditional VPN protocol. Desktop clients may rely on the system proxy or a virtual network adapter to handle traffic. When a permission prompt appears, check that the app is from a trusted source and that the prompt matches the guide. Do not assume setup steps are the same across platforms.
Import the configuration and check that routes appear
Open the client and choose the appropriate import method from its subscription, configuration, or profile settings. Paste the link, save it, and then update or download the configuration. If the panel offers one-click import, your browser may ask to open the client. Confirm that it is the right app before proceeding. Some clients also require you to set the imported configuration as the active one.
- Confirm that the configuration comes from your user panel and that its format matches your client.
- Save the configuration, update the subscription, and check for any error messages.
- Check that routes appear in the list, their names look right, and the intended configuration is selected.
- Choose an exit route, then open the proxy mode or connection settings. Do not stop at the “Import complete” screen.
You should see a list of available routes and be able to select the configuration you want to use. If the list is empty, check your account status, the full link, and format compatibility. If the update cannot connect, check whether your local network can reach the configuration URL. Existing proxy settings can also affect subscription downloads, so consult your client's instructions for the network path used during updates.
If you see a certificate or security verification error, do not disable checks just to continue. Note the error message, check your device's time and software version, and report the issue to support. You need a valid configuration before it makes sense to troubleshoot route selection or connection.
Choose an exit route and routing mode
For your first connection, choose a route in a region that meets the target website's requirements. A nearby location does not necessarily mean a shorter network path, and a region in the route name is no substitute for testing access. VPNDV covers 120+ countries with 230+ routes. Choose based on the current list in your panel and the requirements of the service you want to use, not just the route name.
Direct connection usually means your device connects straight to an overseas entry point. A relay adds a forwarding node to the path. IEPL refers to a dedicated carrier-provided link. These terms describe different ways of organizing network traffic, not guaranteed app access. Even a route labeled as dedicated may be affected by your local connection, exit load, or the destination server. These are definitions, not guarantees about every route's configuration.
Rule mode uses domain, address, or app rules to decide which traffic goes through the proxy. It can be useful when you need both local services and international access. Global mode uses the proxy for traffic handled by the client, but that does not mean every app on your device is covered. Direct mode generally sends traffic without the proxy, so make sure you do not select it by mistake when testing your first connection.
The system proxy mainly affects apps that follow the system settings. TUN or a similar virtual network adapter can handle more traffic, but may require extra permissions and can conflict with routes set up by other network tools. For your first setup, use the mode recommended in the guide. Consider another method only if you have confirmed that the target app does not follow the system proxy.
Verify access and check the DNS path after connecting
Once connected, check that the client shows no errors. Then open the network check page to see the browser's exit address and detected region, and test the app you actually want to use. The check page shows the exit used by the current browser request, not by every background process, and it cannot by itself confirm that streaming content is available.
- ✅ The intended configuration and route are selected, and the client shows no connection errors.
- ✅ Requests from the browser that should use the proxy show the expected exit; use the detected region as a secondary check.
- ✅ The target website opens, and you can sign in, load content, and use the service.
- ✅ Local websites you commonly use still work, and routing behaves as expected.
- ❌ Do not assume the entire connection is working just because a route latency test gets a response.
DNS translates domain names into addresses. A DNS leak generally means that requests expected to go through the intended tunnel are instead using the local network path. Assess this in context, including the client's DNS settings, traffic-handling mode, and test method. Seeing the name of a particular DNS resolver does not by itself prove there is a leak.
Browser encrypted DNS settings, system caches, and client resolution rules can all affect the results. If a site will not open but other requests work, check the logs to see whether the issue is a failed lookup, a failed connection, or traffic taking the wrong route. Do not enter unfamiliar DNS addresses or treat “change DNS” as a universal fix for connection problems.
Streaming and AI tools can also be affected by account region, content licensing, and platform risk controls. Changing your exit location and making a service available are separate outcomes. For help understanding how a region is determined, see the complete access troubleshooting guide. Do not substitute repeated sign-ins or rapid route changes for troubleshooting.
Narrow down the issue based on what you observe
If no routes connect, test your local network first, then check whether the configuration is valid, the client is compatible, and your account is active. If only one route fails, keep the client and mode unchanged and test another route suitable for the target region. Change one thing at a time so you can tell what made a difference.
If the client says it is connected but the browser's exit has not changed, check the system proxy toggle, current rules, and other network tools. If the browser works but one app does not, check whether that app follows the system proxy, is excluded, or is subject to restrictions on the service's end. Different symptoms point to different layers; do not assume every issue is caused by low bandwidth.
If a mobile device disconnects when its screen locks, check whether the system restricts the client from running in the background. If a desktop device has issues after waking from sleep, reconnect and check for changes to its network interfaces. VPNDV has no device limit, but that does not eliminate differences in permissions, background policies, or local networks, nor does it guarantee the performance of an individual route.
When submitting a support ticket, include your device's operating system, client name and version, selected route, when the issue occurred, and the full error message. Hide subscription links, account credentials, and payment details before sharing screenshots. List the troubleshooting steps you have already tried to avoid repeating them.
Before you finish setting up
Once the target app works, save the configuration that is currently working and learn where to pause the connection, update the subscription, and switch routes. Set whether to connect automatically after a restart based on your needs; do not rely on the previous session's state. When you stop using the client, make sure the system proxy or tunnel is properly turned off so leftover settings do not affect your next connection.
Use the billing records in your panel to track data usage. Background syncing, system updates, and video playback can all consume data. The download amount shown by a client or the usage figures in an app may not match the plan's billing records. To choose between a monthly plan and a data package, review the plan details based on how often you expect to use the service. There is no need to upgrade before your first connection is working.
Getting started: Confirm your account, retrieve the configuration, import it into a client, and connect successfully. Then check the exit used by your target requests and whether the service works. Connection status, exit region, and app availability are separate things to verify. If something goes wrong, keep the settings that are working and troubleshoot one step at a time; that is more useful than repeatedly reinstalling the client.