Nodes and Connections FAQ
Troubleshoot Clash timeouts, connection failures, latency, and subscriptions that update without working traffic by checking nodes, time, protocols, network, and real browsing.
Locate the failing layer from the connection symptom
Unavailable nodes, slow access despite normal latency, and TLS errors require checks at different connection stages.
What If a Node Shows timeout, connect failed, or Cannot Connect?Connection failures can result from an unreachable node address, a blocked port, mismatched protocol parameters, TLS/SNI errors, an incorrect system clock, or restrictions on the local network.What If the Subscription Updates but Browsers or Apps Cannot Connect?This usually means the system proxy is disabled, the browser is bypassing it, a rule matched DIRECT, DNS resolution is failing, or TUN is not capturing traffic correctly.How Do I Diagnose a Slow Node, Unstable Latency, or Intermittent Disconnects?Speed and stability depend on node load, routing, the network provider, protocol, DNS, MTU, UDP support, and local resources. The latency number shown by the client is not enough on its own.What If an Incorrect System Clock Breaks TLS, Certificates, or Subscription Updates?Reality, HTTPS subscription updates, certificate validation, and some handshakes depend on system time. A clock offset can make certificates invalid or break the handshake.What If Latency Looks Normal but Browsing Is Slow?A latency test usually contacts a single probe address. Real browsing speed also depends on the destination, DNS, the matched rule, congestion, bandwidth, and protocol behavior.