From d63eca76bc5f72d9f74e7670d4178e0707039a40 Mon Sep 17 00:00:00 2001 From: Fernando Miguel Date: Sun, 24 Sep 2017 12:49:00 +0100 Subject: [PATCH] Updated Simple guide to add TLS cert to cpanel (markdown) --- Simple-guide-to-add-TLS-cert-to-cpanel.md | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/Simple-guide-to-add-TLS-cert-to-cpanel.md b/Simple-guide-to-add-TLS-cert-to-cpanel.md index a9dfd29..85ce6d3 100644 --- a/Simple-guide-to-add-TLS-cert-to-cpanel.md +++ b/Simple-guide-to-add-TLS-cert-to-cpanel.md @@ -25,13 +25,32 @@ The default one is ~/public_html , but if you are using an addon domain, it will `$ acme.sh --issue --webroot ~/public_html/ -d `_EXAMPLE.COM_ **--staging** -## If successful, then we issue the real cert: + +### Be sure that the cert was issued without errors before proceeding. + +Keep in mind Let's Encrypt API limits https://letsencrypt.org/docs/rate-limits/ + +If errors happen, rerun the command with --debug 2 and see if you detect the problem. + + +## Once successful issue the real cert: + `$ acme.sh --issue --webroot ~/public_html/ -d `_EXAMPLE.COM_ **--force** +We use --force to replace the initially issued staging cert + +https://letsencrypt.org/docs/staging-environment/ + + +*** + + ## Next we enter the cPanel username (replace with your account name): -`$ export DEPLOY_cPanel_USER=_username_` + +`$ export DEPLOY_cPanel_USER=`_username_ ## Next we add the cert to the cPanel database: + `$ acme.sh --deploy --deploy-hook cpanel_uapi --domain `_EXAMPLE.COM_ `[Sat Sep 23 06:53:08 EDT 2017] Certificate successfully deployed`