VPN basics: clients, subscriptions, and routes

This complete VPN guide for beginners takes you from choosing a service to verifying your connection. If you’re new to VPNs, start by understanding three components: the client manages the connection, the subscription supplies configuration to the client, and the route determines where routed traffic exits. A client showing “Connected” doesn’t necessarily mean the app you want to use is going through the selected route.

VPN clients can also manage proxy routes. System-wide routing can cover more apps, while apps that ignore system proxy settings may continue using your regular connection. Split tunneling lets some requests connect directly while others go through a route. What gets routed depends on the client mode and rules—not just whether an icon appears in your status bar.

Choose a plan based on your devices and usage

List the devices and apps you actually plan to use, then compare billing options. Check that the service offers a compatible client or import method for each device. For work devices in particular, confirm that you can install apps and add network configurations. There’s no need to choose a region or pay for a large data allowance before checking device compatibility.

Usage pattern Best fit Why it fits
Daily work with consistent usage Monthly plan Data resets monthly on the activation date, so estimate usage based on a typical month.
Occasional travel with long gaps between trips Data bundle Never expires; use it as needed without relying on a monthly reset.

Estimate usage separately for web browsing and text messages, video calls, and large file syncs. The latter activities can use much more data. If you mostly browse but occasionally sync project files, don’t base your estimate on your lightest day. Before choosing, check current prices, data allowances, and terms on the Plans page.

Get started: find your subscription link and client

Check your selected plan and billing option in the user panel. Once your service is active, find the subscription section and copy the link for your client. 9MVPN doesn’t require an email address. Your account credentials let you sign in to the panel; the subscription link lets your client retrieve its configuration. They serve different purposes, so don’t import the panel URL as a subscription link.

Find installation instructions for your platform on the client downloads page. A client that can import a subscription may not support every protocol it contains. If the list is empty or expected routes are missing after import, check which client and subscription format are recommended, then try refreshing the configuration. Before switching clients, disconnect the old one to avoid having two apps route your traffic at once.

Connect to a route: from import to first launch

  1. Make sure your regular connection works first. Leave the client disconnected and open a website you can normally access. If a hotel or public network requires a sign-in page, follow the network’s instructions before starting the client.
  2. Import and refresh your subscription. In the client, look for “Subscription,” “Configuration,” or “Import from link,” then paste the link to load the route list. Menu names vary by platform. If you see an import error, note what it says instead of repeatedly reinstalling the client.
  3. Choose a route and routing mode. Select a region that suits your needs. For your first test, use the client’s proxy mode so you can make sure your test browser is routed through the proxy. For everyday use, enable split tunneling rules as needed.
  4. Check permissions after starting. If your system asks to add a VPN configuration or allow network access, make sure the request came from the client you just installed. After starting the client, check for connection errors before testing where your traffic goes.

Latency in the route list is only a rough guide for an initial choice. It doesn’t indicate file transfer speed or guarantee that a website will accept the route’s exit IP. For work, test the tasks you need to do—opening your workspace, syncing files, or joining a meeting—instead of simply choosing the route with the lowest latency.

Verify your connection: check your exit IP, then test your apps

Before and after connecting, use the same browser and IP protocol version to open the IP check page and compare the public IP shown. A change means that request used a different exit; it doesn’t mean every app uses the same one. If the check page is set to connect directly by your rules, an unchanged IP may be expected. Check which rule matched before deciding the connection failed.

  • ✅ Expected exit: Requests that should use a route show its exit IP. Switch back to your everyday rules and test the target request again.
  • ✅ Your task works: Open a document, send a message, or test a meeting in the app you actually use to confirm the features you need are available.
  • ❌ Don’t rely only on “Connected” or a region name: a system icon doesn’t prove where traffic is routed, and IP geolocation databases can disagree.

If you need to check whether DNS is working as expected, inspect the resolver and the client’s DNS logs separately. A browser may use its own encrypted DNS, affecting test results. A resolver’s location differing from the exit location doesn’t by itself indicate a DNS leak. First check which DNS method the client is expected to use, then see whether requests bypass that setting.

How to tell it’s working: Requests that should use a route go through the expected exit, the target app can complete the task you need, and traffic meant to connect directly hasn’t been rerouted. Use these results to assess both route selection and split tunneling rules.

First connection failed? Check each troubleshooting step

Subscription won’t load: Disconnect the client, make sure your regular connection works, then check the service status in the panel, confirm the link was copied in full, and verify the subscription format is supported. If the list refreshes but one route won’t connect, try another route in the same region. Change one setting at a time so you can tell what helped.

Browser works, but an app doesn’t: Check whether the app uses the system proxy or is set to connect directly by a split tunneling rule. If only one website fails, note the error and distinguish a timeout from account permissions or restrictions imposed by the site. Changing routes won’t necessarily fix the latter two.

Still stuck? Contact support with your device’s operating system, client name, route region, the step where the error occurs, and a redacted error message. Mention whether your regular connection works with the client disconnected; that’s more useful for troubleshooting than simply saying “it won’t connect.”