Node HandbookNODE HANDBOOK中文
FlClash · cross-platform

FlClash: profiles and the empty-list problem

One report about this client keeps repeating: the profile switches and config.yaml comes back blank. That is a profile-management question, not a network question, and it has a different diagnostic path.

Node Handbook editorial team ·

Profiles are files, and files get replaced

A Clash-family client stores each profile as a file and points the core at the active one. When the client switches profiles or applies an update, the file that the core reads can change — and if the new content is empty or does not parse, the result is an interface with a profile name and no nodes.

Two habits prevent most of these incidents:

  • Keep an exported copy of the profile that worked.
  • Confirm which profile is active before editing anything, because editing an inactive file changes nothing.

Decide which failure you have

SymptomLayerFirst check
Profile file blank or unexpectedly shortLocal file stateWhether a switch or update rewrote it; restore your copy
Profile present, list emptyContent or activationWhich profile is active, and what it contains
List populated, pages failCapture or forwardingThe four contrasts below
Import reports an errorFetch or parseStatus code and whether the body is a configuration

Importing

  1. Use the address or file the provider documents for Clash-family clients.
  2. After import, confirm the profile is selected and active.
  3. Check that the proxy list has entries and the group names are the provider's, not leftovers from a previous profile.
  4. Test one real request.

The four contrasts when pages fail

  • Client off, ordinary site — base network.
  • Another node — one node versus the subscription.
  • Another network — current path versus the service.
  • One app versus the browser — capture scope versus forwarding.

Capture modes

System proxy writes a local port into the system settings and covers applications that read them. TUN captures at the IP stack and covers more, at the cost of an adapter, routes, DNS handling and permissions. Start with the simpler one, and record the pre-change DNS and routing state before enabling TUN.

What to record

  • Client version, platform, and the profile name in use.
  • Whether the profile file was replaced, and by what action.
  • Whether the list was empty, partial or complete.
  • Mode used, and the result of each contrast.
  • A copy of the profile that worked, stored outside the client's data directory.

Scope

This page describes profile handling and the order of checks. Interface wording follows the installed version. Nothing here evaluates a provider or guarantees that a profile from one client family behaves identically here.