Why won’t my free node connect? This guide helps you tell the difference between a failed node, client settings, network IP issues, DNS problems, and browser issues. Follow the steps in order to avoid repeatedly switching nodes without finding the cause. It’s intended for everyday users of clients such as Clash, V2Ray, and sing-box, and does not cover setting up your own server.
First, check: Is the node down, or is the browser unable to load pages?
When a client shows “Connected,” it usually only means the local proxy has started—not that the remote node is working. A latency test can return a result without guaranteeing that every website will load. First identify the scope of the problem, then change settings. Change only one thing at a time so you can pinpoint the cause.
- Temporarily turn off the proxy and open a website you can normally access. If it still won’t load, first check your Wi-Fi, mobile data, or router.
- Update the subscription once and check for a download failure, parsing error, or empty content. If the update fails, the list may still contain outdated nodes.
- Select a node and enable the system proxy. On a phone, make sure you’ve authorized the VPN connection. Test with the default rules first, then temporarily switch to global mode for comparison.
- Try another node and compare the results on Wi-Fi and mobile data. Note whether the problem occurs only with a particular node or network.
How can you tell whether a node is down or there’s an IP issue?
Free nodes may stop working because of maintenance, increased sharing, traffic limits, or an unreachable server address. If only one node keeps timing out while others work, suspect that node first rather than reinstalling the client. You can check the original announcement page or our free nodes section for updates, but a recent update doesn’t guarantee that a node is working.
If the same node works on mobile data but fails on Wi-Fi, the issue may be related to restrictions or routing on your current network. Don’t assume your device’s IP has been blocked just because of a timeout. If only one website denies access or frequently shows CAPTCHAs, the shared exit IP’s reputation may be the issue. A failed node connection and a website restricting an exit IP are two different problems.
DNS issues: Connected, but domain names won’t load
DNS translates domain names into IP addresses. If the logs show messages such as “resolution failed” or “DNS timeout,” check the DNS resolution step first. However, an ordinary connection timeout alone doesn’t mean DNS is the cause.
- Check that your system network settings don’t have a manually configured DNS server left over. If you’re unsure, restore automatic DNS, then reconnect to the network.
- Prefer the DNS settings included with the client’s configuration. Don’t paste configuration snippets from unknown online sources.
- If TUN mode or DNS interception is enabled, check that the client has the required permissions, and avoid running multiple proxy tools at the same time.
- Reconnect the client, then close and reopen the browser. If necessary, clear the system DNS cache and test the same website again.
If only the browser fails, check these settings
If other apps can connect but one browser can’t, compare the results in a private window or another browser. If the private window works, check your extensions, cache, or site data—but this alone doesn’t confirm the cause.
Temporarily disable proxy-switching extensions and make sure they aren’t overriding the system proxy. Check whether the browser’s “Secure DNS” is using a resolver that your current network can’t reach; you can temporarily restore the default setting for comparison. Some apps don’t follow the system proxy, so check their individual proxy settings rather than immediately assuming the node is down.
Don’t disable certificate verification or install unfamiliar root certificates as part of troubleshooting. If the problem persists, save the time of the error, the client version, and redacted logs, then report it to the node provider. Don’t share your subscription link, UUID, or full connection QR code publicly.