User Guide / COMPLETE GUIDE

CitiVPN Complete Guide

Plans, subscriptions, apps, and connection maintenance. Read from start to finish, or use the contents to find the issue you’re dealing with.

90+ countries / 190+ routes Unlimited devices No email address required 7-day no-questions-asked refund

Just want to get connected? Start with the Getting Started Guide. It covers the essential steps; this guide explains how to make decisions at each stage, account for platform differences, and handle exceptions. Use it as a reference during setup or whenever questions come up later. App interfaces may change, so follow the options and instructions currently provided in the panel.

About cross-border network services

What the service, account, and app each do

CitiVPN is a subscription service for cross-border network access, with 90+ countries / 190+ routes and support for Windows / macOS / iOS / Android / Linux. Using the service involves two distinct parts: account management and connecting your device. Your account stores plan, order, and subscription details; the app reads your subscription, lets you choose a route, and handles the network requests you want routed. Browsing the marketing site does not change your device’s network route, and paying for a plan does not automatically connect a device that has not been configured. Understanding this distinction makes the steps ahead easier to follow.

The user panel is where you manage your account, not where you turn on a connection. Sign in to check your plan, get your subscription, download a client, or submit a support ticket. Check the actual connection status in the app on your device. The routes shown in the app depend on your account benefits and may also depend on whether the configuration is up to date. “The panel opens,” “the subscription loads,” “the app is connected,” and “the target site works” are separate steps. Check each one when troubleshooting rather than treating success at one stage as proof that everything is working.

A route’s location doesn’t guarantee access

A route’s location is the network egress point used when your requests travel through that route. City names such as Tokyo, Hong Kong, and Singapore indicate the direction of the egress point; they do not change your device’s physical location or the region listed in your account with another service. Access also depends on the target platform’s service areas, account eligibility, browser session, and local network conditions. After choosing a location, verify the result in the app you intend to use. This is particularly important for AI tools and streaming services: a route name alone cannot confirm that every feature will work.

IEPL, transit, and direct routes describe how network traffic is carried; they are not a simple ranking of fixed speeds. Your experience also depends on your local connection, distance to the egress point, destination, and current network conditions. Nearby routes are reasonable starting points, but geographic proximity does not necessarily mean a shorter end-to-end path. Choose a location based on the service you want to use, then compare the available routes there. The Routes page explains route types and location choices. The current list of available routes is shown in the user panel and your updated subscription.

Decide what you need before setup

Before getting started, identify your main goal: browsing international websites, working across borders, using AI tools, or streaming. Your needs affect location choices, data estimates, and routing rules. For example, regular streaming makes data use a key consideration, while work use may depend on whether your everyday apps follow the intended route. Avoid changing a lot of network settings at once. First establish a basic setup that works, then fine-tune it as needed. If something goes wrong, it will be easier to return to a known working configuration.

Quantum encryption is part of CitiVPN’s security messaging, but an encrypted connection does not address every risk on your devices. Keep your operating system, browser extensions, account passwords, and the websites you use secure as separate concerns. Protect your subscription details too: they give a client access to your configuration. Unlimited devices means you can set up the service on your own devices; it does not mean you should share your subscription publicly. Keep these limits in mind: a network tool is no substitute for account security, platform eligibility, or device maintenance.

Choose a plan based on your usage

The key difference between monthly plans and data packs

Choose a plan based on how you use the service, not by starting with the most expensive option. A monthly plan suits regular use and a monthly data allowance; a data pack suits irregular use if you’re happy to keep an eye on your remaining data. CitiVPN monthly plans reset their data on the monthly anniversary of activation. Data packs last until the data is used and never expire. These plans have different time rules, so don’t compare data amounts alone or assume a data pack renews each month with the same allowance.

Prices and data allowances, as listed
TypePriceDataHow it works
Monthly plan¥9.9/month60GBResets monthly on the activation date
Monthly plan¥18/month250GBResets monthly on the activation date
Monthly plan¥28/month500GBResets monthly on the activation date
Data pack¥158300GBUse it until it runs out; never expires
Data pack¥3581000GBUse it until it runs out; never expires
Data pack¥6583000GBUse it until it runs out; never expires

To estimate your data needs, group your main activities by frequency and data intensity. Browsing and document collaboration use data differently from video calls; streaming, file transfers, and background syncing can also consume significant amounts. Start by checking your devices’ network usage records to see which activities need to use an accelerated route, then refine your estimate based on the account usage shown in the panel. Don’t extrapolate long-term needs from a brief trial or estimate data solely from the number of devices.

With multiple devices, track total account usage

Unlimited devices refers to the number of devices you can connect, not unlimited data. When your computer and other devices are in use, check the account’s data status rather than assuming each device gets the plan’s full allowance. Whether large file syncs, cloud backups, and app updates use a route depends on the client mode and rules. If usage changes significantly, check recent activity and routing settings first. That is more likely to explain the change than simply switching routes.

When you upgrade mid-cycle, the price difference is converted into remaining days. Before submitting a plan change, check the target plan, amount due, and change details in the panel. Don’t assume an upgrade starts a full new billing period or that data resets on the first of each calendar month. For details not covered here, such as how simultaneous plans are handled or how benefits appear after a change, follow the current panel instructions. If anything is unclear, confirm it through a support ticket before placing the order.

Check payment, refunds, and your needs together

Payment methods: Alipay / WeChat Pay / USDT. The refund policy offers a 7-day no-questions-asked refund. Before choosing, check the full pricing page and compare data, billing method, and your usage pattern side by side. For a closer look at when a monthly plan or data pack may suit you, read Data Packs vs. Monthly Plans. The goal isn’t to find one option that suits everyone, but to avoid a mismatch between your needs and how you’re billed.

Before paying, check the order itself rather than relying on what you remember from the marketing copy. Make sure you’re signed in to the account you intend to use, the price and plan name match your selection, and the payment method works for you. Don’t create multiple identical orders just to get the payment through. If you’ve started a payment but the status hasn’t changed, keep the order details and follow the checks in the next section. This helps prevent duplicate actions and makes it easier to explain exactly where things went wrong if you need support.

Create an account and complete your order

Save your account details, then open the panel

CitiVPN doesn’t require an email address. Create an account with a username and password using the free trial. Fill in the fields on the panel and confirm. Choose a username you can recognize that doesn’t reveal too much personal information. Use a unique password and store it in a trusted password manager. Because no email address is required, you provide less information when creating an account; don’t assume that account recovery necessarily works by email.

After submitting, make sure you can open your account page before choosing a plan. If your browser fills in an old username, check that you’re using the intended account so the order doesn’t end up in the wrong one. On a shared device, don’t leave your account signed in; sign out of the panel when you’re done. If you forget your password or can’t sign in, use the recovery options and help instructions currently shown in the panel. Never post your password, full subscription details, or payment credentials in public comments to ask for help.

Check the order and payment separately

Choose a plan in the plans section of the panel, then check the plan, data, amount, and billing method again at checkout. Clicking the payment button starts the payment process; it doesn’t mean the order is complete. When you return from the payment page, check the order and plan status in your account. A payment provider’s transaction notice, the order record in the panel, and the benefits applied to your account are related, but each is a separate way to verify what happened.

If the payment window closes, the page reports an error, or your network changes, don’t immediately try the same payment again. Reopen your order list and check whether the order is still pending or has a confirmed result. Keep the transaction record from your payment provider for reference. If you send a screenshot to support, hide personal details that aren’t relevant to the issue. If the order status hasn’t changed, explain what you’ve already tried in a panel support ticket and ask support to check it. Don’t assume a payment failed just because the page hasn’t refreshed yet.

Set up the client after your plan is active

Once your plan is available, check the current plan and data status in your account overview before downloading a client or getting your subscription. For a monthly plan, note that data resets monthly on the activation date; for a data pack, check the remaining data. The overview is the first place to confirm your benefits are ready. If it still shows no available plan, repeatedly importing your subscription usually won’t resolve an order issue. Confirm the account and order first, then set up your device so the troubleshooting steps stay separate.

For support, use support tickets in the user panel. Describe the order issue with the plan you chose, the status shown in the panel, the payment method, and the step where things stopped matching your expectations. You can include identifying details that the order page allows you to copy, but never send your account password. Keep each ticket focused on one issue and add updates as needed. Mixing unrelated connection problems, payment questions, and app installation issues into one long message makes it harder for support to identify what needs attention.

To request a refund, check the Terms of Service under the 7-day no-questions-asked refund policy and submit your request through the panel. Having your order details and a description of what happened ready will help identify the right transaction. Deleting a client configuration, stopping a connection, or closing your browser does not count as a refund request or replace the account process. By the end of this section, you should be able to answer three questions: which account you’re using, whether the order is complete, and whether the panel shows your plan as available.

Get and protect your subscription

A subscription is not an installer or your sign-in password

Your subscription gives a client access to routes and related configuration. The installer puts the app on your device; your account password gets you into the panel; the subscription gives the app the configuration associated with your account. Don’t use one in place of another. If the app is installed but the route list is empty, you may not have imported a subscription yet. If you’ve copied a subscription but can’t install the app, that’s a different issue. Identify which item you need before choosing an input field, and don’t mistake the panel address for a subscription URL.

Open the account overview or subscription section in the panel, then choose an import method that works with your client. If one-click import is available, your browser may ask permission to open an app on your device. Confirm it’s the client you installed before proceeding. If the app doesn’t open, that doesn’t necessarily mean the subscription is invalid. The system may not have an app association set up, or the browser may have blocked the request. Check the panel for a manual copy option instead of repeatedly creating accounts or placing new orders.

Check the item and format before importing

For manual import, look in the client for an option such as Configuration, Subscription, or Import from URL. The wording varies by app, but the goal is to have it read the subscription—not to fill in a server’s details one field at a time. Before pasting, make sure the clipboard contains the subscription for your current account, without extra spaces, line breaks, or text added by a messaging app. The URL may include parameters that identify access rights. Don’t remove or change any part just to make it look neater.

If the panel offers formats for different clients, choose the one that matches the app you installed. The same file extension doesn’t guarantee that the contents are compatible; some apps accept a subscription URL, while others need a specific configuration format. If you see a format error, check the panel’s selection and the client name before changing any protocol fields. Don’t assume that third-party tools not explicitly supported by CitiVPN can use the same content. Check compatibility guidance first if you need to adapt it.

Tell apart update, connection, and access issues

Updating a subscription reloads the configuration; connecting uses the routes already loaded to make network requests. Either action can succeed or fail independently. If an update fails, the client may still show previously saved routes. If a connection fails, the subscription may still be fine. Note whether the error occurred during the update or connection step. If the list changes after an update, recheck the selected route and routing rules. A populated list alone doesn’t confirm that requests are still using the intended egress point.

Treat your subscription URL as sensitive. Don’t put it in public notes, code repositories, screenshots, or online conversion tools. To use it on another device of your own, sign in to the panel on that device and get the subscription there, then follow the platform-specific steps. If you think the subscription has been exposed, check whether the panel offers a reset or replacement option. Afterward, you may need to update your personal devices; follow the instructions shown on the page. Don’t reset it repeatedly without checking what the option does, as that can leave your devices with different configurations.

Give the configuration an easy-to-recognize local name, such as “Daily work,” to distinguish it from other entries in the client. The name is for your own organization; it won’t change your plan or route access. You can note any local settings you need before making changes, but keep those notes private too. By the end of this section, you should know how to find the right subscription in the panel, import it into your client, and check the format, account status, and network first if loading fails—rather than changing every setting at random.

Import on each platform

Get the right client from the panel first

Download clients through the download section in the user panel. Sign in to get a client for Windows / Android / macOS / Linux. A valid plan is required for iOS. You must also sign in to get your subscription. Don’t install an app with a similar name from search results and assume it works with the panel’s configuration. The steps below cover shared setup tasks and permission checks for each operating system. Actual button names, features, and import options depend on the software and instructions currently provided in the panel.

System settings to check after installation
PlatformWhat to checkWhere to verify
WindowsSystem proxy and app-specific proxy settingsClient status and target app
macOSSystem permissions and menu bar statusNetwork settings and target app
iOSValid plan and permission to configure network settingsClient and system connection status
AndroidNetwork access permission and background restrictionsClient status and foreground app
LinuxDesktop proxy settings and separate terminal configurationTest your browser and terminal separately

Windows: check which traffic is routed after import

Install and open the Windows client provided in the panel. Import your subscription, wait for it to load, then choose a configuration and route. If the client offers a system proxy toggle, enable it as instructed and check that your browser can open the target website. A system proxy doesn’t necessarily cover every app: some programs use their own proxy settings, while others don’t use the system proxy. A working browser doesn’t prove that your work apps, games, or command-line tools use the same route.

If you need broader traffic coverage, first check whether the client offers the relevant mode and whether it requires system permission. Don’t enable multiple network tools without understanding what they do. Before closing the client, check that the system proxy is restored as expected. If the client is closed but your browser can’t access regular websites, check whether your system still points to the local client as a proxy. For more on your options, see Windows: Global Proxy vs. Split Tunneling.

macOS: check permissions and background status

On macOS, open the client download section and follow the system prompts to install the app. If it asks for network-related permission on first launch, check the app’s source and why it needs access before allowing it, following the panel’s instructions. After importing your subscription, make sure the configuration is enabled; don’t stop at the “import successful” message. Use the menu bar icon, main window, and system network status to cross-check, then verify the actual route in the app you want to use.

Closing a window doesn’t necessarily quit the app, and quitting the app doesn’t necessarily restore every system network setting. If something goes wrong after waking from sleep or switching networks, first check whether the client is still running, then try reconnecting. Don’t overwrite settings left by other network tools; note the current setup and make changes one at a time. On a managed work device, follow your organization’s requirements. Don’t change unfamiliar system security settings just to get connected.

iOS: check your plan before allowing a connection

You need a valid plan to get the iOS client. Open the download section in the panel and follow the instructions there; don’t use download links from unverified sources. After installing the app, import your subscription. If iOS asks for permission to add a network configuration when you first connect, check the app name and purpose before confirming. If another connection configuration is already on your device, check which one is active in Settings. A connection indicator alone doesn’t prove that the active configuration belongs to CitiVPN.

After returning to the app from the import flow, check the route list and selected location, then open the service you want to use. If the app keeps loading after switching between Wi-Fi and mobile data, first check that the device has a working internet connection, then reconnect to the selected route. Don’t delete every network configuration and hope for the best; keeping useful status information makes diagnosis easier. If the target app has an old session, close and reopen it after confirming the connection, then check again.

Android: check connection permissions and background limits

Sign in on Android to get the client. After installing it, import your subscription, choose a configuration, and allow the network connection when prompted by the system. Background management varies by device. If the client works in the foreground but disconnects easily when you switch apps, check whether the system restricts its background activity. Make changes based on your device’s documentation and what you’re seeing. Don’t turn off every battery, security, or permission setting across the board.

If the system says another network service is in use, identify which app is running before deciding which one to keep. After connecting, test your browser and everyday apps separately to check that routing rules aren’t excluding the apps you need. After restoring an old configuration or moving to a new device, your subscription may be imported but not enabled. Check which configuration is active, not just whether a file is present. When you exit the client, also confirm that the system connection has ended.

Linux: test desktop apps and terminal tools separately

Sign in on Linux to get the client. Follow the installation instructions currently provided in the panel. Don’t copy an entire command from instructions for a different distribution or environment. After importing your subscription, test with a desktop browser first, then check terminal apps separately. Desktop proxy settings, environment variables, and app-specific proxy options may all be independent. If the browser works but a terminal tool doesn’t, check whether that tool is reading the expected settings.

If you need to enter a local proxy address manually, get the settings from the running client; don’t copy a fixed port number from the internet. Before configuring a service to start automatically, system-wide routing, or elevated permissions, establish a working baseline in the default mode and then follow the client documentation one step at a time. When moving between platforms, reuse only the subscription option suited to the new system. Don’t copy all local settings from another operating system, as they may include invalid paths, permissions, or network options.

Verify your connection in stages

Check your local network before testing the routed connection

Start verification with the step closest to your device. Make sure your current network works first. If a public Wi-Fi network has a sign-in page, complete that step according to the venue’s requirements. Then open the client and check that the subscription has loaded, the configuration is enabled, and the selected route suits your needs before connecting. If the underlying network isn’t available, repeatedly switching international routes is unlikely to help. Separating local access issues from route issues can save you from changing settings that were already correct.

A connected status in the client is the start of your checks, not the final result. Open a regular website first to make sure requests go through, then try the service you actually need and see whether you can sign in and complete the main task. If regular websites work but one platform doesn’t, narrow the issue down to its supported regions, your account eligibility, the app session, or routing rules rather than assuming every route is down. Keep the device, network, and destination the same while testing so you can compare results.

Check the egress point and the app’s route

Use the egress IP lookup to see the egress information for your browser’s current requests. It reflects the browser’s route, which may not be the same route used by every app. Location databases can also disagree. If the lookup fails, don’t use that page alone to decide that the client is disconnected; check other regular websites and the app you actually use too. For work software and terminal tools, test in their own environments.

With rule-based routing, some requests going direct while others use your selected route can be expected. The key is whether that matches your settings. If a browser and an app behave differently, check the client’s connection log or rule-match details, if available, to see which route the request took. Don’t guess based on the app’s name; one app may contact several domains. Logs can help locate the issue, but check screenshots for account details, browsing activity, or sensitive links before sharing them.

Narrow down the issue by what you observe

If a subscription won’t update, first check that your account is active, the subscription format is correct, the full address was pasted, and your current network can reach the panel. If the list loads but none of the routes connect, check system permissions, proxy mode, and possible conflicts with other network tools. If only one route has an issue, compare it with another option in the same location. If regular browsing works but an AI tool or streaming service doesn’t, check the platform’s regional policies, your account eligibility, and the current session.

Find the failing stage before changing settings
SymptomCheck firstAvoid for now
Subscription won’t updateAccount status, format, and loading pathDeleting every client configuration repeatedly
Browser and app behave differentlySystem proxy, app proxy, and rule matchesAssuming the chosen location is the problem
Connection drops after switching networksLocal network access and client connection statusTrying the payment again immediately
A particular service reports a location issueEgress point, account eligibility, and old sessionsAssuming access based only on a route name

Describe the issue so it can be reproduced

Change one main condition at a time. For example, keep the target service the same and try another route in the same location, or keep the route unchanged and compare the browser with the app. That way you can see which step affects the outcome. Don’t reset the subscription, change locations, clear browser data, and modify the system proxy all at once. Even if the issue goes away, you won’t know why. In a work environment, keep a brief record of what you changed once things are working again; it can help you recognize similar issues later.

When asking support for help, include your operating system, where you got the client, the location and route type you’re using, the exact error message, and what happens in regular websites versus the target app. Say whether the issue occurs during import, connection, or use, and mention any recent network switch or configuration update. Avoid saying only “it doesn’t work,” and never send your full subscription. The goal isn’t just to see a connected message; it’s to confirm that the apps you need use the intended route and can complete the tasks you rely on.

Routine maintenance, renewals, and recovery

Keep account maintenance separate from device maintenance

Once your connection is stable, split routine checks between your account and your device. On the account side, check plan status, remaining data, orders, and the subscription section. On the device side, check that the client is running, the configuration is current, and the system proxy and local network are as expected. Monthly plan data resets monthly on the activation date, not at the start of each calendar month. Data packs last until used and never expire. If the connection drops, check your account status before assuming the app is broken.

Renew or change your plan through the panel and check the confirmation details on the page. Don’t assume your previous plan will renew automatically, or that placing a new order means it’s active. After payment, check the result in your account. If the status hasn’t synced, use the order checks in the earlier section. When you upgrade mid-cycle, the price difference is converted into remaining days; read the panel’s instructions before submitting. Don’t calculate or assume how benefits carry over if the details aren’t specified. Follow the current order information or confirm with support.

Check for changes after updating; don’t reset unnecessarily

You can update your subscription in the client when the panel announces a configuration change or the list no longer matches the current instructions. After updating, check that the active configuration, selected route, and routing mode still suit your needs. Some clients store local customizations separately from subscription settings; others may change them during an update. Check how your client handles configuration before editing. Don’t repeatedly modify settings managed by your subscription as if they were permanent local files.

Get client updates from a trusted source too. Before updating, note any local settings you need and make sure you can still access the panel to get your subscription. After updating, follow the connection checks in this guide for the apps you use most. Avoid stacking a client update, operating system upgrade, and route change while you’re in the middle of important work. If something breaks afterward, review your recent changes and distinguish app behavior from account status. Backups help you recover; they shouldn’t become a collection of sensitive files shared publicly.

Keep a working baseline when changing devices or networks

When adding a device, sign in to the panel on that device to get the appropriate client and subscription rather than copying the entire app folder from an old device. Operating systems differ in paths, permissions, and proxy behavior, so local rules from another device may not apply. Unlimited devices make it easier to set up your own devices, but you still need to verify each one. After connecting the new device, sign out of the old one, remove configurations you no longer need, and clear browser sign-in states to avoid leaving unnecessary ways into your account.

After traveling, a business trip, or switching networks, make sure local network access works before checking your usual configuration. Hotel Wi-Fi may have a separate sign-in page; work networks may have organizational policies. Don’t change managed settings on a work device just to get connected. For tips on preparing for a short trip, see Cross-Border Setup for Business Travel. Check your client, account access, and essential apps before you leave.

Tidy up after restoring your connection

If regular internet access is still broken after you close the client, check whether the system has retained proxy settings and follow the operating system and client instructions to restore them. If you’ve used other network tools, identify which settings each one manages before removing anything; a configuration may be required for work. Once access is back, remove subscriptions and local backups you no longer need. Don’t make wiping all settings your default response when the cause is unclear. You could lose useful evidence or disrupt other apps that were working fine.

A short maintenance note is enough: your usual locations, the connection mode that works, where to get the client, what you last changed, and how to recover if something goes wrong. Don’t store a password in plain text or include your full subscription. For more help, visit the Help Center and browse by account, connection, speed, or billing. The goal is to keep changes traceable and statuses easy to check, not to keep adding toggles or making your setup more complicated.

Routing, route selection, and advanced settings

Rule-based and global modes solve different problems

Once your basic connection works, you can consider routing rules. Rule-based mode uses the configuration to decide which requests go direct and which use a proxy. Global mode generally applies one policy to requests handled by the client. The important distinction is “handled by the client”: enabling global mode does not necessarily route every program on your device through it. Coverage also depends on system proxy settings, app-specific options, and the client’s traffic-handling method. Don’t assume a mode name means every bit of device traffic is covered.

For everyday use, start with the recommended settings in the panel client and make changes only to meet a clear need. For example, if a work app needs a consistent egress point, check how its requests match the rules. If a local service should connect directly, check that it hasn’t been routed through a proxy by mistake. Note the original setting before changing it, then test the same app afterward. Rule order and behavior depend on the client; an earlier rule may override one you add later, so adding a rule doesn’t guarantee it will take effect.

Choose a location and route for the service you need

Choose a location that meets the target service’s requirements first, then compare how routes perform on your current network. IEPL, transit, and direct routes use different network paths; don’t judge them by their labels alone. If you regularly use an account service in one location, avoid unnecessary changes between regions that could introduce extra session verification. When you do switch, finish any important task first, then verify the new egress point and the features you need. A successful connection doesn’t prove that every account feature is working.

Using AI tools depends on the location, platform account requirements, and current session. For more on these limits, see the AI Access Guide. Verify streaming services on each platform by checking its pages and playback; a route name isn’t a promise of compatibility. For tips on choosing routes by location, type, and use case, read How to Choose a Route: A Beginner’s Guide. For unfamiliar terms, see A Quick Guide to Subscriptions, Routes, and Routing Rules.

How DNS relates to proxy routing

DNS translates domain names into network addresses; a proxy determines how requests are sent. They’re related, but they aren’t the same thing. A browser may use its own DNS settings, the system may retain cached results, and the client may provide its own DNS handling. So a correct egress location doesn’t prove that every DNS request follows the same route. Check the client’s default DNS behavior and adjust settings in response to a specific issue; don’t copy configuration snippets that may not suit your device.

If changing DNS settings causes some services to stop working, restore the last known good setup first, then identify which apps are affected. Don’t enter unrelated settings in your browser, system, and client all at once and judge them by chance results. When troubleshooting, be clear about which app, request, and network mode you’re testing. If you use internal company domains or local network services, preserve the DNS path required by your organization. Don’t disrupt existing work tools just to make all requests use one route.

Check support before configuring a router or automation

The platforms explicitly supported by this service are Windows / macOS / iOS / Android / Linux. That doesn’t mean every router can import a subscription directly. Router setup depends on its firmware, available clients, subscription format, and how it handles network traffic. First check whether the panel provides instructions for your router. If compatibility isn’t confirmed, use a supported device instead. Changes to work or shared networks can affect other people, so don’t treat a test on one device as proof that a whole network is ready for deployment.

Automation scripts must not expose subscription URLs in public repositories, command examples, or logs. If you need a client to start automatically, first confirm that manual startup, subscription import, and connection all work. Then follow the client documentation for startup conditions and recovery after unexpected exits. Starting before the network is ready may produce different results from connecting manually; check the startup order instead of repeatedly resetting your account. Complex configuration is useful when it meets a specific need, not simply because it has more settings.

Keep a clear way to roll back: make sure you can access your account, get your subscription again, restore a verified basic client configuration, and refer to brief notes about important local changes. If something goes wrong, restore your baseline before reproducing the issue. For help, use the ticket form on the Contact page. This gives you a consistent way to handle first-time setup, everyday use, and troubleshooting without having to guess from scratch each time.