FlClash Help · Install / Profile / Proxy / TUN / DNS
Find answers for FlClash on Android, Windows, macOS and Linux, including installation, Profiles, Override, System Proxy, TUN, DNS, ports, Connections, Requests and Logs. Start with FlClash and Mihomo Core status, then isolate configuration, traffic entry and upstream network issues.
Common issues
FlClash is the client and configuration layer, Mihomo Core executes proxying, Rules, DNS and TUN, and the active Profile defines nodes and policy. Checking those layers separately is faster than changing multiple settings at once.
FlClash does not provide proxy nodes or subscription service by itself. Add a valid remote or local Profile, confirm Mihomo Core can load it, choose a proxy group, then enable the network entry method for your platform.
Check whether the source returns valid Mihomo configuration, whether the Profile actually refreshed, and whether Override / Override Script or config errors changed what the Core finally loads.
Desktop System Proxy affects apps that follow OS proxy settings, desktop TUN captures a broader traffic range through a virtual interface, and Android uses the operating system VpnService. All three feed traffic into Mihomo; Rules still decide the outbound path.
Separate installation, Profile handling, traffic entry and runtime troubleshooting so client issues, Mihomo config problems and upstream failures do not get mixed together.
Downloads & installation
FlClash officially supports Android, Windows, macOS and Linux. Confirm the platform, CPU architecture and package format before troubleshooting permissions, dependencies or compatibility.
The official project supports Android, Windows, macOS and Linux and is built with Flutter. iOS is not listed as an official FlClash platform, so separate iOS clients should not be treated as FlClash releases.
Use amd64 on most Intel and AMD Windows systems. Choose ARM64 only for Windows on ARM devices. Package format can vary by release, so confirm the current Release assets before downloading.
Use the arm64 build on Apple Silicon Macs and the amd64 build on Intel Macs. The official README also documents installation through the FlClash Homebrew cask.
Most modern Android phones and tablets use arm64. Older 32-bit ARM devices or x86_64 emulators may require a different APK architecture, so check the device ABI if you are unsure.
The official README lists libayatana-appindicator3-dev and libkeybinder-3.0-dev as Linux dependencies. Also make sure the package format and CPU architecture match your distribution and device.
The project maintainer closed Windows 7 support requests as not planned. Use a currently supported Windows environment rather than assuming modern FlClash releases will run correctly on Windows 7.
Profiles & Override
A Profile is the base configuration source. FlClash can apply local Override settings, added Rules and Override Script changes before Mihomo Core loads the final runtime configuration.
A Profile is the configuration source managed by FlClash, usually from a remote subscription or local file. FlClash combines it with local settings and Override layers before passing the final configuration to Mihomo Core.
Confirm the source returns valid content, the intended Profile is active and updated, and Override / Override Script did not alter proxies, proxy-groups or related fields. A Core config error can also prevent groups from loading.
Standard Override changes base configuration and supports simple added Rules. Script mode uses an external extension script for more flexible configuration changes. Both affect the final config Mihomo actually loads.
Multi-profile Merge should not be treated as a stable built-in capability. Current FlClash terminology centers on a Profile plus Override, Override Script and added Rules for local changes.
Confirm the subscription URL is reachable and returns valid data, then inspect custom User-Agent, TLS, network errors and update logs. Troubleshoot the client only after the source itself is known to be working.
Clients may bundle different Mihomo versions, apply different defaults or overrides, and integrate DNS, TUN and System Proxy differently. Compare the effective runtime config, Core version and operating system environment.
System Proxy & TUN
Outbound mode decides how Mihomo chooses the route after traffic enters the Core. System Proxy, Android VPN and TUN decide how device traffic reaches the Core. These are separate layers.
Rule mode follows the active Mihomo Rules. Global sends traffic through the selected global policy, while Direct bypasses proxy routing as much as possible. Choose the mode according to the Profile and what you are testing.
Some applications do not read operating system proxy settings or use their own network stack. Check the app's own proxy options first, then use TUN only when broader traffic capture is actually needed.
System Proxy changes desktop OS proxy settings for applications that follow them. TUN uses a virtual interface and system routing to capture a broader range of traffic and usually requires elevated permissions.
FlClash primarily uses Android VpnService to route device traffic into Mihomo. Android, Windows, macOS and Linux expose different network APIs, so the available controls and permission prompts are not identical.
No. On desktop, System Proxy is enough for many browsers and conventional applications. Android uses the system VPN interface. TUN is mainly for desktop traffic that does not follow normal proxy settings.
Disable TUN first to confirm the base network recovers, then inspect Core state, administrator permissions, TUN stack, auto-route, DNS, strict-route and conflicts with other VPNs or virtual adapters. Change one variable at a time.
DNS & runtime troubleshooting
Start with FlClash and Mihomo Core status, then verify the final Profile, ports, DNS, Rules and connection records before deciding whether the problem belongs to the proxy node or upstream network.
Latency tests only measure response time to a specific test target. Real performance also depends on the selected proxy group, node load, DNS, destination routing, bandwidth and your local network.
FlClash exposes local ports such as Mixed Port, SOCKS Port, Redir Port and TProxy Port. If one is already in use, choose an unused port and make sure System Proxy or any manual proxy settings point to the new listener.
Read Logs and Core status first, then check the effective configuration, port conflicts, file integrity and platform permissions. The error can come from Override, DNS or TUN settings rather than the original Profile.
Inspect DNS first: enhanced mode, default nameserver, nameserver, proxy-server-nameserver, nameserver policy, Fake-IP and respect rules. DNS and Rules can interact in ways that make node hostname resolution or destination routing fail.
Connections shows active flows and their paths, Requests records request activity, and Logs exposes client/Core messages. Together they help determine whether traffic reaches Mihomo, which Rule or proxy group is involved, and whether the Core reports an error.
If FlClash and Mihomo Core are running, the final config loads, System Proxy/TUN/Android VPN is active, and only one node, domain or network environment fails, investigate the node service, DNS upstream, destination site or local network next.
Continue troubleshooting
Use the download page for Android, Windows, macOS and Linux builds. Use the tutorial for Profiles, Override, routing modes, System Proxy, Android VPN and TUN, then return here for deeper troubleshooting.