From c9c430b8875a6a8dd316c2f3f347bccffccdbf58 Mon Sep 17 00:00:00 2001 From: Guillaume Boudrias Date: Tue, 26 Apr 2016 15:18:45 -0400 Subject: [PATCH] Update wellknown.md --- docs/wellknown.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/wellknown.md b/docs/wellknown.md index f5444f3..9d6cfde 100644 --- a/docs/wellknown.md +++ b/docs/wellknown.md @@ -4,7 +4,7 @@ Let's Encrypt (or the ACME-protocol in general) is checking if you are in contro `http-01`-type verification (default in this script, there is also support for [dns based verification](dns-verification.md)) so you need to have that directory available over normal http (redirect to https will be acceptable, but you definitively have to be able to access the http url!). -letsencrypt.sh has a config variable called `WELLKNOWN`, which corresponds to the directory which should be served under `/.well-known/acme-challenge` on your domain. To be clear, your `WELLKNOWN` variable **must** include the "acme-challenge" subdirectory, and must not have a trailing slash (eg, `WELLKNOWN="/etc/wellknown/acme-challenge`, **not** `WELLKNOWN="/etc/wellknown`). +letsencrypt.sh has a config variable called `WELLKNOWN`, which corresponds to the directory which should be served under `/.well-known/acme-challenge` on your domain. To be clear, your `WELLKNOWN` variable **must** include the "acme-challenge" subdirectory, and should not have a trailing slash (eg, `WELLKNOWN="/etc/wellknown/acme-challenge"`, **not** `WELLKNOWN="/etc/wellknown"`). An example config would be to create a directory `/var/www/letsencrypt`, set `WELLKNOWN=/var/www/letsencrypt`. -- 2.39.5