public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2] config: check if acme domain with wildcard uses dns challenge
Date: Thu, 19 Sep 2024 15:29:33 +0200	[thread overview]
Message-ID: <f6cf436a-0a9d-41a5-8de0-a19adae9bdea@proxmox.com> (raw)
In-Reply-To: <f82bd095-6d74-4798-a080-c8c5e7178c62@proxmox.com>

On 9/19/24 15:07, Christian Ebner wrote:
> Just tested again, with an DNS api token which has full zone access, but 
> still get a `failed - status: Invalid` so something might still not be 
> right here. The TXT record is published with name 
> `_acme-challenge.*.domain.tld` when trying for `*.domain.tld` so that 
> should be fine?

No, it should be named `_acme-challenge.domain.tld` according to the 
article [0] linked to by [1] so that is why it does not get validated.

[0] 
https://www.eff.org/deeplinks/2018/02/technical-deep-dive-securing-automation-acme-dns-challenge-validation
[1] https://letsencrypt.org/docs/challenge-types/#dns-01-challenge


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


      reply	other threads:[~2024-09-19 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 12:06 Gabriel Goller
2024-09-18 12:06 ` [pbs-devel] [PATCH v2] schema: add regex for dns domains with wildcard Gabriel Goller
2024-09-19 10:52 ` [pbs-devel] [PATCH proxmox-backup v2] config: check if acme domain with wildcard uses dns challenge Christian Ebner
2024-09-19 13:07   ` Christian Ebner
2024-09-19 13:29     ` Christian Ebner [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=f6cf436a-0a9d-41a5-8de0-a19adae9bdea@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=g.goller@proxmox.com \
    --cc=pbs-devel@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal