Connection and speed troubleshooting
Choose the closest symptom, then work through its checks. Change one condition at a time and keep the before-and-after results.
↔ Swipe left or right to see all columns
| Symptom | Check first |
|---|---|
| Cannot sign in or no nodes appear | Website, account, credentials and plan validity |
| Connected but websites do not load | Local network, traffic capture, mode and selected node |
| Slow speeds or high latency | High-speed allowance, restrictions and comparable node tests |
| Limited with traffic remaining | Points, requests, Working nodes and account notices |
| Wrong streaming region | Actual exit, unlock settings and platform conditions |
| Local resolvers in a DNS test | Intentional direct access, routing lookups and traffic capture |
Cannot sign in, or no nodes appear
First check that the website is reachable and your account is in good standing. Confirm that you are using the correct sign-in details: enter an Access Token in the token field and your account password in the password field. Check that your plan is valid, then refresh the configuration. Keep the client version and exact error message; avoid repeatedly submitting sign-in requests after consecutive failures.
Connected, but websites do not load
Pause other VPNs or proxies and check that your network works. Then verify that system proxy, VPN, or TUN is enabled, and check the current mode and selected node in the policy group. Try another available node against the same website. If only one app has trouble, check whether it follows the system proxy settings or needs TUN.
It works, but speed is low or latency is high
Check your remaining high-speed allowance, pay-as-you-go settings, and whether low-speed or fair-use restrictions apply. Compare a few nodes on the same network and at roughly the same time. Speed tests consume traffic. Assess latency, bandwidth, and streaming access separately, and avoid changing every setting based on one test.
Why am I limited with traffic still remaining?
Traffic allowance, points and plan speed apply separately. Use the limit comparison, then inspect activity requests and Working nodes in Account Profile. Few currently open connections do not mean few new requests over a minute; repeated speed tests add activity too.
For a points-limit notice, reduce abnormal activity and observe subsequent points using the fair-use recovery rules. Disconnecting completely leaves no activity records and does not guarantee points will rise. Avoid guessing by repeatedly changing nodes, reinstalling the client or buying plans.
Automated abnormal-use detection is active. If the account shows a suspension or ban, stop abnormal use and follow the support instructions. Do not treat it as temporary throttling that points recovery will automatically remove.
The node works, but the streaming region is wrong
Check the node actually used by the streaming service's policy group, its exit region, and your streaming settings. Reconnect, then reopen the app. Account region, platform caches, and the platform's own restrictions can also affect the result. Include the specific platform, node, and time of the error in your support ticket.
A DNS test lists local resolvers
Distinguish intentional direct lookups, lookups needed for routing and queries that bypass the client. DNS encryption, proxy DNS and VPN / TUN capture address different stages; Global mode does not guarantee zero leaks.
Follow the client-specific steps and verification guidance: oixCloud DNS and IPv6 or FlClash for oixCloud DNS and capture.
Client-specific tools
