Why can’t free nodes connect? This guide helps you distinguish between an unavailable node, traffic not being routed through the client, DNS resolution issues, and browser-related problems. Follow the steps in order to troubleshoot “timed out,” “connected but webpages won’t load,” and “only some websites are inaccessible.” It applies to Clash, sing-box, and V2Ray-style clients and does not cover setting up your own server.
First, determine whether the node has failed or the webpage won’t load
If the client says “started,” that only means the local proxy service is running; it does not mean the remote node is available. Free nodes may stop working due to maintenance, route changes, heavy usage, or an expired subscription. Check the node test and connection logs first, then determine whether it’s a DNS issue. Latency tests are only a guide; actual webpage access is the best measure.
- Turn off the proxy and visit a commonly used domestic website. If that won’t load either, check your Wi-Fi, mobile network, and system connectivity. Public Wi-Fi may require you to sign in first.
- Update your subscription and check for download failures or configuration parsing errors. If the update fails, the list may still show old nodes. Back up your configuration before importing it again.
- Select a node manually and test it using the client’s built-in feature, then try another node to compare. Don’t rely solely on automatic selection.
- Make sure the system proxy or the client’s recommended traffic-routing mode is enabled. On phones, check the VPN permission. On computers, temporarily quit other proxy tools to avoid conflicts.
- Open a webpage and check the logs. For connection timeouts, check the node and network first. If you see a domain resolution error, proceed to DNS troubleshooting.
IP address and network environment: switching networks is more effective than repeatedly reinstalling
It’s important to distinguish between your local network’s public IP address and the node’s exit IP address. The former may affect whether you can connect to a node, while the latter may affect whether a destination website allows access. If only one website denies access or repeatedly asks you to verify your identity, that doesn’t mean the node as a whole has failed. A shared exit IP may trigger a website’s security checks, so test again after switching nodes.
Keep the same node and configuration, and test separately over Wi-Fi and a mobile hotspot. If it fails on only one network, the issue is more likely related to that network’s access restrictions or routing. If multiple nodes fail on both networks, check the client version, subscription format, and system time. Install or update the client through the project’s official channels; don’t try your luck by turning off the firewall.
DNS: What to check when you’re connected but domains won’t load
DNS translates domain names into IP addresses. If the logs show a resolution timeout or failure, or only some domains won’t load, first restore the client’s recommended DNS settings, remove any rules you previously added manually, and then restart the client and browser. If necessary, follow your operating system’s official instructions to clear the DNS cache.
Don’t change the system DNS, client DNS, and browser Secure DNS settings all at once. Change one setting at a time and record the result; otherwise, it’s difficult to pinpoint the cause. Switching to a public DNS server is no guarantee of a fix. Different proxy modes may also route DNS requests differently. Avoid testing HTTPS by entering a website’s IP address directly, as certificates and virtual hosting can make the results misleading.
Browser: Rule out extensions, cache, and separate proxy settings
If other apps work but the browser doesn’t, first test in a private window or another browser. Then temporarily disable proxy extensions and check for any separate proxy settings that may still be enabled. Private browsing doesn’t necessarily disable all extensions, and it won’t automatically bypass the system proxy. If you see a certificate warning, check your system time; don’t ignore the warning and continue signing in.
Finally, retest in this order: “basic network → subscription and nodes → traffic routing → DNS → browser,” changing only one condition at a time. If you’re using this site’s free nodes, update them before testing as well; availability can change over time and across networks. If you still can’t connect, ask for help with your client version, operating system version, and a redacted error log. Never share your full subscription link or node credentials publicly.