After importing a free node, it times out, shows as connected but won’t load webpages, or works in every browser except one. Where should you start troubleshooting? This guide walks through checks for the node, client, IP, DNS, and browser environment to help diagnose why a free node won’t connect. It applies to clients such as Clash, V2Ray, and sing-box. Menu names may differ between versions, so follow the options available in your interface.
First, tell whether the node is down or webpage access is the problem
A connected status does not mean the proxy connection is working. A successfully started client only confirms that its local proxy service is running. The node may have expired, its server may be temporarily unavailable, or your current network may be unable to reach its address. Latency tests can help with diagnosis, but they do not replace testing actual webpage access.
- Turn off the proxy and open a website you can normally access to confirm that your Wi-Fi or mobile data is working. On public Wi-Fi, you may also need to sign in.
- Update your subscription and check when it was last updated. If the update fails, check that the subscription URL is complete and still valid. Don’t keep importing the same old link.
- Manually select a different node and try accessing two different websites. If only one node fails, the node itself is the most likely cause.
- Check the error in the logs: timeouts usually point to a connection or node issue; resolution failures call for a DNS check; authentication failures mean you should check whether the node details have expired.
When getting free nodes from this site or other pages, refer to the latest published information. Free resources may become unavailable, and repeatedly clicking Connect usually won’t fix an expired node.
Check the client and IP: Make sure traffic is taking the right route
Confirm that the client’s system proxy is enabled, or turn on TUN/VPN mode as instructed by the client. On a phone, you must also allow it to create a VPN connection. For troubleshooting, run only one proxy or VPN client at a time to avoid multiple apps competing for control of network traffic. You can temporarily switch to global proxy mode for comparison, then switch back to rule mode.
If your client supports connection logs, check whether requests are being routed through the proxy and which rule they match. If you can access a trusted IP lookup page, compare your public IP with the proxy on and off. An unchanged IP does not necessarily mean the node is broken; the site may be set to connect directly by your rules. Don’t judge whether the connection is working based only on the IP’s reported location.
Next, test the same node over both Wi-Fi and mobile data. If it fails only on one network, the issue may involve that network’s access restrictions or differences in DNS resolution. This is more likely to narrow down the cause than repeatedly switching clients.
Check DNS: Don’t change addresses at random right away
DNS translates domain names into IP addresses. If the logs repeatedly show resolution failures, first make sure your device’s date and time are correct, then check whether the client’s recommended DNS settings are enabled. DNS handling varies between clients, so don’t change DNS in your system, client, and browser all at once, or it will be difficult to tell which setting took effect.
Change only one setting at a time, restart the client, and test again. If there’s no improvement, restore the original setting. Switching to a public DNS service won’t solve every problem, and some networks may restrict access to it. If the logs show a certificate error, don’t disable certificate checks to “fix” it. Check the time and update the client first.
Can’t access sites in just one browser? Check extensions and cache
If other apps work normally, try another browser or test in a private window. Temporarily disable proxy extensions and check that the browser isn’t using a separate manual proxy. If Secure DNS is enabled, you can temporarily restore the default setting for comparison. Private browsing can’t bypass network restrictions; it can only help rule out some cache and extension issues.
If only one website fails while the others work, the site may restrict the exit IP, trigger a verification check, or be experiencing an outage. You don’t need to reinstall the client right away. If you still can’t identify the cause, note the client version, network type, and error message before asking for help. Hide your subscription URL, password, and node authentication details before sharing screenshots.