I chanced upon this finding from the list of client options ( https://letsencrypt.org/docs/client-options/)
Announcement blog post ( October 2017 ) : https://letsencrypt.org/2017/10/17/acme-support-in-apache-httpd.html
And here I was running the traditional certbot+apache combination 🤦♂️
I checked my apt-cache for libapache2-mod-md and it was there ( though the description read 'transitional package` ).
No initial run goes smooth. This was no different.
After commenting out well-documented 'Invalid command's, I finally got #apache to start at least, only to get thrown a bunch more errors at me.
In the end, what was it? The module was still stuck with the 'experimental' ACMEv1 client.
I guess I should've backed off when I noticed the 'transitional package' label on the package before even installing it.
I'm cozying back up with good ol' #certbot. I don't it's going anywhere anytime soon.
I hope the latest version will be packaged in at least with #Debian #BullsEye maybe.
I'm guessing #Ubuntu might already have the right packages. At least with an LTS coming right around the corner ( even if #bionic does not have it ).
Until then ( or until I build it from source; and it works ), certbot, we're going to continue our relationship.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!