Common YAML config errors, with fixes

Hand-editing configs or Mixin? YAML syntax errors stop the profile from loading. Match your error against these:

Error 1: inconsistent indentation (the #1 killer)

# wrong: the two fields are indented differently
proxies:
  - name: node-A
     type: ss        # one space too many
# right: siblings align exactly; spaces only, never Tab

Signature errors: did not find expected key or mapping values are not allowed. Turning on "show whitespace" in your editor is a lifesaver.

Error 2: no space after the colon

port:7890     # wrong — a space must follow the colon
port: 7890    # right

Error 3: special characters unquoted

password: p@ss:word!   # colon inside → parse ambiguity
password: "p@ss:word!" # right: quote it

Passwords, node names with emoji, and values starting with * (like fake-ip-filter's "*.lan") should all be quoted.

Validating

After editing, re-select the profile in Profiles and watch Logs for parse errors; or paste the snippet into any online YAML validator first. Note the line numbers in errors refer to the merged config — with Mixin in play, locate by field name rather than line number.