From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id BA63A1FF37F for <inbox@lore.proxmox.com>; Tue, 18 Jun 2024 16:16:09 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D84911C7E9; Tue, 18 Jun 2024 16:16:10 +0200 (CEST) From: Folke Gleumes <f.gleumes@proxmox.com> To: pve-devel@lists.proxmox.com Date: Tue, 18 Jun 2024 16:15:27 +0200 Message-Id: <20240618141527.1465807-1-f.gleumes@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.016 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [acme.sh] Subject: [pve-devel] [PATCH docs v2] acme: add note about validation delay X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> The effect and unit of the validation delay was unclear from our documentation, and the link to the acme.sh documentation didn't explain it either Signed-off-by: Folke Gleumes <f.gleumes@proxmox.com> --- since v1: * slight rewording suggested by Alex certificate-management.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/certificate-management.adoc b/certificate-management.adoc index 639c15a..fb22398 100644 --- a/certificate-management.adoc +++ b/certificate-management.adoc @@ -177,7 +177,9 @@ interface (`Datacenter -> ACME`). [thumbnail="screenshot/gui-datacenter-acme-add-dns-plugin.png"] Choose `DNS` as challenge type. Then you can select your API provider, enter -the credential data to access your account over their API. +the credential data to access your account over their API. The validation delay determines the +time in seconds between setting the DNS record and prompting the ACME provider to validate it, +as providers often need some time to propagate the record in their infrastructure. TIP: See the acme.sh https://github.com/acmesh-official/acme.sh/wiki/dnsapi#how-to-use-dns-api[How to use DNS API] -- 2.39.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel