## TL;DR

On Flatcar, a silent agent install is usually a config problem, not a network problem. First verify the API key and target are valid by pasting them into a browser check or a second machine.

## Steps

1. On Flatcar, a silent agent install is usually a config problem, not a network problem. First verify the API key and target are valid by pasting them into a browser check or a second machine. Then confirm the ignition config actually contains them: ssh in and check the rendered config for the values. Host tags go in MW_HOST_TAGS as a comma-separated list like tag1,tag2; a stray space breaks matching. Read the agent's systemd unit logs with journalctl; the first error line tells you whether it is auth, network, or a bad target.

## When to use

You are seeing this: First verify the API key and target are valid by pasting them into a browser check or a second machine. Use this skill when you run into "Middleware on Flatcar: validate key and target, then check the ignition config".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
