What If Multiple VPNs, Proxy Tools, or Security Apps Conflict?

When multiple tools change the system proxy, routes, DNS, VPN interfaces, or certificates, Clash may lose connectivity, rules, or TUN. Test one network path at a time.

  • Security, Privacy, and Permissions
  • Troubleshooting
Short answer

When multiple tools change the system proxy, routes, DNS, VPN interfaces, or certificate policy, they can break connectivity, invalidate rules, prevent TUN creation, or capture traffic more than once. Run only one capture tool at a time, restore networking, then re-enable tools one by one. Stop adding settings when you identify the conflict.

Which tool is changing the proxy, routes, or DNS?

Several tools may change the system proxy, virtual adapter, routes, or DNS at the same time. First identify which one currently controls the network.

  • Are multiple VPN or proxy clients running at the same time?
  • Is security software blocking a local port, TUN driver, or network extension?
  • Are different tools repeatedly changing the system proxy and DNS?
  • Do logs show permission denied, route failed, or address already in use?

Keep one capture tool and restore the network

  1. Run only one primary proxy client first
  2. Close other VPNs, transparent proxies, accelerators, and packet-capture tools, then retry(See TUN Permissions FAQ)
  3. Restore the system proxy and DNS, then restart the Clash client(See No Internet After Exit FAQ)
  4. When tools must coexist, assign clear responsibilities for ports, routing, and DNS
  5. On enterprise devices, request an allowlist according to device-management policy

Running multiple network-capture tools greatly increases troubleshooting difficulty

Do not leave system protections disabled long term for troubleshooting

On mobile devices, only one VPN configuration can generally be active at a time

How to confirm the conflict is resolved

Connectivity works when run alone
With only one proxy or VPN tool running, the system proxy, routes, and DNS restore correctly.
Networking still fails after closing it
Inspect leftover system proxy settings, virtual adapters, filter drivers, and security-software rules; do not add more network tools.