On Sun, 2023-04-23 at 15:21 +0200, Markus Schönhaber wrote:
22.04.23, 23:40 +0200, Patrick O'Callaghan:
> On Sat, 2023-04-22 at 23:31 +0200, Markus Schönhaber wrote:
> > 22.04.23, 19:42 +0200, Patrick O'Callaghan:
> >
> > > On Sat, 2023-04-22 at 15:30 +0200, Markus Schönhaber wrote:
> >
> > > > If certbot --apache doesn't work, you could try to only fetch
> > > > the
> > > > certificates and manually configure httpd to actually use
> > > > them
> > > > afterwards. I. e. do something like
> > > >
> > > > # certbot certonly --webroot -w /path/to/webroot -d $DOMAIN
> > > > ...
> > >
> > > I've considered that (there are several other ACME clients on
> > > Fedora)
> > > but Certbot is the recommended one so I'm sticking with it for
> > > now.
> >
> > What are you talking about?
> > The command I showed you above *is* a certbot invocation.
>
> I know it's a Certbot invocation. I'm merely saying that Certbot is
> not
> the only way to obtain certificates using the ACME protocol.
Yes, and you're also saying that you don't want to use those other
ACME
clients but rather stick to certbot. So you dismiss my proposed way
to
use certbot because there are other ACME clients but you'd rather use
certbot. Now, that makes sense.
You're parsing too strictly. I'm saying I would prefer to use Certbot
(as it seems to be the solution recommended by LetsEncrypt) but I'm
aware of other ACME clients.
In fact I'm also looking at Apache's mod_md as an alternative.
Currently, the most likely source of the problem I'm having is not
Certbot as such but something in my Apache configuration. I'm going
over it again to check everything.
poc