Shows "Connected" but Pages Still Won't Load
Common causes: the currently selected node has expired or is overloaded; the subscription list has expired and needs refreshing; the system proxy/TUN mode isn't properly enabled; the local proxy mode doesn't match what you actually need.
Troubleshooting steps:
Confirm the System Proxy Is On
Go back to the client's main screen and check whether the "System Proxy" or "TUN Mode" toggle is enabled — a lot of "connected but not working" cases actually just mean the node connected but system traffic was never actually routed through it.
Switch Nodes and Retry
Go back to the node list, switch to another node with normal latency, and test again to see whether pages load — this rules out a single failed node.
Re-Fetch the Subscription
If switching several nodes doesn't help, run "Update Subscription" to fetch the latest node list, then pick a node and connect again.
Restart the Client
If none of the above works, fully quit the client (not just minimize to the tray) and reopen it — in some cases this is caused by the local proxy process getting into a bad state.
Adding or Updating a Subscription Fails
Common causes: the subscription link itself has expired or was entered incorrectly (extra spaces, missing characters, incomplete copy); your device's current network can't reach the subscription address; the service hosting the subscription address is temporarily unavailable.
Fix: re-copy the subscription link in full from the original source and check for extra spaces or line breaks before pasting; switch to a different network (e.g., between Wi-Fi and mobile data) and try again; wait a few minutes and retry to rule out a temporary service issue; if it keeps failing, confirm with your node/service provider whether the subscription address is still valid.
Flagged as a Virus or Blocked by Antivirus During Install or Run
Common cause: network proxy tools need to modify system network settings, create a virtual network adapter, and similar operations — this behavior pattern is often misjudged as risky by heuristic antivirus rules. It's a known, common false positive and doesn't indicate an actual problem with the software.
Fix: choose "Run/Install Anyway" or "Allow" in the system or antivirus prompt, or temporarily disable real-time protection before installing (you can re-enable it afterward). If you're still concerned, only download the installer from this site's official download links and verify the file size matches what's listed on the download page.
Connected but Speeds Are Very Slow
Common causes: the current node is overloaded or on a distant route; other nodes in the same subscription are performing better; your local network itself is fluctuating; other bandwidth-heavy downloads/updates are running at the same time.
Fixes: test latency in the node list and switch to a node with lower latency and a normal status; update the subscription to fetch the latest node list (the old node may be overloaded); pause other bandwidth-heavy tasks and test again; if every node is slow, disconnect the proxy and test your raw local speed to check whether it's a local network issue.
Android Shows "Can't Install" or "Unknown App Blocked"
Common cause: Android blocks installing app packages from sources like browsers or file managers by default — this is a system-level security restriction and has nothing to do with the installer itself.
Fix: in the system prompt that appears, find "Settings" or "Allow from this source," enable that permission for the app you used to open the installer, then go back and tap install again. You can disable the permission afterward without affecting anything.
Some Sites Load, Others Don't
Common causes: the client is in "Rule/PAC mode" and some domains are classified as "direct" instead of going through the node; local DNS is returning incorrect results; a specific site itself restricts access from proxy IPs.
Fix: temporarily switch to "Global mode" and test the same site — if it works, the issue is a rule misclassification, and you can check whether that domain is being incorrectly matched in your routing rules. If it still won't load in global mode, the issue is most likely the node or the target site itself, so try switching nodes.
macOS Asks for "Network Extension" or "VPN Configuration" Permission
Common cause: the client needs to create a system-level network extension/VPN configuration to take over your traffic. For security, macOS requires manual confirmation — this is standard system behavior.
Fix: click "Allow" in the system prompt when it appears. If it didn't show up or you accidentally denied it, go to "System Settings → Privacy & Security → VPN & Network Extensions," find the app, enable the permission manually, then restart the system proxy.
The Proxy Suddenly Stops Working After a Restart or System Update
Common cause: the client isn't set to launch at startup, or the system reset the network proxy settings after restarting, requiring you to turn it back on manually.
Fix: reopen the client and manually enable "System Proxy" again. If you want this to happen automatically every time you boot up, enable "Launch on Startup" and "Auto-Connect to Last Node" in the client settings (if your client supports these options).