public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Folke Gleumes <f.gleumes@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2] acme: add note about validation delay
Date: Tue, 18 Jun 2024 16:15:27 +0200	[thread overview]
Message-ID: <20240618141527.1465807-1-f.gleumes@proxmox.com> (raw)

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


             reply	other threads:[~2024-06-18 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 14:15 Folke Gleumes [this message]
2024-06-18 14:37 ` [pve-devel] applied: " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240618141527.1465807-1-f.gleumes@proxmox.com \
    --to=f.gleumes@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal