VPNWorth User Guide

Stage / Service & Setup

About the Service and What You’ll Need

VPNWorth is a subscription service for cross-border connectivity. Getting started involves more than downloading an app: first create an account and choose a plan, then import the subscription provided in your account dashboard into a client. The client handles network requests on your device and routes them according to its mode and rules; the service’s routes provide the corresponding international network paths. Keeping your account, subscription, and client distinct makes it easier to identify which part to check if something goes wrong, rather than reinstalling everything.

Understand Accounts, Plans, and Subscriptions

Your account is your control panel. Use your username and password to sign in, view plans and orders, find client downloads, and contact support. Your plan defines your service. It determines the included data and billing terms. Your subscription provides the client configuration. The client uses it to retrieve routes and related settings. Saving your account password doesn’t mean you’ve imported the subscription, and seeing old routes in the client doesn’t mean your plan is still active. Check each of these separately before troubleshooting.

VPNWorth covers 100+ countries / 220+ routes and supports Windows / macOS / iOS / Android / Linux, with unlimited devices online at once. This describes the service as a whole; it doesn’t mean every route suits every network or that every app will automatically use the client. Quantum encryption is the service’s core security message. You should still protect your password and subscription URL, and avoid sharing pages, logs, or configuration files that contain account information.

Prepare Your Device and a Backup Network

Before you begin, make sure your device can open familiar local websites, its date and time are set correctly, and you have another network you can switch to if needed. A client can’t connect on your behalf if the device itself has no network access. If other proxy or tunnel tools are installed, note their settings first, then pause anything that might conflict over the system proxy, virtual network adapter, or DNS. Don’t delete existing adapters or change system network settings in bulk without understanding the impact.

Check installation permissions in advance, too. Devices managed by an employer or school may restrict app installation, system proxies, or network extension permissions. Follow the administrator’s requirements on those devices. If a client requests system permissions, read what they’re for and continue only after confirming the app came from the download link in the account dashboard. Being able to access the dashboard in a browser doesn’t prove the device can create a tunnel, so check permissions and web access separately.

Set a Goal and Keep Track of What You Check

First, define what you want to do—for example, browse international websites, use AI tools, stream content from a particular region, or set a network route for developer tools. Different scenarios have different requirements for region consistency, connection stability, and app support for proxies. Don’t assume that a farther-away region or a more elaborate route name is better. Start by choosing a target region, keep other conditions constant, and test it in the app you actually plan to use. If you’re using an account with a platform, follow that service’s rules, too.

Keep a local note of your platform, network type, selected route, and connection mode, but don’t record the full subscription URL. After each stage, check the expected result: you can sign in to the dashboard, your plan is active, the client shows routes, and the target app works after you connect. If something fails, troubleshoot that stage before moving on. This avoids duplicate payments and gives you a clear account of what happened if you need to contact support. For terminology, see A Quick Guide to Subscriptions, Nodes, and Routing.

Stage / Choose a Plan

Choosing a Monthly Plan or Data Pack

Choose a plan based on how often you’ll use the service, then consider your data needs. A monthly plan may suit regular use and a predictable allowance; a data pack may suit occasional use when you’d rather track usage as you go. The key difference is how data relates to time—not just the price. Don’t estimate long-term needs from the size of one download alone; account for streaming, app updates, cloud sync, and background usage on other devices.

Check the Full Price and Billing Terms

Monthly plan data resets each month on the activation date, not necessarily at the end of the calendar month. In your dashboard, check your plan status, remaining data, and reset date together. Your remaining balance reflects the current billing period; don’t assume it carries over to the next one. If you expect heavier use, check whether the current tier covers your needs before you run into connection issues.

Data packs remain available until used and never expire. Unlike monthly plans, they don’t reset on a schedule, so check your remaining data rather than looking for a monthly top-up date. This no-expiry term applies to data pack usage; it doesn’t guarantee the future availability of routes, third-party apps, or client versions. Check the current plan options and order details in your dashboard. Don’t assume plans can be combined or exchanged.

Account for Shared Devices and Background Usage

Unlimited devices means there’s no limit on how many devices can be online at once; it doesn’t mean unlimited data. Keep an eye on your account usage when using a computer, tablet, or other devices at the same time. Video quality, file sync, and system updates can change how quickly data is used. Whether that traffic goes through a route depends on the client mode and app settings. If usage changes more than expected, check running tasks and which rules are being applied rather than judging by the number of connected devices alone.

You don’t need to choose a higher tier just to leave room for more devices. Instead, identify your main use case, check the dashboard’s data usage during normal use, and decide whether to change plans based on that. Dashboard and device usage totals may cover different traffic: device statistics can include direct connections, local network traffic, or other interfaces. If the numbers don’t match, compare what each statistic includes and when it was updated. Don’t subtract figures with different scopes to infer a billing error.

Check Upgrades, Payments, and Refunds Separately

If you upgrade a monthly plan mid-cycle, the price difference is prorated against the remaining days. Before upgrading, review the amount and new term on the confirmation page. Don’t calculate the amount due from the difference between full monthly prices, or assume a change in data tier leaves the term unchanged. If the result differs from what you expected, note your current plan and pending order details, then contact support before paying. Don’t create duplicate orders to try to get a different calculation.

VPNWorth accepts Alipay / WeChat Pay / USDT and offers a 60-day no-questions-asked refund policy. Refunds are separate from choosing a plan; read the Terms of Service for the application rules. Don’t count discounts, bonus data, or extra services unless they’re explicitly listed in your current order. See the pricing page for all available plans. Once you’ve found the right fit, choose it in your dashboard and check the billing terms—not just the price label.

Stage / Account & Ordering

Create an Account and Confirm Your Order

VPNWorth doesn’t require an email address; create an account with a username and password. Your account is where you manage plans, orders, and subscriptions, so save your credentials securely before placing an order. Not needing an email address means you shouldn’t assume there’s an email-based account recovery option. A browser that’s still signed in doesn’t mean you’ve saved your password. You’ll need to be able to sign in again after switching devices, clearing browser data, or ending your session.

Open the User Dashboard from This Site

Go to the user dashboard using the sign-in link in this site’s navigation or the start free link. Before signing in, check that the domain in your browser matches this site. Don’t enter your password on lookalike pages in search results. If someone sent you a link, return to this site and navigate to the dashboard yourself. The marketing site describes the service; the dashboard handles accounts and delivery. They can look different, and that alone doesn’t mean sign-in failed.

Choose a username that’s easy to remember and distinguish over time. Use a unique password rather than reusing one from another important account, and save it securely. If the dashboard says your input doesn’t meet its requirements, follow the current prompt instead of guessing a fixed character limit. After submitting, check whether you’ve reached your account page. If not, read the error message first. Repeatedly clicking submit can make the result harder to diagnose. Once your connection is back, try signing in to the existing account before creating another one.

Creating an Order Doesn’t Mean It’s Paid

After signing in, open the plans section and check the product name, billing terms, data allowance, and price before creating an order. An order means the system has recorded your selection; it doesn’t mean payment has been confirmed or the service is active. If you selected the wrong tier, check the order status before paying and use the options available in the dashboard. Don’t pay for multiple unchecked orders in different tabs.

Payment methods are Alipay / WeChat Pay / USDT. Follow the current instructions on the payment page, and use the amount, recipient, and order details shown for that order. For on-chain payments, double-check the network and recipient information displayed on the page. Don’t use an address from an old screenshot or a different order. This guide doesn’t provide payment addresses or credentials to copy manually; complete payments only through the flow opened by your current dashboard.

After paying, return to the dashboard, check whether the order has updated, and then verify your plan details. The payment page, your bank or payment app, and the dashboard each show a different part of the process: payment completion, funds charged, and service activation. If the page hasn’t changed yet, refresh the order status rather than paying again. If the details still don’t match, keep the order ID, payment record, and a description of the page where the issue occurred, then contact support through the dashboard. Hide unrelated personal information before submitting anything.

How to Continue if a Redirect or Session Fails

Switching browsers, signing out, or clearing site data during payment can interrupt the current session. If that happens, return to this site, sign in to your existing account, and check your orders instead of creating a new account. If the original order doesn’t appear automatically, find it in your account. The browser’s Back button changes the page you’re viewing; it may not cancel an order. Always check the actual order status in your dashboard before trying again.

If you’ve paid but can’t see the order, first make sure you’re signed in with the same username you used to place it. Using multiple devices can make it easy to confuse pages from different accounts, so check each one. Don’t post payment screenshots publicly or share your full password with anyone. If you need help, use the support ticket link in the dashboard. If the page won’t open, restore basic network and account access before continuing with account support.

After placing your order, you can also check the First-Day Setup Guide for Beginners to follow the main steps. Get your subscription from the same account. A payment receipt can’t be imported into a client, and the URL of a plan page isn’t a substitute for your subscription URL.

Stage / Get Your Subscription

Get and Manage Your Subscription

Your subscription URL lets the client retrieve route settings. It may contain account-specific identifiers, so treat it like a sensitive credential—not an ordinary web address to share. The client typically downloads a configuration from this URL and may request it again when updating. The subscription delivers the configuration; whether network traffic uses a route also depends on whether the configuration is enabled, a route is selected, and proxy or tunnel features are active.

Get the Right Link from Your Signed-In Dashboard

After signing in, check your plan status, then look for a copy-link or client-import option in the subscription section. Don’t copy the URL in your browser’s address bar: that’s the dashboard page, not your subscription. If the dashboard offers formats for different clients, choose the one that matches yours. A mismatched format may open as an address but still be unreadable by the client. Go back and select the right format instead of changing parameters in the link.

Automatic import usually requires your browser to open an installed client. When prompted to open an external app, check its name before proceeding. If nothing happens, confirm the client is installed and your system allows the link association. An automatic import failure doesn’t mean the subscription is invalid; copy the link and add it manually in the client instead. Don’t repeatedly install lookalike tools from other websites just to trigger the import.

When Adding Manually, Check the Link and Save

In the client’s configuration or subscription manager, choose the option to add a link, paste the full URL from your dashboard, and give the configuration a recognizable local name. Check for spaces, line breaks, or punctuation added by a chat app at either end of the pasted link. Save it, then update and check whether a route list appears. If you see the configuration name but no routes, adding it is only part of the process—the configuration still needs to download. Check the update result and any error message.

The address below is only an example of what a subscription URL looks like. It isn’t from VPNWorth and can’t be used to connect. Get your real URL from your signed-in dashboard. When sharing logs or demonstrating a setup, use an obviously fictitious example like this. Replacing a real URL with a QR code doesn’t anonymize it; the code may still contain the full credential.

https://example.com/sub?token=YOUR_TOKEN

If your client supports multiple configurations, make sure the selected one is the VPNWorth configuration you just imported. An old configuration may contain routes with the same region names, so a route name alone doesn’t identify its source. Give each configuration a clear local label, and check whether the route list changes when you switch. Don’t delete old configurations immediately. First confirm the new one connects successfully, then remove only what you no longer need to avoid losing existing rules or work settings.

Updating a Subscription vs. Changing Its URL

Updating a subscription means the client uses the existing URL to retrieve the configuration again, usually to sync route changes. Changing the URL replaces the configuration source. An update doesn’t give you a new plan, and changing the URL isn’t a routine way to improve speed. If your dashboard offers a reset option, consider that other devices may still have the old URL saved; you’ll need to update them as instructed. Don’t assume every device will receive the change automatically.

If a subscription update fails, check your account and plan status, the copied URL, the client format, and your basic network—in that order. If the client reports a parsing error, first look for the matching format. If it times out, check whether your network can reach the dashboard and subscription URL. The page returned might be a sign-in page, network authentication page, or other non-configuration content. Don’t save a web page and force it to act as a route configuration, or assume a download failure is caused by a particular region.

You’re done with this stage when the client successfully updates the configuration and shows routes you can select. Check access to your target app in the connection stage. To understand the difference between subscriptions, nodes, and protocols, see our terminology guide. Don’t adjust complex routing rules before the configuration has updated successfully.

Stage / Set Up Your Platform

Set Up the Client on Each Platform

The basic process is the same on Windows / macOS / iOS / Android / Linux: get the client, add your subscription, update the configuration, choose a route, and enable the appropriate traffic-handling mode. Interfaces may differ, but each step should have a clear result. Find client downloads in the dashboard download section; this guide doesn’t link directly to installers. Except on iOS, sign in to access the client. On iOS, you need a purchased, unexpired plan to access the download; follow the dashboard instructions.

Windows: Check the Configuration and System Proxy Separately

Sign in to the dashboard to get the appropriate client, install it as directed, and open its configuration manager. Add your subscription link and update it. Once the route list appears, enable the configuration and choose a target region. If the client has a system proxy switch, enable it as instructed, then test in a browser. An open client window doesn’t mean the system proxy is active, and a successful import doesn’t mean the selected route is working.

When a permissions prompt appears, make sure it names the client you just installed. Virtual adapters and tunnel features may need additional permissions; try them only if needed after checking the regular proxy setup. If your browser still uses the old route, check whether browser extensions or other proxy tools are overriding the system settings. Before closing the client, check whether it will restore the system proxy. If web pages stop loading after you exit, see whether the system is still pointing to a local proxy that’s no longer running.

macOS: Check Network Extensions and System Permissions

Get the client for your device from the dashboard, then install and open it as directed by macOS. If the system asks you to approve network permissions, confirm the app’s source and read the permission details. Don’t disable system protections to bypass the prompt. Add and update your subscription in the configuration manager, enable it, then choose a route. The menu bar icon can show whether the client is running, but it doesn’t replace checking the configuration and connection status.

On macOS, the system proxy, app-specific proxies, and tunnel mode can coexist. If only your browser works, check whether the target app reads the system proxy before deciding whether to use a tunnel feature supported by the client. If changing the system proxy causes network problems, restore the original settings one at a time. Don’t delete network services you don’t recognize or clear proxy settings that other work apps rely on.

iOS: Check System Connection Status After Importing

Check in your dashboard that your plan has been purchased and hasn’t expired, then get the client through the link in the download section. Return to the dashboard and use the compatible import option, or paste the matching subscription link into the client. Update the configuration, select a route, and allow the system prompt to add a VPN configuration. This permission enables network traffic handling; it isn’t another payment, and you shouldn’t be asked to give your account password to an unrelated page.

After connecting, check the client and system VPN status, then open the target app to test it. If you run into problems after switching Wi-Fi networks, disconnect and reconnect in the client and see whether that helps. If other VPN configurations are saved on the device, make sure the expected one is active. Don’t rely on the status indicator alone to confirm a region. It shows that the connection feature is active; check the selected route and a lookup result to confirm the exit region.

Android: Check Subscription Updates and Background Operation Separately

Sign in to the dashboard to get the Android client, install it as directed by the system, and open it. Add your subscription, update the configuration, choose a route, and allow the system’s VPN connection request. If another tool is already using the system VPN interface, check whether it conflicts with the client. Browser extensions, filtering apps, and work profiles can also affect the network path, so first establish a baseline with a single client in a simple setup.

If the connection works in the foreground but drops when you switch apps, check battery management and background operation limits. Adjust the relevant settings only for a client that needs to keep running; you don’t need to disable all device protections. If a downloaded file won’t install, check compatibility, system messages, and the file source, then download it again from the dashboard. Don’t use repackaged files from unknown sources or assume an installation failure means your plan is inactive.

Linux: Desktop Proxy Settings Differ from Terminal Settings

Get a Linux client for your system from the dashboard, then follow the current installation instructions. Add and update your subscription in the graphical interface, select a route, and check the desktop environment’s proxy settings. If the client needs extra system permissions to create a tunnel, read its instructions first. Desktop environments differ in which apps use their proxy settings. A browser connection doesn’t prove that every terminal command will use the same route.

Whether a terminal program uses a proxy depends on the program’s support and settings such as environment variables. If you need to configure one, first check the local listening address, port, and proxy type shown in your client, then follow the target tool’s documentation. Don’t copy someone else’s port number. To limit a setting to the current terminal, avoid writing it directly into a global startup file. Revert temporary changes after testing to avoid hard-to-trace issues when you switch networks later.

Stage / Check Your Connection

Choose a Route and Verify Your Connection

After importing, establish a connection you can test consistently: keep the current network unchanged, choose a route in your target region, connect using the client’s standard mode, and open the target website. Don’t switch routes, change DNS, enable a tunnel, and clear browser data all at once. Even if things work afterward, you won’t know which change helped. Check in order: basic network, client, exit route, then target app—and record a clear result at each step.

Route Types Can Offer Clues, but Testing Matters

IEPL, relay, and direct routes describe how network traffic is carried. A dedicated line generally refers to a particular transport arrangement; a relay sends requests through an intermediate path; a direct route connects to the destination without an intermediary. Actual performance still depends on your local connection, carrier routing, destination region, and target app. A route’s name can’t predict its speed in every situation, and a result on one route doesn’t apply to the whole service.

First match the route region to what your app needs, then compare options in that region. For general browsing, check whether pages load consistently and files transfer normally. For account services, try to keep the region consistent rather than switching frequently for a faster page load. For route types and regional coverage, see the global routes page. This guide doesn’t provide fixed latency or bandwidth figures; choose based on how routes perform on your current network.

Tell a Successful Import, Connection, and App Request Apart

A successful import means the client retrieved and parsed the route configuration. A successful connection means it established the relevant network path. A successful app request means the target service completed the request. These are different checks. If the client says it’s connected but a page won’t load, first check whether the request actually passes through the client. If the client log shows no request to the target, check the traffic-handling scope before switching every route or buying another plan.

Open the What’s My IP page in your browser. Check the current exit address and region against the route you selected. If the lookup fails, treat it as a missing result, not proof that the connection failed. A matching exit region still doesn’t guarantee that a target platform will accept it. Some apps use separate network settings or have account-region requirements or their own risk checks. Continue testing within the app.

Web Pages Load, but the Target App Doesn’t Work

First check whether the app supports the system proxy or needs its own network settings. A working browser doesn’t mean developer tools, games, or desktop apps use the same route. If the app supports proxy settings, enter the details shown in your client and follow the app’s documentation. If it doesn’t, check whether the client’s tunnel feature is appropriate. Don’t assume an app permission issue, account restriction, or service maintenance is a route problem.

For AI tools, distinguish browser access from API requests. A page loading successfully doesn’t guarantee that a developer process uses the same proxy settings. An API error might also be caused by credentials, permissions, quota, or request content. Check the error type first, then inspect the process’s exit route and connection path. For guidance on stable exits, concurrency, and timeouts, see Choosing a Route for AI API Requests. Don’t use repeated retries to hide an error you haven’t identified.

Streaming access can also depend on the content library’s region, account requirements, and the platform’s own checks. If content isn’t available, first make sure the selected region matches the content, then check whether the app is still using an old session. Reopen the app or sign in again using its usual process. Avoid repeated sign-ins across regions in a short period. Route listings show regional information; they don’t guarantee access to every platform or content library.

If every target fails, check your basic network and plan status first. If only one app fails, focus on its settings and the service’s response. If the issue happens only on your current network, compare results on another network you’re allowed to use. This narrows down the cause without turning a local problem into a complete configuration rebuild.

Stage / Maintenance & Renewals

Everyday Maintenance and Plan Renewals

Once connected, focus on keeping configuration sources clear, plan status easy to check, and changes easy to undo—not constantly adjusting advanced settings. Establish a baseline for normal use and make changes only when you have a clear problem or the dashboard indicates something has changed. A client running for a long time doesn’t mean your plan status can’t change. Likewise, being unable to access one site doesn’t mean your account benefits have ended. Check each through its own status page.

Track Usage, Plan Terms, and Subscription Updates Separately

Monthly plan data resets each month on the activation date. When checking usage, look at your tier, reset date, and plan status—not just the remaining balance. If usage increases, check streaming, file sync, and background tasks on your devices before deciding whether to move to a higher tier. Unlimited devices makes it convenient to use multiple devices, but they can still share your account’s data allowance. Turning off unnecessary background tasks can make usage changes easier to understand than switching routes at random.

Data packs remain available until used and never expire. Keep an eye on your remaining balance and current account details. Don’t apply monthly plan reset rules to a data pack or assume that updating a subscription adds data. A subscription update syncs configuration; it doesn’t change your order, payment status, or product terms. If the route list changes but your balance doesn’t, there’s no contradiction—check the dashboard and client separately.

Review the Confirmation Before Renewing or Upgrading

When you’re ready to continue, check the available plans and order details in your dashboard, then review how the renewal will appear. This guide doesn’t assume how the dashboard handles expiry or combines products. If you already have a data pack and choose a monthly plan, follow the current confirmation page. If you can’t tell how your benefits will change, ask before paying instead of relying on an old page afterward.

If you upgrade a monthly plan mid-cycle, the price difference is prorated against the remaining days. Check the amount and term on the confirmation page; don’t treat an upgrade as a simple data increase while overlooking a change to the term. After paying, return to the dashboard to check the order and plan status. If the client still shows old details, update the configuration and check again—but don’t pay a second time just because the client’s text hasn’t changed. See the pricing page for full pricing details.

Keep a Way to Restore Your Client and Configuration

When updating the client, get it from the dashboard rather than a repackaged third-party file. Before updating, note the configuration name, traffic-handling mode, and any local settings you need. If the client supports secure local backups, follow its instructions, and don’t sync files containing credentials to a public location. After updating, test the subscription and your usual apps before restoring optional features. This makes compatibility changes easier to spot.

Check subscription update results, too. If the route list is empty, regions are clearly missing, or a parsing warning appears, first check whether the update succeeded, then verify the format and plan status. An empty list after a failed update isn’t evidence that the service has less coverage. If you need to restore local settings, use the configuration you recorded—not a block of unknown rules copied from a forum. Unfamiliar rules can change DNS, local network access, or app routing.

Switching Devices, Pausing, and Refunds

On a new device, get the client and subscription from your dashboard, grant the required permissions for that platform, and test the apps you use. When you stop using an old device, remove its account session and configurations containing the subscription, especially before handing it over or recycling it. Deleting a desktop shortcut doesn’t remove credentials; configurations, clipboard history, and exported files may still contain sensitive information. Use the system and client features to remove them.

When you pause service, disconnect and check that the system proxy or tunnel has been restored. VPNWorth offers a 60-day no-questions-asked refund policy. Before requesting a refund, read the Terms of Service and submit a support ticket in your dashboard. Include the relevant order and what you’re requesting; you don’t need to publish your full subscription or password as proof. Check the result in your account and keep the order and ticket details for follow-up.

Stage / Advanced Setup & Troubleshooting

Advanced Routing and Troubleshooting

Make advanced changes only after a standard connection works. First identify the problem—for example, an app isn’t using the proxy, a local network device is unreachable, or a terminal request exits differently from a browser. Then choose the feature that addresses it. If you don’t have a clear goal, don’t import complex rules, change DNS, and enable a tunnel all at once. Advanced options change how requests are handled; they don’t add data to your account or override app permissions and usage rules.

Rules, Global Mode, and Tunneling Work at Different Levels

Rule mode uses domains, addresses, or other matching conditions to decide how requests are handled. It’s useful for separating local and international traffic. Global mode generally sends requests that reach the client through the selected policy, but it can’t ensure that every app is covered. Tunnel mode expands the scope of system traffic handling and may involve a virtual adapter, routing, and DNS. Understanding how these modes differ helps explain why an app may still connect directly even after you switch to global mode.

Before changing rules, check the matching order and default action in your current configuration. An earlier matching rule may prevent a later one from taking effect. If adding a domain changes nothing, check which rule actually matched rather than adding the same entry repeatedly. Custom rules may also be overwritten by subscription updates. If your client supports overrides or local rules, follow its instructions instead of editing a generated subscription file.

Troubleshoot DNS and Local Network Issues Separately

DNS resolution translates a name into an address that can be reached; proxy routing determines the subsequent network path. If a domain won’t open but a known service still connects, check DNS resolution. If the name resolves but a connection can’t be established, check the route and app response. Don’t replace your DNS with a public server just because you see a particular error message, or interpret a change in the resolution result as proof of better privacy. Use the client documentation, system settings, and actual request results together.

If a printer, shared folder, or other local network service becomes unavailable after you enable a tunnel, check whether your setup has an option to bypass the tunnel for local traffic and whether a rule is incorrectly routing local addresses. Confirm your workplace or school network requirements before making changes. To troubleshoot, temporarily restore the settings you had before enabling the tunnel. If local access returns, you’ve found a useful clue—there’s no need to reinstall the system or delete all network settings.

Check the Proxy Environment Used by Developer Tools

Terminals, editors, and background services may inherit different environments. If your browser works but a developer request times out, check whether the process making the request has a proxy configured and whether its protocol matches the client’s listening proxy. The command below only checks whether common proxy variables are set in the current terminal; it doesn’t establish a connection. Redact any sensitive output before sharing it. No variables shown doesn’t prove every program is connecting directly.

printenv HTTP_PROXY HTTPS_PROXY ALL_PROXY NO_PROXY
printenv http_proxy https_proxy all_proxy no_proxy

An app may also use its own settings and ignore environment variables. After making a change, check whether a new process actually picked it up; background tasks and already-open editors may not update automatically. When checking an API, distinguish network errors from authentication, quota, and request-parameter errors. Don’t keep changing your network when the service has explicitly rejected a request. For more scenarios, see the ChatGPT Connectivity Guide and Developer Guide to Choosing a Route for API Requests.

Make the Smallest Change Needed to Reproduce the Issue

When something fails, first describe what happened: a subscription won’t update, the client can’t connect, no websites load, or a single app returns an error. Then check your plan status, basic network, configuration source, and current mode. Keep other conditions unchanged while you test a different route in the same region or switch networks. Record the result before moving on. This helps distinguish account, device, route, and app problems—and prevents you from mistaking a temporary recovery for proof that a complex setting worked.

When submitting a support ticket, include your system platform, client status, the step where the error occurred, selected region, and what you’ve tried. Attach redacted error text. Don’t share your password, full subscription URL, access tokens, or unrelated payment information. If the issue affects one app, add the error type and whether the app uses the system proxy. Find common answers in the Help Center, or open a support ticket in your dashboard for individual help.