Something has gone wrong with the Certbot instruction generator. There was a content migration to a new website system recently and it might be related to that.
Hi @codesalatdev and welcome to the LE community forum
Even if "latest certbot snap release now doesn't include an --apache plugin" is true (haven't checked; don't rely on Apache much), one can always use certbot with --webroot [with any web service].
So, I don't see how that nukes anybody to anywhere.
Unless... you are implying that Apache users aren't capable of handling the issued certificate by hand?
If users go to your install how-to page, select both OS and Webserver and the instructions just don't work because there is no installation candidate, I would call that issue pretty substantial. So while "nuking" was merely a joke (taken a little bit too seriously), relying on users to find an alternative way to install certbot despite the official docs saying otherwise is IMHO a pretty low standard to go by in the first place.
This has nothing to do with Apache users, since installing certbot is the issue, not handling it as you imply.
Thank you. I read that. I wrote my comment to add the information that certbot-apache was also missing. I didn't intent to start a convo about handling certificates by hand.
The Certbot snap comes with both the Apache and nginx plugins built-in.
If you don't see the Apache plugin after installing the Certbot snap, it most likely means that you have a second copy of Certbot installed and it is taking priority in your PATH.
