go/lego
go/lego
1
0
Fork 0
mirror of https://github.com/go-acme/lego.git synced 2024-12-26 11:18:00 +02:00
Code Issues Releases Activity

Merge pull request #58 from flibustenet/patch-1

Browse Source 
Update README.md
This commit is contained in:
Matt Holt 2015-12-20 09:32:45 -07:00
commit cb9a6e8207
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -52,7 +52,7 @@ If this is not possible in your environment, you can use the `--port` option to
lego to listen on that port for any incoming challenges.
If you are using this option, make sure you proxy all of the following traffic to that port:
- All plaintext HTTP requests to port 80 which begin with a request path of `/.well-known/acme/` for the HTTP-01 challenge.
- All plaintext HTTP requests to port 80 which begin with a request path of `/.well-known/acme-challenge/` for the HTTP-01 challenge.
- All TLS handshakes on port 443 for TLS-SNI-01.
This traffic redirection is only needed as long as lego solves challenges. As soon as you have received your certificates you can deactivate the forwarding.