docs: update API conflict status, ACME config, request flow, deployment, and security sudoers
This commit is contained in:
+2
-1
@@ -32,6 +32,7 @@ Error responses carry one of the following HTTP status codes:
|
||||
|------|---------|
|
||||
| `400` | Bad request — invalid body, missing required field, or malformed value |
|
||||
| `404` | Not found — the requested resource does not exist |
|
||||
| `409` | Conflict — the requested operation conflicts with an existing resource |
|
||||
| `500` | Internal server error — unexpected failure in the backend |
|
||||
|
||||
### Route Patterns
|
||||
@@ -910,7 +911,7 @@ Request a new certificate for a domain. Returns HTTP `500` if issuance fails.
|
||||
|
||||
**Response:** `data` is `null` on success.
|
||||
|
||||
Returns HTTP `400` if the domain is missing. An ACME account must be registered before issuance (verified by the `account_registered` blocking check in the validation pipeline).
|
||||
Returns HTTP `400` if the domain is missing. Returns HTTP `409` if a valid certificate already exists for the domain (renew instead). An ACME account must be registered before issuance (verified by the `account_registered` blocking check in the validation pipeline).
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user