It seems that the Debian packager chose to only include
certbot.1
in the deb:
debian/certbot.manpages · master · Debian Lets Encrypt Team / certbot / certbot · GitLab.
Bug report filed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028535
[quote="kop, post:1, topic:191024"]
But in order to do http validation the .well-known path must not be
redirected. [/quote]Let's Encrypt will happily follow redirects for HTTP validation FWIW.
Whatever did not work for you, was probably some other factor.
By redirect, I meant redirected to a HTTPS URL. As one
would typically do after enabling TLS communication.
Sorry if that wasn't clear.
Without real awareness of the protocol it's an easy
mistake.
Yeah, on second thought the descriptions are not very helpful. I've
made this basic change at:
docs: give webroot and standalone better descriptions by alexzorin · Pull Request #9536 · certbot/certbot · GitHub.
That looks good to me. Thanks.
To my mind you could remove the word "separate"
from the line 61 sentence: "A seperate HTTP server ...".
It's a bit of a distraction and seems unnecessary,
at least to me.
I like the "nominated webroot path" phrase.
While you're at it. I don't find the beginning sentence
of the --webroot-path description, "public_html / webroot path."
to be helpful. Much more clear would be something like:
"Path in the file system from the HTTP server obtains
web content."
And, so long as I'm reviewing the whole man page,
the first occurrence of the term "webroot" uses
the word "folder". Elsewhere "directory" is used.
I don't know if this is an issue but if the man
page is focused on a Un*x audience then "directory"
might be better than "folder".
While I've got your attention it's not clear to me
how to discover the github pages from the letsencrypt.org
website. (I'd have found it easier to open an issue there.)
No need to reply to this unless you'd care to.
Thanks for the help.
Regards,
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein