MeveVPN User Guide

Service overview and cross-border access

Understand the service, dashboard, and client

MeveVPN is a subscription service for cross-border access and network acceleration. Its international network covers 100+ countries and 240+ routes, with support for Windows / macOS / iOS / Android / Linux and unlimited simultaneous devices. To understand how it works, distinguish the service, user dashboard, and client: the service provides routes and plans; the dashboard manages your account, orders, and subscription access; the client reads your subscription settings and directs matching network requests through the route you select. The marketing website provides information—it does not connect your devices or automatically change their network settings.

The connection path starts when an app on your device sends a request. The client uses its connection mode to decide how to handle it, then the selected route connects to the destination. Whether the client is running, system permissions are in effect, and the request matches the relevant rules all affect the path. So an active account does not mean your device is connected, and a client showing “connected” does not mean every app uses the same route. The verification section below checks these states separately, so you don’t waste time switching routes at the wrong stage.

Know what the service can—and cannot—do

People typically choose an international route to access global websites, use AI tools, or stream video. Network routing is just one factor: a platform may also restrict access based on account region, content licensing, payment eligibility, or its own risk controls. Changing your exit region does not change your account details or provide a content subscription. If access fails, first distinguish a network connection problem from a platform refusing access. They can look similar but require different fixes, so don’t assume every error is caused by the route.

“Bank-grade encryption” is a core marketing claim for this service. In practice, you should still protect your account password and subscription link, check the address of the page you visit, and keep your device and apps up to date. An encrypted connection does not make a website trustworthy or replace the platform’s own login protections. On public networks in particular, don’t ignore certificate warnings from your system, and never disable security checks just to open a page. Check network performance and account security separately; a connection icon cannot tell you about every risk.

Keep a useful record of your setup

Before you begin, note your device platform, usual network, main apps, and current plan type. Don’t include passwords or subscription links. The goal is to make it easy to answer: “Which device, on which network, had trouble with which service?” The same route can perform differently on different networks, and sleep mode, app updates, or switching networks can change connection status. A clear account of what you did before and after a problem is far more useful than simply saying “the internet isn’t working.”

Work through the contents in order, or come back to a specific section once you have a basic connection. For plan and data questions, see Choose a plan; for setup questions, see Get your subscription and Set up your platform; if a page won’t load, start with Check your connection. The route list shows regions and route types, while the plans page has full pricing details. This guide explains how to put that information into practice. Button names can vary, so follow what your dashboard or client currently shows rather than assuming one screenshot applies to every platform.

You’re ready to move on when you can explain the roles of your account, subscription, client, and route—and identify the app you need to check. Successfully opening the website does not mean client setup is complete.

Choose a plan and manage data

Start with how often you use it, then estimate your data needs

Choose a plan based on your usage habits, not just the price. If you regularly use international websites, work on documents, or stream video across desktop and mobile, compare the data allowances on monthly plans. If you use the service less often and prefer to draw down data as needed, consider a data package. Monthly plans manage an allowance by billing period; data packages last until used and never expire. They use different billing models: a monthly plan’s price is not a recurring fee for a data package, and a data package does not automatically top up every month.

Break down your actual usage to estimate your needs. Text pages, file syncing, long video sessions, and large downloads use data differently; background app updates can also transfer data without you actively using your device. Don’t estimate a fixed allowance based only on viewing time: quality, encoding, caching, and app behavior all affect usage. A better approach is to check usage in your dashboard after you start, then compare it with your own habits instead of copying someone else’s plan choice.

Understand resets, upgrades, and shared data

Monthly plan data resets each month on your activation date; don’t assume every account resets on the first of the calendar month. Check both your plan status and the reset date shown in your dashboard to see how much data remains. If you upgrade mid-cycle, the price difference is converted into remaining days. Check the dashboard’s confirmation before submitting; don’t try to calculate the credited time by simply subtracting prices. Renewing, upgrading, and changing billing types are different actions. If the order details are unclear, confirm how the change will be handled before paying.

Unlimited simultaneous devices means you can use the service on multiple supported platforms; it does not increase your data allowance with each device. Check usage in your account dashboard rather than treating desktop and mobile as separate allowances. File syncing, video, and background tasks running on several devices at once can use data faster. Check background activity on your regular devices before changing plans. Choosing a higher tier just because you have more devices may not match your actual needs.

Check more than just the price

This service accepts Alipay / WeChat Pay / USDT and offers a 7-day refund policy. Review the payment methods and refund policy alongside plan prices, but don’t infer discounts, trial data, or other terms that aren’t stated in the available facts. The “Start Free Trial” link on the marketing site takes you to the user dashboard; check the dashboard for your actual account status. To request a refund, read the refund policy and describe your order in a support ticket from your account. Don’t post complete payment records in public comments or screenshots.

Before confirming your choice, double-check the billing type, data allowance, and order summary shown in the dashboard. If you already have an active plan, confirm whether this action renews or changes it rather than relying on the button’s position. Compare options on the plans and pricing page, then go to the plans section of the dashboard to proceed. The goal isn’t to choose a plan that will never change; it’s to understand the rules, track your actual usage, and adjust when your needs change.

Plan balance, remaining data, and client connection status are different things. Having data left doesn’t mean your device is configured correctly; a connected device doesn’t confirm that your plan is active.

Set up your account and confirm orders

Open the user dashboard from the right page

The marketing website and user dashboard serve different purposes. After reviewing the plans, use the free trial link to open the dashboard; if you already have an account, use the login link. MeveVPN requires no email address: create an account with a username and password. Before entering your details, make sure you’re on the official site; don’t mistake a lookalike page in search results for the right place. Use the account form shown in the dashboard, and never enter your MeveVPN credentials on a third-party site.

Choose a username you can recognize and keep track of, and don’t reuse a password from another site. Since no email address is required, don’t assume you’ll be able to recover your account by email later. After creating your account, store the username, password, and official site address securely in a trusted password manager, and make sure you can log in again. Don’t rely only on autofill on one device, and don’t save login details on a public computer. If you have trouble accessing your account, use the options shown in the dashboard rather than guessing at a recovery process that may not exist.

What to check before and after placing an order

After logging in, open the plans section and review your account status before choosing a monthly plan or data package. Before submitting, check the order summary for the name, price, billing type, and data allowance. If anything differs from what you expect, go back and check rather than proceeding to payment. If you already have a plan, pay close attention to the renewal or change details: the price label alone doesn’t explain how the order will affect your current plan. If the information shown isn’t enough to decide, ask through a support ticket before submitting.

Pay using the Alipay / WeChat Pay / USDT options provided in the dashboard. For USDT, check the network, recipient details, and amount shown on the payment page. Don’t reuse details from an old order or use payment information forwarded through a chat. If the payment page expires or returns an error, go back to your orders and check the existing order rather than paying again right away. The order status in your dashboard is the source of truth; a payment app’s confirmation alone doesn’t mean your plan is active.

After paying, return to the dashboard and check the order status and account overview. Payment submission, order confirmation, plan activation, and client configuration are related but separate steps. If the order hasn’t been confirmed, keep its details and check the current page rather than creating the same order again. If the order is complete but the plan doesn’t look right, refresh the dashboard and check your account status again. If the issue persists, submit a support ticket so the team can check the specific order; don’t repeatedly delete all your client settings.

Keep the order details needed for support

Keep a record of the plan, payment method, payment status, and when the issue occurred. These details help with support; don’t share complete transaction records publicly. Before taking a screenshot, hide sensitive fields, subscription links, and payment details. Only include information that’s needed to resolve the issue in your support ticket. Describe whether you couldn’t open the payment page, the order stayed incomplete after payment, or the order completed but your account status didn’t change. Each points to a different part of the process.

Once the account overview shows an active status, move on to client setup and subscription import. Being logged in through a browser does not authorize a client: the client reads configuration, and it won’t connect just because you opened the dashboard. When setting up a new device, get the relevant information from the official site rather than copying a link of uncertain origin from an old chat. For details on account data and permitted use, see the Privacy Policy and Terms of Service, then manage your account using the options currently available in the dashboard.

Checkpoint: you can log in again, find this order, and confirm your plan status. If any of these are unclear, resolve the account or order issue before moving on to client setup.

Get your subscription and manage configuration

What a subscription link is for

A subscription link lets a client retrieve route configuration. The client reads the link and turns the returned data into selectable routes and settings. The link is not a regular webpage to view in a browser or an installer download. The usual process is to check your plan status in the dashboard, get the subscription, then import it into the client. Supported formats vary, so use the option provided for your client in the dashboard. Don’t assume that anything that looks like a URL can be imported as configuration.

A subscription may contain route names, connection parameters, rules, and other settings; the dashboard determines exactly what it provides. Account data balance and the client’s route list are also different things. Seeing a list means the client has read configuration; it doesn’t prove your account is still active. Likewise, an active dashboard status doesn’t mean your client has the latest list. If a route is missing or its name has changed, check your dashboard status and subscription update time separately rather than relying on an old cache.

Import the subscription using the appropriate method

After logging in, open Clients and subscription, confirm your platform, and choose the method for your client. If one-click import is available, selecting it may prompt your device to open the client. Make sure it’s the right app, then check that the new configuration appears in the client. A completed browser redirect doesn’t mean the import is complete; proceed only when the configuration and route list are visible in the client. If nothing happens, the required app may not be installed, so install the client first.

If you’re copying a link, copy the complete address from the dashboard and paste it into the client’s subscription or remote configuration section. Don’t remove query parameters or assume a truncated address is complete. If import fails, check for extra spaces, line breaks, or copied instructions, then confirm the format is supported by your client. Don’t send your subscription to a public conversion website to try to fix it. That would expose your configuration credentials to another service and make them harder to manage.

Updating and re-importing are not the same

Updating a subscription usually means the client re-reads an existing source; re-importing may create a new configuration entry. If the route list is out of date, try updating the existing configuration first, then make sure you’ve selected the updated entry. Repeated imports can leave several configurations with the same name. Even if you update one, you might still be using another. You can add a note to help identify each configuration, but don’t change connection parameters you don’t understand or put account credentials in the note.

If an update fails, first work out whether the client couldn’t read the link or read it but couldn’t parse it. For a read failure, check your local network, dashboard access, and whether the link is still valid. For a parsing failure, check the import format and client compatibility. A working existing connection doesn’t prove that updates are working; likewise, a successful update doesn’t mean every route will suit your current network. Save the error text shown in the client so you can distinguish subscription retrieval issues from route connection problems.

Protect your subscription like a password

Treat your subscription link like a password: don’t share it publicly or put it in articles, shared documents, or screenshots that haven’t been redacted. If you think it has been exposed, check whether your dashboard offers a reset or regeneration option, and use it if available. Then update the saved source on your devices. Deleting a chat message won’t invalidate a link that someone has already copied. If you can’t find the right option, ask through an account support ticket. Don’t try to revoke access by editing fields in the URL, and don’t assume changing your account password invalidates an existing subscription link.

This example URL https://example.com/sub?token=YOUR_TOKEN is shown only to illustrate the format of a subscription link; it cannot be used for import. Get your own link from your user dashboard. This article does not provide working credentials.

For more on the differences between getting, importing, and updating a subscription, read the beginner’s guide to subscription links. By the end of this section, you should know where your configuration came from, which entry the client is using, and how to record import errors without exposing credentials.

Set up clients on each platform

The user dashboard provides client access for Windows / macOS / iOS / Android / Linux. Log in to get your subscription; the dashboard handles client access according to your plan status. The instructions below account for platform differences without assuming a specific app version or identical button labels across clients. The general order is: get the client, load your subscription, select a configuration, grant any required permissions, then connect. If the interface uses different labels, identify the relevant function rather than relying on button color.

Windows: Check the configuration and system connection mode

On Windows, get the client from the dashboard and follow its installer, then open subscription or configuration management to import the source. First check that the route list appears, then select the configuration and route you want. If the client offers system proxy and tunnel modes, read its explanation before choosing. A system proxy mainly affects apps that follow Windows proxy settings; turning it on doesn’t mean every app is connected. Grant extra permissions only when the client requests them, and don’t change system services you don’t understand.

After connecting, check your exit IP in a browser, then test the apps you actually need. If the browser works but another app doesn’t, that app may not use the system proxy or may have its own network settings. Close other tools that manage proxies while testing, so they don’t override one another. If your everyday network behaves differently after you quit the client, check whether the system proxy has been restored instead of immediately uninstalling the app or resetting the whole network. Start by correcting settings you can clearly identify.

macOS: Check permissions and connection status

On macOS, get the client from the dashboard, complete first-run setup and confirm system permissions, then import your subscription. If macOS asks to approve a network extension or connection permission, check that the request comes from the app you just installed. Don’t treat configuration profiles from unknown sources as a requirement for MeveVPN. After importing, check the active configuration and selected route, start the connection, and review both system and client status. Seeing the app icon in the menu bar only means the app is running; it doesn’t confirm the network connection is active.

After your device wakes from sleep or switches networks, the client may need to reconnect. If an app keeps waiting or a page stalls, first check whether your current network can reach the services you normally use, then check the connection toggle. If other network extensions are installed, check their instructions for possible conflicts; avoid enabling multiple configurations that manage the same traffic path. Without a clear error, don’t delete all your network settings. Keeping the current configuration makes it easier to compare what changed.

iOS: Confirm VPN permission after importing

Get the iOS client using the method provided in the dashboard. If a webpage prompts you to open the app during import, check the app name, then look for the new configuration inside the app. If you’re copying the link manually, paste it into the remote configuration or subscription section, not the browser’s address bar. The first time you connect, you may need to allow the app to add a VPN configuration. Follow the system prompt, then check the client status. A VPN indicator in iOS can be a useful clue, but verify the actual route using the target app and exit information.

If access stops after switching networks, check that the client still has the intended configuration and route selected. An app running in the background does not necessarily mean the connection has stopped or is working normally; check its current status and test an actual request. If you have other VPN configurations, confirm which one is active. Don’t copy system settings from an old screenshot, and don’t rely on a browser test alone when other apps have different results.

Android: Account for connection permissions and background limits

On Android, import your subscription and select the configuration, then allow the client to establish a VPN connection when prompted by the system. Background management can affect whether the client keeps running. If it behaves unexpectedly after the screen locks, check the device’s battery and background settings for the app, then adjust them according to the app’s instructions. Don’t disable every battery-saving feature at the outset or grant unrelated permissions. After the configuration loads, check the route list, connection status, and target app separately to locate the problem.

Linux: Identify your desktop or command-line setup first

On Linux, the setup depends on the client provided in your dashboard and your local environment. In a desktop client, import the remote configuration as usual. In a command-line environment, follow the client’s instructions to save configuration, start the process, and check logs; don’t copy installation steps from another platform. Distinguish your user permissions, whether the process is running, and whether your app is using the proxy. A successful launch only means the process exists; verify that network requests actually go through it. Store configuration files somewhere you control, not in a shared directory or public code repository.

Checkpoint: your platform displays the subscription routes, lets you select the right configuration, and can start a connection. Verify that the apps you need use the intended route in the next section; don’t substitute a status icon for an actual check.

Verify the connection and troubleshoot by layer

Compare conditions before and after connecting

Before testing the connection, make sure your local network works normally. Then connect the client and select a route. Record what you observe before and after, including exit region, behavior in the target app, and client logs. Don’t change networks, switch routes, and edit rules all at once; if the result changes, you won’t know which action made the difference. Use a test page you trust to check the exit, and don’t treat every label it displays as definitive. Results reflect only that request and the information the page can observe.

An exit IP and region check answers a specific question: “Where did this request leave the network?” If you select a Japan route but the check still shows your previous exit, confirm that the right configuration is selected, the connection is active, and your browser is using the proxy. Also check whether a browser extension is changing the route. Geolocation databases can disagree, so if the displayed region differs, consider the actual exit change and app behavior together rather than declaring the route broken based on one place name.

Check DNS and the target app separately

A DNS check looks at the path taken by domain lookup requests; it does not observe exactly the same thing as the exit used for webpage content. Your browser may use its own encrypted DNS, and your system may cache previous results. A test page’s DNS provider label therefore doesn’t describe how every app handles DNS. Check the client and browser settings, then compare results before and after connecting. If you need to change DNS, follow the client’s instructions rather than copying configuration snippets from an unknown source.

After checking your browser, open the app you actually want to use and test sign-in, content loading, and any key features. Being able to open an AI tool’s homepage doesn’t guarantee that in-app requests use the same route. Opening a streaming service doesn’t mean every title in a given region is playable. If a platform reports an account or region issue, save the exact message and check your account status. Verify network access and content rights separately; a platform restriction doesn’t mean every route is unusable.

Narrow down the issue with minimal changes

If no routes connect, check your account and local environment first rather than testing every route in the list. Confirm that your plan is active, the subscription can update, and the client has the required permissions. Then compare with another available network. If the same device works on a different network, the original network may be a factor. If other devices work on the same network, focus on this device’s settings. These comparisons narrow down the possibilities; they don’t prove a specific cause. Check logs and error messages too.

If only some routes fail, keep the network and client mode unchanged while comparing routes in other regions or categories. Don’t assume the nearest route is always best, or that one successful test guarantees consistent performance. Note whether the failure happens while connecting, resolving a domain, or loading content. This helps distinguish route connectivity from the destination service’s response. For more testing tips, see the guide to checking your exit IP and DNS. For reliability comparisons, see how to test connection success and disconnections.

When contacting support, include your device platform, client mode, selected route name, network environment, and the exact error message. Logs may contain sensitive information, so review and redact credentials, subscription links, and unrelated account details before sending them. Describe a repeatable scenario—for example, the browser works after connecting but an app gets stuck on the sign-in page—instead of simply saying “it’s slow.” Clear observations help support focus on the relevant stage and avoid changing settings across all your devices to troubleshoot one app.

A reliable connection check combines client status, exit information, and results in the target app. None of these alone describes every network request on your device.

Routine maintenance and renewals

Turn status checks into clear next steps

Once connected, focus routine maintenance on account status, subscription source, device environment, and data usage. You don’t need to re-import every time you connect. Update the subscription if the route list is clearly out of date, the current route stops working, or the dashboard reports a change. Before updating, confirm which configuration you’re using. Afterward, check the route list and selected exit so you don’t update a backup entry while continuing to use the old one. Keep the source clear instead of accumulating duplicate entries.

After your device wakes from sleep, updates its system, or switches networks, first check whether the connection recovers. If something goes wrong, note when the change occurred, then troubleshoot step by step using the verification section. Don’t conflate a system update with route maintenance, and don’t repeatedly uninstall and reinstall the client if it hasn’t reported an error. Reinstallation can remove existing configuration and diagnostic clues; save it for cases where it’s clearly needed rather than making it the first response to an access problem. Pinpointing what changed is usually more effective than trying everything.

Track data use and background activity

When checking account usage, consider what you’ve been doing recently. Video quality, file syncing, system updates, and background tasks across multiple devices can all affect data consumption. If your balance is falling faster than expected, first check device activity and the client’s connection mode to see which apps are using the subscription route. Don’t assume there’s an account problem based on the balance alone. If you’ve checked your devices and still have questions, share your usage observations and network environment through a support ticket. Don’t publish your subscription link and ask others to check it for you.

Monthly plan data resets each month on your activation date. Check the date in your dashboard; the start of a calendar month is not a shared reset date for every account. Data packages last until used and never expire, but that doesn’t mean data automatically replenishes or bypasses usage limits. Unlimited simultaneous devices and the account’s data allowance are separate things. Keeping these two limits clear can help you avoid mistaking an exhausted allowance for a client configuration problem.

Double-check your order before renewing or upgrading

When you’re ready to renew, check your current plan and the order summary in the dashboard, then make sure the proposed change matches what you expect. Don’t skip this check just because you used the same payment option last time. If you upgrade mid-cycle, the price difference is converted into remaining days; use the result shown in the dashboard before submitting. Don’t assume or promise a fixed number of extra days. If you’re switching between a monthly plan and a data package, read the current instructions first. Don’t treat the change as a simple add-on or assume unused data will automatically transfer in a particular way.

After paying, confirm the result in your account and orders, then update the configuration your client needs to read. If your dashboard looks correct but the client still shows old information, check that you refreshed the right source. Don’t use cached text in the client as a billing record; the dashboard is authoritative for your plan and orders. To request a refund, read the 7-day refund policy and submit a support ticket from your account. Don’t seek payment help on unofficial sites or send your password to strangers.

Move to a new device or retire an old one

On a new device, get the client and subscription for its platform from the dashboard rather than copying a configuration file of uncertain purpose. After importing, check the exit and target app as before, and confirm the connection mode suits the device. Before handing over, selling, or retiring an old device, sign out and remove saved subscriptions and configurations. Check whether your password manager and browser still have your login details stored. Quitting the client alone does not delete configuration or remove saved account details.

If you keep maintenance notes, record the plan type, subscription update time, configuration labels, and troubleshooting results. Don’t write complete links or passwords in shared notes. The most useful long-term question is: “What’s different now from the last time everything worked?” If a problem is hard to reproduce, save a redacted copy of the exact error message so you can compare it if it happens again. For account or order issues you can’t resolve yourself, use the support ticket area in the dashboard. See the contact page for available support channels.

Advanced routing and route selection

Understand the mode before changing rules

Adjust routing only after you’ve established and checked a basic connection. Rule-based mode typically uses domain, address, or app-related conditions to choose a request’s path. Global mode generally sends requests within the client’s control through the selected proxy. Direct mode sends the relevant requests without using that proxy route. “Global” does not guarantee that every request on the device is managed; the actual scope still depends on system proxy settings, tunneling support, and app behavior. When discussing a mode, include how the client handles traffic rather than referring only to the toggle name.

Before making changes, record the configuration that currently works. Check whether a subscription update could overwrite local edits, then consult your client’s supported override method. Don’t assume edits to automatically retrieved configuration will persist, and don’t copy parameter names from another client. Similar-looking configuration syntax doesn’t mean the processing order and defaults are the same. When troubleshooting, restore a working baseline first, then adjust rules for a specific app. Adding a lot of unfamiliar rules at once makes the original issue harder to diagnose.

Choose an exit for your needs, not its label

Route types help explain how traffic travels; they aren’t a fixed performance ranking. If you need content from a specific region, check the exit region and the platform’s requirements. For general international access, prioritize a route that completes requests reliably on your current network. Actual performance on IEPL dedicated, relay, and direct routes still depends on your network and destination service, so the route name alone can’t predict the outcome. See regions and types in the route list, then compare using the same device and app.

For streaming, check the catalog, the specific title, and playback separately. Being able to open a service’s homepage doesn’t mean every title is available to your account, and a route label doesn’t guarantee continuous access. For AI tools, distinguish network access from account eligibility; changing your exit region does not override platform account policies. See the streaming access guide for related scenarios, and Netflix regional catalogs and playback checks for guidance on catalogs and picture quality. Don’t treat methods described in an article as verified performance claims.

Check your system with a local command

For advanced troubleshooting, you can check whether your operating system has saved proxy settings. The command below is for Windows Command Prompt. It only reads the current WinHTTP configuration; it changes no settings and contains no MeveVPN credentials. WinHTTP may use a different proxy mechanism from your browser or other apps. So no proxy in the output doesn’t prove the client isn’t working, and a listed proxy doesn’t prove your target app is using it. Treat the result as one clue about your system, and interpret it alongside client logs and app checks.

netsh winhttp show proxy

If you need to check whether a rule matched, start with the connection history or logs provided by your client. Find the relevant app request, then check its policy and exit route. The address returned by DNS, the rule’s matching condition, and the route ultimately selected are related but distinct pieces of information. One connection label alone can’t explain every request from an app. Redact logs before sharing them. Don’t paste large, unchecked logs on public forums, or give others your subscription credentials to troubleshoot on your behalf.

Keep a baseline configuration you can restore

Router setup and native IP are common search terms, but the available facts only confirm support for Windows / macOS / iOS / Android / Linux. They don’t establish that this service offers a router setup method or any particular IP attribute. If you need support for a specialized setup, first check the options in your dashboard, then confirm through a support ticket. Keep advanced configuration within supported platforms; don’t install unknown plugins, apply unfamiliar firmware settings, or promise unverified route capabilities based on related search terms.

The aim of this guide is to give you a process you can follow independently: check your account and plan, confirm the subscription source and active configuration, verify the exit and target app, and only then adjust rules or routes. Keep a working setup you can restore before each change, and make changes to address a specific issue rather than turning on every option. To start the connection process from the beginning, return to the quick-start guide. If the problem is limited to one stage, use the contents to find it, and rely on what your dashboard and client currently show.