Subscription & Connection Help

No email address is required. Create an account with a username and password, and store both securely—ideally in a trusted password manager rather than relying on your browser’s current sign-in session. Your account password and subscription link serve different purposes: the password gets you into the dashboard, while the link lets your client retrieve route configurations. Never share your full password, subscription link, or screenshots containing account credentials when asking for help. If you can’t sign in, check your username, keyboard input settings, and any spaces in your password, then use an available account support option in the dashboard.

Sign in to the user dashboard and check your subscription details. Then open the subscription or configuration manager in your client, select the existing configuration, and update it. If route names or configurations change, update the existing entry instead of repeatedly adding the same subscription. If your client says the old address is invalid, verify the current address in the dashboard and replace the saved one. If the dashboard offers a reset option, update the link on your other devices as well. Your subscription address is an account credential—don’t post it on public forums, shared documents, or public speed test sites.

There’s no device limit for simultaneous connections, so switching devices alone doesn’t mean you need to buy again. Sign in to the user dashboard on your new device, download the client for that platform, and import your subscription configuration. VPN83 supports Windows / macOS / iOS / Android / Linux. Sign in to download the client for Android, Windows, macOS, and Linux; subscription details are available after sign-in. Available options for iOS depend on your active plan and are shown in the dashboard. Once you’ve moved over, remove saved subscription and account details from any old device you no longer use, especially before handing it to someone else.

A successful import only means the client received the configuration entry; it doesn’t confirm that route details were retrieved. First, check your plan and data status in the dashboard. Then make sure your client has selected the subscription you just imported and run an update manually. When copying the address, check for extra spaces, line breaks, or truncation, and don’t use the dashboard page address as the subscription address. If the update fails, save the error message and check that your local network can reach the dashboard. If the issue persists, open a support ticket with your device platform, the client’s error message, and the steps you’ve tried. Hide the full subscription address in any screenshots.

Disconnect the client and confirm that your local network can open familiar websites. Then reconnect and try other pages. If your local connection works, check that you’ve selected an available route and enabled the system proxy or connection mode required by your client. Try another route in the dashboard and see whether all websites fail or just one. Change one setting at a time so you can identify the cause. If the problem continues, note the exact error, when it occurred, and what changed after connecting, then send those details in a support ticket.

Your browser and other apps may not use the same network settings. Some apps follow the system proxy, while others use their own connection method or are set to connect directly by your client’s routing rules. Check whether the app has its own proxy settings, then look in your client’s rules or connection logs for requests from that app. If your client supports other connection modes, check its documentation for the required permissions and settings. After making a change, quit and reopen the app, then test the connection again. A working browser doesn’t mean every app is using the proxy; the target platform’s account or regional rules may also affect access.

First, confirm the update finished and check whether your selected route is still listed. An update may make a previously saved selection unavailable, so try selecting another route and reconnecting. If the client reports an invalid configuration format, don’t delete fields you don’t understand. Check that the subscription entry matches your client in the dashboard, then retrieve the configuration again. Also check whether another proxy or network management tool is running, as it could conflict with the settings. If you open a support ticket, say whether the issue began before or after the update and include a redacted error message to help distinguish a retrieval problem from a connection problem.

Sign in to the user dashboard and open the support ticket form. Include your device platform, client name, local network type, selected route name, when the problem occurred, and the full error message. Also say whether your local connection works, whether other routes connect, whether other apps are affected, and what you’ve already tried. These details help reduce follow-up questions and make it easier to reproduce the problem. Before sharing screenshots, hide account credentials, the full subscription address, and sensitive payment information. Don’t publicly share configuration files you haven’t checked. If the issue only affects a particular website, name the site and describe what happens instead of simply saying it doesn’t work.

Pause downloads, cloud sync, and other tasks using your local connection, then check whether both regular websites and the affected app are slow. If only one app is affected, try another route in the same region while keeping your account region and other settings unchanged. This helps show whether the current path is congested. If everything is slow, compare other regions that suit your needs. Peak-hour performance depends on your local connection, international routes, and the destination service, so a route name alone can’t predict the result. Note when slowdowns occur and which routes still work, and keep a suitable alternative for your network. A single test isn’t a guarantee of future performance.

VPN83 covers 90+ countries / 230+ routes. Check the user dashboard for currently available regions and route types. IEPL, transit, and direct routes describe different ways of routing traffic. The label alone can’t tell you how a route will perform on your network, and not every type is available in every region. First check which regions the destination service supports, then compare connection reliability and performance on the available routes. For work, pay attention to whether sessions disconnect; for video, check for repeated buffering. Don’t choose based only on distance, labels, or the number of entries—keep the routes you’ve tested successfully.

Speed tests usually measure the connection between your device and a specific test server. Video and meeting services may use different destinations and routes. Video playback can also depend on resolution, caching, and the platform’s content delivery; calls are more sensitive to connection fluctuations and packet loss. Test directly in the affected app. Keep the same route and settings at first, check whether other content or calls are affected, and then try another route. Pause large background transfers and compare Wi-Fi with other available connection types. If only specific content fails, check the platform’s status and your account permissions too—bandwidth isn’t always the cause.

Frequently switching regions isn’t a good default fix. AI tools and streaming services may consider your exit region, account details, browser state, and their own policies. A working connection doesn’t guarantee that your account is eligible for access. Check which regions the service currently supports, choose a suitable exit region, and keep your setup consistent where possible. If you see a region warning, note the exact message and check whether it relates to account permissions, content availability, or the network route before making changes. Don’t change account details and network settings at the same time just to keep retrying. VPN83 provides international routes, but can’t replace a third-party platform’s eligibility checks or guarantee that specific content will always be available.

Monthly plans: ¥9.9/month for 60GB · ¥18/month for 250GB · ¥28/month for 500GB. Data packages: ¥158/300GB · ¥358/1000GB · ¥658/3000GB. Data packages remain available until used and never expire. If you use the service regularly, choose a monthly plan based on your actual usage. If your usage is occasional, compare the data packages to see whether one better suits your habits. Check usage in your client or dashboard before choosing; browsing time alone isn’t a reliable estimate, since video, file transfers, and text pages use very different amounts of data. See the plans page for full pricing and billing details, and check your order status in the dashboard.

Monthly plan data resets each month on your activation date. If you upgrade partway through, the price difference is prorated based on the remaining days. Check your activation details, data status, and order history in the dashboard; don’t assume every account resets on the first day of the calendar month. Data packages work differently: they remain available until used and never expire. Before upgrading, review your current plan and the details shown in the dashboard, then confirm before proceeding. If you have questions about remaining days or changes to an order, mention the relevant order in a support ticket. Don’t add monthly plan data and data package balances together to estimate your available data; use the balance shown in your account.

VPN83 accepts Alipay / WeChat Pay / USDT. Start payment from the order flow in the user dashboard. If your plan status hasn’t updated after payment, check the order status in your order list, then review your plan and subscription details. This helps avoid paying twice because a page hasn’t refreshed. If the payment page and dashboard show different information, keep your order details and payment result, then explain the issue in a support ticket for review. Hide sensitive payment details in screenshots and never post credentials publicly. Refer to the current order page for the amount, payment method, and order status. If the page appears to be in error, check the original order before taking further action.

VPN83 offers a 14-day no-questions-asked refund. To request one, sign in to the user dashboard, open a support ticket, explain that you’re seeking a refund, and include the order details needed for review. Before submitting, check your order history and terms of service to make sure you identify the right payment. If you’re also experiencing connection issues, you can include what you’ve tried to help support understand the situation, but there’s no need to write a technical report. The terms of service govern refunds. Follow the ticket for updates; this page doesn’t promise a specific processing time, and payment screenshots that haven’t been verified don’t replace the order record in your account.