We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Let's Encrypt recently switched their default to ECDSA instead of RSA; Synology only accepts RSA, so adding --keylength 2048 to obtain RCA certificate
Task Scheduler has to be told where the acme.sh file and path are.
correct $./acme.sh to ./acme.sh in copy command section
Updated Synology NAS Guide (markdown)
pre-modify
Fix Typo
link to the DNS API wiki for a little added convenience
Acme.sh is updating their defaults to use zerossl instead of letsencrypt [0]. This has resulted in errors like: Can not resolve _eab_id When our runs of acme.sh attempt to communicate with zerossl. While the default change isn't supposed to happen until August 1 we hit it early because we consume the dev branch of acme.sh. We avoid this entirely by being explicit about the server to communicate to in our acme.sh driver script. We explicitly set --server to letsencrypt. https://opendev.org/opendev/system-config/commit/3d5d2779d284af52c23af69ae4fc1a99e7ecdcbc?style=unified&whitespace=
Fixed example using `--insecure`
Add additional details per @dibas in #2727
mention missing curl http2 dependencies
mention --insecure in combination with "localhost" only
mention --insecure option in command to prevent curl error on https deployment
Specify `--home` for issue and deploy steps in order to prevent certs being placed in the default `/root/.acme.sh` location (and thus wiped after a DSM update).
Fixed 2FA issue help (logins with 2FA enabled _are_ possible!)