Skip to content
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.

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

acme-dns only saves a single TXT record, not 2 #331

Open
Exagone313 opened this issue Feb 12, 2023 · 0 comments
Open

acme-dns only saves a single TXT record, not 2 #331

Exagone313 opened this issue Feb 12, 2023 · 0 comments

Comments

@Exagone313
Copy link

Hello,

I have acme-dns v1.0 self-hosted and I'm trying to use it along with dehydrated to create a wildcard certificate (with both foo.example and *.foo.example in alt names in the same certificate).

This requires being able to return two different TXT records for solving both challenges at the same time.

However, each time I call the /update endpoint, the TXT record is updated and acme-dns will only send a single TXT record for my domain. This means that when the challenges are checked, the first challenge will be invalid (since only the second one is returned).

Unfortunately, dehydrated doesn't support handling one challenge at once (see the issue here), unlike cert-manager on Kubernetes (by specifying --max-concurrent-challenges=1). dehydrated requires all challenges to be valid at once, before it asks the server to check the challenges.

This seems like a regression from #28.

Do you have the same issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant