FAQ

No email address is required. Create an account with a username and password. Store both in a trusted password manager rather than relying on your browser’s current login session. Your username gives you access to the user panel, while your subscription link lets your client retrieve routes; they serve different purposes and cannot replace one another. Before signing out, clearing browser data, or switching devices, make sure your credentials are safely stored. If you can’t log in, check your keyboard layout, capitalization, and any spaces copied by mistake. Never post your password or full subscription link in a public forum.

VPNMove allows an unlimited number of devices to be online at the same time, so changing devices alone doesn’t require you to choose a new plan. Sign in to the same account on your new device, get the client for your platform from the user panel, and import your subscription. Supported platforms: Windows / macOS / iOS / Android / Linux. When using multiple devices, keep an eye on your plan status and remaining data. Unlimited devices doesn’t mean unlimited data. Before handing off an old device, remove any saved subscription links and account credentials to prevent the next user from accessing your account resources.

Sign in to the user panel and look for your subscription details or import option in the account overview, then import the subscription into your client. To refresh the route list, open the client’s subscription or configuration manager, find the relevant subscription, and update it. Then check that the active configuration is the one you just updated. Menu names vary by client, so follow the labels in your app. Check the client settings for its automatic update schedule rather than assuming a standard interval. If an update fails, check your plan status, make sure the link was copied in full, and verify your local network. Avoid adding the same subscription repeatedly, which can clutter the list.

Your subscription link contains information needed to access your account’s route resources, so protect it like your account credentials. Don’t forward it to others or include it in screenshots. Anyone with the link may use those resources, consuming data and making troubleshooting harder. If you suspect it has been exposed, check the user panel for an option to reset the subscription. If one is available, follow the on-screen instructions; otherwise, contact support through a ticket. After resetting, replace the old link on each device and update the configuration. Deleting a public post won’t invalidate a link that someone has already copied. Before sharing a screenshot, hide the link and any credentials it contains.

Disconnect the client and make sure your local network can access websites you normally use. Then reconnect to a route and test your browser and the affected app separately. A “connected” status usually means the connection or proxy feature has started; it doesn’t confirm that the entire path to a particular site is working. Next, check your plan status, remaining data, active configuration, and current route. Update the subscription and try another route. If only one site fails, troubleshoot that app or site first. If nothing works, check your system proxy settings, tunnel permissions, and whether other proxy tools are running at the same time. Change one setting at a time to identify the cause.

Some apps don’t follow the system proxy or use their own connection method, so a working browser doesn’t mean every app uses the same route. Check whether the client is in rule mode, whether the service is set to connect directly, and whether the routing rules are up to date. If the client offers a tunnel or an option to handle app traffic, read the platform instructions before enabling it and check the required system permissions. Work devices may have policies that restrict these changes. Save the original settings before making changes, then undo anything you don’t need after testing. Don’t disable device security features as a substitute for troubleshooting.

Keep the client configuration unchanged and switch to another available local network. See whether the disconnections continue. Then stay on the same local network and try a different route to compare the results. This helps you isolate the local connection from the remote route and is easier to assess than changing protocols, rules, and system settings at once. Device sleep, network changes, and background permissions can also affect connections; on mobile devices, check whether the system is pausing the client. If you submit a support ticket, include when the disconnections occur, your platform, route name, and any error message. Note what changed when you switched networks or routes.

First check whether other websites are accessible, then confirm that the app or browser is actually using the current route. If the sign-in page loads but you can’t continue, the cause may involve the service’s supported regions, your account status, browser session, or the platform’s own risk controls. An error message alone doesn’t prove the route has failed. Try another route while keeping the exit region the same, and check whether your routing rules are missing relevant requests. If needed, test in a separate browser session. Refer to the platform’s official guidance for supported regions and usage requirements. Changing routes can’t replace the account eligibility or service access required by the platform.

Pause large local transfers, cloud sync, and other tasks first to make sure your local connection isn’t saturated. Then compare routes in the same app. If another route clearly performs better, keep testing it during the times you normally use the service. If all routes are slow, check both your local network and the target service. Leave protocol changes until later, and make sure your client supports the configuration you choose. Don’t change everything at once. For video, check whether playback stays smooth; for work, look at call and request stability. A single latency reading can’t tell you how the whole connection will perform.

These terms describe route paths, not a speed ranking that applies to every network. A direct route takes a more straightforward path, but performance depends on the actual routing between your local network and the exit. Transit routes pass through an intermediate access point, so performance depends on both the initial connection and the onward path. An IEPL route uses a dedicated transmission path, but local access and the target service still matter. Start by choosing the exit region you need, then compare connection stability, loading, and sustained transfers in the apps you use. Don’t judge by route name or geographic distance alone. See the Routes and Protocols page for more detail.

VPNMove covers 90+ countries / 220+ routes. Check the regions and route types on the Routes page, then use the current availability shown in the user panel and client to make your choice. If a service has regional requirements, read its official guidance and choose a route in a supported region rather than simply picking the nearest exit. Coverage gives you route options; it doesn’t mean every route can access all region-restricted content. When troubleshooting, note the exit region, route name, and any message from the service to help distinguish routing issues from region detection or account permissions.

Web browsing, video playback, and file downloads place different demands on a connection. A webpage loading shows that basic access works, but sustained transfers can also be affected by your local Wi-Fi signal, remote content delivery, the destination server, and route congestion. Compare the same content on different routes, check whether the slowdown affects only one site or type of task, and see whether other devices are using your network. For video, temporarily lower the resolution and check whether buffering improves. For downloads, check the file source’s transfer performance. A one-time test isn’t a guaranteed bandwidth commitment, and low latency alone doesn’t guarantee fast sustained transfers.

Monthly plans: ¥9.9/month for 60GB · ¥18/month for 250GB · ¥28/month for 500GB. Data packs: ¥158 for 300GB · ¥358 for 1000GB · ¥658 for 3000GB; data lasts until used and never expires. If you use the service regularly and prefer a monthly data allowance, compare the monthly plans. If your usage is less predictable, consider a data pack. Check your account’s current usage and expected needs before choosing; the number of devices doesn’t directly determine how much data you’ll need. See the Plans page for full pricing and billing details, then confirm the plan type and order details in the user panel.

Monthly plan data resets each month on the date you activated the plan. If you upgrade partway through, the price difference is prorated for the remaining days. The reset doesn’t happen on the same date for everyone, and you shouldn’t estimate the upgrade outcome from the data difference alone. To upgrade, check the available plans and order details in the user panel, then confirm the updated status before proceeding. Data packs last until used and never expire; they don’t reset like monthly plan data. If the panel shows something unexpected, keep the relevant order details and submit a ticket with your original plan, the change you made, and what the panel currently shows.

Supported payment methods: Alipay / WeChat Pay / USDT. Before paying, check the plan, amount, and payment method in your order, then follow the instructions on the payment page. For transfers, use the details shown on the current order page; don’t rely on payment details forwarded by someone else. If your plan status hasn’t changed after payment, check the relevant order in the user panel before trying to pay again. If you still need help, submit a ticket with the order ID, payment method, and a screenshot of the payment result. Hide any account details that aren’t relevant to the issue. A closed payment page or failed redirect doesn’t necessarily mean the order was canceled or that you need to pay again.

VPNMove offers refunds within 60 days; see the Terms of Service for the specific eligibility requirements. To request a refund, sign in to the user panel, open a support ticket, and include the relevant order details. You can also mention any questions about payment status in the same ticket. Before submitting, check that the order belongs to your current account. Don’t share payment records, passwords, or full subscription links publicly. If you’re temporarily unable to connect, try the troubleshooting steps on this page or ask about the refund process directly; there’s no need to make repeated payments to try to restore service. Track your request through ticket replies and the order status; no processing or arrival time is guaranteed.