challenge-types.md remove specific note#2135
Merged
aarongable merged 2 commits intoletsencrypt:mainfrom Feb 12, 2026
Merged
Conversation
Remove specific not about http-01 and let's encrypt http-01 cannot be used for wildcard, regardless of let's encrypt setup
Contributor
|
The tests failed because when this PR was opened (on the 27th), the lastmod date was in the future (28th). And now it's stale. Can you update the date to today (currently 2026-02-11), and then we can merge? |
aarongable
approved these changes
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove specific note about http-01 and let's encrypt
As far as I'm aware, http-01 cannot be used at all to issue wildcard certificates, this is not a limitation specific to Let's Encrypt