Why can’t free nodes connect? This guide helps you distinguish between an unavailable node, a proxy that isn’t taking effect, DNS resolution issues, and conflicting browser settings. Troubleshoot in this order: nodes first, then your system, and finally your browser. It applies when you’ve imported a free subscription into a client such as Clash, V2Ray, or sing-box and websites won’t open or only some sites are affected.
1. Determine whether the problem is with the node or your local settings
Free nodes may become temporarily unavailable because they have expired, are undergoing maintenance, are overloaded, or are restricted by your network. Successfully importing a subscription only means the client has read the configuration; it doesn’t mean the nodes are still online. A latency test returning a result doesn’t guarantee that websites will open properly—check actual access and the logs as well.
- Temporarily turn off the proxy and open a website you can normally access directly. If that also fails, first check your Wi-Fi, mobile network, or router connection.
- Manually update the subscription in your client and check whether the update succeeds. If you get an error, make sure the subscription URL has no extra spaces and hasn’t expired.
- Switch to another node and test the same website. If only one node fails, that node is the most likely cause.
- Briefly switch between Wi-Fi and mobile data. If the issue occurs on only one network, it may be related to network restrictions, routing, or DNS.
Don’t run multiple proxy clients at the same time. Keep only one client running while you test to prevent repeated changes to the system proxy. Treat free nodes on this site as available only if they work in practice. If an old configuration no longer works, get it again and test it.
2. Check whether your IP and proxy are actually working
An unreachable node server or an inaccessible port can cause timeouts. If a website says “region not supported” or repeatedly asks you to verify, the issue may be related to the location or reputation of the exit IP; this doesn’t necessarily mean the entire proxy is disconnected.
First, make sure the client is running and a valid node is selected. Browsers generally require “System Proxy” to be enabled. If you’re using TUN mode, confirm that the virtual network adapter is running and has the necessary permissions. When troubleshooting, choose one traffic-routing method instead of blindly enabling multiple options.
You can check a trusted IP lookup page to see whether your exit IP has changed, but with split tunneling, the lookup site may use a direct connection. If needed, temporarily switch to Global mode for comparison, then restore your original mode when you’re done. If the logs show a timeout, connection refusal, or authentication failure, check node reachability, service status, and whether the subscription is up to date, respectively.
3. How to check for DNS issues
DNS translates domain names into IP addresses. If the logs show a resolution failure or some domains won’t open, check the DNS resolution path. However, a page that keeps loading doesn’t by itself confirm a DNS problem.
- Keep the client’s recommended DNS settings and remove any recently added manual resolution rules whose purpose you’re unsure of.
- Check whether the browser’s “Secure DNS” is set to a custom service that can’t be reached. Temporarily switch to the default setting for comparison.
- Restart the client and browser. On Windows, run
ipconfig /flushdnsin Command Prompt to clear the system DNS cache.
Don’t simply replace a website’s domain with its IP address to test it: HTTPS certificates and website virtual hosting can make the results misleading. Also, don’t copy DNS addresses from untrusted sources.
4. What to do if only your browser fails
If other apps work normally, try another browser or an incognito window, and temporarily disable extensions such as proxies or ad blockers. Also check extensions that are still allowed to run in incognito mode. Make sure the browser isn’t configured with an old proxy address of its own. If necessary, clear only the affected website’s cache and cookies.
If the issue persists, note the client version, time of the error, affected website, and a redacted log before asking for help. Don’t share your subscription URL, node password, or full configuration publicly. Don’t ignore certificate warnings, and don’t leave your firewall or security software disabled just to connect to a node.