Why won’t free nodes connect? This guide helps you distinguish between a failed node, an unreachable IP, DNS resolution issues, and browser configuration conflicts, then troubleshoot them step by step. It’s intended for cases where, after importing nodes into clients such as Clash, V2Ray, or sing-box, you encounter timeouts, pages that won’t load, or trouble accessing certain websites.
First, identify the issue: is the node offline, or is the website unavailable?
If the client shows “Started,” that only means the local proxy is running—it doesn’t mean the remote node is available. Latency tests are only a guide, and results may vary depending on the test address and method. First, check whether regular websites open when the proxy is off. If they don’t, check your Wi-Fi, mobile data, or network sign-in page first.
If only one website is having trouble while others work, don’t immediately assume the node has failed. The target website may restrict the exit IP, or the issue could be caused by routing rules, DNS, or your browser environment.
Check the node and client with these six steps
- Update the subscription: Find subscription management in the client, update it, and check the result. If the update fails, make sure the subscription URL is complete and hasn’t expired. The free nodes on this site are also subject to the latest content shown on the page; an update doesn’t guarantee that every node will remain available.
- Make sure the right node is selected: Check that the current policy group is using an imported node, not “Direct” or another group. Avoid running multiple proxy clients at the same time, as this can cause conflicts with ports or system proxy settings.
- Enable the proxy: On desktop, you usually need to enable the system proxy; on mobile, you need to allow the client to create a VPN connection. Some apps don’t follow the system proxy settings. If your client supports it, you can try TUN mode, but there’s no need to enable it right away.
- Compare with another node: If the same node keeps timing out while other nodes work, it’s more likely that the node is offline, congested, or unreachable. Don’t draw conclusions based on a single speed test.
- Test another network: Switch between Wi-Fi and mobile data, keeping an eye on data usage. If the same node only fails on one network, the issue may be related to that network’s restrictions or routing.
- Check the connection logs: Try opening a webpage again and see whether the logs show a timeout, resolution failure, or certificate error. Before sharing logs, hide subscription links, node passwords, and personal information.
How IP and DNS issues differ
The node’s entry IP and the exit IP used to access a website are two different things. An unreachable entry IP can cause connection timeouts. If the target website restricts the exit IP, you may see more CAPTCHAs or access-denied messages, while other websites still open normally.
DNS resolves domain names to addresses. If the logs show a resolution failure or some domains won’t load, first restore the client’s DNS settings to the recommended defaults, then reconnect. Don’t enter an unfamiliar DNS address at random or disable certificate verification without a good reason. Your browser’s “Secure DNS” setting may conflict with the client’s routing mode, so you can temporarily restore the system default and compare the results.
What to do if the browser is acting up
If other apps work and only the browser won’t load pages, first try an incognito window. Then temporarily disable proxy and ad-blocking extensions, and check whether the browser has its own proxy settings. Incognito mode doesn’t always disable every extension, so check extension permissions.
If you’re stuck in a login loop or seeing an unexpected region message, clear the cookies for that website only. If you see a certificate date error, check the system clock. Change only one setting at a time, and record the result after each test. If a change doesn’t help, revert it. If multiple nodes fail on different networks, check the client version, subscription format, and import errors—this is more useful than repeatedly changing DNS settings.