2RVPN · User Guide
VPN Troubleshooting Guide
Haven’t installed a client or imported your subscription yet? Start with the Setup Guide. If everything is configured but you’re seeing errors, use this page to troubleshoot by symptom. Note when the issue occurred, which route you were using, and the exact error message. Change one setting at a time so you can tell what made a difference.
Establishing a connection
Connection failure: the client won’t connect
First, check that your device can access the internet
Disconnect the client, then use your browser to open a website you can normally access without acceleration. Refresh the page and check that the content loads. A connected network icon only means your device is connected to Wi-Fi or Ethernet; it doesn’t mean you can reach the internet. Hotel, station, and guest networks often require you to confirm access on a sign-in page. If one appears, follow that network’s instructions before trying again. Never enter your 2RVPN panel password on a network sign-in page, and don’t enter account details if you see a certificate warning.
If ordinary websites still won’t load with the client disconnected, switch to another network you’re authorized to use and try again on the same device. Don’t also change clients or DNS settings. If basic access works on the new network, focus on the original network. If it still fails, check for an old system proxy setting or another network tool that’s still running. For work- or school-managed devices, check with the administrator; don’t remove managed policies to troubleshoot. Until basic internet access works, testing different acceleration routes won’t tell you anything useful.
Troubleshoot based on when the error appears
If a permission prompt appears as soon as you tap Connect, check whether the system is waiting for you to approve a network extension or VPN configuration. If you previously denied permission, open system settings, find the permissions for the 2RVPN client, and try connecting again. If you see an authentication error, open the User Panel overview to confirm the account, plan status, and remaining data, then check that the correct subscription is selected locally. If multiple configurations have the same name, verify where each came from rather than relying on its name. Don’t assume previously saved connection details belong to your current account.
If the client stays on Connecting for a long time and eventually times out, keep the device and network unchanged and try another route that’s currently available in the client. If the original route fails but the alternative connects, keep using the working route and note the failed route’s full name and type. If both fail, restore the original configuration and try another network. The route list explains route types, but it doesn’t show what’s currently selectable in your client or indicate real-time connection quality.
Resolve conflicts with permissions or other apps
After switching clients, an old program may still be using the network extension, or the system proxy may still point to a closed process. Disconnect the old program normally, quit it from the menu bar or system tray, and check whether the system still shows an old connection. Change only settings you enabled yourself. On a shared computer, note the original settings and check with the device manager before changing anything. Reopen the 2RVPN client and try connecting once. Wait for the attempt to finish so multiple error messages don’t get mixed together.
If the connection log shows both a permission prompt and a timeout, focus on the first error that appears and can be reproduced. Keep the selected route unchanged, quit and reopen the client, then check whether the system displays an authorization prompt for this connection attempt. If the client connects after authorization, move on to the website access section for testing. If authorization is complete but the client always stalls at the same step, note the exact message on screen. Reinstalling repeatedly is unlikely to help, and it won’t fix a network that can’t access the internet in the first place.
When to contact support: Basic internet access works, system permissions are correct, and the same step still fails after trying another working network and route. Say whether the error appears immediately, times out after waiting, or reports an authentication failure, and include your test results. Share only the relevant screen; don’t include subscription links, account passwords, or a full configuration.
Website access
Connected, but websites won’t load
Tell whether all websites fail or just one
A connected status only means the client established a tunnel; it doesn’t prove that browser requests are using it. Leave the client connected, open a new tab, and test a website you can normally access, then try the site that’s failing. Note whether the landing page, sign-in page, and page content load. If ordinary websites also fail, disconnect and retry the same address in the same browser. If it only fails while connected, focus on the proxy route, system network settings, and DNS resolution.
If only one site or page fails, don’t confuse a site-side restriction with a connection failure. Seeing the platform’s sign-in page, regional notice, or error page means at least one request reached its server. Note the exact message and check the site’s account status, public service announcements, and access rules. If the homepage loads but images or the player keep spinning, specify whether sign-in, content loading, or playback startup failed. That’s more useful than simply saying “the website won’t load.”
Compare browsers using the same address
Keep the route and system settings unchanged. First open the same address in a private browsing session. If extensions are allowed in that mode, try another browser that doesn’t have its own proxy configured. If only the original browser fails, check whether an extension is modifying requests, whether the browser uses its own proxy or secure DNS, and whether the site has stored an outdated session. Clear data for the affected site first rather than erasing all browsing history. Check for unsaved forms and be ready to sign in again before clearing anything.
If the same site won’t load in either browser but other apps can connect, check whether the system proxy is active and whether the client uses app-based routing or system-wide routing. Follow the IP and DNS leak test guide to compare where requests go before and after connecting. Use the same browser and page for both tests. Don’t use one browser’s results to draw conclusions about another app, or assume an account issue just because the exit IP hasn’t changed.
| What you see | Check first | Next step |
|---|---|---|
| Domain not found | Domain spelling and DNS response | Compare results using the DNS steps |
| Connection times out | Scope of failure, route, and network | Retry the same address on another route |
| Certificate warning | System time and network sign-in page | Keep the warning; don’t sign in |
| Website shows an access notice | Platform announcements, account status, and regional rules | Record the exact message |
Make sure the fix addresses the actual failure
After switching routes, don’t just check whether the tab’s title appears. A previously opened page may load from cache, showing its title and text even though form submissions or content requests are still failing. Refresh normally, then retry the action that failed, such as opening an article or loading a non-sensitive page. For payments or form submissions, check the relevant records first to confirm whether the last attempt succeeded. That way, troubleshooting won’t cause duplicate submissions.
If a certificate warning appears only while connected, first check that the address is spelled correctly, your device’s date and time zone are accurate, and the network hasn’t redirected you to a sign-in page. Don’t install certificates offered by a webpage or lower your browser’s security settings. Save the warning text and check whether the same address triggers it while disconnected. If your network is managed by an organization, ask its administrator to investigate. On a regular network, try another connection instead; there’s no need to reimport your subscription.
When to contact support: Ordinary websites work while disconnected, but most fail after connecting—even on another route and in another browser. Include the connection status, error type, and comparison results. For example addresses, share only the public domain; remove query parameters and private page paths.
DNS resolution
DNS resolution issues and how to check them
First, confirm that the failure is at the domain lookup stage
DNS resolves domain names into network addresses. If your browser says a name can’t be resolved, check the address bar for extra spaces, punctuation, or an invalid subdomain, then test a public domain you can normally access. If just one domain fails, distinguish a typo from an issue with the site’s DNS records or your device’s resolver. If several commonly used domains fail at once, check your device’s DNS settings. Don’t test certificates or sign-in by visiting a site’s IP address directly; many sites need the correct domain to recognize the request.
Before testing, note your current network, route, and the client’s DNS setting. Then change only the connection state. Disconnect the client and look up a public domain, then connect and look up the same domain. Compare whether you get an address, a “domain not found” response, or no response. You can then test the public domain that failed. Don’t share private domains, subscription hostnames containing account identifiers, or internal lookup results with the service. Don’t send organization-managed domains to an untrusted public resolver just to reproduce the issue.
Use a tool to check the result before changing settings
On systems with nslookup installed, use the command below to look up an example domain. The default query doesn’t specify another DNS server, so it’s useful for checking whether your command-line tool can get a response. If you don’t have the tool, try your device’s network diagnostics or compare the same domain in another browser. A successful command-line lookup doesn’t guarantee the browser will work: secure DNS, caching, or client routing may use a different path.
nslookup example.com
The server address in the output is the resolver queried by the tool; the address in the answer belongs to the domain you looked up. An unknown server name doesn’t mean the target domain failed to resolve—check whether the result includes an address record for it. A query timeout means no response arrived in time; a nonexistent domain means the resolver returned a negative answer. These require different troubleshooting steps. Different networks may return different addresses for the same public site, so a difference alone doesn’t indicate a leak or DNS tampering.
Restore settings based on what differs
If the command line works but the browser doesn’t, note the browser’s original secure DNS setting, restart the browser, and compare with another browser. If you need to test the default DNS behavior, temporarily change one setting at a time on a device you manage, then restore the original value. Don’t change both system DNS and router settings at once. If both the command line and browser fail only while connected, check whether the client has custom DNS settings or conflicts with another encrypted DNS tool on the device. Don’t remove system settings from an unknown source; first find out who configured them and whether they’re managed by work or school.
If the issue occurs on only one network, disconnect the client normally, reconnect to that network, and check whether you need to complete its sign-in process again. A second network working is a useful comparison, but it doesn’t identify which device or DNS server is at fault. If you changed that network’s DNS yourself, note the custom setting, restore the original configuration, and try again. Keep the same domain and browser for each test. Don’t treat a one-off success as a fix; confirm it under the original conditions.
If lookups consistently return an address but the page still times out, shows a certificate error, or reports a server error, stop changing DNS and return to the website access section to check what happens next. Clearing the DNS cache can’t fix account permissions or bring a website back online. After changing a setting, test with the browser or app that showed the original error—not just the command line—to make sure the actual service works.
When to contact support: Multiple public domains resolve while disconnected but keep failing on different routes after you connect. Include the public test domains, the types of results before and after connecting, whether the client uses default DNS settings, and whether the browser and command line agree. Remove private domains and internal addresses.
Route performance
Slow speeds and peak-time buffering
First, identify what’s slow
A page that takes a long time to load after clicking, a download that starts but runs slowly, and a video that repeatedly buffers are different symptoms. Choose a public page or accessible piece of content that often gives you trouble, and repeat the same action. Note whether the slowdown happens on the initial page load, when more content loads as you scroll, or during playback. When comparing video, keep the resolution consistent and note if the player automatically lowers the quality. Buffering isn’t directly comparable when the content or quality differs.
Run a separate test with cloud sync, system updates, backups, and other high-traffic tasks paused. On a shared network, traffic from other devices can saturate the connection; having no downloads on your own device doesn’t mean the network is idle. Try closer to the Wi-Fi access point or compare with a wired connection. If ordinary websites and similar tasks are also slow with the client disconnected, address local connectivity or congestion before comparing acceleration routes. Don’t use uploads containing private data as test material.
Compare the same task in the same region
To compare routes, first confirm which regions the app allows, then choose different routes in the same region from the options currently available in the client. Note your original route, finish the current test, switch routes, and wait for the connection to stabilize. Reopen the same page or content. If you keep using an old persistent connection after switching, you may still be seeing results from the previous route. When comparing playback, don’t change the video, resolution, and device at the same time; too many variables make it hard to tell what helped.
| Route type | What it means | Troubleshooting tip |
|---|---|---|
| IEPL dedicated route | A dedicated route describes the link type, not the quality of your local connection | Compare the same task in the same region |
| Relayed | Traffic reaches the exit through an intermediate hop | Note whether changing networks changes the result |
| Direct | The path depends on network conditions between your location and the exit | Don’t judge by geographic distance alone |
Route type can help you decide what to compare first, but it can’t replace testing in real conditions. Latency mainly affects how long short requests take to respond, while downloads and streaming also depend on a steady data flow. A responsive interface doesn’t guarantee uninterrupted playback, and a smooth large-file download doesn’t mean every request in an interactive app will be fast. See the route list for route types, but judge by how your actual task performs—not a single speed test.
Tell peak-time slowdowns from persistent issues
If you suspect peak-time congestion, keep the device, network connection, route, and test content the same. Record results during a normally smooth period and again when slowdowns occur. Note the local time and time zone, and whether the issue happens at a similar time each day or only after a particular network change. If different routes are all slow at the same time, that doesn’t prove congestion on the route side. If another network performs differently at the same time, local connectivity and upstream routing are also worth checking.
If only one platform is slow while similar services work normally, check its public status updates and use the streaming guide to review app region and playback requirements. If the slowdown coincides with the client disconnecting, troubleshoot the trigger in the disconnection section instead of treating it as a speed issue. Once you find a workaround, use it for a while on the original task to confirm the improvement isn’t due to caching, automatic quality reduction, or a temporary change right after switching routes.
While investigating, use a route you’ve verified works for the task and schedule downloads or backups for another time. If your comparison shows that the original route works during regular hours but repeatedly stutters in the evening, keep that finding; you don’t need to move all your traffic to the same region. If poor Wi-Fi and platform buffering happen together, first fix the local issue that’s easiest to reproduce, then test the route again. Otherwise, support won’t be able to compare results under consistent conditions.
When to contact support: At a repeatable time, the same route repeatedly slows down multiple tasks, while an alternative route performs differently. Include the time and time zone, route name and type, the step where the slowdown occurs, and the results of switching routes and networks.
Maintaining a connection
Frequent disconnections and mobile background drops
First, determine whether the tunnel or the app session dropped
Check whether the connection status changed in the client, and note the earliest time you can confirm the issue. If an app prompts you to reconnect while the client still shows Connected, the app’s own session may have expired, or a brief network interruption may have occurred and recovered. Check whether another app in use was affected at the same time, and whether the local connection log shows a matching disconnect or reconnect event. A popup from an app alone can’t tell you which part of the connection dropped.
Test one common trigger at a time: locking the screen, switching to another app, closing the lid or sleeping the device, switching from Wi-Fi to mobile data, or moving between access points. Connect the route, then test locking the screen without moving the device or changing networks. For comparison, keep the app in the foreground and change only the network. If two things happen at once—for example, you leave a building, the device switches networks, and the screen locks—record that they happened together. Don’t immediately blame battery management.
Check sleep and background behavior by platform
These are troubleshooting areas, not settings with identical names on every device. Check only settings related to your device and the 2RVPN client. Don’t remove organization-managed configurations yourself. If a setting is locked, note the message and ask the administrator to check it.
| Platform | Check first | How to verify |
|---|---|---|
| Windows / macOS | Sleep, wake, network extension permissions | Compare staying awake with reconnecting after sleep |
| iOS | System VPN status, network changes, whether the configuration is managed | Compare foreground use and screen lock on the same network |
| Android | App battery restrictions, background data, other VPN apps | Change settings for the target client only, then repeat the same action |
| Linux | Interface status after sleep, how the client runs | Confirm the network is back, then check client status |
On Android, if the system shows the client as restricted, note the original setting, then compare after restoring the app’s permission to run normally in the background. Don’t disable battery management for every app. On iOS, compare the system VPN status with what the client shows. Changing Background App Refresh for regular apps won’t necessarily restore the tunnel. If the issue happens only after locking the screen, reproduce it on the same network first, then test a network switch. After bringing the app to the foreground, check whether the system reestablished the connection instead of relying on an old page that still appears on screen.
Rule out network changes and conflicts with old configurations
Changing networks can change your IP address and route. A new connection being established doesn’t mean an existing download or app session will continue. Wait for the client to reconnect, then test with a new request instead of watching a page that stalled before the switch. An old client configuration with auto-connect enabled may also take over the system connection after wake. First confirm the old configuration is yours and can be disabled, then disable only that item for comparison. Restore unrelated settings after testing; don’t leave experimental settings enabled.
If the device stays awake and the client disconnects even in the foreground, test another route on the same network, then test another network using the same route. Start each test with a stable connection and note whether the same disconnection message appears and whether the client reconnects automatically. If the issue follows a particular route, keep using a verified alternative. If it follows a particular network, check the network equipment or ask its administrator. If disconnections also happen outside those conditions, keep the failure records and avoid switching repeatedly without a clear test plan.
Sometimes you only notice an issue afterward—for example, the device shows Disconnected when it wakes, but you don’t know whether the connection dropped as sleep began or whether reconnecting after wake failed. In your support ticket, say “noticed after waking” rather than presenting the time you saw it as the exact disconnection time. When you reproduce it, note the state before sleep and after waking, whether the system reconnected to the internet, and whether a manual reconnect worked. This is enough to help distinguish sleep behavior, a network interface that didn’t recover, and a client reconnection issue.
When to contact support: Disconnections keep happening on a stable network while the app is in the foreground, or a specific screen lock, sleep, or network-switch action reliably triggers an unrecoverable drop. Include the trigger, system VPN status, whether the connection recovered automatically, and results from an alternative route. Don’t send a full system diagnostic report.
Subscriptions and configurations
Subscription update failed or the list didn’t refresh
Check the panel, local configuration, and update result separately
Open the User Panel overview to confirm you’re signed in to the expected account and check the plan status and remaining data shown there. Being able to load the panel doesn’t mean the subscription was successfully added to the client. A client showing old routes doesn’t mean they’re still available to your account. If the panel and client don’t match, check in this order: panel access, account status, update completion, and whether the route list took effect. This helps you find where the process stopped.
Monthly plan data resets each month on the date your plan started. If you upgrade partway through, the price difference is prorated for the remaining days. Data top-ups remain available until used and never expire. Check the category, status, and data shown in the panel; don’t estimate the reset date from the calendar month or assume that using all your data means the subscription URL is broken. See the Pricing page for the full policy. If the panel status differs from your order, keep the order record and contact support. Don’t pay again just to test a subscription refresh.
Keep a working configuration if an update fails
In the client, confirm which subscription source is selected, then update that subscription. If you have multiple subscriptions on the device, check which one you’re updating rather than just looking for changes in the route list. If the client says it couldn’t fetch the subscription, note the message and confirm that basic internet access and the panel both work on that device. If switching networks might help, keep the same subscription and compare on the other network. Don’t paste the URL into a search box, online converter, or public checking site.
Separate fetch failures from parsing failures. If you see a message about an expired login, account permissions, or an unavailable URL, check the panel for the current import option. If content was fetched but couldn’t be recognized, check whether the client supports your selected import method and whether you imported the right type of configuration. Follow the import steps in the Setup Guide. If you need a client, download it only through the download section of the User Panel. There’s no need to assemble subscription links by hand for troubleshooting.
If the update completed but the old list is still in use
If the client says the update completed, open its configuration selection page and confirm that the subscription is selected as the active configuration. In some cases, only the saved content is refreshed while the connection keeps using the previous configuration. If there are no transfers in progress, disconnect, select the target configuration, and reconnect. Then check which route is actually in use. If the route you previously selected is no longer listed, note its name and test a currently available option instead. Don’t judge whether the list updated by the position of its entries.
The list not changing after a refresh isn’t necessarily a problem. Check whether the original error still appears, whether you can select a working route, and whether the client recorded an update failure. Conversely, new names appearing in the list doesn’t mean they’re in use; check the active configuration and access results. If you need to import again, note any custom routing rules and settings. Keep the original configuration until the new one has been tested, then remove only duplicates you’ve confirmed you no longer need.
If you accidentally shared your subscription URL in a contact conversation, public screenshot, or shared file, treat it as exposed account access information and follow the subscription and account security guide. When contacting support, describe the extent of the exposure and its current status, but don’t send the original URL again. Reinstalling the client won’t revoke an exposed URL. Instead, ask through the panel or a support ticket which account details need to be updated and which devices will need to reimport the subscription afterward.
When to contact support: The panel shows your plan is active, and you’ve rechecked the import method through the panel, but the update still fails or no routes are available. Include the platform, client version as shown in the app, the error message, and when it occurred. Specify whether the failure happened during fetching, reading, or applying the updated list.
App routing
A specific app isn’t being routed as expected
First, pinpoint the first step that fails
A website working in your browser doesn’t mean desktop or mobile apps will use the same proxy settings. First check whether regular websites and other apps work. Then note whether the target app shows a network error on launch, only when you sign in, or when a particular feature fails after sign-in. Sometimes the sign-in page opens in a browser, but the app takes over again after you submit your details. Seeing the sign-in page doesn’t mean the app session is working. Describing the exact step that fails is more useful than saying “this app isn’t using the proxy.”
On the same device, route, and account, compare the service’s website with its app. If the website works but the app doesn’t, check the app’s own settings, whether it uses the system proxy, and the client’s routing rules. If both fail only for the same feature, check the service’s public status and your account permissions. For AI app account, regional, and usage requirements, see the AI guide and the relevant platform’s documentation. A route connecting successfully doesn’t mean a third-party platform will allow every region or account.
Distinguish system proxy, smart routing, and app settings
A system proxy usually affects only programs that use the system proxy settings. Some apps use their own network stack or proxy settings, and background processes may also make requests. Check how the client is currently operating, then see whether the target app has its own proxy or network options. If it doesn’t, don’t guess a port or copy settings from elsewhere. Check whether the client’s built-in routing settings include the app, or—if your device and management policies allow it—test another supported routing mode.
Smart routing uses rules to choose a path, and an app may connect separately to services for sign-in, resources, and content. If only sign-in fails, check the rules for sign-in domains or the app. If only images or syncing fail, check whether that feature uses a different process or domain. If the client provides local connection logs, use the timestamp to check which rule matched and which path was used. Review only your own session; don’t capture or share full request headers, authentication details, private addresses, or file contents.
Change one setting, then restart and retest the app
If the client supports app-specific rules, note the original rule and selected route, then temporarily add one rule with a clearly defined scope. Leave all other settings unchanged, quit the target app, reopen it, and repeat the action that failed. Persistent connections and background processes may continue using the old route; closing a window may not quit the app, so use the system’s normal quit option. If the change doesn’t help, restore the original rule before testing anything else. Don’t leave multiple overlapping temporary rules in place.
If you authorize sign-in in a browser but don’t return to the app, check whether the system actually handed the completed sign-in back to the target app. If you’ve installed multiple versions or similar apps, confirm which one received the handoff. If the browser confirms sign-in but the app didn’t receive the result, don’t start by changing routes for every domain. Try signing in again from the current app and note whether a system prompt appears, what error shows after you return to the app, and whether it still says you’re signed out.
If a feature shows a service error on only one route, test another available route in the same region using the same steps. If the error clearly points to regional rules, account restrictions, or server maintenance, follow the platform’s policies instead of repeatedly switching exit locations and resubmitting. Don’t make repeated sign-in attempts just to test. For work apps that require a fixed network or a specific proxy, use the administrator’s settings and don’t override managed configurations with general routing advice for this service.
When to contact support: The website works, but the app consistently fails under the same conditions, and you’ve checked the current routing rules. Include the app name, operating system, failed step, website test result, and relevant rule name. If you suspect a rule matched incorrectly, provide a public domain and a single redacted log entry.
Devices and support
Device alerts and contacting support
If you see a device limit alert, first identify where it came from
2RVPN has no simultaneous device limit. If you see a device limit, existing connection, or can’t-add-device message, first check whether it came from the User Panel, your system’s VPN settings, the client, or a third-party app. Alerts from one source don’t explain alerts from another. A streaming platform may limit playback sessions on its own account, and a system may not allow two network extensions to take control at once. Neither indicates a change to 2RVPN’s device policy.
On the affected device, check that the panel account matches the active subscription, then compare it with a device that’s already working. If they use different accounts or subscriptions, correct the configuration before comparing. Switching devices, clearing all sessions, or removing existing configurations isn’t the default fix for a device alert. If you suspect an old and new client are competing on the affected device, quit the old process on that device only. Leave other devices’ working connections untouched.
Narrow it down with a controlled comparison
On the same network, check whether both a working device and the affected device can open the same public website through their respective clients. If one works and the other doesn’t, check the affected device’s system permissions, active configuration, and other network tools. If both fail on that network, try another network you’re authorized to use on the affected device. If the issue occurs only on a specific network, focus on that connection. If the panel itself shows a device restriction, save the full message and note where it appears; don’t dismiss it as a third-party alert.
If you own the account but your device is managed by your organization, the system administrator may restrict network configuration changes. Take the issue to the administrator rather than deleting system policies or changing subscriptions on other devices. After switching devices or reinstalling, configurations saved locally on the old device may not sync automatically. Get the right configuration from the current panel and import it using the setup guide. If you no longer control the old device, treat it as a potential exposure of account information rather than just checking how many devices are online.
Submit a reproducible, redacted support ticket
Contact support through User Panel tickets, or see the Contact page for other options. Use “symptom + trigger” as the subject. In the message, state the expected result, what actually happened, and the steps to reproduce it. Include the time zone, the route name and type shown in the client, the device platform and operating system version, and the client version shown in the app. For comparisons, clearly say what changed—for example, the original network failed but another network worked, while the route stayed the same.
If several symptoms seem related, record them in order. For example, the system changed networks, the page then failed to load, and finally the client prompted you to reconnect. Mark any unobserved steps as unconfirmed; don’t present a guess as a log entry. If the issue stops happening, include when it last occurred, whether you changed networks or the device went to sleep, and which conditions previously triggered it. Add any new test results to the same ticket with the test conditions, rather than creating duplicate tickets and splitting up the history.
- Connection or access: Share the exact message, whether only one app is affected, and the results of switching routes or networks while keeping other conditions unchanged.
- Subscription or device: Say where the alert came from, whether you can confirm the panel status, and whether the failure happened during import, update, or connection.
- Billing: Include when the relevant order was placed and the status shown in the panel. Provide only the order details needed for verification in your support ticket, not payment credentials. The service offers a 7-day money-back guarantee. See the Terms of Service for details.
Keep screenshots focused on the error and necessary context. Hide usernames, subscription links, keys, session IDs, and personal information unrelated to troubleshooting. Address bars are easy to overlook, so check them before sending a screenshot. For logs, share only the relevant lines around the error and its timestamp; don’t upload a full configuration file. If you see an unexpected charge, suspect your account details have been exposed, or the panel explicitly says something violates the service rules, contact support before finishing every comparison test.
Sample ticket summary: On the same network, an existing device connects, but a new device shows an error after I approve the connection configuration. The issue also occurs on another network. I’ve included the time, platform, and client version; the screenshot shows only the error.