From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Martin Dziobek <dziobek@hlrs.de>
Subject: Re: [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 - FIXED
Date: Fri, 6 Jan 2023 11:15:02 +0100 [thread overview]
Message-ID: <7dc750d1-2bc3-be76-ab88-0838cb921b62@proxmox.com> (raw)
In-Reply-To: <20230103150321.005ab826@schleppmd.hlrs.de>
Hi!
Am 03/01/2023 um 15:03 schrieb Martin Dziobek:
> Ok - here is the fix:
much thanks for your report and even proposing a fix, appreciated!
>
> in /usr/share/proxmox-acme/dns-challenge-schema.json:
>
> diff dns-challenge-schema.json dns-challenge-schema.json_save:
fyi, using the -u and -p param (can be combined as -up) makes the diff output more
like the git default, also putting original file first and the modified second is
more common and thus a bit easier to understand.
> 13,14c13,14
> < "ACMEDNS_BASE_URL" : {
> < "description" : "The API base url",
> ---
>> "ACMEDNS_UPDATE_URL" : {
>> "description" : "The API update endpoint",
>
> Then restart pveproxy.
> Works.
Applied the change to git so that its fixed again with the next proxmox-acme package
version bump:
https://git.proxmox.com/?p=proxmox-acme.git;a=commitdiff;h=963319d031d43bbdc5dd78414852989eb9e9e40f
- Thomas
prev parent reply other threads:[~2023-01-06 10:15 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 ` [PVE-User] Trouble with LetsEncrypt/acme-dns in pve 7.3-4 - FIXED Martin Dziobek
2023-01-06 10:15 ` Thomas Lamprecht [this message]
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=7dc750d1-2bc3-be76-ab88-0838cb921b62@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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