Subscription and connection FAQs

No email address is required. Create an account with a username and password. After opening the user dashboard, keep your account details somewhere safe, then check the plans and client downloads that suit your needs. Choose a username that is distinct from public usernames you use elsewhere, and avoid reusing passwords. Since account creation does not require an email address, plan ahead for how you will regain access before logging out. If you run into an account issue, keep the session open on a device where you are already signed in and describe the problem in a dashboard ticket. Share only the account details needed to investigate; never send your password or full subscription link.

Sign in to the user dashboard and check your account’s subscription details. In your client, open subscription management, find the VPNOC profile, and update it. Once the update finishes, check that the route list has refreshed, then connect to a route. Routine refreshes usually do not require deleting the entire profile. Use the client’s built-in update option first to preserve your local rules. Reimport only if the dashboard has generated a new subscription address, the old one no longer works, or the client cannot recognize the profile. Subscription links contain access credentials: use them only in your own client, and never show the full link in screenshots, support tickets, or public discussions.

There is no device limit, so you do not need to choose a new plan just because you have changed devices. Sign in to the same account on your new device, download the client for that platform from the user dashboard, and import the account’s subscription details. Data usage is still based on your selected plan; unlimited devices does not mean unlimited data. During the switch, first confirm that the route connects and your usual apps work on the new device, then remove the configuration from the old one. If you no longer control the old device, sign out and remove the subscription. If you suspect the link has been exposed, check whether the dashboard offers a reset option, then update the configuration on any devices you still use.

VPNOC supports Windows / macOS / iOS / Android / Linux. Download clients from the user dashboard—not from chat attachments or unverified installers. Sign in to download clients for Windows, macOS, Android, and Linux; the iOS download requires an active plan. You also need to sign in to access subscription details. After installation, grant any network permissions requested by the client, then import your subscription and choose a route. If the system says permission was not granted, check your system settings rather than reinstalling repeatedly. For platform-specific steps, see the Guides and follow the client instructions currently shown in the dashboard.

Disconnect first and check that your local network can open the websites you normally use. If the local network itself is having issues, resolve those first. Then reconnect and check that the system proxy or network-routing permission is active. Use an IP-check page to see whether your exit IP matches your current routing rules. A connected status confirms that the connection process completed; it does not confirm that apps can reach their destinations. If your exit IP has not changed, check whether another network tool is overriding the proxy settings. If it has changed but the site still will not load, check DNS, browser cache, and the destination service’s status. Change one setting at a time so you can identify what actually helps.

Browsers and other apps may use different ways to connect. Some follow the system proxy; others connect directly or may be routed locally by your current rules. First check the client’s rule-match details or connection log to see where the app’s requests are going. Then check whether the app has its own proxy settings and whether the client has the required network-routing permissions. If the client offers a global mode for troubleshooting, switch to it temporarily to test, then restore your usual rules. Avoid running multiple proxy tools at the same time. If the app still has problems, describe its name, your platform, what happens, and which settings you have tried in a support ticket.

Sign in to the user dashboard and check that your account and subscription are in good standing. Then confirm that your current network can reach the dashboard. When copying the subscription address, make sure you have not missed any characters, added spaces, or copied a webpage URL instead. In the client, manually update the relevant profile and note whether the error indicates a download failure, a parsing error, or an account issue. For download failures, check the network and address; for parsing errors, check that the client supports the configuration. Do not delete an old profile that still works. If you need to import the subscription again, save any local rules you need first. You can include the error message in a support ticket, but conceal subscription credentials and other sensitive account details.

When a device wakes from sleep or switches between networks, an existing connection may retain outdated network state. First confirm that the new local network is working, then disconnect and reconnect in the client. If that does not help, quit and reopen the client, and check for leftover system proxy settings. On mobile devices, also check whether the system is restricting the client’s background activity. While troubleshooting, avoid repeatedly switching routes and protocols; otherwise, it can be hard to tell whether the cause was a network or configuration change. If the issue occurs only on one network, compare it with another and include the trigger, platform, and error message in a support ticket.

First check whether downloads, cloud sync, or other devices are using up your local network bandwidth. Then compare your usual browsing with the VPN disconnected. If your local connection is working normally, try another route in a nearby region and test the same destination again. Compare page response, video buffering, and connection drops. Peak-time slowdowns may be caused by your local connection, congestion along the route, or load on the destination service; a single speed test cannot identify the cause. Keep the app, network, and content as consistent as possible, and avoid changing protocols and routing rules at the same time. If the problem persists, note when it happens, the route name, and the app involved so support can investigate.

VPNOC covers 110+ countries and 250+ routes. Start with the region required by your destination service, then compare how routes to that region perform from your network. A nearby location can mean a shorter path, but it is not necessarily faster on every network; the destination’s location and the routing along the way also matter. For everyday use, keep a preferred route and a backup, and compare them with the same app if something goes wrong. If a service requires a specific region, check its own regional rules rather than assuming the route location determines where your account can be used. See the current route list in the dashboard or client.

Direct, relay, and IEPL routes describe different network paths and transport methods, not comparable speed tiers. A direct route takes a more straightforward path, with performance affected by your local connection and international routing. A relay route forwards traffic through an access node, so results depend on both the access segment and the onward path. IEPL refers to a dedicated transport path, but real-world performance still depends on your local network and the destination service. Choose routes based on page response, connection stability, and whether your apps work—not just the route label. Protocols describe how a connection is made; route types describe its path. For more on the trade-offs, see the protocol reference.

A speed test shows how data transfers to its test server; it cannot represent every app. Video performance can also depend on content delivery routes, playback buffering, and regional rules set by the service. AI tools may be affected by long-connection stability, account status, and the service’s current load. First check whether other websites work normally on the same route. Then note whether the problem occurs during sign-in, page loading, playback, or an ongoing response. Verify streaming access and available content in practice; a route’s location does not guarantee access. To troubleshoot, keep the destination app fixed and compare routes and routing rules separately. This helps distinguish a service-side issue from a local connection problem.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on the day your plan starts, not at the beginning of each calendar month. Before choosing, consider how often you stream video, sync large files, or browse the web; you do not need to choose a higher tier just because you use more devices. If you upgrade partway through a plan, the price difference is prorated against the remaining days. Check the billing details shown in the dashboard before proceeding. If you have questions about your current billing period or data usage, review your account overview and order history, then include the relevant order details in a support ticket. Do not rely on the client’s local usage estimate to determine billing.

Data packs cost ¥158 for 300GB, ¥358 for 1000GB, and ¥658 for 3000GB. They remain valid until used and never expire. Unlike monthly plans, which reset data each month on the plan’s start date, data packs suit people with variable usage who prefer to use data as needed. Before choosing, consider whether you need a recurring monthly allowance or prefer to keep unused data available over time. A data pack does not issue the same allowance again each month. If your account includes different product types, check the dashboard for details on your current plan and data. If you have questions, confirm them through a support ticket rather than assuming how products stack, how data is deducted, or how plan changes work.

We accept Alipay / WeChat Pay / USDT. Before paying, check the order, plan, and amount in the user dashboard, then follow the instructions on the current order page. After payment, return to the dashboard and check your order history and account status. If the status has not updated, keep your payment confirmation and order number; do not repeatedly create the same order or pay again. In a support ticket, include the plan you chose, payment method, and any message shown on the page. Attach the relevant payment confirmation and conceal any sensitive details that are not needed for verification. Use your order record to help check the payment. Never share your account password or subscription link, and do not send them to unverified chat accounts.

VPNOC offers a 60-day no-questions-asked refund. Before requesting one, you can review the refund terms in the Terms of Service. Then sign in to the user dashboard, open the support ticket page, and submit your request with the relevant order number and payment method. If your account has multiple orders, specify which one the request concerns so it is not confused with a connection troubleshooting issue. You can describe any connection problems to help us investigate, but a speed-test screenshot is not required to request a refund. Keep a record of the ticket and add any necessary details to the same thread. Check the dashboard for updates; do not assume or promise a specific refund processing time or method.