From: Martin Dziobek <dziobek@hlrs.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 - FIXED
Date: Tue, 3 Jan 2023 15:03:21 +0100 [thread overview]
Message-ID: <20230103150321.005ab826@schleppmd.hlrs.de> (raw)
In-Reply-To: <20230103144308.491d9e63@schleppmd.hlrs.de>
Ok - here is the fix:
in /usr/share/proxmox-acme/dns-challenge-schema.json:
diff dns-challenge-schema.json dns-challenge-schema.json_save:
13,14c13,14
< "ACMEDNS_BASE_URL" : {
< "description" : "The API base url",
---
> "ACMEDNS_UPDATE_URL" : {
> "description" : "The API update endpoint",
Then restart pveproxy.
Works.
Best regards,
Martin
On Tue, 3 Jan 2023 14:43:08 +0100
Martin Dziobek <dziobek@hlrs.de> wrote:
> Update:
>
> I've been able to get those certificates on pprod by hard-coding
> the ACMEDNS_BASE_URL of our internal acme-dns-Server into
> /usr/share/proxmox-acme/dnsapi/dns_acmedns.sh
>
> but needless to say that is only a POC, not a fix.
>
> Best regards,
> Martin
>
>
> On Tue, 3 Jan 2023 13:34:58 +0100
> Martin Dziobek <dziobek@hlrs.de> wrote:
>
> > 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
> >
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2023-01-03 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:34 [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 Martin Dziobek
2023-01-03 13:43 ` Martin Dziobek
2023-01-03 14:03 ` Martin Dziobek [this message]
2023-01-06 10:15 ` [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 - FIXED 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=20230103150321.005ab826@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.