## TL;DR

Certbot tried several challenges and at least one failed; the summary line hides the per-domain reasons. Open the log, list each failed domain with its specific error (DNS, http-01, rate limit), fix them one by one, and re-run. Multi-domain certs fail as a unit, so one bad domain blocks the rest.

## Error

```text
Some challenges have failed.
```

## Steps

1. Open `/var/log/letsencrypt/letsencrypt.log` and search for `Failed authorization procedure`; list every domain and its error type. Expected: a per-domain breakdown (e.g. two DNS failures, one 403).
2. Group by error type and fix the most common first; a single DNS misconfiguration often explains several. Expected: the list shrinks.
3. For http-01 failures, verify each domain serves the challenge path (see the authorization-error skill). Expected: each domain returns 200 for a test file.
4. For dns-01 failures, verify each `_acme-challenge` TXT record propagates: `dig TXT _acme-challenge.YOUR_HOST @8.8.8.8`. Expected: the expected token value appears.
5. Re-run `certbot --dry-run` covering all domains, then the real run. Expected: all challenges pass together.

## When to use

- certbot prints exactly `Some challenges have failed`.
- Certificates covering multiple domains or wildcards.

## When not to use

- A single domain fails (the single-domain skills are more direct).
- The failure is a rate limit (no challenge fix helps).

## Tool compatibility

- certbot; dig/drill for DNS checks; Let's Encrypt staging for retries.

## Variant phrasings

### Exiting abnormally: Some challenges have failed

Wrapper variants of the same summary; the log holds the detail.

### 1 of 3 challenges failed

Partial failure; fix only the failing domains, the passing ones need no changes.

## Why it happens

One certificate order validates every name in it. Mixed infrastructure (some domains on one server, some elsewhere) means each name can fail for a different reason, and certbot reports only the summary.

## Edge cases

- Wildcard orders require dns-01 for every name; mixing http-01 and dns-01 in one order is not allowed.
- A domain that recently moved DNS may validate against the old nameservers from some vantage points; wait out the TTL.
- `--allow-subset-of-names` exists but silently drops failing domains from the cert; prefer fixing over dropping.