From: Manuel Federanko <m.federanko@proxmox.com>
To: Shan Shaji <s.shaji@proxmox.com>,
pbs-devel@lists.proxmox.com, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox{,-backup,-datacenter-manager} 0/7] acme: fix #6372 implement basic ARI support
Date: Wed, 29 Jul 2026 11:01:43 +0200 [thread overview]
Message-ID: <f206ec4f-f443-4196-857b-3fff184d0212@proxmox.com> (raw)
In-Reply-To: <DK9HKVEGQHGE.3O639U96ED8EO@proxmox.com>
Thanks for testing.
On 2026-07-27 6:15 PM, Shan Shaji wrote:
> Hi,
>
> I applied the patches and performed some testing with Proxmox Backup Server.
>
> * In the UI, the force option is always set to true, so the lead-time check is
> skipped and a new certificate is ordered every time.
> * I ordered a certificate through the UI, which generated a certificate valid from:
>
> 2026-07-27 16:40:42 to 2026-10-25 15:40:41
>
> * Then, tried to order the certificate using proxmox-backup-manager with
> the --force option set to false. The certificate was not renewed, and
> the renewal time from the suggested window was shown in the task log.
> However, it was not displayed in the console, as I mentioned in an
> earlier reply.
>
Since the ARI workflow is a bit more involved I moved these checks into
the worker process. I'm not sure how best to go about passing messages back
at the CLI, but would also prefer this. Suggestions are welcome :)
> Certificate is scheduled for renewal in 1M 4w 2d 8h 33m 13s by ARI
>
> * Now deleted the custom certificate. Since PBS was now using the self-signed
> certificate, the initial ordering request failed because it included a
> certificate ID that the server could not parse. It then retried without the
> ARI certificate ID, and the request succeeded. Observed the same behavior
> when ordering through the CLI using proxmox-backup-manager, as long as
> the --force option was set to true.
>
> However, when --force is set to false, parsing the ARI certificate ID fails
> and the certificate is not created.
>
> TASK ERROR: urn:ietf:params:acme:error:malformed: Parsing ARI CertID failed: urn:ietf:params:acme:error:malformed :: Invalid path
>
> Shouldn't we also need to retry without the certificate ID in this case?
> I may have missed something, so please correct me if I am wrong.
IMO we could either improve the error here or retry when ari parsing fails, I'll
look into it.
> Will do further testing tomorrow.
>
> On Thu Jun 25, 2026 at 4:13 PM CEST, Manuel Federanko wrote:
>>
>> This series implements basic ACME ARI [0] support for Proxmox Backup
>> Server and Proxmox Datacenter Manager. Currently both projects renew
>> once a fixed time has passed:
>>
> [snip]
prev parent reply other threads:[~2026-07-29 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 14:13 [PATCH proxmox{,-backup,-datacenter-manager} 0/7] acme: fix #6372 implement basic ARI support Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 1/7] acme: client: add methods to fetch renewal information Manuel Federanko
2026-07-24 11:16 ` Shan Shaji
2026-07-29 9:04 ` Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 2/7] acme: add retry-after header to " Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 3/7] acme: allow specifying the certificate that is replaced by an order Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox 4/7] acme: cert: add dedicated ari_id field to the certificate info Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox-backup 5/7] acme: add ari_id to cert info Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox-backup 6/7] acme: fix #6372 implement ARI renewal information fetching Manuel Federanko
2026-07-27 13:31 ` Shan Shaji
2026-07-29 9:07 ` Manuel Federanko
2026-07-30 15:09 ` Shan Shaji
2026-07-28 13:32 ` Shan Shaji
2026-07-29 9:08 ` Manuel Federanko
2026-06-25 14:13 ` [PATCH proxmox-datacenter-manager 7/7] acme: fix #6372 use ARI for renewal if available Manuel Federanko
2026-07-27 16:15 ` [PATCH proxmox{,-backup,-datacenter-manager} 0/7] acme: fix #6372 implement basic ARI support Shan Shaji
2026-07-29 9:01 ` Manuel Federanko [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=f206ec4f-f443-4196-857b-3fff184d0212@proxmox.com \
--to=m.federanko@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.shaji@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.