Cannot connect after updating FlClash? Troubleshoot these 4 types of issues
Users have reported core startup and access-control issues in FlClash 0.8.96. TUN-related local network and batch speed-test issues may also occur in other versions or under specific configurations, so this does not mean that 0.8.96 introduced them. Classify the issue by its error first instead of repeatedly switching nodes or resetting the network at the outset.
Before you start
Operation steps
- 01
If the core fails to start, check the client first
If DesktopCoreFailure(start_failed) appears in the logs, the proxy core has not started successfully. Note the FlClash and Windows versions, then check the installer architecture and whether security software is blocking it. Switching nodes is usually pointless when the core has not started.
- 02
If access control causes crashes, disable the feature first
If FlClash crashes after access control is enabled on Android, or the allowlist and blocklist cannot display apps, this is more likely a client feature malfunction. Keep the default routing rules for now and do not repeatedly re-import the subscription. If you must use app lists, retain redacted logs and wait for a fix, or use a version previously confirmed to work.
- 03
Run a comparison test when TUN affects local network access
This behavior may be caused by routing, allowlist settings, or conflicts with other networking tools; it is not a confirmed general regression in 0.8.96. If internet access works with TUN enabled but you cannot reach your NAS, printer, or corporate intranet, disable TUN and use only the system proxy. If local network access is restored immediately, check whether private network addresses are routed directly and whether the allowlist rules are matching.
- 04
A batch speed-test timeout does not mean all nodes are down
Batch speed-test issues occurred in older versions, and the 0.8.96 release notes include related fixes, so do not describe this as a new issue introduced in 0.8.96. Test one node individually, then try opening a web page. If only the batch speed test fails while the individual node test and actual browsing work normally, treat it primarily as a speed-test or display issue.
- 05
Complete the minimum verification before deciding what to do next
Disable TUN, update the subscription, select one node, and open a web page through the system proxy. If that works, enable TUN again and test local network access. If an error already occurs while the core is starting, troubleshoot the version, architecture, or permissions instead.
After completion, check like this
- The proxy core has started successfully
- Tested one node individually
- Web pages can be accessed through the system proxy
- Local network access still works as expected after enabling TUN
FAQ
Should you downgrade FlClash immediately?
Do not download installers from untrusted sources. Back up your current configuration first and confirm that the issue can be reproduced consistently. If a rollback is necessary, use only installers provided on the official FlClash project releases page.
What can you include in a troubleshooting screenshot?
You may provide the client version, operating system version, and full error message, but you must redact the subscription URL, QR code, tokens, and node keys.