From ad0592fd9ba8f39edcc8863bb9f84255f40bd28c Mon Sep 17 00:00:00 2001 From: Luc Gommans Date: Fri, 9 Sep 2016 13:18:43 +0300 Subject: [PATCH] Emphasized "will use untrusted by default" It's entirely my fault for killing a production site for 10 minutes while I figured this out, and for not making a backup of the working private key and certificate, but I think it would help people to emphasize that it uses the staging server by default. (Other than that, 10/10! So much simpler and better than the default letsencrypt client, loved it.) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 549eaf9..fc74fdd 100644 --- a/README.md +++ b/README.md @@ -86,7 +86,7 @@ copying private key to ssh:server5:/home/yourdomain/ssl/domain.key copying CA certificate to ssh:server5:/home/yourdomain/ssl/chain.crt reloading SSL services ``` -This will (by default) use the staging server, so should give you a certificate that isn't trusted ( Fake Let's Encrypt). +**This will (by default) use the staging server, so should give you a certificate that isn't trusted ( Fake Let's Encrypt).** Change the server in your config file to get a fully valid certificate. **Note:** Verification is done via port 80(http), port 443(https) or dns. The certificate can be used ( and checked with getssl) on alternate ports.