starred/certbot-certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-08-01 02:44:21 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix example links (#4678)

Browse Source 
* fix example links

* use single backticks not double
This commit is contained in:
Brad Warren
2017-05-18 08:15:00 -07:00
committed by GitHub
parent 462c0aba62
commit 04759095c2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/challenges.rst
+2 -2
View File
@@ -58,7 +58,7 @@ HTTP-01 challenge:
files in order to have them served by your existing web server.
If you said your webroot for example.com was /var/www/example.com,
then a file placed in /var/www/example.com/.well-known/acme-challenge/testfile should appear on
your web site at http://example.com/.well-known/acme-challenge/testfile (which you can test using a web browser). (A redirection to HTTPS
your web site at `http://example.com/.well-known/acme-challenge/testfile` (which you can test using a web browser). (A redirection to HTTPS
is OK here and should not stop the challenge from working.)
Note that you should *not* specify the .well-known/acme-challenge directory itself. Instead, you should specify the top level directory that web content is served from.
@@ -70,7 +70,7 @@ HTTP-01 challenge:
* (With manual plugin) You updated the webroot directory incorrectly
If you used `--manual`, you need to know where you can put files in order to have them served by your existing web server. If you think your webroot for example.com is /var/www/example.com, then a file placed in /var/www/example.com/.well-known/acme-challenge/testfile should appear on
your web site at http://example.com/.well-known/acme-challenge/testfile. (A redirection to HTTPS
your web site at `http://example.com/.well-known/acme-challenge/testfile`. (A redirection to HTTPS
is OK here and should not stop the challenge from working.) You should also make sure that you don't make a typo in the name of the file when creating it.
* Your existing web server's configuration refuses to serve files