This beginner’s VPN guide follows the setup process in order: create an account, choose a plan, get your subscription, import it into a client, and verify that traffic is using the intended route. A successful order doesn’t mean you’re connected, and a client showing “Connected” doesn’t mean every app is using the proxy. Check the result at each step instead of repeatedly clicking Connect.
Account setup: Keep your login details safe
VPNSelf doesn’t require an email address; you can get started with a username and password. Open the user panel, follow the on-screen instructions to create an account, and save your credentials in a trusted password manager. Don’t reuse a password from another site. Since no email address is provided, don’t assume you can recover your account by email. Use the recovery options actually available in the panel.
Once setup is complete, you should be able to open your account overview and check your plan status and data usage. If you’ve already placed an order, first make sure you’re signed in to the account associated with it and that the payment status has synced before configuring a client. A payment confirmation and an active plan shown in the panel are separate steps. If they don’t match, keep your order record and contact support through a panel ticket. Don’t make another payment and hope it fixes the issue.
Choosing a plan: Match it to your usage and data needs
A monthly subscription suits regular use. Data resets monthly on the day you activate the plan, not at the start of each calendar month. A data package works well if your usage varies: it stays valid until used and never expires. Start by estimating what you’ll use it for. Browsing text-heavy sites and making API requests typically use less data than streaming video for hours or downloading large files. Page loading speed alone isn’t a good way to estimate data needs.
| Billing type | Price and data | Usage terms |
|---|---|---|
| Monthly subscription | ¥9.9/month, 60GB | Data resets monthly on the activation date |
| Monthly subscription | ¥18/month, 250GB | Data resets monthly on the activation date |
| Monthly subscription | ¥28/month, 500GB | Data resets monthly on the activation date |
| Data package | ¥158/300GB | Use it whenever you need; it never expires |
| Data package | ¥358/1000GB | Use it whenever you need; it never expires |
| Data package | ¥658/3000GB | Use it whenever you need; it never expires |
If you upgrade a monthly subscription mid-cycle, the price difference is converted into remaining days. Check the panel for the exact result. VPNSelf has no device limit, but that doesn’t mean data is unlimited. Keep an eye on your account usage when multiple devices are connected. Payment methods include Alipay, WeChat Pay, and USDT. See the plans page for full details.
In short: Choose a monthly subscription for regular use and a data package for occasional use. You can request a full refund for any reason within 7 days of your first payment. A refund policy doesn’t mean a plan is free, and unlimited devices doesn’t mean unlimited data.
Getting the client: Choose your platform and verify the source
VPNSelf supports Windows, macOS, iOS, Android, and Linux. Get the client from the downloads section in the panel; installers aren’t linked publicly in this guide. Sign in to download on all platforms except iOS. For iOS, eligibility depends on the active plan shown in the panel; follow the instructions there to get the app.
Desktop systems usually require you to enable the system proxy in the client or turn on virtual network adapter mode as instructed. The system proxy may not cover command-line tools, games, or apps that manage their own network connections. The first time you enable a connection on a mobile device, the system may ask to add a VPN configuration. This lets the system route network traffic through the app. Check the app’s source before granting permission, and don’t approve apps from unknown sources.
On Linux, desktop apps, background services, and terminal sessions may each use different proxy settings. Being able to browse the web doesn’t mean terminal apps are using the proxy. If you’re new to Linux, start with the default setup for your platform in the panel. Avoid mixing in port, routing, or DNS settings from other guides for now.
Importing a subscription: Check the configuration, not just the confirmation
A subscription lets your client retrieve routes and related settings; it isn’t a regular web page to keep opening in your browser. Sign in to get your subscription. The panel may offer a copy link, an import button, or another supported method. Labels vary by client, so choose the format that matches the client you’re using.
- Get your subscription. Sign in to the panel and copy the appropriate configuration link from the subscription section. Make sure you have the full link, without spaces, line breaks, or extra text added by a chat app.
- Add the configuration. Open the subscription or configuration manager in your client, choose import from link, paste the link, and save. If you use the panel’s import button, make sure it opens the client you just installed.
- Update the subscription. Run an update and check whether available routes appear. If you see a configuration name but no list of nodes, you may not be ready to connect yet. Check the update error.
- Enable the configuration. Select the configuration you just imported, then choose a route and connection mode. Some clients let you save multiple configurations; saving one doesn’t mean it’s currently in use.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols or protocol suites, not plan tiers, and not every client supports them. An incompatible subscription format or an unsupported core version can cause nodes to be skipped. These names are provided to help you understand compatibility; they don’t mean VPNSelf offers every protocol listed. Check the panel and your client for supported options.
Routes and split tunneling: Start with the default rules
Route types describe the network path; they don’t determine whether a particular site will be accessible. A direct route usually connects from your network straight to an overseas entry point. A relayed route passes through an intermediary node. IEPL refers to a dedicated transmission link. Actual performance also depends on your local carrier, distance to the entry point, congestion at the exit, and the destination service. The route label alone can’t tell you which option will be faster.
VPNSelf covers 110+ countries with 160+ routes, but that doesn’t guarantee access through every individual route. Start by choosing a route in a region that meets the destination service’s requirements, then check whether it works in practice. A farther-away region isn’t necessarily better. The service’s requirements, your account region, and the exit location can all affect access.
Split tunneling rules determine whether requests connect directly, use a proxy, or are blocked. Rule-based mode typically evaluates domains and addresses in a set order. Global proxy mode typically sends requests handled by the client through the selected proxy, but it doesn’t automatically cover every app on your device. For your first setup, use the default rules recommended in the panel. If one app has a problem, troubleshoot that app first. Don’t change the route, rules, and DNS settings all at once.
Testing your connection: Check websites, exit location, and DNS separately
After enabling the connection, first open a site you can normally access to make sure the configuration hasn’t disrupted your local connection. Then try the destination service that requires an international route. Next, check your exit location using a trusted IP lookup site, and review the client’s connection log to confirm which rule and node matched the request. The exit location shown in your browser only describes that browser’s request; it doesn’t tell you what happened in other apps.
- ✅ The configuration is enabled, the subscription has routes to choose from, and updates aren’t failing repeatedly.
- ✅ The target site loads, and you’ve tested access in the app you actually need to use.
- ✅ The client’s connection log shows that the target request matched the expected rule and route.
- ✅ After disconnecting and reconnecting, access still works as expected; you haven’t relied on an old cached page.
- ✅ Your account data status is normal, your device’s clock is correct, and your current network can access the internet.
DNS translates domain names into addresses. If a domain lookup that should use a protected route bypasses your expected configuration, it may expose query information or cause a mismatch between the DNS resolution and exit location. A DNS test page’s reported resolver location is only a clue; on its own, it can’t prove that all requests are leaking or secure. Browser Secure DNS, system resolvers, and client settings may each operate independently.
If you find an unexpected DNS result, first check your client’s documentation for how DNS settings interact with virtual network adapter mode. Then see whether your browser has its own Secure DNS setting enabled. Don’t blindly switch to a public resolver. What matters is that the request path matches your routing rules. A proxy service is no substitute for HTTPS, system updates, or protecting your account.
Common issues: Narrow down the cause by symptoms
The subscription updates, but websites won’t load. First check that the configuration is selected and that the system proxy or virtual network adapter is enabled as instructed. Then review the request log. If there’s no connection record for the target app, check whether its traffic is being routed through the client. If a record appears but the connection times out, try a different route. Don’t mistake a local proxy that isn’t enabled for a route issue.
Websites load, but one app doesn’t. Check whether the app follows the system proxy, has its own proxy settings, or has a domain routed directly by your rules. Account requirements or regional policies on the destination platform may also be the cause; an error page alone doesn’t mean your connection is down.
It worked earlier, but now it’s slow. First check your remaining data and plan status, then look at your local network, background downloads, and any other proxy apps. Keep the test destination the same and switch only the route. If you also change networks, switch clients, and edit rules at the same time, it’s hard to tell which change made a difference.
If you still can’t resolve the issue, submit a support ticket in the panel with your operating system, client version, error message, what you were doing, and the checks you’ve already tried. Hide subscription links, passwords, and other credentials in screenshots; check logs for sensitive information before sharing them. For installation help, see the beginner’s guide and FAQ.
You’re all set when: your account is active, the subscription updates, the configuration is enabled, the target request follows the right rule, and the app you need works. After your first successful connection, save the working configuration and make changes one at a time. If something breaks, returning to the last working setup is easier to troubleshoot than layering on more settings.