github
/
acme.sh
mirror of https://github.com/acmesh-official/acme.sh
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated How to debug acme.sh (markdown)

master
Shanto5830 2023-09-16 01:23:56 +06:00
parent 264e54e72f
commit 963e810761
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
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 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. 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: ### Common Errors using DNS API:
#### Mistake 1: Clumsy fingers - newline in `~/.acme.sh/account.conf` #### 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` > `# 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>/[your domain].key; > ssl_certificate_key [your home directory]/.acme.sh/<binanceearn.org>/[your domain].key;
#### Do I need to include the webroot `-w [your webroot]` for DNS? #### 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! You'll end up back failing the port 80 access to your webroot folder if that was your issue.