On Fri, Nov 21, 2025 at 10:45:21AM +0100, Aleksandar Lazic wrote:
> > > acme: none.at.pem: Starting update of the certificate.
> > [...]
> > > acme: none.at.pem: dns-01 requires to set the "_acme-challenge.none.at"
> > > TXT
> > > record to "9MMRzvJDo0zBFT72sBY0R_qprSj2DDpgGp_BtU8IqfY" and use the "acme
> > [...]
> >
> > > acme: none.at.pem: dns-01 requires to set the "_acme-challenge.none.at"
> > > TXT
> > > record to "jr7eGbpPeNcVHlbpwRM0MeqNZvXYhH351mrUw1EMCuk" and use the "acme
> > > challenge_ready none.at.pem domain none.at" command over the CLI
> > [...]
> > > -:- [21/Nov/2025:04:31:12.901] <ACME> -/- 5/0/0/485/488 200 1010 - - ----
> > > 0/0/0/0/0 0/0 {2606:4700:60:0:f41b:d4fe:4325:6026} "POST
> > > https://acme-staging-v02.api.letsencrypt.org/acme/chall/244744183/20346316043/1_f3SQ
> >
> > Seems like a bug to me, since there are 2 domains it generated 2 challenges
> > to
> > set but your wildcard has the same base as the 2nd domain so there's a
> > problem. I'll take a look.
> >
> > The task seems stuck waiting for every challenge_ready. I think I'll add
> > more
> > states in the `acme status` command so we can debug this more easily.
>
> Thank you.
> Maybe some `trace acme ...???` can help here?
That won't help because it's not the traffic, it's just waiting for all
challenge_ready commands.
But traces are already available with -dt acme:developer:complete if you need
them.
> I will wait for your patches to test the ACME DNS setup to make it
> production reday :-)
>
> Should I create an Issue for that or do you want to keept the work on the ML?
I don't think a ticket is needed, unless you really want one. I'm already
working on it.
--
William Lallemand
