From: Martin Dziobek <dziobek@hlrs.de>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4
Date: Tue, 3 Jan 2023 13:34:58 +0100 [thread overview]
Message-ID: <20230103133458.378a56b3@schleppmd.hlrs.de> (raw)
Howdy, list members !
The situation:
I have a proxmox host (say ptest) running pve 7.3-3,
and one (say pprod) running 7.3-4
On ptest, getting Letsencrypt certificates with the acme-dns plugin
and our internal acme-dns server works fine.
Trying the same config on pprod (for the first time with LE) fails with
"invalid response of acme-dns"
Investigation:
/etc/pve/.version:
ptest shows "priv/acme/plugins.cfg": 2,
pprod shows "priv/acme/plugins.cfg": 3,
The handler scripts in
/usr/share/proxmox-acme/dnsapi/dns_acmedns.sh
have lots of differences for that reason.
The GUI dialog at Datacenter->ACME for configuring
Challenge plugins (type acme-dns), however, do show
*exactly the same predefined fields* on pprod and ptest,
namely "ACMEDNS_UPDATE_URL".
Unfortunately, "ACMEDNS_UPDATE_URL" has been
dropped in the latest versions of acme.sh
(and in the handler scripts v.3)
In v.3 , this is now all based on ACMEDNS_BASE_URL,
but the change has obviously not been reflected to
the GUI dialog.
Would you proxmox guys kindly mind to fix this ?
Best regards,
Martin
next reply other threads:[~2023-01-03 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:34 Martin Dziobek [this message]
2023-01-03 13:43 ` Martin Dziobek
2023-01-03 14:03 ` [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 - FIXED Martin Dziobek
2023-01-06 10:15 ` 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=20230103133458.378a56b3@schleppmd.hlrs.de \
--to=dziobek@hlrs.de \
--cc=pve-user@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