Step-by-step troubleshooting for connection settings, slow browsing, timeouts, port conflicts, public Wi-Fi, certificates and provider-side outages.
Jump from symptoms such as no connection, slow speed, DNS issues, occupied ports, certificate errors or apps bypassing proxy to the right answer.
When Clash is enabled but websites do not open, check whether the profile updated successfully, the selected node is reachable, the system proxy or VPN mode is active, and DNS is returning usable results.
Read answerFast speed tests with slow browsing usually indicate DNS delay, overloaded target sites, wrong node selection, rule mismatch, packet loss or a test server that does not represent your real traffic.
Read answerDNS can affect a connected client. Symptoms include websites opening by IP but not domain, wrong regional routing, certificate mismatches or logs showing lookup connection symptoms.
Read answerWhen the browser works but other apps do not, the browser is probably using HTTP/SOCKS proxy settings while the other app is bypassing them. TUN/VPN mode is often needed for apps that do not respect system proxy.
Read answerConnection settings after quitting Clash usually means the system proxy, VPN route or DNS setting was not restored. Turn off proxy settings manually or restart the network service after closing the client.
Read answerConnection refused or bind failed means the expected local port is unavailable or the app is connecting to the wrong address. Another process may already occupy the port, or Clash may not have started its listener.
Read answerPing timeout can be normal because many nodes or test targets block ICMP. Judge usability with real browsing, TCP connection tests or the client latency test that matches your proxy group.
Read answerCertificate prompts should not be ignored automatically. Check system time, DNS hijacking, captive portals, antivirus HTTPS interception and whether the target site is being reached through the intended node.
Read answerPublic Wi-Fi login pages often need direct local network access before any proxy starts. Temporarily disable system proxy or TUN, complete the portal login, then re-enable Clash after normal internet access is available.
Read answerA proxy loop happens when Clash traffic is accidentally sent back into Clash or through a rule that selects itself. Check system proxy, external proxy settings and rules for recursive routing.
Read answerIPv6 can cause connection symptoms when rules, DNS or the selected node only handle IPv4 cleanly. Temporarily disable IPv6 or add explicit IPv6 rules to confirm whether it is the cause.
Read answerIncorrect system time can break TLS handshakes, subscription authentication and certificate checks. Sync the system clock before troubleshooting certificate or provider login status messages.
Read answerCheck external-controller, secret, port, firewall and access address first.
Read guideFocus on config paths, ports, logs, TUN permission and dashboard access.
Read guideRecover network first, then check permission, virtual adapter, DNS and route conflicts.
Read guide