Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.
Judge by the stage first
| Symptom | More likely stage | Do first | Do not do first |
|---|---|---|---|
config.yaml is empty immediately on switching — consistent with issue #1784, but still check your version and current profile | Configuration switch | Record version, profile name and exact error text | Do not wipe app data straight away |
| Node list empty after a subscription update | Fetch, response or parsing | Move to a subscription update checklist | Do not just keep re-testing latency |
| Node list fine, error only when starting the core | Loading or runtime | Save the core log and work by stage | Do not apply this page's conclusion |
| Appears on an old build, gone after updating | Possibly an already-fixed path | Keep a before/after comparison | Do not generalise to all empty-config problems |
Step 1 — Keep a restore point and get ordinary networking back
Record the FlClash version, the OS version, the time of the error, the action that triggered it, and whether the profile is still listed. A full subscription URL usually carries a token — keep it out of public screenshots, issues and unredacted logs.
If ordinary networking is also affected, disable the system proxy or TUN and confirm whether plain HTTPS sites load without the proxy. This reduces the number of variables; the available evidence does not show that it repairs an empty configuration error.
Step 2 — Check the version and the scope of the official fix
- Below v0.8.97: back up the configuration and any override copies first, then check the official Releases for an upgrade.
- v0.8.97 or newer: do not assume it is still the same defect. Continue with the current profile and the subscription response.
- Crossing v0.9.0: the official release notes state a breaking change — custom overrides were removed and must be rebuilt as a custom profile.
- After updating, test the base configuration before restoring TUN, WebDAV and custom settings one by one.
A version number narrows the field. It does not replace the log and the current profile state.
Step 3 — Confirm the current profile still exists
- Go back to the profiles screen and check whether the selected profile is still listed.
- Keep the original profile for now; do not delete, reinstall and clear data in the same attempt.
- If you need to re-add it, create an independent test profile first.
- Record whether the test profile can be added, and whether switching to it produces the same error.
- Only remove the old profile once the comparison is stable.
A new profile switching successfully proves that the two profiles behave differently. On its own it does not establish why the old one fails.
Step 4 — Separate a successful fetch from a generated configuration
If the problem occurs while fetching the subscription rather than while switching, use a subscription update checklist instead. A browser receiving HTTP 200 does not mean the client has parsed the payload, written it to disk and loaded it.
Record the HTTP status, the response type and whether the body is empty, without publishing the body. Connection reset by peer is a separate case at the fetch stage and cannot be explained by an empty-configuration fix. If the error appears only after content is retrieved, keep checking the format, the current profile, and the configuration generation stage.
Step 5 — Restore advanced settings one at a time
Once the base configuration switches correctly, restore one variable per attempt: custom profile, system proxy, TUN, WebDAV. Re-check the current profile, proxy groups and ordinary networking after each one. If the error returns after restoring a particular item, stop stacking changes and keep the before/after difference.
If names fail to resolve while raw IPs still work, move to DNS troubleshooting — that link does not imply DNS is the cause of an empty config error.
Sources and scope
Material checked 2026-10-31 against FlClash issue #1784, the official FlClash Releases page, and issue #1284 as a separate fetch-stage case. This page was not reproduced on every platform and version. Official issues describe individual environments, and they do not guarantee that an upgrade resolves every empty-configuration problem.
Frequently asked questions
Does 'config.yaml is empty' mean the nodes are dead?
No. The available evidence concerns profile switching and an empty configuration being written. It says nothing about node connectivity.
Will upgrading to v0.8.97 fix it?
Not guaranteed. That version fixed one confirmed path; other causes still have to be checked separately.
Can I delete the FlClash data directory?
Not as a first step. It removes the configuration, the overrides and the diagnostic trail.
The browser opens the subscription, so why does FlClash fail?
The browser only proves a response was returned. The client still has to parse it, generate a configuration and load it.
Is 'Connection reset by peer' the same problem?
No. It is a distinct error recorded at the fetch stage and should not be merged with this one.
What should I include in an issue?
Version, OS, the stage that triggers it, the shortest reproduction steps, and the redacted error text. Do not attach a full subscription or node details.
Continue reading
the remote profile data is invalid yaml · ArgumentOutOfRange_Count when updating subscriptions · Full error string index