From bb237538a08d84b6fe1cb40d29a119bff2017682 Mon Sep 17 00:00:00 2001 From: Romuald Brunet Date: Tue, 27 Jan 2026 17:54:20 +0100 Subject: [PATCH 1/2] challenge-types.md remove specific note Remove specific not about http-01 and let's encrypt http-01 cannot be used for wildcard, regardless of let's encrypt setup --- content/en/docs/challenge-types.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/challenge-types.md b/content/en/docs/challenge-types.md index 133b6fe5e..5c5051836 100644 --- a/content/en/docs/challenge-types.md +++ b/content/en/docs/challenge-types.md @@ -1,7 +1,7 @@ --- title: Challenge Types slug: challenge-types -lastmod: 2025-12-03 +lastmod: 2026-01-28 show_lastmod: 1 --- @@ -48,7 +48,7 @@ Pros: Cons: - It doesn’t work if your ISP blocks port 80 (this is rare, but some residential ISPs do this). -- Let’s Encrypt doesn’t let you use this challenge to issue wildcard certificates. +- This challenge cannot be used to issue wildcard certificates. - If you have multiple web servers, you have to make sure the file is available on all of them. # DNS-01 challenge From 77792fc2a2ddd6c519fc92e471783c8bdc5635be Mon Sep 17 00:00:00 2001 From: Aaron Gable Date: Thu, 12 Feb 2026 15:08:57 -0800 Subject: [PATCH 2/2] Update lastmod --- content/en/docs/challenge-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/challenge-types.md b/content/en/docs/challenge-types.md index 5c5051836..dd105656f 100644 --- a/content/en/docs/challenge-types.md +++ b/content/en/docs/challenge-types.md @@ -1,7 +1,7 @@ --- title: Challenge Types slug: challenge-types -lastmod: 2026-01-28 +lastmod: 2026-02-12 show_lastmod: 1 ---