What If the Network Still Does Not Work After Exiting Clash?

After Clash exits, connectivity may fail because of a stale system proxy, TUN/VPN interface, changed DNS, a browser's manual proxy, or another proxy tool still controlling traffic.

  • Proxy Modes and System Proxy
  • Troubleshooting
Short answer

Loss of connectivity after exit usually means the system proxy was not restored, a TUN/VPN interface remains, DNS was changed, the browser still uses a manual proxy, or another proxy tool still controls the network. Restore the system proxy, VPN/TUN, browser proxy, and DNS in that order, testing after each step. Stop resetting settings once you find the leftover configuration.

Which of the system proxy, TUN, VPN, and DNS is still active?

After exiting the client, check whether the system proxy still points to 127.0.0.1, then review VPN/TUN status, the browser's manual proxy, and system DNS.

  • Does the system proxy still point to 127.0.0.1 and a local port?(See System Proxy FAQ)
  • Is a TUN, VPN, or network extension still enabled?
  • Does the browser or app have a separate proxy configured?
  • Was system DNS changed to an unavailable address?

Restore network settings after exiting the client

  1. Disable the system proxy and TUN inside the client before quitting(See TUN FAQ)
  2. Clear manual HTTP, HTTPS, and SOCKS proxies in system network settings
  3. Disable any leftover VPN or network extension, then reconnect to the network
  4. Remove browser proxy extensions or return them to system settings
  5. Restart network services or the device if necessary

Do not run multiple proxy clients that repeatedly take over the system proxy

Exiting a client does not always restore every system-level setting automatically

Management policy may lock proxy settings on enterprise devices