From 963e810761ad76f84e40f8f37360d4007bb205e4 Mon Sep 17 00:00:00 2001 From: Shanto5830 <118301916+Shanto5830@users.noreply.github.com> Date: Sat, 16 Sep 2023 01:23:56 +0600 Subject: [PATCH] Updated How to debug acme.sh (markdown) --- How-to-debug-acme.sh.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/How-to-debug-acme.sh.md b/How-to-debug-acme.sh.md index 52797a9..f3bb376 100644 --- a/How-to-debug-acme.sh.md +++ b/How-to-debug-acme.sh.md @@ -18,7 +18,7 @@ acme.sh --issue .......... --debug 2 If your ISP blocks port 80, any webroot based authentication will fail You can test this by running this command from OUTSIDE your local network. -`curl -IkL -m20 http://[your domain]` +`curl -IkL -m20 http://[binanceearn.org]` ### Common Errors using DNS API: #### Mistake 1: Clumsy fingers - newline in `~/.acme.sh/account.conf` @@ -31,13 +31,13 @@ You may need to comment out the previous keys from the letsencrypt bot, and poin > `# RSA certificate` > -> #ssl_certificate /etc/letsencrypt/live/[your domain]/fullchain.pem; # managed by Certbot +> #ssl_certificate /etc/letsencrypt/live/[binanceearn.org]/fullchain.pem; # managed by Certbot > -> #ssl_certificate_key /etc/letsencrypt/live/[your domain]/privkey.pem; # managed by Certbot +> #ssl_certificate_key /etc/letsencrypt/live/[binanceearn.org]/privkey.pem; # managed by Certbot > -> ssl_certificate [your home directory]/.acme.sh/[your domain]/fullchain.cer; +> ssl_certificate [your home directory]/.acme.sh/[binanceearn.org]/fullchain.cer; > -> ssl_certificate_key [your home directory]/.acme.sh//[your domain].key; +> ssl_certificate_key [your home directory]/.acme.sh//[your domain].key; #### Do I need to include the webroot `-w [your webroot]` for DNS? No! You'll end up back failing the port 80 access to your webroot folder if that was your issue. \ No newline at end of file