From 27f646827d2bd6cd5d4bab15183beb49bb11ded5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= Date: Wed, 5 Jun 2024 12:30:19 +0200 Subject: [PATCH] certs: make it more clear where to set `alias` MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit see https://bugzilla.proxmox.com/show_bug.cgi?id=5506 Signed-off-by: Fabian Grünbichler --- certificate-management.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/certificate-management.adoc b/certificate-management.adoc index 8d3b855..639c15a 100644 --- a/certificate-management.adoc +++ b/certificate-management.adoc @@ -195,9 +195,9 @@ A special `alias` mode can be used to handle the validation on a different domain/DNS server, in case your primary/real DNS does not support provisioning via an API. Manually set up a permanent `CNAME` record for `_acme-challenge.domain1.example` pointing to `_acme-challenge.domain2.example` -and set the `alias` property in the {PVE} node configuration file to -`domain2.example` to allow the DNS server of `domain2.example` to validate all -challenges for `domain1.example`. +and set the `alias` property on the corresponding `acmedomainX` key in the +{PVE} node configuration file to `domain2.example` to allow the DNS server of +`domain2.example` to validate all challenges for `domain1.example`. Combination of Plugins