public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Cc: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [RFC backup 00/23] Implements ACME suport for PBS
Date: Wed, 21 Apr 2021 13:56:18 +0200	[thread overview]
Message-ID: <20210421115618.GA87005@mala> (raw)
In-Reply-To: <137355824.4295.1618915991154@webmail.proxmox.com>

I am not sure how much of what I noticed today is for this series or general

On Tue, Apr 20, 2021 at 12:53:11PM +0200, Wolfgang Bumiller wrote:
> > In the window "Register Account" the textfield "Account Name" has the empty
> > text "default".  As far as I know, we use empty texts for real default values.
> > So this should be removed and get a validator (already in the GUI) instead.
> 
> GUI specifics aren't really in scope of this series as this just reuses the existing components.
> So this should be handled separately.

or would be magically solved by the packaging changes
> 
> Yeah we should turn the proxmox-acme repo into a split package and have the acme.sh
> wrapper separate so we can depend/suggest that without pulling in the perl code.

but a few things looked working to me in PVE but not PBS:

1. In the "Create: Domain" window, when attempting to create a duplicate entry:
PVE shows an error "duplicate domain" while PBS silently replaces the previous
entry

2. I installed libproxmox-acme-perl as disucssed. The dropdown list for DNS API
then did appear.  However, I haven't found a dropdown entry yet that made the
general API Data field change to the API specific fields. This includes APIs
like kappernet for which this certainly works in PVE.

3. When trying around I got some error like
> TASK ERROR: validating challenge 'https://acme-staging-v02.api.letsencrypt.org/acme/...' failed - status: Invalid
and after editing (=removing a line) the contents of the API Data field the
error message became less useful
>Placing ACME order
>Order URL: https://acme-staging-v02.api.letsencrypt.org/acme/order/....
>Getting authorization details from 'https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/...'
>The validation for dominicjaeger.com is pending
>Setting up validation plugin
>TASK ERROR: '/usr/share/proxmox-acme/proxmox-acme setup' exited with error (1)

Would it be possible to show more reasons for the error here?

4. The dropdown list is different for PBS and PVE. For example, PVE contains
"Cloudflare Managed DNS" while PBS contains just "cf"




  reply	other threads:[~2021-04-21 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 10:53 Wolfgang Bumiller
2021-04-21 11:56 ` Dominic Jäger [this message]
2021-04-21 12:19   ` Wolfgang Bumiller
  -- strict thread matches above, loose matches on Subject: below --
2021-04-16 13:34 Wolfgang Bumiller
2021-04-20 10:27 ` Dominic Jäger

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=20210421115618.GA87005@mala \
    --to=d.jaeger@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=w.bumiller@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal