Skip to content

Add warning re: DNS-01 challenge + additional components #341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simonhammes merged 1 commit into from
Jul 9, 2026
Merged

Add warning re: DNS-01 challenge + additional components #341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/installation/advanced/webserver-dns-challenge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,17 @@ The exact configuration depends on your DNS provider. In most cases, the API tok
caddy_0.tls.dns: "cloudflare {CLOUDFLARE_API_TOKEN:?Variable is not set or empty}"
```

!!! warning "Additional components require the same `caddy.tls.dns` label"

If you have deployed additional components such as [Collabora](../components/collabora.md) or [n8n](../components/n8n.md) that are directly exposed by Caddy
and they use the same hostname as your SeaTable installation, you need to also add the `caddy.tls.dns` label to these services.

Otherwise Caddy will log the following error:

```
Removing invalid block: hostname appears in more than one automation policy, making certificate management ambiguous
```

## Step 3: Create and Configure the DNS API Token

Log in to your DNS provider’s account and generate an API token with permission to manage DNS records for the required zone.
Expand Down
Loading